Location-based services onboard aircraft
US-9380428-B1 · Jun 28, 2016 · US
US12073665B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12073665-B2 |
| Application number | US-202318123188-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 17, 2023 |
| Priority date | Sep 20, 2019 |
| Publication date | Aug 27, 2024 |
| Grant date | Aug 27, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A vehicle that includes a policy manager circuit, an endpoint, and a vehicle data interface. The policy manager circuit interprets a data collection policy including a trigger condition and a trigger evaluation data identifier. The endpoint captures a trigger evaluation data stream in response to the trigger evaluation data identifier and the trigger condition. The vehicle data interface receives the trigger evaluation data stream.
Opening claim text (preview).
What is claimed is: 1. A vehicle comprising: a policy manager circuit configured to interpret a data collection policy including: a vehicle data identifier, a trigger configured to define a trigger condition, and a plurality of trigger conditions having a plurality of trigger types, the plurality of trigger types including at least two of a signal trigger, a vehicle status trigger, a timing trigger, a schedule trigger, a geofence trigger, an error trigger, an environment trigger, or a user input trigger; and a trigger evaluation circuit configured to: determine a trigger event occurrence in response to a trigger condition and trigger evaluation data and based on a first portion of the plurality of trigger conditions, the first portion including a first trigger having a first trigger type and a second trigger having a second trigger type, determine a trigger event termination based on a second portion of the plurality of trigger conditions, wherein the second portion includes a first trigger having a first trigger type and a second trigger having a second trigger type, determine a data capture window in response to the trigger event occurrence, trigger event termination, and the data collection policy, and capture identified vehicle data in response to the data capture window and the vehicle data identifier. 2. The vehicle of claim 1 , wherein the trigger evaluation circuit determines the trigger event occurrence by evaluating the trigger evaluation data using the trigger condition, wherein the trigger condition defines a relationship with a present value that may be satisfied or unsatisfied by the trigger evaluation data. 3. The vehicle of claim 1 , wherein the trigger evaluation data includes at least one of a vehicle state, a vehicle status, a vehicle operating mode, or a vehicle discrete event. 4. The vehicle of claim 1 , wherein the identified vehicle data is generated by the vehicle before the trigger event occurrence and stored using a rotating buffer circuit. 5. The vehicle of claim 1 , wherein the plurality of trigger conditions corresponds to one of a plurality of trigger evaluation data values. 6. The vehicle of claim 5 , wherein the trigger evaluation circuit determines the trigger event occurrence in response to at least two of the plurality of trigger conditions. 7. The vehicle of claim 5 , wherein: the plurality of trigger conditions includes a trigger condition that corresponds to one of the plurality of trigger evaluation data values; and the trigger evaluation circuit determines the trigger event occurrence in response to the trigger condition. 8. The vehicle of claim 5 , wherein the plurality of trigger evaluation data values correspond to a plurality of data types, including at least two of a controller area network (CAN) message, a CAN signal, an ethernet packet, a vehicle location, a vehicle status, and a diagnostic trouble code. 9. The vehicle of claim 5 , wherein the plurality of trigger evaluation data values correspond to a plurality of data types, including at least one of a controller area network (CAN) message, a CAN signal, an ethernet packet, a vehicle location, a vehicle status, and a diagnostic trouble code. 10. The vehicle of claim 1 , wherein the trigger evaluation data includes a virtual sensor value derived from a plurality of vehicle data values. 11. The vehicle of claim 1 , wherein the data capture window terminates after a delay following the trigger event termination in response to the data collection policy. 12. The vehicle of claim 1 , wherein the data capture window terminates based at least in part on one or more trigger conditions.
involving control of end-device applications over a network · CPC title
Diagnosing performance data (testing of vehicles G01M17/00; testing of electrical installation on vehicles G01R31/005) · CPC title
Indicating performance data, e.g. occurrence of a malfunction · CPC title
communicating information to a remotely located station (transmission systems for measured values G08C) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.