Sensor fusion for electromagnetic tracking.
By integrating EM tracking with IMUs and data fusion, the system addresses inaccuracies and latency in AR/VR systems, achieving precise and efficient object tracking within a global reference frame for enhanced user experiences.
Patent Information
- Application Number
- JP2021560020
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-04-15
- Filing Date
- 2020-03-06
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2040-03-06
AI Technical Summary
Current systems for determining the position and orientation of objects in augmented reality (AR) and virtual reality (VR) environments suffer from inaccuracies and high latency, particularly when using sensors like accelerometers and gyroscopes, which can lead to position drift and require conversion to a global reference frame, and optical tracking methods face challenges with occlusion and computational complexity.
The integration of electromagnetic (EM) tracking systems with inertial measurement units (IMUs) and data fusion techniques, such as Kalman filters, to accurately determine the pose of objects within a global reference frame, reducing errors and latency by combining EM field sensing with IMU data.
This approach provides high-accuracy, low-latency tracking of objects, enabling more stable and immersive AR and VR experiences by accurately correlating the position and orientation of real and virtual objects, even in occluded conditions, and reducing computational burden on processors.
Smart Images

Figure 0007592024000007 
Figure 0007592024000008 
Figure 0007592024000009
Abstract
Description
[Technical field]
[0001] (Priority Claim) This application claims the benefit of priority to U.S. Provisional Application No. 62 / 834,081, filed April 15, 2019, which is incorporated herein by reference.
[0002] The present disclosure relates generally to systems and methods for determining the position or orientation of an object, and more specifically, to fusing electromagnetic tracking techniques with other sensor inputs. [Background technology]
[0003] Modern computing and display technologies have facilitated the development of systems for so-called "virtual reality" or "augmented reality" experiences, in which digitally reproduced images or portions thereof are presented to a user in a manner that appears or may be perceived as real. Virtual reality, or "VR", scenarios typically involve the presentation of digital or virtual image information without transparency to other actual real-world visual inputs. Augmented reality, or "AR", scenarios typically involve the presentation of digital or virtual image information as an extension to the visualization of the real world around the user. Summary of the Invention [Means for solving the problem]
[0004] A head-mounted augmented reality (AR) device can track the pose of the wearer's head (or other body parts) so as to be able to provide a three-dimensional virtual representation of objects in the wearer's environment. An embodiment of an electromagnetic (EM) tracking system can be used to track head pose or body gestures. For example, a handheld user input device can include an EM emitter and a head-mounted AR device can include an EM sensor. In some implementations, the EM emitter generates an EM field that can be sensed by the EM sensor. The EM information from the sensor can be analyzed to determine the location and / or orientation of the sensor and thereby the wearer's head pose within the reference frame of the AR device. The pose can be a six-degree-of-freedom (6DOF) pose, including three spatial coordinates and three angular coordinates within the reference frame of the AR device. The reference frame of the AR device can be a global (or world) coordinate system that represents fixed objects in the wearer's real-world environment.
[0005] The AR device may include other sensors that provide orientation information, such as, for example, an accelerometer, a gyroscope, a magnetometer, an optical sensor, or a camera. As an example, the accelerometer data may be integrated twice to provide an estimated position. However, errors in the sensor signal may cause the estimated position to drift relative to the actual position. Also, the position or orientation inferred from the sensor may be in a reference frame associated with the sensor, rather than the reference frame of the AR device (e.g., a world coordinate system).
[0006] Examples of techniques for fusing outputs from an electromagnetic tracking system and another sensor modality (e.g., accelerometer, gyroscope, magnetometer) to reduce attitude error or transform attitude into the reference frame of the AR device are described herein. A Kalman filter or other type of data fusion technique can be used to fuse the outputs.
[0007] Sensor fusion techniques are not limited to AR or VR applications, but can also be applied in other implementations to pose determination of any object where sensors of different modalities (e.g., accelerometers and EM tracking devices) are used. For example, sensor fusion techniques can be applied to track medical devices and instruments in an operating room.
[0008] Details of one or more implementations of the subject matter described herein are set forth in the accompanying drawings and the following description. Other features, aspects, and advantages will become apparent from the description, drawings, and claims. Neither this summary nor the following detailed description purports to define or limit the scope of the inventive subject matter. The present invention provides, for example, the following: (Item 1) A wearable system, comprising: A head-mounted display; a handheld user input device comprising an inertial measurement unit (IMU); 1. An electromagnetic (EM) tracking system, comprising: an EM emitter disposed within or on the handheld user input device, the EM emitter configured to generate an EM field; an EM sensor disposed in or on the head mounted display, the EM sensor configured to sense the EM field; an EM tracking system configured to output an EM field matrix associated with an estimated pose of the EM sensor relative to the EM emitter; A hardware processor, the hardware processor comprising: accessing IMU data from the IMU, the IMU data representing an estimated pose of the handheld user input device within a frame of reference associated with the handheld user input device; accessing the EM field matrix from the EM tracking system; Calculating a predicted EM field matrix representing a predicted pose of the handheld user input device within a world reference frame associated with an environment of the wearable system; generating an error state based at least in part on the EM field matrix and the predicted EM field matrix, the error state representing at least one of a bias or noise in the IMU or an offset between a frame of reference of the handheld user input device and the world frame of reference; applying a Kalman filter to the IMU data based on the error state; and determining a pose of the handheld user input device in the world reference frame using the Kalman filter; a hardware processor programmed to A wearable system comprising: (Item 2) 2. The wearable system of claim 1, wherein the IMU comprises at least one of an accelerometer or a gyroscope. (Item 3) To calculate the predicted EM field matrix, the hardware processor comprises: calculating an estimate for the EM emitter attitude in the world frame of reference; calculating an estimate for the EM sensor pose in the world reference frame; calculating a relative attitude between the EM emitter attitude in the world frame of reference and the EM sensor attitude in the world frame of reference; The wearable system of item 1 or 2, programmed to perform the following: (Item 4) To calculate an estimate for the EM emitter pose in the world reference frame, the hardware processor: accessing a pose of the handheld user input device within the world reference frame; applying an EM transmitter associated property configured to adjust a position of the EM emitter relative to a fiducial position of the handheld user input device; 4. The wearable system of item 3, programmed to: (Item 5) 5. The wearable system of claim 4, wherein the EM transmitter associated property comprises a displacement between a position of the EM emitter and a base position of the handheld user input device. (Item 6) To calculate an estimate for the EM sensor in the world reference frame, the hardware processor: accessing an estimate of a pose relative to the head mounted display; applying an EM receiver associated property configured to adjust the position of the EM sensor relative to a fiducial position of the head mounted display; The wearable system of any one of items 3-5, programmed to perform the following: (Item 7) 7. The wearable system of claim 6, wherein the EM receiver associated property comprises a displacement between the position of the EM sensor and a base position of the head mounted display. (Item 8) The hardware processor further comprises: calculating a predicted pose of the handheld user input device based on the pose determined from the EM tracking system; or Resolving ambiguities in the orientation of the handheld user input device The wearable system of any one of items 1-7, programmed to perform an initialization procedure including one or more of the following: (Item 9) To resolve ambiguity in the orientation of the handheld user input device, the hardware processor executing a first thread with an initial orientation of the handheld user input device located within a first hemisphere, the first thread determining a first estimate of a pose of the handheld user input device within the world reference frame; executing a second thread, the initial orientation of the handheld user input device being located in a second hemisphere opposite the first hemisphere, the second thread determining a second estimate of a pose of the handheld user input device in the world frame of reference; 9. The wearable system of item 8, programmed to: (Item 10) 10. The wearable system of claim 9, wherein the hardware processor is programmed to terminate execution of either the first thread or the second thread when the first estimate or the second estimate, respectively, diverges from a true pose of the handheld user input device. (Item 11) 11. A wearable system according to any one of claims 1-10, wherein the hardware processor is programmed to implement an error detection routine and, in response to determining an error, the system implements corrective action. (Item 12) Item 12. The wearable system of item 11, wherein the error detection routine includes determining that a distance between the EM emitter and the EM sensor exceeds a threshold distance. (Item 13) Item 13. The wearable system of item 11 or item 12, wherein the corrective action includes reinitializing the system. (Item 14) The hardware processor further comprises: presenting virtual content to a user of the wearable system via the head mounted display; or Enabling interaction of the wearable system with an environment based, at least in part, on the movement or rotation of the handheld user input device. 14. The wearable system of any one of items 1-13, programmed to: (Item 15) A wearable system, comprising: A head-mounted display; a handheld user input device comprising an inertial measurement unit (IMU); 1. An electromagnetic (EM) tracking system, comprising: one or more EM emitters configured to generate an EM field; one or more EM sensors configured to sense the EM field; an EM tracking system configured to output an EM field matrix associated with an estimated pose of the one or more EM sensors relative to the one or more EM emitters; An inertial navigation system (INS), accessing IMU data from the IMU; accessing the EM field matrix from the EM tracking system; applying a data fusion algorithm to the IMU data and the EM field matrix to generate a predicted pose of the handheld user input device within a world frame associated with the wearable system; The INS and A wearable system comprising: (Item 16) Item 16. The wearable system of item 15, wherein the one or more EM emitters are disposed within or on the handheld user input device and the one or more EM sensors are disposed within or on the head mounted display. (Item 17) Item 17. The wearable system of item 15 or 16, wherein the one or more EM sensors include a first EM sensor positioned on a left side of the head-mounted display and a second EM sensor positioned on a right side of the head-mounted display. (Item 18) Item 18. The wearable system of item 17, wherein the EM field matrix is determined based on a first weighting associated with the first EM sensor and a second weighting associated with the second EM sensor. (Item 19) 20. The wearable system of claim 18, wherein the weighting is determined based on a respective distance between the sensor and the handheld user input device. (Item 20) Item 17. The wearable system of item 15 or 16, wherein the data fusion algorithm comprises a Kalman filter. (Item 21) 20. The wearable system of any one of items 15-19, wherein the INS is configured to generate an error state based on a comparison of the EM field matrix with a predicted EM field matrix representing a predicted pose of the handheld user input device. (Item 22) 19. The wearable system of any one of claims 15-18, wherein the predicted pose comprises a six degree of freedom pose. (Item 23) 1. A method for calculating a pose of a handheld user input device for a wearable system, the method comprising: Under the control of an inertial navigation system (INS) equipped with computer hardware, accessing posture data from a posture sensor associated with the handheld user input device; accessing electromagnetic (EM) tracking data associated with an EM tracking system associated with the handheld user input device; applying a data fusion technique to combine the pose data and the EM tracking data; determining a pose of the handheld user input device within a reference frame associated with an environment of the wearable system; A method comprising: (Item 24) 24. The method of claim 23, wherein the attitude sensor comprises an inertial measurement unit. (Item 25) 25. The method of claim 23 or 24, wherein the attitude sensor comprises an accelerometer, a gyroscope, a magnetometer, or an optical sensor. (Item 26) 26. The method of any one of claims 23-25, wherein the EM tracking system comprises an EM emitter and an EM sensor. (Item 27) 27. The method of claim 26, wherein the EM emitter is located within or on the user input device. (Item 28) 28. The method of any one of claims 23-27, wherein the data fusion technique comprises a Kalman filter. (Item 29) An INS configured to carry out the method according to any one of items 20-25. (Item 30) A wearable system, comprising: the handheld user input device; the EM tracking system; Item 26. An INS according to item 26; A wearable system comprising: [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 depicts an illustration of an augmented reality scenario involving a virtual reality object and a physical object viewed by a person.
[0010] [Figure 2A] 2A-2D diagrammatically illustrate an embodiment of a wearable system. [Figure 2B] 2A-2D diagrammatically illustrate an embodiment of a wearable system. [Figure 2C] 2A-2D diagrammatically illustrate an embodiment of a wearable system. [Figure 2D] 2A-2D diagrammatically illustrate an embodiment of a wearable system.
[0011] [Diagram 3] FIG. 3 diagrammatically illustrates collaboration between cloud computing assets and local processing assets.
[0012] [Figure 4] FIG. 4 diagrammatically illustrates an example system diagram of an electromagnetic (EM) tracking system.
[0013] [Diagram 5] FIG. 5 is a flow chart illustrating an exemplary function of an embodiment of an EM tracking system.
[0014] [Figure 6] FIG. 6 diagrammatically illustrates an embodiment of an EM tracking system integrated with an AR system.
[0015] [Figure 7] FIG. 7 is a flow chart illustrating the functionality of an embodiment of an EM tracking system in the context of an AR device.
[0016] [Figure 8] FIG. 8 diagrammatically illustrates an example of components of an embodiment of an AR system.
[0017] [Figure 9A] 9A and 9B diagrammatically illustrate an example of an EM sensing coil coupled to a head mounted display. [Figure 9B] 9A and 9B diagrammatically illustrate an example of an EM sensing coil coupled to a head mounted display.
[0018] [Figure 9C] 9C and 9D diagrammatically illustrate an exemplary head-mounted headset with multiple EM sensors. [Figure 9D] 9C and 9D diagrammatically illustrate an exemplary head-mounted headset with multiple EM sensors.
[0019] [Figure 9E] 9E and 9F diagrammatically illustrate an example controller with multiple EM emitters. [Figure 9F] 9E and 9F diagrammatically illustrate an example controller with multiple EM emitters.
[0020] [Figure 10] 10 and 11 are flow charts illustrating an example of pose tracking using an EM tracking system in a head-mounted AR system. [Figure 11] 10 and 11 are flow charts illustrating an example of pose tracking using an EM tracking system in a head-mounted AR system.
[0021] [Figure 12] FIG. 12 is a block diagram that diagrammatically illustrates an example of an inertial navigation system (INS) that can receive input from an IMU on a handheld user input device and provide a pose (e.g., position or orientation) of the device within a world frame associated with the AR system.
[0022] [Figure 13A] 13A-13C are block diagrams that diagrammatically illustrate examples of sensor fusion systems that can be used with an augmented reality display system. [Figure 13B] 13A-13C are block diagrams that diagrammatically illustrate examples of sensor fusion systems that can be used with an augmented reality display system. [Figure 13C] 13A-13C are block diagrams that diagrammatically illustrate examples of sensor fusion systems that can be used with an augmented reality display system.
[0023] [Figure 14] FIG. 14 is a flow chart illustrating an embodiment of a method for calculating a pose of a handheld user input device for a wearable system.
[0024] Throughout the drawings, reference numbers may be reused to indicate correspondence between referenced elements. The drawings are provided to illustrate example embodiments described herein and are not intended to limit the scope of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0025] (Overview of AR, VR, and Location Systems) In Fig. 1, an augmented reality scene (4) is depicted in which a user of the AR technology sees a real-world park-like setting (6) featuring people, trees, buildings in the background, and a concrete platform (1120). In addition to these items, the user of the AR technology also perceives that they "see" a robotic figure (1110) standing on the real-world platform (1120) and a flying cartoon-like avatar character (2) that appears to be an anthropomorphic bumblebee, although these elements (2, 1110) do not exist in the real world. In conclusion, the human visual perception system is highly complex, making it difficult to produce VR or AR technology that facilitates a comfortable, natural-feeling, and rich presentation of virtual image elements among other virtual or real-world image elements.
[0026] For example, a head-mounted AR display (or helmet-mounted display or smart glasses) is typically at least loosely coupled to a user's head and may therefore move as the user's head moves. When movement of the user's head is detected by the display system, the displayed data can be updated to account for the change in head pose.
[0027] As an example, when a user wearing a head mounted display views a virtual representation of a three-dimensional (3D) object on the display and walks around the area in which the 3D object appears, the 3D object can be re-rendered for each viewpoint, giving the user the perception that they are walking around objects that occupy real space. When a head mounted display is used to present multiple objects (e.g., a rich virtual world) in a virtual space, measurements of head pose (e.g., the location and orientation of the user's head) can be used to re-render the scene to match the user's dynamically changing head location and orientation, providing an increased sense of immersion in the virtual space.
[0028] In an AR system, head pose detection or calculation can facilitate the display system rendering virtual objects so that they appear to occupy space in the real world in a manner that makes sense to the user. In addition, detection of the position and / or orientation of a real object, such as a handheld device (which may also be referred to as a "totem"), a tactile device, or other real physical object in conjunction with the user's head or the AR system, can also facilitate the display system presenting display information to the user and allowing the user to effectively interact with certain aspects of the AR system. As the user's head moves around in the real world, virtual objects can be re-rendered as a function of head pose so that the virtual objects appear to remain stable relative to the real world. At least for AR applications, placement of virtual objects in spatial conjunction with physical objects (e.g., presented to appear spatially proximate to the physical objects in two or three dimensions) may not be a trivial issue. For example, head movement can significantly complicate placement of virtual objects in a view of the surrounding environment. This applies whether the view is captured as an image of the surrounding environment and then projected or displayed to the end user, or whether the end user directly perceives the view of the surrounding environment. For example, head movement will likely change the end user's field of view, which will likely require updates to where various virtual objects are displayed in the end user's field of view. In addition, head movements may occur in a wide variety of ranges and speeds. Head movement speed may vary not only between different head movements, but also within or across the range of a single head movement. For example, head movement speed may initially increase (e.g., linearly or non-linearly) from a starting point, decrease as an end point is reached, and achieve a maximum speed at some location between the start and end points of the head movement. High speed head movements may exceed the capabilities of even a particular display or projection technology, rendering an image that appears to the end user as uniform and / or smooth motion.
[0029] Head tracking accuracy and latency (e.g., the time elapsed between the time a user moves their head and the time an image is updated and displayed to the user) are challenges for VR and AR systems. In particular, for display systems that fill a substantial portion of the user's field of view with virtual elements, it is advantageous if the head tracking accuracy is high and the overall system latency from the initial detection of head movement to the update of the light delivered by the display to the user's visual system is very low. If the latency is high, the system may create a user perception scenario that results in a mismatch between the user's vestibular and visual sensory systems, leading to motion sickness or 3D sickness. If the system latency is high, the apparent location of virtual objects may appear unstable during fast head movements.
[0030] In addition to head-mounted display systems, other display systems can also benefit from accurate and low-latency head pose detection. These include head-tracked display systems, where the display is not worn on the user's body, but is mounted, for example, on a wall or other surface. The head-tracked display can act like a window on the scene, and as the user moves his or her head relative to the "window," the scene is re-rendered to match the user's changing viewpoint. Other systems include head-mounted projection systems, where the head-mounted display projects light onto the real world.
[0031] In addition, the AR system may be designed to interact with the user to provide a realistic augmented reality experience. For example, multiple users may play a ball game with a virtual ball and / or other virtual objects. One user may "catch" the virtual ball and throw the ball back to another user. In some embodiments, a first user may be provided with a totem (e.g., an actual bat communicatively coupled to the AR system) to hit the virtual ball. In some embodiments, a virtual user interface may be presented to the AR user to allow the user to select one of many options. The user may use a totem, a tactile device, a wearable component, or simply touch a virtual screen and interact with the system.
[0032] Detecting the pose and orientation of a user's head and the physical location of real objects in space enable AR systems to display virtual content in an effective and enjoyable manner. However, these capabilities, while important for AR systems, are difficult to achieve. In other words, an AR system must recognize the physical location of real objects (e.g., the user's head, a totem, a tactile device, a wearable component, the user's hand, etc.) and correlate the physical coordinates of the real objects to virtual coordinates corresponding to one or more virtual objects being displayed to the user. This generally requires highly accurate sensors and sensor recognition systems that track the position and orientation of one or more objects at a fast rate. Current approaches do not perform localization at a satisfactory speed or accuracy standard.
[0033] Therefore, there is a need for better localization systems in the context of AR and VR devices. Exemplary AR and VR Systems and Components
[0034] 2A-2D, several general component options are illustrated. In the detailed description section that follows the discussion of FIGs. 2A-2D, various systems, subsystems, and components are presented to address the objective of providing a high quality and comfortable perceived display system for human VR and / or AR.
[0035] As shown in Figure 2A, an AR system user (60) is depicted wearing a head-mounted component (58) featuring a frame (64) structure coupled to a display system (62) positioned in front of the user's eyes. Speakers (66) are coupled to the frame (64) in the depicted configuration and positioned adjacent the user's ear canal (in one embodiment, another speaker, not shown, is positioned adjacent the user's other ear canal to provide stereo / shapeable sound control). The display (62) is operatively coupled (68), such as by wired leads or wireless connectivity, to a local processing and data module (70), which may be mounted in a variety of configurations, such as fixedly attached to the frame (64), fixedly attached to a helmet or hat (80) as shown in the embodiment of FIG. 2B, integrated into headphones, removably attached to the torso (82) of the user (60) in a backpack-style configuration as shown in the embodiment of FIG. 2C, or removably attached to the waist (84) of the user (60) in a belt-coupled configuration as shown in the embodiment of FIG. 2D.
[0036] The local processing and data module (70) may include a power-efficient processor or controller and digital memory, such as flash memory, both of which may be utilized to aid in the processing, caching, and storage of a) data captured from sensors, such as image capture devices (such as cameras), microphones, inertial measurement units (which may include accelerometers and gyroscopes or magnetometers), accelerometers, compasses, gyroscopes, or magnetometers, or GPS units, wireless devices, etc., which may be operatively coupled to the frame (64), and / or b) data that may be obtained and / or processed using the remote processing module (72) and / or remote data repository (74), potentially for passing to the display (62) after processing or readout. The local processing and data module (70) may be operatively coupled (76, 78) to remote processing modules (72) and remote data repositories (74), such as via wired or wireless communication links, such that the remote modules (72, 74) are operatively coupled to each other and available as resources to the local processing and data module (70).
[0037] In one embodiment, the remote processing module (72) may include one or more relatively powerful processors or controllers configured to analyze and process the data and / or image information. In one embodiment, the remote data repository (74) may include a relatively large digital data storage facility, which may be available through the Internet or other networking configurations in a "cloud" resource configuration. In one embodiment, all data may be stored and all calculations may be performed in the local processing and data module, allowing for fully autonomous use from any remote module.
[0038] 3, a schematic diagram illustrates the coordination between cloud computing assets (46) and local processing assets, which may reside, for example, in a head-mounted component (58) coupled to a user's head (120) and a local processing and data module (70) coupled to the user's belt (308) (thus, the component 70 may also be referred to as a "belt pack" 70, as shown in FIG. 3). In one embodiment, cloud (46) assets, such as one or more server systems (110), are operatively coupled (115) to one or both of the local computing assets (40, 42), such as processor and memory configurations coupled to the user's head (120) and belt (308), directly, as described above, or via wired or wireless networking (wireless being preferred for mobile use, wired being preferred for some high bandwidth or high data volume transfer that may be desired). These computing assets local to the user may likewise be operatively coupled to one another via wired and / or wireless connectivity arrangements (44), such as the wired coupling (68) discussed below with reference to Figure 8. In one embodiment, to maintain the low inertia and small size of the subsystem mounted on the user's head (120), the primary transfer between the user and the cloud (46) may be via a link between the belt (308)-mounted subsystem and the cloud, with the head-mounted subsystem (120) being primarily data tethered to the belt-based subsystem (308) using wireless connectivity, such as, for example, ultra-wideband ("UWB") connectivity as currently employed in personal computing peripheral connectivity applications.
[0039] By using efficient local and remote processing coordination and an appropriate display device for the user, such as the user interface or user display system (62) shown in FIG. 2A or a variation thereof, aspects of the world related to the user's current real or virtual location can be transferred or "passed" to the user and updated in an efficient manner. In other words, a map of the world can be continuously updated in a storage location that may reside partially on the user's AR system and partially in cloud resources. The map (also referred to as a "passable world model") may be a large database that includes raster images, 3D and 2D points, parameter information, and other information about the real world. As more and more AR users continuously capture information about their real environment (e.g., through cameras, sensors, IMUs, etc.), the map becomes more and more accurate and complete.
[0040] With the configuration as described above, there is one world model that resides on and can be delivered from cloud computing resources, and such world can be "passed" to one or more users in a relatively low bandwidth fashion that is preferable for attempting to route real-time video data or the like. The augmented experience of a person standing near the statue (e.g., as shown in FIG. 1) may be informed by the cloud-based world model, a subset of which may be passed to them and their local display device to complete the view. A person sitting at a remote display device, which may be as simple as a personal computer on a desk, can effectively download the same section of information from the cloud and have it rendered on its display. In fact, a person physically present in the park near the statue may take a walk through the park with a remotely located friend, who participates through virtual and augmented reality. The system would need to know where the streets are, where the trees are, where the statue is, but with that information on the cloud, a participating friend can download aspects of the scenario from the cloud and then start walking along the augmented reality that is local to the person physically in the park.
[0041] Three-dimensional (3D) points may be captured from the environment, and the poses (e.g., vectors and / or home position information relative to the world) of the cameras capturing those images or points may be determined so that those points or images may be "tagged" or associated with this pose information. The points captured by the second camera may then be utilized to determine the pose of the second camera. In other words, the second camera may be oriented and / or located based on a comparison with the tagged images from the first camera. This knowledge may then be utilized to extract textures, create maps, and create virtual copies of the real world (as there are now two aligned cameras around).
[0042] Thus, at a basic level, in one embodiment, a person-worn system can be utilized to capture both the 3D points and the 2D images that produced the points, which can be sent to cloud storage and processing resources. They can also be cached locally with on-board pose information (i.e., cache tagged images). Thus, the cloud can have tagged 2D images (e.g., tagged with 3D pose) with the 3D points at its fingertips (i.e., in its available cache). If the user is observing something dynamic, they may also send additional information about the movement to the cloud (e.g., if looking at another person's face, the user can take a texture map of the face and push it at an optimized frequency, even though the surrounding world is otherwise essentially static). Further information regarding object recognizers and passable world models may be found in U.S. Patent Publication No. 2014 / 0306866, entitled "System and method for augmented and virtual reality," which is incorporated herein by reference in its entirety, as well as the following additional disclosures relating to augmented and virtual reality systems such as those developed by Magic Leap, Inc. (Plantation, Florida): U.S. Patent Publication No. 2015 / 0178939, U.S. Patent Publication No. 2015 / 0205126, U.S. Patent Publication No. 2014 / 0267420, U.S. Patent Publication No. 2015 / 0302652, U.S. Patent Publication No. 2013 / 0117377, and U.S. Patent Publication No. 2013 / 0128230, each of which is incorporated herein by reference in its entirety.
[0043] GPS and other location information may be utilized as input for such processing. Highly accurate location of the user's head, totem, hand gestures, tactile devices, etc. may be advantageous for displaying appropriate virtual content to the user.
[0044] The head mounted device (58) may include a display positionable in front of the eye of a wearer of the device. The display may include a light field display. The display may be configured to present images to the wearer at multiple depth planes. The display may include a planar waveguide with diffractive elements. Examples of displays, head mounted devices, and other AR components that may be used with any of the embodiments disclosed herein are described in U.S. Patent Publication No. 2015 / 0016777, which is incorporated herein by reference in its entirety. Electromagnetic Location Example
[0045] One approach to achieving high-precision localization may involve the use of electromagnetic fields (EM) coupled with EM sensors strategically placed on the user's AR headset, beltpack, and / or other auxiliary devices (e.g., totems, tactile devices, gaming equipment, etc.). An EM tracking system typically includes at least an EM field emitter (sometimes also generally referred to as a transmitter or emitter) and at least one EM field sensor (sometimes also generally referred to as a receiver or sensor). The EM emitter generates an EM field with a known spatial (and / or temporal) distribution in the environment of the wearer of the AR headset. The EM field sensor measures the generated EM field at the location of the sensor. Based on these measurements and knowledge of the distribution of the generated EM field, the pose (e.g., position and / or orientation) of the electromagnetic field sensor relative to the emitter can be determined. Thus, the pose of the object to which the sensor is attached can be determined.
[0046] EM tracking may be a promising approach for locating and tracking objects in multiple fields, including applications in AR, VR, medicine, sports, manufacturing, and gaming. A possible advantage of EM localization over some other methods that use optical imaging techniques is that EM tracking can locate objects in the presence of occlusion (e.g., a first object is in front of a second object and at least partially blocks the second object from the view of the imaging system). EM tracking can also provide good dynamic response time and may not require the implementation of complex image processing and computer vision techniques sometimes implemented with camera methods. Camera-based tracking systems may require dedicated algorithms and hardware due to their high computational workload and may lack robustness against fast motion dynamics and occlusion. In AR and VR applications, a processor (e.g., local processing and data module 70) performs many computationally intensive tasks (e.g., rendering virtual content to a user, as described with reference to FIG. 1), and performs many of these tasks in real time. Therefore, reducing the computational complexity of tasks performed by a processor can be advantageous in AR and VR applications, and the use of EM tracking systems can also be advantageous in offloading tasks from the processor.
[0047] 4, an example system diagram of an EM tracking system (e.g., those developed by organizations such as Biosense, a subsidiary of Johnson & Johnson Corporation, Polhemus, Inc. (Colchester, Vermont), and those manufactured by Sixense Entertainment, Inc. (Los Gatos, California), as well as other tracking device manufacturers) is illustrated. In one or more embodiments, the EM tracking system includes an EM emitter 402 (which may sometimes be referred to as an EM field emitter or simply an emitter) configured to emit a known magnetic field. As shown in FIG. 4, the EM emitter may be coupled to a power source (e.g., electrical current, a battery, etc.) to provide power to the emitter 402.
[0048] In one or more embodiments, the EM emitter 402 comprises several coils (e.g., at least three coils positioned perpendicular to each other and producing fields in the X, Y, and Z directions) that generate a magnetic field. This magnetic field is used to establish a coordinate space (e.g., an XYZ Cartesian coordinate space). This allows the system to map the position of the sensor (e.g., an (X,Y,Z) position) relative to a known magnetic field and helps determine the position and / or orientation of the sensor. In one or more embodiments, the EM sensors 404a, 404b, etc. may be attached to one or more real objects. The EM sensors 404 (which may sometimes be referred to as EM field sensors or simply sensors) may include smaller coils in which a current may be induced through an emitted EM field. In general, the “sensor” component (404) may include small coils or loops, such as a set of three differently oriented (e.g., oriented orthogonally with respect to each other) coils coupled together in a small structure, such as a cube or other container, positioned / oriented to capture magnetic flux incoming from the magnetic field emitted by the emitter (402); by comparing the currents induced through these coils, and knowing the relative positions and orientations of the coils with respect to each other, the relative position and orientation of the sensor with respect to the emitter can be calculated.
[0049] One or more parameters related to the behavior of the coil and inertial measurement unit ("IMU") components operatively coupled to the EM tracking sensor may be measured to detect the position and / or orientation of the sensor (and the object to which it is attached) relative to a coordinate system to which the EM emitter is coupled. In one or more embodiments, multiple sensors may be used in conjunction with the EM emitter to detect the position and orientation of each of the sensors in the coordinate space. The EM tracking system may provide position in three directions (i.e., X, Y, and Z directions) and also in two or three orientation angles (e.g., yaw, pitch, and roll). For example, the EM tracking system may determine a six degree of freedom (6DOF) attitude, including three spatial coordinates (e.g., X, Y, and Z) and three orientation angles (e.g., yaw, pitch, and roll). In one or more embodiments, the IMU measurements may be compared to the coil measurements to determine the position and orientation of the sensor. In one or more embodiments, both EM and IMU data may be combined with various other data sources, such as cameras, depth sensors, and other sensors, to determine position and orientation. This information may be transmitted to the controller 406 (e.g., wireless communication, Bluetooth, etc.). In one or more embodiments, the pose (or position and orientation) may be reported at a relatively high refresh rate in conventional systems. Traditionally, an EM emitter is coupled to a relatively stable large object, such as a table, operating table, wall, or ceiling, and one or more sensors are coupled to a smaller object, such as a medical device, handheld game component, or the like. Alternatively, as described below with reference to FIG. 6, various features of an EM tracking system may be employed to produce a configuration in which changes or deltas in position and / or orientation between two objects moving in space relative to a more stable global coordinate system may be tracked.In other words, a variation of the EM tracking system may be utilized in the configuration shown in FIG. 6 to track position and orientation deltas between the head-mounted and handheld components, while the head pose relative to a global coordinate system (e.g., of the indoor environment local to the user) is determined otherwise, such as by simultaneous localization and mapping ("SLAM") techniques, using an outward-facing capture camera that may be coupled to the head-mounted component of the system.
[0050] The controller 406 may control the EM field generator 402 and may also capture data from the various EM sensors 404. It should be understood that the various components of the system may be coupled to each other through any electromechanical or wireless / Bluetooth means. The controller 406 may also include data regarding the known magnetic field and the coordinate space associated with the magnetic field. This information is then used to detect the position and orientation of the sensor relative to the coordinate space corresponding to the known EM field.
[0051] One advantage of EM tracking systems is that they can produce highly accurate tracking results with minimal latency and high resolution. In addition, EM tracking systems do not necessarily rely on optical trackers, and sensors / objects that are not within the user's line of sight can easily be tracked.
[0052] It should be appreciated that the strength of the EM field falls off as a cubic function of the distance ("r") from the coil transmitter (e.g., EM emitter 402). Thus, algorithms may be used based on the distance from the EM emitter. The controller 406 may be configured to use such algorithms to determine the position and orientation (e.g., 6DOF pose) of the sensor / object at variable distances from the EM emitter. Given the rapid falloff in the strength of the EM field as the sensor moves away from the EM emitter, best results in terms of accuracy, efficiency, and low latency may be achieved at closer distances. In a typical EM tracking system, the EM emitter is powered by an electric current (e.g., a plug-in power supply) and has a sensor located within a 20-foot radius of the EM emitter. A shorter radius between the sensor and the emitter may be more desirable in many applications, including AR applications.
[0053] Referring now to FIG. 5, an exemplary flow diagram illustrating the functioning of an exemplary electromagnetic tracking system is briefly described. At 502, a known EM field is emitted. In one or more embodiments, a magnetic field emitter may generate a magnetic field, and each coil may generate an electric field in one direction (e.g., X, Y, or Z). The magnetic field may be generated with an arbitrary waveform. In one or more embodiments, the magnetic field components along each of the axes may oscillate at a slightly different frequency than other magnetic field components along other directions. At 504, a coordinate space corresponding to the EM field may be determined. For example, the control 406 of FIG. 4 may automatically determine the coordinate space around the emitter based on the EM field. At 506, the behavior of the coil in the sensor (which may be attached to a known object) may be detected. For example, the current induced in the coil may be calculated. In some embodiments, the rotation or any other quantifiable behavior of the coil may be tracked and measured. At 508, this behavior may be used to detect the position or orientation of the sensor and / or the known object. For example, the controller 406 may consult a mapping table that correlates the behavior of the coils in the sensor to various positions or orientations. Based on these calculations, a position in coordinate space may be determined along with the orientation of the sensor. The order of the blocks in the flowchart of FIG. 5 is intended to be illustrative rather than limiting. For example, block 506 can be performed before block 504 is performed in some embodiments.
[0054] In the context of an AR system, one or more components of the EM tracking system may need to be modified to facilitate accurate tracking of the mobile component. As described above, tracking of the user's head pose and orientation may be desirable in many AR applications. Accurate determination of the user's head pose and orientation allows the AR system to display the correct virtual content to the user. For example, a virtual scene may include a monster hidden behind a real building. Depending on the user's head pose and orientation relative to the building, the view of the virtual monster may need to be modified so that a realistic AR experience is provided. Alternatively, the position and / or orientation of a totem, tactile device, or some other means of interacting with the virtual content may be important in enabling the AR user to interact with the AR system. For example, in many gaming applications, the AR system must detect the position and orientation of a real object associated with the virtual content. Alternatively, when displaying a virtual interface, the position of a totem, a user's hand, a tactile device, or any other real object configured for interaction with the AR system may be known in relation to the displayed virtual interface in order for the system to understand commands, etc. Conventional localization methods, including optical tracking and other methods, typically suffer from high latency and low resolution problems, making rendering virtual content difficult in many augmented reality applications.
[0055] In one or more embodiments, an EM tracking system, discussed in connection with Figures 4 and 5, may be adapted to an AR system to detect the position and orientation of one or more objects relative to the emitted EM field. Typical EM systems tend to have large and bulky EM emitters (e.g., 402 in Figure 4), which is problematic for head-mounted AR devices. However, smaller electromagnetic emitters (e.g., in the millimeter range) may be used to emit a known EM field in the context of an AR system.
[0056] 6, an EM tracking system 600 may be incorporated with an AR system as shown, with an EM emitter 602 incorporated as part of a handheld controller 606. The controller 606 may be independently movable with respect to the AR headset (or belt pack 70). For example, a user may hold the controller 606 in their hand, or the controller may be mounted on the user's hand or arm (e.g., as a ring or bracelet, or as part of a glove worn by the user). In one or more embodiments, the handheld controller may be a totem for use in gaming scenarios, or for providing a rich user experience within an AR environment, or for allowing a user to interact with the AR system (e.g., a multi-degree-of-freedom controller). In some embodiments, the handheld controller may be a tactile device. In some embodiments, the EM emitter may simply be incorporated as part of the belt pack 70. The controller 606 may include a battery 610 or other power source that powers the EM emitter 602. It should be appreciated that the EM emitter 602 may also include or be coupled to an IMU component 650 configured to aid in determining the position and / or orientation of the EM emitter 602 relative to other components. This may be particularly advantageous when both the emitter 602 and the sensor (604) are mobile. The IMU 650 may include an accelerometer and a gyroscope in some embodiments. As shown in the embodiment of FIG. 6, locating the EM emitter 602 in the handheld controller rather than the beltpack helps ensure that the EM emitter does not compete for resources in the beltpack, but rather uses its own battery source in the controller 606. In some embodiments, the EM emitter 602 may be located on the AR headset 58 and the sensor 604 may be located on the controller 606 or the beltpack 70.
[0057] In one or more embodiments, the EM sensor 604 may be placed in one or more locations on the user's headset along with other sensing devices, such as one or more IMUs or additional flux capture coils (608). For example, as shown in FIG. 6, the sensors (604, 608) may be placed on one or both sides of the headset (58). These sensors are fabricated to be very small (and therefore in some cases may be less sensitive), so having multiple sensors may improve efficiency and accuracy. In one or more embodiments, one or more sensors may also be placed on the belt pack 70 or any other part of the user's body, or in the controller 606. The sensors (604, 608) may communicate wirelessly or through Bluetooth with a computing device that determines the attitude and orientation of the sensor (and the AR headset to which it is attached). In some embodiments, the computing device may reside in the belt pack 70. In some embodiments, the computing device may reside in the headset itself or even in the controller 606. The computing device may then contain a mapping database (e.g., a passable world model, a coordinate space, etc.), detect pose, determine coordinates of real and virtual objects, and, in one or more embodiments, connect to cloud resources and passable world models.
[0058] As explained above, conventional EM emitters may be too bulky for use in AR devices. Thus, the EM emitter may be fabricated compactly using smaller coils compared to conventional systems. However, a shorter radius between the EM sensor 604 and the EM emitter 602 (e.g., about 3-3.5 feet) may reduce power consumption compared to conventional systems such as those detailed in FIG. 4, provided that the strength of the EM field decreases as a cubic function of the distance from the emitter.
[0059] This aspect may be utilized in one or more embodiments to extend the life of the battery 610, which may power either the controller 606 and the EM emitter 602. In some embodiments, this aspect may be utilized to reduce the size of the coils that generate the magnetic field in the EM emitter 602. However, to obtain the same strength of the magnetic field, the power may need to be increased. This allows for a compact EM emitter unit 602 that may fit compactly in the controller 606.
[0060] Some other modifications may be made when using the EM tracking system 600 for an AR device. While the present attitude reporting rate is quite good, AR systems may require an even more efficient attitude reporting rate. To this end, IMU-based attitude tracking may be used within the sensor (in addition or as an alternative). Advantageously, the IMU may remain as stable as possible to increase the efficiency of the attitude detection process. The IMU may be engineered to remain stable for up to 50-100 milliseconds. It should be appreciated that some embodiments may utilize an external attitude estimator module, which may allow attitude updates to be reported at a rate of 10-20 Hz (e.g., the IMU may drift over time). By keeping the IMU stable to a reasonable rate, the attitude update rate may be significantly reduced to 10-20 Hz (compared to higher frequencies in conventional systems).
[0061] If the EM tracking system 600 could be woken up, for example, at a 10% duty cycle (e.g., pinging for ground truth only every 100 ms), this would be another way to save power in an AR system. This would mean that the EM tracking system would wake up for 10 ms every 100 ms to generate a pose estimate. This could directly translate into power consumption savings, which in turn could impact the size, battery life, and cost of the AR device.
[0062] In one or more embodiments, this reduction in duty cycle may be strategically utilized by providing two handheld controllers (not shown) instead of only one. For example, a user may play a game that requires two totems, etc. Or, in a multi-user game, two users may have their own totem / handheld controllers and play the game. When two controllers (e.g., symmetrical controllers per hand) are used instead of one, the controllers may operate with an offset duty cycle. The same concept may also be applied to controllers utilized by two different users, for example, playing a multiplayer game.
[0063] 7, an exemplary flow diagram illustrating an electromagnetic tracking system 600 in the context of an AR device is described. At 702, a portable (e.g., handheld) controller containing an EM emitter emits a magnetic field. At 704, an EM sensor (located on a headset, beltpack, etc.) detects the magnetic field. At 706, the pose (e.g., position or orientation) of the headset / belt is determined based on the behavior of the coil / IMU in the sensor. The pose may include a 6DOF pose, or may have less than all six degrees of freedom (e.g., one or more spatial coordinates or one or more orientation angles). At 708, the pose information is communicated to a computing device (e.g., in the beltpack or headset). At 710, optionally, a mapping database (e.g., a passable world model) may be consulted to correlate real world coordinates (e.g., determined with respect to the pose of the headset / belt) with virtual world coordinates. At 712, the virtual content may be delivered to the user in the AR headset and displayed to the user (e.g., via a light field display as described herein). It should be understood that the flow diagrams described above are for illustrative purposes only and should not be read as limiting.
[0064] Advantageously, the use of an EM tracking system similar to that outlined in Figure 6 allows for low latency pose tracking (e.g., head position or orientation, totem, beltpack, and other controller position and orientation), which allows the AR system to project virtual content (based at least in part on the determined pose) with greater accuracy and lower latency compared to optical tracking techniques.
[0065] Referring to Figure 8, an augmented reality system configuration featuring a number of sensing components is illustrated. The head mounted wearable component (58) is shown here operatively coupled (68) to a local processing and data module (70), such as a belt pack, using a physical multi-core conductor that also features a control and quick release module (86). The control and quick release module (86) may include buttons for operation of the associated system, such as an on / off button and an up / down volume control. Opposite ends of the module (86) may be connected to electrical conductors extending between the local processing and data module (70) and the display (62), as shown in Figure 8.
[0066] The local processing and data module (70) is operatively coupled (100) to the handheld component / controller (606), here by a wireless connection such as low-power Bluetooth®. The component (606) may also be operatively coupled (94) directly to the head-mounted wearable component (58), such as by a wireless connection such as low-power Bluetooth®. Generally, if IMU data is passed to coordinate orientation detection of the various components, a high frequency connection is desirable, such as in the range of hundreds or thousands of cycles per second or higher. For EM localization sensing, such as by sensor (604) and transmitter (602) pairing, tens of cycles per second may be adequate. Also shown is a global (or sometimes referred to as world) coordinate system (10), which represents fixed objects in the real world around the user, such as walls (8).
[0067] The cloud resources (46) may also be operatively coupled (42, 40, 88, 90) to resources that may be coupled to a local processing and data module (70), to a head-mounted wearable component (58), to a wall (8) or other item fixed relative to the global coordinate system (10), respectively. Resources coupled to a wall (8) or having a known position and / or orientation relative to the global coordinate system (10) may include a wireless transceiver (114), an EM emitter (602) and / or receiver (604), a beacon or reflector (112) configured to emit or reflect a given type of radiation, such as an infrared LED beacon, a cellular network transceiver (110), a RADAR emitter or detector (108), a LIDAR emitter or detector (106), a GPS transceiver (118), a poster or marker having a known detectable pattern (122), and a camera (124).
[0068] The head mounted wearable component (58) features similar components as shown in addition to an optical emitter (130) configured to assist the camera (124) detector, such as an infrared emitter (130) for the infrared camera (124). The head mounted wearable component (58) also features one or more strain gauges (116) fixedly coupled to the frame or mechanical platform of the head mounted wearable component (58) and configured to determine deflection of such platform between components such as the EM receiver sensor (604) or the display element (62), which may be important to understand when bending of the platform occurs, such as in thin portions of the platform, such as the portions above the protrusions on the glasses-like platform depicted in FIG.
[0069] The head-mounted wearable component (58) also features a processor (128) and one or more IMUs (102). Each of the components is preferably operatively coupled to the processor (128), which may include a hardware controller, a hardware microprocessor, an application specific integrated circuit (ASIC), or the like. The component (606) and the local processing and data module (70) are illustrated as featuring similar components. As shown in FIG. 8, with so many sensing and connectivity means, such a system is likely to be heavy, power hungry, large, and relatively expensive. However, for illustrative purposes, such a system may be utilized to provide a very high level of connectivity, system component integration, and position / orientation tracking. For example, with such a configuration, the various primary mobile components (58, 70, 606) may be located in terms of position relative to a global coordinate system using Wi-Fi, GPS, or cellular signal triangulation, and beacons, EM tracking (as described herein), RADAR, and LIDIR systems may further provide location and / or orientation information and feedback. Markers and cameras may also be utilized to provide further information regarding relative and absolute position and orientation. For example, various camera components (124), such as the one shown coupled to the head-mounted wearable component (58), may be utilized to capture data that may be utilized in a simultaneous localization and mapping protocol, or "SLAM," to determine where and how the component (58) is oriented relative to other components.
[0070] In some embodiments, in addition to or as an alternative to a LIDAR (106) type depth sensor, the system includes a general-purpose depth camera or depth sensor, which may be, for example, either a stereo triangulation depth sensor (such as a passive stereo depth sensor, a texture projection stereo depth sensor, or a structured light stereo depth sensor) or a time-of-flight depth sensor (such as a LIDAR depth sensor or a modulated emission depth sensor). Furthermore, the system may include an additional forward-looking "world" camera (which may be a grayscale camera, having a sensor capable of resolution in the 124, 720p range) and a relatively high resolution "photo camera" (which may be a full color camera, having a sensor capable of resolutions as high as 2 megapixels or higher, for example). (Example Electromagnetic Sensing Components in an AR System)
[0071] With reference to FIG. 9A, an EM sensing coil assembly (604, e.g., three individual coils coupled to a housing) is shown coupled to the head mounted component (58). Such a configuration adds additional geometry to the overall assembly, which may not be desirable. With reference to FIG. 9B, rather than storing the coils in a box or single housing 604, as in the configuration of FIG. 9A, the individual coils may be integrated into various structures of the head mounted component (58), as shown in FIG. 9B. FIG. 9B shows an example of locations on the head mounted display 58 for the X-axis coil (148), Y-axis coil (150), and Z-axis coil (152). Thus, the sensing coils may be spatially distributed on or about the head mounted display (58) to provide a desired spatial resolution or accuracy of localization and / or orientation of the display (58) by an EM tracking system.
[0072] Referring again to FIG. 9B, a distributed sensor coil configuration is shown for the AR device 58. The AR device 58 can have a single EM sensor device (604), such as a housing, containing three orthogonal sensing coils, one for each of the X, Y, and Z directions, which can be coupled to the wearable component (58) for six degrees of freedom (6DOF) tracking, as described herein. Also, as noted above, such a device can be broken down with three sub-parts (e.g., coils) attached at different locations on the wearable component (58), as shown in FIG. 9B. To provide further design alternatives, each individual sensor coil can be replaced with a group of similarly oriented coils such that the overall magnetic flux for any given orthogonal direction is captured by the group rather than a single coil for that orthogonal direction. In other words, rather than one coil for each orthogonal direction, a group of smaller coils can be utilized and their signals can be aggregated to form a signal for that orthogonal direction. In some embodiments where a particular system component, such as the head mounted component (58), features two or more EM coil sensor sets, the system may be configured to selectively utilize sensor and emitter pairings that are closest to each other (e.g., within 1 cm, 2 cm, 3 cm, 4 cm, 5 cm, or 10 cm) to improve or optimize system performance. In some embodiments, the EM emitters and EM sensors can be arranged differently. For example, the EM emitters can be located in or on the head mounted component (58) and the EM sensors can be located in or on the controller (606) or belt pack (70). As another example, the EM sensors can be located in or on the head mounted component (58) and the EM emitters can be located in or on the controller (606) or belt pack (70). As yet another example, the EM emitters can be located in or on the belt (70) and the EM sensors can be located in or on the controller (606) or head mounted component (58).
[0073] EM tracking updates may be relatively "expensive" in terms of power for a portable system and may not allow for very frequent updates. In a "sensor fusion" configuration, more frequently updated localization information from another sensor, such as an IMU, may be combined with data from another sensor, such as an optical sensor (e.g., a camera or depth camera), which may or may not be at a relatively high frequency. The point of fusing all of these inputs may place lower demands on the EM system and provide more rapid updates. As described herein, in some embodiments, sensor fusion techniques may include fusing or combining IMU (or other sensor) data and EM tracking data to provide a robust estimate of the pose of the handheld or head-mounted component.
[0074] 9C and 9D illustrate an example headset with more than one EM sensor 604C, 604D. FIGs. 9E and 9F illustrate an example handheld controller with more than one EM emitter 602E, 602F. Depending on the implementation, such as to improve the accuracy of the pose detection generated by the EM tracking system, the amount of EM sensors and / or EM emitters may vary. For example, a headset with two EM sensors 604C (e.g., FIG. 9C) may be used with a controller with one EM emitter, two EM emitters 602E (e.g., FIG. 9E), three EM emitters 602F (e.g., FIG. 9F), or more EM emitters. Similarly, a headset with three (or any other quantity) EM sensors 604D (e.g., FIG. 9D) may be used with a controller with one EM emitter, two EM emitters 602E (e.g., FIG. 9E), three EM emitters 602F (e.g., FIG. 9F), or more EM emitters.
[0075] Embodiments with multiple EM sensors on different sides of the headset (e.g., FIG. 9C) may reduce the effects of metal distortion. For example, in some implementations, input from EM sensor 604C may be weighted based on proximity or location relative to the controller with EM emitter 602. For example, if the controller with EM emitter 602 is to the right of the user, the EM sensor 604 on the right side of the headset may have a higher weighted input than other EM sensors that have a less direct communication channel with the controller (e.g., the EM sensor 604 on the left or center of the headset).
[0076] The use of multiple EM sensors may further provide data that can be used to quantitatively monitor distortion that may be caused by interference of EM signals between the EM emitters and the EM sensors. For example, with two EM sensors on the headset in known locations and one EM emitter on the controller, the two resolved position vectors between the EM sensors and the EM emitter can be used to form a triangle. This "sensed" displacement between the EM sensors may be compared to the "known" EM sensor locations, for example, in a model of the headset. This quantitative estimate of distortion may then be used to provide feedback to a user, software application, etc., such as an indication of "expected distortion" (e.g., distortion effect measured between the headset and the controller in a clean environment) and "environmental distortion" (e.g., amount of distortion remaining after subtracting out the expected distortion). Similar weighting and distortion calculations may be determined in configurations with other amounts of emitters and sensors. (Example of EM tracking of user head or hand pose)
[0077] 10, in one embodiment, after a user powers on their wearable computing system (160), the head-mounted component assembly may capture a combination of IMU and camera data (the camera data is used for SLAM analysis, e.g., for a beltpack processor, where there may be more raw processing power) or EM tracking system data to determine and update the pose (e.g., position or orientation) of the head relative to a real-world global coordinate system (162; an example of a real-world global coordinate system 10 is shown in FIG. 8). The user may also activate a handheld component, for example, to play an augmented reality game (164), which may include an EM transmitter operably coupled to one or both of the beltpack and head-mounted components (166). One or more EM field coil receiver sets (e.g., a set being three differently oriented individual coils) coupled to the head-mounted component capture magnetic flux from the transmitter, which may be utilized to determine the position or orientation difference (or "delta") between the head-mounted component and the handheld component (168). The combination of the head-mounted component helping to determine pose with respect to a global coordinate system and the handheld helping to determine the relative location and orientation of the handheld with respect to the head-mounted component allows the system to generally determine where each component is located with respect to the global coordinate system, and thus the pose of the user's head, which may be tracked with relatively low latency for presentation of augmented reality image features and interaction using movement and rotation of the handheld component (170).
[0078] Referring to Figure 11, an embodiment is illustrated that is somewhat similar to that of Figure 10, but in which the system has more sensing devices and configurations available to assist in determining the pose of both the head-mounted component (172) and the handheld components (176, 178) so that the user's head pose and handheld pose can be tracked with relatively low latency, preferably for presentation of augmented reality image features and interaction using movement and rotation of the handheld component (180).
[0079] In various implementations, the augmented reality device may include a computer vision system configured to implement one or more computer vision techniques and identify objects in the system's environment, user gestures, or perform other computer vision procedures used or described herein. For example, as described below, the computer vision system may analyze images of the user input device / controller 606 captured by the outward-facing camera 124 and determine the device's pose (e.g., position or orientation) for use in compensating for EM distortions in the electromagnetic tracking system. Non-limiting examples of computer vision techniques include Scale Invariant Feature Transform (SIFT), Speed Up Robust Features (SURF), Orientation FAST and Rotation BRIEF (ORB), Binary Robust Invariant Scalable Keypoints (BRISK), Fast Retinal Keypoints (FREAK), Viola-Jones algorithm, Eigenfaces approach, Lucas-Kanade algorithm, Horn-Schunk algorithm, Mean-shift algorithm, visual simultaneous localization and mapping (vSLAM) techniques, sequential Bayes estimators, Kalman filters, extended Kalman filters, bundle adjustment, adaptive thresholding (and other thresholding techniques), iterative nearest neighbors (ICP), semi-global matching (SGM), semi-global block matching (SGBM), feature point histograms, various machine learning algorithms (e.g., support vector machines, k-nearest neighbor algorithms, naive Bayes, neural networks (including convolutional or deep neural networks), or other supervised / unsupervised models, etc.), etc. (Electromagnetic Location Overview)
[0080] EM localization is based on magnetic field coupling, measured by one or more EM sensors, resulting from excitation of a magnetic field by one or more EM emitters. There are two common ways to excite the magnetic field: one is based on a pulsed alternating current (AC) field, and the other is based on a pulsed direct current (DC) field. Currently, EM tracking systems that utilize AC EM fields are more common because they tend to be less sensitive to noise. As described with reference to FIGS. 9A and 9B, for 6DOF localization, the EM sensor (e.g., EM sensor 604) and the EM emitter (e.g., EM emitter 602) can each include three orthogonal matching coils (e.g., along separate X, Y, and Z axes). In many applications using this configuration, the emitter coil current in EM emitter 602 is pulsed sequentially (e.g., in X, then in Y, then in Z) and the resulting magnetic field induces a current in each sensor coil in EM sensor 604 which is then used to determine the position or orientation of the sensor coil relative to the emitter coil and thus the EM sensor 604 relative to the EM emitter 602.
[0081] Without being bound or limited by the following theoretical developments, an EM model for EM localization will now be presented. In this model, the magnetic field generated by the emitter coil in the EM emitter 602 is assumed to be an equivalent magnetic dipole field (which tends to be accurate when the size of the emitter coil in the EM emitter 602 is smaller than the distance between the emitter coil and the sensor coil). The dipole field decreases with increasing distance between the EM emitter 602 and the EM sensor 604 as the inverse cube of the distance.
[0082] Equations for 6DOF localization can use Euler angle transformations (or quaternions) and describe the position and orientation of the EM sensor 604 relative to the EM emitter 602. The EM field sensed by the EM sensor 604 can be represented by a matrix equation: [ka] where F is a 3×3 EM field matrix, c is a constant for any given coil configuration (e.g., proportional to the product of the number of loops of wire, the area of the loops, and the sensor gain), r is the distance between the EM emitter 602 and the EM sensor 604, T is a 3×3 rotation matrix representing the three degrees of freedom (3DOF) orientation of the EM sensor 604 relative to the EM emitter 602, P is a 3×3 rotation matrix representing the position of the EM sensor 604 relative to the EM emitter 602, K is a 3×3 diagonal matrix with diagonal elements proportional to [1, −½, −½], and E is a 3×3 diagonal matrix whose diagonal elements represent the EM field strength measured by the three orthogonal emitter coils of the EM emitter 602. The matrix P may be expressed in terms of azimuth angle θ and pitch φ by: [ka] where roty is a 3x3 rotation matrix around the Y axis and rotz is a 3x3 rotation matrix around the Z axis.
[0083] Since the matrix elements involve trigonometric functions, Equation (1) is actually a simultaneous nonlinear equation with six unknowns (three position variables and three orientation variables) that can be solved simultaneously (e.g., via iterative numerical techniques) to obtain the 6DOF pose of the EM sensor 604 relative to the EM emitter 602. The position and orientation from the method described above may need to be transformed to a different reference frame due to the placement of the EM sensor coil relative to a global reference frame. This frame (or reference frame) is sometimes referred to as the world frame (or world reference frame or world or global coordinate system). An example of the world coordinate system 10 is described with reference to FIG. 8. In some implementations, the world coordinate system 10 is established when the AR device is turned on by the user, for example, when the user's initial head pose is determined. The origin of the world frame can be set to any point in the environment, for example, a corner of a room in which the user is operating the device can be set as the origin (e.g., with coordinates (0,0,0) in the Cartesian system). (Overview of Sensor Fusion for Augmented Reality Systems)
[0084] 12 is a block diagram for an example of an inertial navigation system (INS) 1202 that can receive input from an IMU 650 on a handheld user input device (e.g., handheld controller / totem 606, described with reference to FIGS. 6 and 8) and provide a 6DOF pose (e.g., position and orientation) of the totem in a world frame (e.g., world coordinate system 10) associated with the AR system 200. The AR system 200 can utilize the 6DOF pose, for example, as described with reference to the flowcharts in FIGS. 7, 10, and 11.
[0085] As described herein, the totem IMU 650 may include, among other components, an accelerometer, which provides acceleration a(t) as a function of time measured in the totem's frame of reference, and a gyroscope, which provides angular velocity ω(t) as a function of time measured in the totem's frame of reference.
[0086] The INS 1202 may include a hardware processor that integrates the acceleration data twice to obtain the position of the totem 606, and integrates the angular velocity once to obtain the angular orientation (e.g., expressed as Euler angles or a quaternion) of the totem 606. For example, the position x(t) of the totem 606 may be written as: [ka] where x0 and v0 are integration constants that represent the initial position and velocity, respectively, of the totem at time t = 0. The orientation θ(t) of the totem 606 can be written as: [ka] where θ is an integral constant that represents the initial angular orientation of the totem at time t=0.
[0087] There are several challenges when implementing equations (3) and (4). First, the initial position, orientation, and angular orientation of the totem 606 in the world reference frame of the AR system 200 are generally not known. Thus, the integral constants x0, v0, and θ0 may be difficult to determine without additional information or input from other sensors to link the position and orientation of the IMU's reference frame at an initial time (e.g., t=0) to the world reference frame of the AR system 200. This link between the two reference frames may sometimes be referred to herein as an offset, since it represents an offset between the position of the totem relative to the world reference frame of the AR system 200 at an initial time (e.g., t=0).
[0088] Data from the Totem IMU 650 is generally subject to error, nonlinearity, and noise. For example, the output from an accelerometer or gyroscope may have a bias that is offset from the true acceleration or angular rate. For some sensors, the bias may be a function of time, temperature, sensor orientation, power supply voltage, etc. Thus, the bias (unknown) may change over time in an unknown manner. Even if the sensor is initially calibrated to remove any bias present in the sensor, the bias will tend to evolve over time.
[0089] Errors in the accelerometer and gyroscope data can lead to drift in the position and orientation determined from equations (3) and (4), respectively. Because of the two integrals in equation (3), errors in the accelerometer data lead to a drift in the determined position that increases quadratically with time. Because of the single integral in equation (4), errors in the gyroscope data lead to a drift in the determined orientation that increases linearly with time. If uncorrected, these drifts can cause the determined position and orientation to deviate substantially from the actual position and orientation.
[0090] As will be described below, inputs from additional sensors to the totem IMU 650 can be fused with IMU data (e.g., accelerometer data and gyroscope data) to reduce drift and link the totem's position and orientation to the world reference frame of the AR system 200. For example, a sensor fusion algorithm such as a Kalman filter can be used to fuse the sensor data inputs along with a model of the sensor error states and reference frame offsets. For example, a Kalman filter can provide a robust prediction of the totem's pose in the presence of sensor bias, noise, and offsets relative to the totem's initial pose in the world reference frame of the AR system 200. The embodiments described below utilize a Kalman filter, but other statistical filters or probabilistic data fusion techniques can also be used. For example, the Kalman filter can include an extended Kalman filter, an unscented Kalman filter, or any other variety of Kalman filters. Probabilistic data fusion techniques can include Markov models, Bayesian filtering, linear quadratic estimation, and the like. Additionally, while described in terms of estimating the 6DOF pose (e.g., position and orientation) of the totem, this is not a requirement and in other embodiments the sensor fusion system may estimate a 3DOF pose (e.g., position or orientation).
[0091] As an illustrative example, if the totem's initial velocity v0 is zero, then the model for the totem's position can be written as follows: [ka] In the formula, offset x is an estimate of the position error between the world reference frame of the AR system 200 and the accelerometer reference frame (relative to an arbitrarily chosen coordinate origin), and ε(t) is an error state estimate to correct for bias in the accelerometer output. A similar equation can be written in terms of angular orientation θ(t) as follows: [ka] In the formula, offset θ is an estimate of the angular error between the world reference frame of the AR system 200 and the gyroscope reference frame (relative to an arbitrarily chosen coordinate origin), and δ(t) is an error state estimate to correct for bias in the gyroscope output (angular rate). A Kalman filter (or other suitable filter) can provide error state estimates (e.g., offsets, ε, and δ), as will be further described below. (Example System for Sensor Fusion)
[0092] 13A is a block diagram that diagrammatically illustrates an example of a sensor fusion system 1300 that can be used with AR system 200, e.g., as described with reference to FIGS. 2A-2D, 6, or 8. An embodiment of sensor fusion system 1300 addresses some or all of the challenges described above with reference to FIG.
[0093] The sensor fusion system 1300 includes an inertial navigation system (INS) 1302 configured to receive and fuse sensor data from multiple types of sensors. For example, as shown in FIG. 13A, the INS 1302 can receive input data from a totem IMU 650, an EM tracking system 600, and additionally or optionally, other sensors 651. As described herein, the totem IMU 650 can include, among other components, an accelerometer and a gyroscope. The other sensors 651 can include, among other components, a magnetometer and an optical sensor (e.g., in an outward-facing or inward-facing camera).
[0094] An embodiment of the EM tracking system 600 is described above with reference to Figures 6-11. For example, the totem 606 may include an EM emitter 602 that emits an EM field, and the head-mounted AR headset 58 may include an EM sensor 604 that measures the emitted EM field and calculates a pose (3DOF or 6DOF) of the EM sensor 604 relative to the EM emitter 602. For example, the 6DOF pose may be calculated from the EM field matrix F, described above with reference to equation (1).
[0095] In other implementations, the EM emitter 602 can be located in the AR headset 58 and the EM sensor 604 can be located in the totem 606. See, for example, Figures 9A and 9B for a description of various arrangements of EM sensors and emitters.
[0096] The sensor fusion system 1300 includes a Kalman filter 1304 that can estimate an error state for the totem pose (e.g., as described with reference to equations (5) and (6)). The Kalman filter 1304 can utilize models (e.g., without bias, noise, etc.) for how the totem IMU 650 should behave and compare these models to actual measurements from the sensors (e.g., the totem IMU 650, the EM tracking system 600, and (optionally) other sensors 651). The Kalman filter 1304 can use the difference between the models and measurements to provide a better estimate of the totem pose. For example, the Kalman filter 1304 can predict an estimate of the current state of the totem pose and compare this state to data from the sensors being fused (e.g., the IMU 650, the EM tracking system 600, and (optionally) other sensors 651) to generate an error state. Knowledge of the error state can be used to update the state of the totem pose (e.g., via equations (5) and (6)). As noted above, the use of a Kalman filter 1304 is not a requirement and in other embodiments, other statistical filters or probabilistic data fusion techniques such as, for example, Markov models, Bayesian filtering, linear quadratic estimation, etc., can also be used.
[0097] The INS 1302 uses a Kalman filter to fuse inputs from the totem IMU and EM tracking system (and optionally any other sensors 651) to provide an estimate of the totem pose that tends to be more statistically accurate than pose estimates that use inputs only from the totem IMU 650 or only from the EM tracking system 600. For example, the Kalman filter 1304 can correct for drift in the totem pose (e.g., due to sensor bias, noise, etc.) and adjust the offset of the AR system 200 relative to the world reference frame.
[0098] Thus, the sensor fusion system 1300 can determine a totem pose (e.g., 3DOF or 6DOF) in the world reference frame of the AR system 200 and provide this totem pose to the AR system 200. The AR system 200 can use the totem pose in the world reference frame of the AR system 200 to, for example, deliver virtual content to a user of the AR system (see, for example, FIGS. 7, 10, 11). The sensor fusion technique provides a more accurate and robust estimate of the totem pose, thereby leading to improved delivery of virtual content to the user and an improved user experience of the AR system 200.
[0099] 13B and 13C provide additional illustrative features of the sensor fusion system 1300. As described above with reference to equation (1), the EM tracking system 600 uses the EM field matrix 1322 measured by the EM sensors 604 to determine the totem pose. The measured EM field matrix 1322 is a 3×3 matrix, denoted by F, having nine elements. In FIG. 13B, the measured EM field matrix 1322 is compared to a predicted EM field matrix 1324, which represents the system's estimate of the expected totem pose. The comparison may include a difference 1328 between the predicted EM field matrix 1324 and the measured EM field matrix 1322. The comparison between the predicted and measured EM field matrices 1324, 1322 provides an estimate of the error state used by the Kalman filter 1304. For example, when the difference between the predicted and measured EM field matrices 1324, 1322 is relatively small, there may not be much drift due to sensor bias or noise, and the determination of the totem attitude by the INS 1302 may be relatively accurate. As drift accumulates, the difference between the predicted and measured EM field matrices 1324, 1322 may increase, and the Kalman filter 1304 acts to restore the accuracy of the totem attitude 1310. As shown by the dashed line 1328 in FIG. 13B, the current value of the totem attitude in the world frame 1310 can be fed back into the prediction of where the totem 606 is expected to be. The Kalman filter 1304 thus works recursively to provide an improved or optimal determination of the totem attitude in the world frame 1310 by fusing inputs from the totem IMU 650 and the EM tracking system 600 (and optionally other sensors 651).
[0100] FIG. 13C illustrates an example of how a predicted EM field matrix 1324 may be determined by the sensor fusion system 1300. In FIG. 13C, the EM emitter 602 is labeled "TX" (an abbreviation for transmitter) and the EM sensor 604 is labeled "RX" (an abbreviation for receiver). The block diagram in FIG. 13C illustrates an example of how measurements made by the EM emitter 602 and the EM sensor 604 may be transformed into the world reference frame of the AR system 200. In this example, the EM emitter 602 is assumed to be located in the totem 606 (see, e.g., FIG. 6) and the EM sensor 604 is assumed to be located in the AR headset 58 (see, e.g., FIG. 9A). This arrangement of EM emitter 602 and EM sensor 604 is not limiting, and in other embodiments, the process described with reference to FIG. 13C may be modified for other arrangements (e.g., EM emitter 602 in AR headset 58 and EM sensor 604 in totem 606).
[0101] In block 1342, the system 1300 accesses head pose data indicating the pose of the AR headset 58 within the world reference frame of the AR system 200. As described above with reference to FIG. 8, sensors within the AR headset 58, such as the IMU 102 or the outward-facing world camera 124, can be used to determine the pose of the headset 58. For example, the camera 124 may be used to capture data that may be used in a simultaneous localization and mapping protocol or "SLAM" to determine where the AR headset 58 is and how it is oriented relative to the system 200 or other components in the world. The pose (e.g., position and orientation) of the AR headset 58 can be referenced to a fiducial origin 900 for the AR headset 58. For example, as shown diagrammatically in FIG. 9A, the fiducial origin 900 may be at a point near the center of the headset 58, e.g., substantially between a pair of outward-facing world cameras.
[0102] As can be seen from FIG. 9A, the EM sensor 604 is not located at the origin of reference 900 of the AR headset 58, but may be displaced from the origin by a displacement 902 (shown as a double arrow). Thus, the measurement made by the EM sensor 604 may not represent the attitude of the AR headset 58 relative to the origin of reference 900 because of this displacement 902. The displacement of the EM sensor 604 relative to the origin of reference 900 may be stored by the sensor fusion system 1300 in block 1344 of FIG. 13C, which is labeled "RX extrinsic properties." To adjust the measurement made by the EM sensor 604 to reflect the position of the AR headset 58 within the world reference frame of the AR system 200, in block 1344 of FIG. 13C, the RX extrinsic properties (e.g., displacement 902) may be applied to the EM sensor 604 measurement. The output of block 1346 is the pose (e.g., position and orientation) of the EM sensor 604 in the world reference frame of the AR system 200 (labeled as "RX in world frame" in FIG. 13C).
[0103] Turning to the lower portion of FIG. 13C, a similar procedure may be used to determine the pose of the EM emitter 602 in the world frame of reference of the AR system 200 (labeled as "TX in world frame" in FIG. 13C). Just as the EM sensor 604 is displaced from the fiducial origin of the AR headset 58, the EM emitter 602 may also be displaced from a fiducial origin 660, which represents the position of the totem 606 in the world frame of reference of the AR system 200. Returning to the example shown in FIG. 6, the totem 606 includes a fiducial origin 660 that is displaced from the position of the EM emitter 602 by a displacement 662. The fiducial origin 660 of the totem 606 may be selected at any suitable location, for example, the center of mass of the totem 606 or the stereocenter of the totem 606.
[0104] The displacement of the EM emitter 602 relative to the totem 606's fiducial origin 660 can be stored by the sensor fusion system 1300 in block 1354 of FIG. 13C, which is labeled "TX extrinsic properties." The totem attitude data from block 1310 (see FIG. 13B) can be used to figure out the location of the totem 606's fiducial origin 660 in the world reference frame of the AR system 200. The TX extrinsic properties (e.g., displacement 662) and the totem attitude of the fiducial origin 660 can be applied in block 1356 of FIG. 13C to adjust the EM emitter 602 to reflect the location of the totem 606 in the world reference frame of the AR system 200. In effect, the totem pose in the world frame 1310 provides the position and orientation of the fiducial origin 660 of the totem 606 in the world reference frame of the AR system 200, and the TX attribute 1354 accommodates the fact that the EM emitter 602 may be displaced from the fiducial origin 660.
[0105] The output of block 1356 is thus the pose (e.g., position and orientation) of EM emitter 602 in the world reference frame of AR system 200 (labeled as "TX in world frame" in FIG. 13C). Thus, at this point in the procedure, the predicted poses of both EM sensor 604 (RX) and EM emitter 602 (TX) are determined in the same reference frame, i.e., the world reference frame of AR system 200.
[0106] At block 1348 labeled "TX → RX resolver," a relative attitude of the EM emitter 602 with respect to the EM sensor 604 can be determined. The relative attitude may include the distance r between the EM emitter 602 and the EM sensor 604 and the angular orientation (e.g., azimuth and pitch angles) of the EM sensor 604 with respect to the EM emitter 602.
[0107] In block 1352, the relative orientation of the EM emitter 602 and the EM sensor 604 can be used to determine values of the EM field matrix 1324 that would be predicted to occur for that particular relative orientation between the EM emitter 602 and the EM sensor 604. For example, the predicted EM field matrix 1324 can be calculated from equations (1) and (2) because the distance r and the orientation angles (e.g., azimuth and pitch) are determined from the relative orientation.
[0108] Thus, the output of block 1324 in Figure 13C provides a prediction for the EM field matrix, which can be compared to the actual measured EM field matrix 1322, as described with reference to Figure 13B. If applicable, the difference between the predicted and measured EM field matrices can be used by the Kalman filter 1304 to provide an error state estimate that is used by the INS 1302 to update the totem pose in the world frame 1310.
[0109] 13C illustrates a calculation of a predicted EM field matrix 1324 for an example system in which an EM emitter 602 is located in or on a totem 606 and an EM sensor 604 is located in or on a head mounted wearable display 58. This is for purposes of illustration and not limitation. In other implementations, the EM emitter 602 may be located in or on the head mounted wearable display 58 and the EM sensor 604 may be located in or on the totem 606. In such implementations, the RX affixed properties may include a displacement of the EM sensor 604 relative to a base position of the totem 606 and the TX affixed properties may include a displacement of the EM emitter 602 relative to a base position of the head mounted display 58.
[0110] In some implementations of the sensor fusion system 1300, the totem IMU 650 operates at approximately 250 Hz. The INS 1302 integrates the IMU data while applying the error state estimate from the Kalman filter 1304 to determine the totem pose in the world frame 1310. For example, the INS 1302 may evaluate equations (5) and (6). The EM tracking system 600 may operate at a different rate than the IMU 650 (e.g., 240 Hz). Each time new data from the EM tracking system 600 is acquired, the procedure described with reference to FIG. 13B / 13C may be performed to provide the measured and predicted EM field matrices to the Kalman filter 1304. This process may be repeated as new IMU 650 or EM tracking system 600 data is acquired to provide an updated world-frame totem pose to the AR system 200 in real time. Use of the sensor fusion system 1300 may advantageously enable the AR system 200 to operate with reduced latency, improved performance (e.g., because the totem pose will be more robust and accurate), thereby providing an improved user experience. (initialization)
[0111] When the AR system 200 is started (or rebooted), the sensor fusion system 1300 may be initialized. For example, an initial totem pose may be calculated from the measured EM field matrix 1322 by the EM tracking system 600. As sensor integration and filtering proceeds, the estimated totem pose may be improved in accuracy by optimization performed by the Kalman filter 1304. In some cases, determining the initial totem pose from the measured EM field matrix 1322 may result in ambiguity regarding the direction in which the totem 606 is pointing (e.g., which hemisphere it is pointing in). In some implementations, to resolve this ambiguity, two threads for the fusion system 1300 are started in parallel, with each thread assuming that the totem 606 is pointing in one of the hemispheres. One of the threads will have the correct hemisphere and one of the threads will have the incorrect hemisphere. As the sensor fusion system 1300 is launched, the thread that assumed the incorrect hemisphere can be easily determined as the pose estimated by this thread will begin to diverge more and more from the true totem pose. At that point, the thread can be terminated and the sensor fusion system 1300 proceeds with only one thread that assumed the correct hemisphere for the initial totem pose. The technique advantageously identifies the correct hemisphere quickly and is not computationally demanding in practice. Error detection
[0112] The totem 606 is typically held in the user's hand, and therefore the distance between the totem 606 and the AR headset 58 typically does not exceed the user's arm's length, approximately. Some embodiments of the sensor fusion system 1300 implement an error protocol that checks whether the estimated distance between the totem 606 and the AR headset 58 exceeds a threshold distance (e.g., comparable to a typical human arm length). For example, the TX→RX resolver block 1348 can calculate the distance between the EM sensor 604 (typically located in the AR headset 58) and the EM emitter 602 (typically located in the totem 606), and if the distance exceeds the threshold distance, the fusion system 1300 can determine that an error is likely occurring. If an error is detected, the fusion system 1300 can take corrective action, such as, for example, reinitializing the system. Example Methods for Calculating User Input Device Pose
[0113] 14 is a flow chart illustrating an example of a method 1400 for calculating a pose of a handheld user input device / controller / totem 606 for a wearable system 200. The method 1400 may be implemented by the INS 1302 described with reference to FIGS.
[0114] At block 1410, the method 1400 accesses attitude data from an attitude sensor associated with the handheld user input device 606. The attitude sensor may include an IMU, an accelerometer, a gyroscope, a magnetometer, an optical sensor, or a combination thereof. At block 1420, the method 1400 accesses EM tracking data associated with the EM tracking system 600 associated with the handheld user input device 606. The EM tracking data may include the EM field matrix F described with reference to equation (1).
[0115] At block 1430, the method 1400 applies a data fusion technique to combine the attitude data and the EM tracking data. The data fusion technique may include a Kalman filter (or any of a variety of Kalman filters, such as, for example, an extended or unscented Kalman filter), a Markov model, a Bayesian estimator, a linear quadratic estimation, a neural network, a machine learning algorithm, etc. The data fusion technique may calculate error states and correct for bias, noise, nonlinearity, errors, etc. in the attitude data output from the attitude sensor.
[0116] In block 1440, the method 1400 determines a pose of the handheld user input device 606 in a world frame of reference associated with the environment of the AR system 200. An example of a world frame of reference is the world coordinate system 10 described with reference to Figure 8. The pose can be a 6DOF pose or a 3DOF pose.
[0117] In block 1450, the pose may be used to present virtual content to a user of the wearable system 200 or provide convenient user interaction with a handheld user input device. For example, as described with reference to FIGS. 10 and 11, the combination of the head mounted display 58, which helps determine the pose with respect to a world coordinate system, and the handheld user input device 606, which helps determine the relative location and orientation of the handheld user input device 606 with respect to the head mounted display 58, can enable the system 200 to generally determine where each component is with respect to a world reference frame, and thus the user's head pose, which can preferably be tracked with relatively low latency for presentation of augmented reality image features and interaction using movement and rotation of the handheld component. Thus, embodiments of the method 1400 can provide low latency performance and an improved user experience for users of the wearable device 200. (Additional Considerations)
[0118] Certain embodiments of sensor fusion technology are described in the context of real-time pose determination for components of a wearable display system (e.g., IMU and EM sensors for tracking head or body pose in an AR or VR context), but this is for illustration and not limitation. Embodiments of the sensor fusion technology can be used with other devices in other applications and can be applied generally to any pose determination system. For example, the sensor fusion technology can be used in a medical or surgical environment to provide improved position or orientation of a medical instrument used during a medical or surgical procedure.
[0119] Each of the processes, methods, and algorithms described herein and / or depicted in the accompanying figures may be embodied in code modules executed by one or more physical computing systems, hardware computer processors, application-specific circuits, and / or electronic hardware configured to execute specific and particular computer instructions, and may be fully or partially automated thereby. For example, the computing systems may include general-purpose computers (e.g., servers) or special-purpose computers programmed with specific computer instructions, special-purpose circuits, etc. The code modules may be compiled and linked into an executable program, installed in a dynamic link library, or written in an interpreted programming language. In some implementations, certain operations and methods may be performed by circuitry specific to a given function.
[0120] Furthermore, certain implementations of the functionality of the present disclosure may be sufficiently mathematically, computationally, or technically complex that application-specific hardware (utilizing appropriate specialized executable instructions) or one or more physical computing devices may be required to perform the functionality, for example, due to the amount or complexity of the calculations involved, or to provide results in substantially real-time. For example, a video may contain many frames, each frame may have millions of pixels, and specifically programmed computer hardware is required to process the video data to provide the desired image processing task or application in a commercially reasonable amount of time. Furthermore, pose estimation using EM tracking typically needs to be performed in real-time in an AR or VR environment, and hardware processing is required to perform the pose estimation task and provide an enjoyable user experience.
[0121] The code modules or any type of data may be stored on any type of non-transitory computer readable medium, such as physical computer storage devices, including hard drives, solid state memory, random access memory (RAM), read only memory (ROM), optical disks, volatile or non-volatile storage devices, combinations of the same, and / or the like. The methods and modules (or data) may also be transmitted as data signals (e.g., as part of a carrier wave or other analog or digital propagated signal) generated over a variety of computer readable transmission media, including wireless-based and wired / cable-based media, and may take a variety of forms (e.g., as part of a single or multiplexed analog signal, or as multiple discrete digital packets or frames). The results of the disclosed processes or process steps may be stored persistently or otherwise in any type of non-transitory tangible computer storage device, or communicated via a computer readable transmission medium.
[0122] Any process, block, state, step, or functionality in the flow diagrams described herein and / or depicted in the accompanying figures should be understood as potentially representing a code module, segment, or portion of code that includes one or more executable instructions for implementing a specific function (e.g., logical or arithmetic) or step in the process. Various processes, blocks, states, steps, or functionality can be combined, rearranged, added to, removed from, modified, or otherwise altered from the illustrative examples provided herein. In some embodiments, additional or different computing systems or code modules may perform some or all of the functionality described herein. The methods and processes described herein are also not limited to any particular sequence, and the blocks, steps, or states associated therewith can be performed in other sequences as appropriate, e.g., serially, in parallel, or in some other manner. Tasks or events can be added to or removed from the disclosed exemplary embodiments. Furthermore, the separation of various system components in the implementations described herein is for illustrative purposes and should not be understood as requiring such separation in all implementations. It should be understood that the described program components, methods, and systems may generally be integrated together in a single computer product or packaged into multiple computer products. Many implementation variations are possible.
[0123] The process, method, and system may be implemented in a network (or distributed) computing environment. Network environments include enterprise-wide computer networks, intranets, local area networks (LANs), wide area networks (WANs), personal area networks (PANs), cloud computing networks, crowdsourced computing networks, the Internet, and the World Wide Web. The network may be a wired or wireless network or any other type of communication network.
[0124] The present invention includes methods that may be implemented using subject devices. The methods may include the act of providing such a suitable device. Such provision may be implemented by an end user. In other words, the act of "providing" merely requires the end user to obtain, access, approach, locate, configure, activate, power on, or otherwise act to provide the device required in the subject method. The methods recited herein may occur in any sequence of the recited events and the recited sequence of events that is logically possible.
[0125] The systems and methods of the present disclosure each have several innovative aspects, none of which is solely responsible for or required for the desirable attributes disclosed herein. The various features and processes described above may be used independently of one another or may be combined in various ways. All possible combinations and subcombinations are intended to fall within the scope of the present disclosure. Various modifications of the implementations described in the present disclosure may be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other implementations without departing from the spirit or scope of the present disclosure. Thus, the claims are not intended to be limited to the implementations shown herein, but should be accorded the widest scope consistent with the present disclosure, the principles, and novel features disclosed herein.
[0126] Certain features described herein in the context of separate implementations can also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation can also be implemented separately in multiple implementations or in any suitable subcombination. Furthermore, although features may be described above as acting in a combination and may even be initially claimed as such, one or more features from the claimed combination may in some cases be deleted from the combination and the claimed combination may be directed to a subcombination or variation of the subcombination. No single feature or group of features is required or essential to every embodiment.
[0127] In particular, conditional statements used herein, such as "can," "could," "might," "may," "eg," and the like, are generally intended to convey that certain embodiments include certain features, elements, and / or steps, while other embodiments do not, unless specifically stated otherwise or understood otherwise within the context as used. Thus, such conditional statements are generally not intended to agree that features, elements, and / or steps are in any way required for one or more embodiments, or that one or more embodiments necessarily include logic for determining whether those features, elements, and / or steps should be included or performed in any particular embodiment, with or without authorial input or prompting. The terms "comprising," "including," "having," and the like, are synonymous and used inclusively in a non-limiting manner and do not exclude additional elements, features, acts, operations, etc. Also, the term "or" is used in its inclusive sense (and not its exclusive sense), thus, for example, when used to connect a list of elements, the term "or" means one, some, or all of the elements in the list. In addition, the articles "a," "an," and "the," as used in this application and the appended claims, unless otherwise specified, should be interpreted to mean "one or more" or "at least one." Except as specifically defined herein, all technical and scientific terms used herein should be given the broadest possible commonly understood meaning while maintaining the validity of the claims.
[0128] As used herein, a phrase referring to a list of items "at least one of" refers to any combination of those items, including single elements. As an example, "at least one of A, B, or C" is intended to cover A, B, C, A and B, A and C, B and C, and A, B, and C. Transitive phrases such as "at least one of X, Y, and Z" are generally understood differently in the context in which they are used to convey that an item, term, etc. may be at least one of X, Y, or Z, unless specifically stated otherwise. Thus, such transitive phrases are generally not intended to suggest that an embodiment requires that at least one of X, at least one of Y, and at least one of Z, respectively, be present.
[0129] Similarly, although operations may be depicted in the figures in a particular order, it should be appreciated that such operations need not be performed in the particular order depicted, or in sequential order, or that all of the depicted operations need not be performed to achieve desirable results. Additionally, the figures may diagrammatically depict one or more exemplary processes in the form of a flow chart. However, other operations not depicted may be incorporated within the diagrammatically depicted exemplary methods and processes. For example, one or more additional operations may be performed before, after, simultaneously with, or during any of the depicted operations. Additionally, operations may be rearranged or reordered in other implementations. In some circumstances, multitasking and parallel processing may be advantageous. Additionally, the separation of various system components in the implementations described above should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products. Additionally, other implementations are within the scope of the following claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve desirable results.
Claims
1. A wearable system, comprising: A head-mounted display; a handheld user input device comprising an inertial measurement unit (IMU), the IMU configured to generate IMU data comprising one or more of accelerometer data or gyroscope data; one or more EM emitters configured to generate an EM field; one or more EM sensors configured to sense the EM field; one or more computer processors, determining an estimated attitude of the one or more EM sensors relative to the one or more EM emitters based at least on the EM field sensed by the one or more EM sensors; accessing the IMU data; applying a data fusion algorithm to the IMU data and the estimated pose to generate a predicted pose of the handheld user input device within a world reference frame associated with the wearable system; generating an error state based at least on a difference between the estimated pose and the predicted pose generated by application of the data fusion algorithm; updating an attitude of the handheld user input device based on the generated error state to correct for drift or other attitude inaccuracies of the handheld user input device; one or more computer processors configured to A wearable system comprising:
2. To calculate the predicted pose, the one or more computer processors: Calculating an estimated EM emitter pose in the world reference frame; Calculating an estimated EM sensor pose in the world reference frame; Calculating a relative attitude between the estimated EM emitter attitude in the world frame of reference and the estimated EM sensor attitude in the world frame of reference; The wearable system of claim 1 , programmed to:
3. Calculating the estimated EM emitter pose in the world reference frame includes: accessing a pose of the handheld user input device within the world reference frame; applying an EM transmitter associated property configured to adjust a position of the EM emitter relative to a fiducial position of the handheld user input device; The wearable system of claim 2 .
4. The wearable system of claim 3 , wherein the EM transmitter associated property comprises a displacement between a position of the EM emitter and the base position of the handheld user input device.
5. The one or more computer processors: presenting virtual content to a user of the wearable system via the head mounted display; or enabling interaction of the wearable system with an environment based at least in part on the movement or rotation of the handheld user input device; The wearable system of claim 1 , further configured to:
6. The wearable system of claim 1 , wherein the error state is calculated based at least on determining that a distance between the EM emitter and the EM sensor exceeds a threshold distance.
7. 1. A computerized method implemented by a computing system, the computing system comprising one or more hardware computer processors and one or more non-transitory computer readable storage devices storing software instructions, the software instructions being executable by the computing system to implement the computerized method, the computerized method comprising: determining an estimated attitude of an EM sensor of a head mounted display system relative to an EM emitter of the head mounted display system based at least on an EM field sensed by the EM sensor of the head mounted display system; accessing IMU data from a handheld user input device, the IMU data comprising one or more of accelerometer data or gyroscope data; applying a data fusion algorithm to the IMU data and the estimated pose to generate a predicted pose of the handheld user input device within a world frame associated with the head mounted display system; generating an error state based at least on a difference between the estimated pose and the predicted pose generated by application of the data fusion algorithm; updating an attitude of the handheld user input device based on the generated error state to correct for drift or other attitude inaccuracies of the handheld user input device; The computerized method includes:
Citation Information
Patent Citations
Image processing apparatus, image processing method, computer program and storage medium
JP2018128739A
Systems and methods for augmented reality
JP2018511122A
Generating and Displaying a Computer Generated Image on a Future Pose of a Real World Object
US20180108179A1
Correcting field distortion in electromagnetic position tracking systems
US20190086482A1
