Emulating a vehicle-communications-center data request to obtain data from a system or subsystem onboard the vehicle
US-11257379-B2 · Feb 22, 2022 · US
US12470404B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12470404-B2 |
| Application number | US-202318465751-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 12, 2023 |
| Priority date | Jul 31, 2023 |
| Publication date | Nov 11, 2025 |
| Grant date | Nov 11, 2025 |
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.
Techniques are provided for facilitating less expensive and more rapid implement and modification of processes, e.g., communications processes, performed in a vehicle, e.g., a commercial aircraft, by implementing those functions on a non-certified computer. This is because the non-certified computer and the functions which it performs do not require certification by a government entity. Optionally, the non-certified computer is communicatively coupled to a communications management unit which requires certification from the government entity. Optionally, the non-certified computer may be an electronic flight bag for commercial aviation applications.
Opening claim text (preview).
What is claimed is: 1 . A method for processing uplink data or downlink data, the method comprising: receiving, at a non-certified computer configured to be mounted in a vehicle and from a communications management unit (CMU) configured to be mounted in the vehicle and to route data between components of the vehicle, and that requires certification by a government entity, first data comprising either (a) a message of a message type or (b) (i) information configured to form or extracted from the message of the message type and (ii) a message type identifier, wherein the message type means a type of message of a set of message types, wherein the non-certified computer does not require the certification by the government entity; determining, with the non-certified computer, whether the message type identifier was received; determining, with the non-certified computer, that the message type identifier was not received, then identifying the message type; determining, with the non-certified computer, whether the first data includes data configured to be transmitted off the vehicle; determining, with the non-certified computer, that the first data includes data configured to be transmitted off the vehicle, then, using the message type identifier, at least one of encoding, encrypting, and compressing at least a portion of the first data to create the downlink data; transmitting the downlink data from the non-certified computer to the CMU; determining, with the non-certified computer, that the first data does not include data configured to be transmitted off the vehicle, then, using the message type identifier, at least one of decoding, decrypting, and decompressing the at least a portion of the first data to create the uplink data; and transmitting the uplink data from the non-certified computer to the CMU. 2 . The method of claim 1 , wherein the set of message types is specified by an industry standard or an Original Equipment Manufacturer. 3 . The method of claim 1 , wherein identifying the message type comprises identifying the message type using at least one of: a structure of a message in the first data and parameters in the first data. 4 . The method of claim 1 , wherein the at least one of encoding, encrypting, and compressing the at least a portion of the first data comprises encoding the at least a portion of the first data to create a downlink message. 5 . The method of claim 1 , wherein the vehicle comprises an aircraft. 6 . The method of claim 1 , wherein the non-certified computer is configured to transmit and receive respectively transmitted data and received data using a wireless technique. 7 . A non-transitory computer readable medium storing a program causing at least one processor of a non-certified computer to execute a process for processing uplink data or downlink data, the process comprising: receiving, at the non-certified computer configured to be mounted in a vehicle and from a communications management unit (CMU) configured to be mounted in the vehicle, configured to route data between components of the vehicle, and that requires certification by a government entity, first data comprising either (a) a message of a message type or (b) (i) information configured to form or extracted from the message of the message type and (ii) a message type identifier, wherein the message type means a type of message of a set of message types, wherein the non-certified computer does not requires the certification by the government entity; determining, with the non-certified computer, whether the message type identifier was received; determining, with the non-certified computer, that the message type identifier was not received, then identifying the message type; determining, with the non-certified computer, whether the first data includes data configured to be transmitted off the vehicle; determining, with the non-certified computer, that the first data includes data configured to be transmitted off the vehicle, then, using the message type identifier, at least one of encoding, encrypting, and compressing at least a portion of the first data to create the downlink data; causing transmission of the downlink data from the non-certified computer to the CMU; determining, with the non-certified computer, that the first data does not include data configured to be transmitted off the vehicle, then, using the message type identifier, at least one of decoding, decrypting, and decompressing the at least a portion of the first data to create the uplink data; and causing transmission of the uplink data from the non-certified computer to the CMU. 8 . The non-transitory computer readable medium of claim 7 , wherein the set of message types is specified by an industry standard or an Original Equipment Manufacturer. 9 . The non-transitory computer readable medium of claim 7 , wherein identifying the message type comprises identifying the message type using at least one of: a structure of a message in the first data and parameters in the first data. 10 . The non-transitory computer readable medium of claim 7 , wherein the at least one of encoding, encrypting, and compressing the at least a portion of the first data comprises encoding the at least a portion of the first data to create a downlink message. 11 . The non-transitory computer readable medium of claim 7 , wherein the vehicle comprises an aircraft. 12 . An apparatus for processing uplink data or downlink data, the apparatus comprising; a non-certified computer comprising at least one memory circuit communicatively coupled to at least one processor circuit, wherein the non-certified computer does not require certification by a government entity, wherein the non-certified computer is configured to be communicatively coupled to a communications management unit (CMU) circuitry that is configured to be mounted in a vehicle, configured to route data between components of the vehicle, and requires the certification by the government entity; wherein the non-certified computer is configured to be mounted in the vehicle, and is further configured to: receive, on the non-certified computer in a vehicle and from the CMU circuitry, first data comprising either (a) a message of a message type or (b) (i) information configured to form or extracted from the message of the message type and (ii) a message type identifier, wherein the message type means a type of message of a set of message types; determine, with the non-certified computer, whether the message type identifier was received; determine, with the non-certified computer, that the message type identifier was not received, then identifying the message type; determine, with the non-certified computer, whether the first data includes data configured to be transmitted off the vehicle; determine, with the non-certified computer, that the first data includes data configured to be transmitted off the vehicle, then, using the message type identifier, at least one of encode, encrypt, and compress at least a portion of the first data to create the downlink data; transmit the downlink data from the non-certified computer to the CMU circuitry; determine, with the non-certified computer, that the first data does not include data configured to be transmitted off the vehicle, then, using the message type identifier, at least one of decode, decrypt, and decompress the at least a portion of the first data to create the uplink data; and transmit the uplink data from the non-certified computer to the CMU circuitry. 13 . The apparatus of claim 12 , wherein the set of message types is specified by an industry standard or an Original Equipment Ma
involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements (network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.