Methods resolving the elevation of a tracked personnel or assets

US10401168B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10401168-B2
Application numberUS-201715591946-A
CountryUS
Kind codeB2
Filing dateMay 10, 2017
Priority dateJun 12, 2012
Publication dateSep 3, 2019
Grant dateSep 3, 2019

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Methods and systems are described for determining the elevation of tracked personnel or assets (trackees) that can take input from mounted sensors on each trackee (including barometric, inertial, magnetometer, radio frequency ranging and signal strength, light and GPS sensors), external constraints (including ranging constraints, feature constraints, and user corrections), and terrain elevation data. An example implementation of this method for determining elevation of persons on foot is described. But this method is not limited to computing elevation of personnel or to on foot movements.

First claim

Opening claim text (preview).

What is claimed: 1. A method for updating a building elevation model, comprising: obtaining sensor data, including location data and inertial sensor data, from a tracked computing device among a plurality of tracked computing devices; using the sensor data to generate a path of the tracked device; using the sensor data to estimate elevation of the tracked device; segmenting the path; generating a node at an endpoint of each path segment; classifying each node based on the node's location and the estimated elevation; generating one or more elevation constraints for each node, wherein the elevation constraints are based on the node's classification; resolving the elevation constraints to refine each node's location and estimated elevation; and updating the building elevation model, including one or more floor heights, using each node's refined location and estimated elevation. 2. The method of claim 1 , wherein the sensor data further includes pressure data, and further comprising applying inertial aiding to remove pressure fluctuations from the pressure data. 3. The method of claim 2 , wherein applying inertial aiding comprises: transforming the inertial sensor data to compensate for tilt; filtering the inertial sensor data; integrating the tilt-compensated data and filtered data to calculate vertical velocity; determining an elevation change using the vertical velocity; and updating the pressure data based on the elevation change. 4. The method of claim 2 , further comprising: determining a stationary pressure reference to remove local pressure variation from the pressure data. 5. The method of claim 1 , further comprising: obtaining local terrain elevation data along the path to determine a local terrain elevation; determining an elevation offset between the local terrain elevation and the estimated elevation; and updating the estimated elevation with the elevation offset. 6. The method of claim 1 , wherein segmenting the path further comprises: parsing the path into points, based on ascending time; determining whether a point on the path is stable relative to a consecutive point on the path using a function of the estimated elevation; and grouping consecutive stable points into a path segment. 7. The method of claim 1 , wherein classifying each node comprises: determining whether each node is located indoors, outdoors, or underground. 8. The method of claim 7 , further comprising: associating indoor nodes with a floor in the building elevation model. 9. The method of claim 1 , wherein an elevation constraint enforces a minimum and a maximum allowed adjustment to each node's estimated elevation. 10. The method of claim 1 , wherein resolving the elevation constraints further comprises: iterating through each of the elevation constraints for each node along a path segment to determine node elevations and floor heights for each node that satisfy corresponding elevation constraint. 11. The method of claim 1 , further comprising: updating the building elevation model using the sensor data obtained from each tracked computing device among the plurality of tracked computing devices. 12. The method of claim 1 , wherein the sensor data does not include pressure data. 13. The method of claim 1 , wherein segmenting the path is based on one or more of time, the estimated elevation, and the location data. 14. A computing system for updating a building elevation model, the computing system comprising: a processor; a memory communicatively coupled to the processor, the memory bearing instructions that, when executed on the processor, cause the computing system to at least: obtain sensor data, including location data and inertial sensor data, from a tracked computing device among a plurality of tracked computing devices; use the sensor data to generate a path of the tracked device; use the sensor data to estimate elevation of the tracked device; segment the path; generate a node at an endpoint of each path segment; classify each node based on the node's location and the estimated elevation; generate one or more elevation constraints for each node, wherein the elevation constraints are based on the node's classification; resolve the elevation constraints to refine each node's location and estimated elevation; and update the building elevation model, including one or more floor heights, using each node's refined location and estimated elevation. 15. The system of claim 14 , wherein the sensor data includes pressure data, and wherein the instructions, when executed on the processor, further cause the computing system to apply inertial aiding to remove pressure fluctuations from the pressure data. 16. The system of claim 15 , wherein the instructions that apply inertial aiding comprise instructions, when executed on the processor, that cause the computing system to: transform the inertial sensor data to compensate for tilt; filter the inertial sensor data; integrate the tilt-compensated data and filtered data to calculate vertical velocity; determine an elevation change using the vertical velocity; and update the pressure data based on the elevation change. 17. The system of claim 15 , wherein the instructions, when executed on the processor, further cause the computing system to at least: determine a stationary pressure reference to remove local pressure variation from the pressure data. 18. The system of claim 14 , wherein the instructions, when executed on the processor, further cause the computing system to at least: obtain local terrain elevation data along the path to determine a local terrain elevation; determine an elevation offset between the local terrain elevation and the estimated elevation; and update the estimated elevation with the elevation offset. 19. The system of claim 14 , wherein the instructions to segment the path, when executed on the processor, further cause the computing system to at least: parse the path into points, based on ascending time; determine whether a point on the path is stable relative to a consecutive point on the path using a function of the estimated elevation; and group consecutive stable points into a path segment. 20. The system of claim 14 , wherein the instructions to classify each node, when executed on the processor, further cause the computing system to at least: determine whether each node is located indoors, outdoors, or underground. 21. The system of claim 20 , wherein the instructions, when executed on the processor, further cause the computing system to: associate indoor nodes with a floor in the building elevation model. 22. The system of claim 14 , wherein an elevation constraint enforces a minimum and a maximum allowed adjustment to the node's estimated elevation. 23. The system of claim 14 , wherein the instructions to resolve the elevation constraints, when executed on the processor, further cause the computing system to at least: iterate through the elevation constraints for each node along a path segment to determine node elevations and floor heights for each node that satisfy the corresponding elevation constraint; and adjust node elevation and/or one or more floor heights in the building model. 24. The system of claim 14 , wherein the instructions, when executed on the processor, further cause the computing system to at least: update the building elevation model using the sensor data obtained from

Assignees

Inventors

Classifications

  • Measuring height; Measuring distances transverse to line of sight; Levelling between separated points; Surveyors' levels (G01C3/20, G01C3/30 take precedence) · CPC title

  • specially adapted for indoor navigation · CPC title

  • G01C5/06Primary

    by using barometric means · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10401168B2 cover?
Methods and systems are described for determining the elevation of tracked personnel or assets (trackees) that can take input from mounted sensors on each trackee (including barometric, inertial, magnetometer, radio frequency ranging and signal strength, light and GPS sensors), external constraints (including ranging constraints, feature constraints, and user corrections), and terrain elevation…
Who is the assignee on this patent?
Trx Systems Inc
What technology area does this patent fall under?
Primary CPC classification G01C5/06. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Sep 03 2019 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 7 related publications on this page (citations in our corpus or others sharing the same primary CPC).