USOO9141830B2
`
`(12) United States Patent
`Uczekaj et al.
`
`(10) Patent No.:
`(45) Date of Patent:
`
`US 9,141,830 B2
`Sep. 22, 2015
`
`(54) AVIONICS GATEWAY INTERFACE, SYSTEMS
`AND METHODS
`
`H04L 29/06
`H04L 29/08
`
`(2006.01)
`(2006.01)
`
`(75) Inventors: John Uczekaj, Albuquerque, NM (US);
`Brad Hayden, Albuquerque, NM (US);
`Peter Lyons, Albuquerque, NM (US);
`Constantinos Kyriakos, Indian Harbour
`Beach, FL (US); Joseph Lyle,
`Albuquerque, NM (US)
`
`(73) Assignee: ASPEN AVIONICS, INC.,
`Albuquerque, NM (US)
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`
`(*) Notice:
`
`(21) Appl. No.:
`(22) PCT Filed:
`
`14/119,966
`Jul. 23, 2012
`
`PCT/US2012/047874
`
`(86). PCT No.:
`S371 (c)(1),
`Jul. 30, 2014
`(2), (4) Date:
`e a V8
`s
`(87) PCT Pub. No.: WO2013/013243
`PCT Pub. Date: Jan. 24, 2013
`
`(65)
`
`Prior Publication Data
`US 2015/OO.19862 A1
`Jan. 15, 2015
`
`Related U.S. Application Data
`(60) Provisional application No. 61/674,340, filed on Jul.
`21, 2012, provisional application No. 61/510,800,
`filed on Jul 22, 2011.
`(51) Int. Cl
`Goof 2I/00
`G06F2L/7
`
`(2013.01)
`(2013.01)
`
`
`
`(Continued)
`
`(52) U.S. Cl.
`CPC .............. G06F 2 1/71 (2013.01); G06F 21/602
`(2013.01); H04B 7/18506 (2013.01); H04L
`63/02 (2013.01); H04L 63/0884 (2013.01);
`H04L 63/10 (2013.01); H04L 67/12 (2013.01)
`(58) Field of Classification Search
`CPC ....... G06F 21/10; G06F 21/105; G06F 21/44;
`G06F 21/57; G06F 21/70
`See application file for complete search history.
`References Cited
`U.S. PATENT DOCUMENTS
`
`(56)
`
`2/1987 Cline et al.
`4,642,775 A
`2/1991 Cummings
`4,994,974 A
`5,270,931 A 12/1993 Appleford
`(Continued)
`OTHER PUBLICATIONS
`
`Wikipedia, Aircraft Communications Addressing and Reporting Sys
`tem, http://en.wikipedia.org/wiki/ Aircraft Communications Ad
`dressing and Reporting Syst (accessed Dec. 17, 2013).
`(Continued)
`Primary Examiner — Edward Zee
`(74) Attorney, Agent, or Firm — Kutak Rock LLP. Bryan P.
`Stanley
`ABSTRACT
`(57)
`Systems and methods are provided for FAA-certified avionics
`devices to safely interface with non-certified mobile telecom
`munications devices before, during, and after flight. Data
`transmitted to the certified devices do not affect functionality
`of the certified device unless and until a user acknowledges
`and/or confirms the data on the certified device. Thus, the
`integrity of the certified device is maintained.
`10 Claims, 15 Drawing Sheets
`
`Portable Electronic
`Device
`Uncertified
`
`2
`:
`
`w Certified
`
`EFoooo 1500
`Navigation and
`Myn Communication
`
`
`
`fixiosafel
`
`ie: 8&srs
`
`agwaa
`
`Gateway hardware X
`
`88ss Ayck;3S
`catchael at
`takes
`
`DJI-1010
`IPR2023-01107
`
`

`

`US 9,141,830 B2
`Page 2
`
`(51) Int. Cl.
`H04B 7/85
`G06F2L/60
`
`(2006.01)
`(2013.01)
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`7, 1998 Coleman
`5,786,995 A
`6,154,637 A 1 1/2000 Wright et al.
`6,167.239 A 12/2000 Wright et al.
`6,401,013 B1* 6/2002 McElreath ........................ TO1/3
`6,597,294 B1
`7/2003 Ariens
`6,803,860 B1
`10/2004 Langner et al.
`6,816,728 B2 11/2004 Igloiet al.
`6,868,320 B1
`3, 2005 Burch
`6,915, 189 B2
`7/2005 Igloi et al.
`6,967,830 B2 11/2005 Cooper et al.
`7,131,136 B2 10/2006 Monroe
`7,356,389 B2
`4/2008 Holstet al.
`7,420,476 B2
`9/2008 Stiffler
`7,421,319 B2
`9, 2008 Stefani
`7,437,221 B2 10/2008 Hardman et al.
`73676, R 1939. sham
`7.620374 B2 11/2009 Ziarno et al.
`7,684,904 B2
`3/2010 Wainwright et al.
`7,689,327 B2
`3/2010 Loda
`7,706,967 B2
`4/2010 Knockeart et al.
`
`8/2010 Lusardi et al.
`7,769,501 B2
`33.9 Eckert et al
`6. B2
`3/2003 Kanno et al.
`2003, OO60952 A1
`8, 2003 Kawakita
`2003. O152145 A1
`7/2004 Rogerson et al.
`2004/O1394.67 A1
`2/2005 Brinkley et al.
`2005/0026609 A1
`2005/0228558 A1 10, 2005 Valette et al.
`2006.00891OO A1
`4/2006 Patenaude et al.
`2007/00276.16 A1
`2/2007 Masson
`2007/0118274 A1
`5/2007 Orebaugh
`2007/O130599 A1
`6/2007 Monroe
`2008, 0208399 A1
`8, 2008 Pham
`2009/0041041 A1
`2/2009 True et al.
`2009 OO58682 A1
`3, 2009 True
`2009.01675.24 A1
`7/2009 Chesnutt et al.
`2009,0192659 A1
`7/2009 Beebe et al.
`2010, 0100887 A1
`4/2010 Beltrand
`2010, O152924 A1
`6, 2010 Pandit et al.
`2010/0287545 A1 11, 2010 Corbefin
`2013/0305391 A1* 11/2013 Haukom et al. ................ 726/29
`
`OTHER PUBLICATIONS
`Teledyne Controls, EFB Software Applications, brochure.http://
`www.teledynecontrols.com/ (Accessed Dec. 17, 2013).
`Teledyne Controls, NFS Network File Server, brochure, http://www.
`teledynecontrols.com/ (Accessed Dec. 17, 2013).
`
`* cited by examiner
`
`

`

`Sheet 1 of 15
`Sheet 1 of 15
`
`US 9,141,830 B2
`US 9,141,830 B2
`
`Figure1
`
`Sewloniun
`
`U.S. Patent
`U.S. Patent
`
`Sep. 22, 2015
`Sep. 22, 2015
`
`
`
`
`
`sennenceneoe
`
`
`
`
`
`De Mobile&
`
`ays
`
`ghtEien§
`
`F
`
`Lassalast
`
`drond}
`ayArRK
`s t
`fas
`:
`
`

`

`U.S. Patent
`U.S. Patent
`
`Sep. 22, 2015
`
`Sheet 2 of 15
`
`US 9,141,830 B2
`US 9,141,830 B2
`
`
`
`
`
`ISyGeY»GEHOU]»SQBVISGG‘LIBELJOLINTHOAY«
`
`SuneyeGumoda;usa,«
`
`WOHNOGNS
`LUDAeyesKEEDUR
`
`slesxe“_@)Pua
`
`SNIBISLOHLTBILUIBYY»
`
`
`
`@anbaussojonasul
`
`Zaunbi-
`
`
`
`
`
`SIQeHOLUODsieBuesseddecry«
`
`
`
`punci8ucsidosdLAASIBOIUTHULUG’)»
`
`
`
`WGLUODsaHuesse
`
`HHCRHRAGURIS
`
`AS
`
`
`
`SUDCUS»juswuebeueeseqp1GeyueYS«
`
`
`
`WUBIN«auibue©1SNLJOHUOHY»
`
`esugugermjuedjubapeay»
`
`
`Sreotunulion‘'SOIDRIGUNL
`
`SGUNESIOIGAUOYMGIAGH»
`
`
`
`1614Buting
`
`
`
`
`
`
`
`
`
`Buiuueidsonsiho;pue
`
`
`
`BaGumuosdnjos.
`
`uedwba¢eine
`
`SOLENESIOURI:
`
`
`
`daidasndpjb
`
`

`

`U.S. Patent
`U.S. Patent
`
`Sep. 22, 2015
`Sep. 22, 2015
`
`Sheet 3 of 15
`Sheet 3 of 15
`
`US 9,141,830 B2
`US 9,141,830 B2
`
`
`
`
`
`- ****§ .*.
`
`&
`
`wyBuyserpy/yb
`
`}
`
`4wopeg
`
`
`
`SugedyARiagPug,
`
`
`
`
`

`

`U.S. Patent
`U.S. Patent
`
`Sep. 22, 2015
`Sep. 22, 2015
`
`Sheet 4 of 15
`Sheet 4 of 15
`
`US 9,141,830 B2
`US 9,141,830 B2
`
`
`
`BORO4 somqpenpioySurg
`
`fora
`
`pyaunbi4
`
`
`
`
`

`

`U.S. Patent
`
`Sep. 22, 2015
`
`Sheet 5 of 15
`
`US 9,141,830 B2
`
`
`
`auoYJSUMMIPULAPOMIAN[120OF
`
`Se
`
`
`
`sajepdnaiemiyos
`
`suoud!/podt
`
`6cONTYV
`
`
`
`SOIUOIAYJ8YJO
`
`4073G43
`
`<>
`
`SdqOOT/OT
`
`<<
`
`
`(IGdS20SZ)NEOOlpny[eHsIq<
`(OdING7/OALZ)UyaUL,:——>podsuctgl/dOd!addy
`
`
`(jouedolpne)INQsu<——$$$$___________—_H+4—
`dW/93SESN—7y{
`WOEMGO|
`
`{LUTFPeessdgogr
`
`Tepeony”
`
`ganol
`
`(X}WEPp)TSSBID-
`
`eneiait
`
`WUIOSSA0VLTA
`
`
`
`SGPTTTO8:
`
`ZHOY'T
`
`
`
`
`
`Butddoy‘balyZHO¢Ze
`
`
`
`
`
`
`

`

`U.S. Patent
`U.S. Patent
`
`Sep. 22, 2015
`
`Sheet 6 of 15
`
`US 9,141,830 B2
`US 9,141,830 B2
`
`Cater
`
`UO
`
`aury
`
`selQAly
`
`qeusiqy
`
`2x01
`
`ayddy
`
`2xMUO
`
`astds
`
`ulead
`
`
`
`
`
`
`
`OSAS
`
`XTSONV'T
`
`GREPdTCXBS0-Z73,
`
`ssarday
`
`
`
`JOWAUIAWOa[BuigymKemayeg
`
`
`
`“OLD$,u9035
`
`JNSpupapy
`
`0OFGS
`
`anPOH paeoqrarpoyy
`
`GGT.apownlVddGSHorev
`
`
`
`
`
`
`
`
`
`SUISNOP]ABMOIBLD)Y}UOS10}NIUUOD0}pUodsoIIONPIBOgIOYJOUOY}OpIsinosuOT|OSUUIO’7),,
`
`
`
`Aemayer)uodsy
`
`GAEL
`
`
`
`DCASIGABZFE
`
`OLE
`
`00T9DA
`
`
`
`Ayddaysamog
`
`9ainbi-4
`9 eun64-)
`
`
`
`JO]IOUUODSSOUIBYSULIIMIOSIO}IOUUOD[PNPTAIPUTsx
`
`
`
`
`
`
`
`

`

`U.S. Patent
`U.S. Patent
`
`Sep. 22, 2015
`Sep. 22, 2015
`
`Sheet 7 Of 15
`Sheet 7 of 15
`
`US 9,141,830 B2
`US 9,141,830 B2
`
`“LEGS
`
`att
`
`3:3
`43
`
`*********3
`LPNs
`
`RUE
`
`RELYAIRS
`
`Rei
`
`Ags
`
`“LAO
`
`LETS
`
`Seis
`
`Aig
`
`3.3$3
`A383
`
`
`
`HOGLOANSJOUIOURY
`
`fee
`ee
`3k
`3
`
`183
`
`3
`
`THSHASPe)
`
`SEUNGRSHPOSTAL
`
`
`
`GOCENWISIS+
`
`
`
`NEQESILENOPod+
`
`4G
`
`! ###3
`Lins
`
`yoursyyyO2gSN
`
`:
`
`;
`x
`
`§§§§
`4SH
`
`Jue
`
`THan
`
`
`
`
`
`Zeinbi
`
`
`
`
`
`

`

`U.S. Patent
`U.S. Patent
`
`Sep. 22, 2015
`
`Sheet 8 of 15
`
`US 9,141,830 B2
`US 9,141,830 B2
`
`
`
`JOWALIAHO¢YMAemayeg
`
`PURO
`
`aUHOD
`
`WHOD,
`
`
`astvas
`
`eeOIPNG
`
`
`;OIA
`
`
`6crONTAY0idsAyddegamog
`TATOOSUBL|joureg
`
`90HpdICXH@SN-20
`
`ssadda
`
`Gosoe
`
`[509
`
`OSTINS:TEA
`
`emmeqiy
`
`oOOVIS
`
`
`
`00T9DdDQASOGARTTT
`
`OUGAEE
`
`
`
`
`
`psvoqsaipoyyAemaeyuadsy
`
`
`
`
`
`SuISNoP]ABAMDTCL)OY]UOS10JIIUTIOD0]puodsadIODPIBOGIOYIOU!OY}OpIsinosUOMIOUUO-),
`
`
`
`
`
`
`
`gainbi-
`9 eun614
`
`
`
`
`
`
`
`JO]IOUUOSSSIUILYSUTIMJOSIOJOAUUOS[ENPTAIPUTy«
`
`

`

`U.S. Patent
`U.S. Patent
`
`Sep. 22, 2015
`Sep. 22, 2015
`
`Sheet 9 of 15
`Sheet 9 of 15
`
`US 9,141,830 B2
`US 9,141,830 B2
`
`
`
`"ABNpur‘CHa
`
`6aunbi-
`
`
`
`iybi4
`
`uvydWYSIPT ddyBuruueld
`
`
`‘JIAIPIIGQOWSso1sepaziuosyoUAS
`
`

`

`U.S. Patent
`U.S. Patent
`
`Sep. 22, 2015
`Sep. 22, 2015
`
`Sheet 10 of 15
`Sheet 10 of 15
`
`US 9,141,830 B2
`US 9,141,830 B2
`
`einaleaalteaaetteteatlag
`
`
`%
`- XY
`z
`---------------------
`
`f
`pinataating fe
`8
`
`---------------------
`
`peemenseeacenencettn,
`w
`
`.
`M
`
`
`
`
`
` AppiasuesNavUpdateRequest
`
`
`GatewayRespondstoRequest
`
`EFOCammumicateswfMav
`pisces
`Seeee
`
`
`spardisteFFD
`
`he
`
`
`
`eicehce
`
`eh
`
`
`
`eicehce
`
`sic
`a
`
`
`
`
`
`i
`seFie>
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` App
`
`issuesMavStatusRequest
`
`
`s
`
`
`
`dsteRequest
`
`is
`
`gsRequest
`State
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`SatewayRespondstoRequest
`
`
`
`
` songstaFED3
`EFDCommunicateswfNaw
`
`Figure10
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`&
`
`
`
`
`
`
`
`
`
`
`:
`
`RayRe
`
`

`

`U.S. Patent
`U.S. Patent
`
`Sep. 22, 2015
`Sep. 22, 2015
`
`Sheet 11 of 15
`Sheet 11 of 15
`
`US 9,141,830 B2
`US 9,141,830 B2
`
`
`
`Figure11
`
`
`
`FlightControl/RadioTuningApp
`
`

`

`US 9,141,830 B2
`US 9,141,830 B2
`
`ZLounbi+
`
`U.S. Patent
`
`Sep. 22, 2015
`
`Sheet 12 of 15
`Sheet 12 of 15
`
`ABD/74SREHERURIS4g
`
`
`
`
`
`sane
`
`ASN(iSeyPIMINED49
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`poanbsyoyspucdsayAemaywes
`
`
`
`santanaaaaanaaanaaaaaaysrrzzzzzz
`
`Sep. 22, 2015 Wanbey
`U.S. Patent *~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
`
`
`
`
`
`
`
`
`
`“Nitaaeeteieteetcateaaetnaaelaateateatauteatelaetcatetatetalteuteatelaatatateattataateatelaatatateattaltaateattaataatetaitataatetatlaetctateattatauteattaatctatetattataatetattaatatateattl.teeetcateeetateaaeateelcateaeaateatelaelcateaealtelaelcateatealataaelaateatetatauteatelaelaatetatetaltauteatetaelcatetatetaltauteatetaelcatetattaltauteatetaetatatetatetattaate
`
`
`
`
`
`
`agendyAsanbargsansaddyPotwanbeysnesAsuanbaysanssiddy
`
`
`
`yserheysepsisyanbeysnmis
`
`“vaata'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'dh'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'n'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'anananaan'a'aannanananaanaanaannaaanannan'an'aaaa's
`
`
`
`
`
`eierharecretercreceepecan
`crehee
`
`
`Nvata'a'a'a'a'a'a'a'a'a'a'a'a'a'a'n'a'de'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'a'an'an'an'an'aaaan'an'ananan'aaan'a
`
`oo
`
`4301spucdsay
`
`Sees
`
`
`

`

`U.S. Patent
`U.S. Patent
`
`Sep. 22, 2015
`Sep. 22, 2015
`
`Sheet 13 of 15
`Sheet 13 of 15
`
`US 9,141,830 B2
`US 9,141,830 B2
`
`
`
`Figure13
`
`LogbookApp
`
`

`

`U.S. Patent
`
`Sep. 22, 2015
`
`Sheet 14 of 15
`
`US 9,141,830 B2
`
`Mobile Oevice
`(client)
`
`WPA2PSK:
`Set by Pilot
`
`FC:
`Asper Fight Connect
`Configuration App
`
`FC App Credentials:
`sef "instale" of "Ser”
`Password: SHA of CN
`
`Credentials are
`downloaded from Aspen
`cloud and stored in
`cache or nobile device.
`
`
`
`
`
`802.11g Wi-Fi Link will
`WPA2 and SSL Encryption
`
`Transaction FOW
`
`gateway App
`(server)
`
`CG100 Authorizatio
`
`ist:
`
`user:SHAOfCN
`; install:SHAOfCN
`Joe'sApp, password
`AspenApp:1234
`PlanesRus:pwd
`lastApp. cewerPwd
`
`
`
`Access Controls
`WPA2 Pre-shared key invalid PSK will be denied a connection to the CG100.
`SSl: Secure sockets connection encrypts configuration traffic between FC app and CG100. Client can validate
`Gateway authenticity,
`
`Client Authentication. HTTP Basic Authentication password contains an SHA-2 hash of the cert CN.
`
`128 Bit AES Encryption Authorization list within the CG100 is encrypted to prevent tampering.
`
`Figure 14
`
`

`

`U.S. Patent
`
`SS
`
`US 9,141,830 B2
`
`Ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss
`XXXXXXXXXXXXXXXXXXXXXXXXXXX-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-XXXXXXXXXXXXXXXXXXXXXXXXXXX
`
`
`
`
`
`S
`
`

`

`US 9,141,830 B2
`
`1.
`AVIONICS GATEWAY INTERFACE, SYSTEMS
`AND METHODS
`
`CROSS-REFERENCES
`
`This is the United States National Stage of Patent Coop
`eration Treaty Application No. PCT/US2012/047874 filed
`Jul. 23, 2012, which claims priority to U.S. Provisional Patent
`Application Ser. No. 61/510,800, filed Jul. 22, 2011, and to
`U.S. Provisional Patent Application Ser. No. 61/674,340,
`filed Jul. 21, 2012, the disclosures of which are incorporated
`herein by reference in their entireties.
`
`BACKGROUND
`
`Field
`
`10
`
`15
`
`2
`devices and the installed avionics, their use in the cockpit has
`been limited by a lack of integration with onboard systems.
`The EVOLUTION FLIGHT DISPLAY (“EFD) products
`available from ASPEN AVIONICS or other similar devices
`such as Multi-function Displays (MFD) and Primary Flight
`Displays (PFD) are interoperable with a large variety of new
`and legacy avionics products from multiple manufacturers,
`making them a natural gateway to certified flight data. Cur
`rently, there is demand for a non-certified, mobile computing
`device to wirelessly interface directly with FAA-certified
`devices during flight, but such a device is not available in the
`market. What is needed is a wireless bridge between handheld
`devices and the aircraft's certified avionics to increase the
`pilot's access to data and the utility of the mobile devices.
`
`SUMMARY
`
`The present general inventive concept provides a platform
`(gateway or interface) to enable two-way communications
`between non-certified devices and FAA-certified devices.
`One object of the general inventive concept is to seamlessly
`integrate non-certified devices with FAA-certified avionics
`devices without interfering with the functionality or other
`wise compromising the integrity of the FAA-certified devices
`and systems. Another object of the general inventive concept
`is to provide wireless connectivity (e.g., a mobile hotspot) for
`non-certified devices within the cockpit. Another object of the
`general inventive concept is to provide an electronics com
`munication interface system that is sufficiently robust as to be
`highly customizable by end-users, and also largely compat
`ible with numerous FAA-certified and non-certified devices
`and systems, whether currently-in-use or yet-to-be-devel
`oped.
`In preferred embodiments, the gateway interfaces with
`FAA-certified devices without interfering with any function
`ality of the FAA-certified devices. Preferred embodiments of
`hardware interfaces include pre-determined specifications
`and Software interfaces include a set of Application Program
`ming Interface (API) rules and specifications that guide
`interaction with the gateway, on both the non-certified end as
`well as the FAA-certified end. To simplify the hardware and
`Software interfaces design, standardized protocols and rules
`are adhered to whenever possible. The use of application
`specific standards or formats is avoided as much as possible.
`In a preferred embodiment, the gateway enables commu
`nication between the FAA-certified devices and non-certified
`devices with both a hardware component and a software
`component. If instructions are sent to the FAA-certified
`device via the gateway that may impact any functionality of
`the FAA-certified device, the instruction does not take effect
`on the FAA-certified device unless and until a user acknowl
`edges and confirms the instructions via an FAA-certified
`device. The confirmation of the instructions ensures that the
`user-acknowledged data or instructions are validated to be
`received accurately by the using FAA-certified device and the
`user informed of the status of the validation. In this manner,
`no activities of the non-certified device or the gateway can
`interfere with the functionality of the FAA-certified device
`absent a confirmation or acknowledgment from the FAA
`certified device. In some embodiments, the gateway, as a
`hardware component, is certified by the FAA as non-interfer
`ing with critical systems. The Software code associated with
`the gateway, requiring the acknowledgement/confirmation, is
`likewise certified by the FAA as non-interfering with critical
`systems.
`In a preferred embodiment, the hardware is enclosed in a
`Small box that is blind-mounted in the aircraft as a separate,
`
`The present general inventive concept relates to gateway
`interface systems and methods for avionics devices. More
`particularly the inventive concept relates to methods and sys
`tems to interface communications between FAA-certified and
`non-certified devices, systems, and equipment.
`The United States Federal Aviation Administration
`(FAA) establishes, via regulations, certain minimum stan
`dards and requirements that must be satisfied by avionics
`devices, systems and equipment, particularly when the avi
`onics device is essential or critical to flight safety. For
`example, FAR 23.1311 (b) is a regulatory requirement that
`requires, among other things, redundant backup instruments
`in the cockpit. As used throughout this specification, an
`“FAA-certified device may include any and all avionics
`devices, systems, and equipment that comply with FAA regu
`lations and are approved for in-flight use. Approval may be
`secured via a Technical Standard Order (TSO). Type Certifi
`cate (TC), Supplemental Type Certificate (STC), or other
`similar processes and procedures. Examples of FAA-certified
`devices include (but are not limited to) Multi-function Flight
`Displays (“MFD) such as the Evolution Flight Display
`(“EFD) available from ASPEN AVIONICS, the KSN 770
`available from HONEY WELL BENDIX/KING, and the
`GNS 430/.530 available from GARMIN.
`Third-party software developers have developed, and are
`expected to continually develop newer, Software applications
`(also known as "apps') for non-certified devices to enhance
`the flight experience. Applications that can be used by pilots
`to add convenience and efficiency have been developed for
`various mobile operating systems such as APPLE iOS,
`ANDROID, BLACKBERRY, and others. As used throughout
`this specification, a “non-certified device' may include any
`mobile electronics communications device. Examples of
`non-certified devices include (but are not limited to) cell
`phones, Smartphones, BLACKBERRY mobile communica
`tions devices, IPADs, IPODs, IPHONEs, laptops, tablet PCs,
`and similar mobile computing platforms. Indeed, non-certi
`fied mobile devices and many Software applications have
`become quite popular and commonly available in recent
`times.
`The FAA strictly regulates interconnectivity of flight sys
`tems to ensure certain minimum standards of flight safety.
`Unfortunately, because the vast majority of popular mobile
`communications devices are non-certified devices, the
`devices and their convenient Software applications are
`unavailable for direct interfacing with FAA-certified devices
`without compromising the integrity, reliability, and certifica
`tion of the FAA-certified devices.
`Mobile devices have revolutionized how pilots obtain and
`use data. Since there is no data link between these mobile
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`

`

`3
`stand-alone component from the non-certified devices and
`FAA-certified devices that it integrates together. The feature
`rich hardware component contains wireless, Bluetooth and
`USB connectivity options as well as flash memory storage. It
`also includes commercially available technology Such as 5
`standard protocol ports and communications slots that will
`allow other third party companies to interface peripheral
`hardware as needed to enhance the utility of their own appli
`cations. It will be appreciated that in other embodiments the
`gateway of the instant invention will be a hardware and/or a 10
`software component that is integrated into a FAA-certified
`device, such as the EFD available from ASPEN AVIONICS.
`Applications on non-certified devices allow users to inter
`face with an aircraft's FAA-certified devices via the gateway.
`Some of these apps allow a user to upload and/or or modify 15
`flight planning data on his or her non-certified device and then
`synchronize this data with the aircraft's navigation and other
`FAA-certified devices via the gateway. Some of these apps
`allow a user to manage the aircraft logbook, maintenance
`records, and/or operational statistics on his or her non-certi- 20
`fied device via the gateway.
`In preferred embodiments, the gateway provides wireless
`telecommunications connectivity for non-certified devices.
`For example, the wireless connectivity is provided via a WiFi
`network (e.g., 802.11a/b/g/n), 3G/4G mobile telecommuni- 25
`cations network, iridium satellite telecommunications net
`work, BLUETOOTH, or similar. In some embodiments, the
`gateway provides wired connectivity to non-certified devices.
`For example, the wired connectivity is provided via USB,
`Ethernet, or similar.
`The foregoing and other objects are intended to be illustra
`tive of the general inventive concept and are not meant in a
`limiting sense. Many possible embodiments of the invention
`may be made and will be readily evident upon a study of this
`specification and accompanying drawings comprising a part 35
`thereof. Various features and subcombinations may be
`employed without reference to other features and subcombi
`nations. Other objects and advantages of this invention will
`become apparent from the following description taken in
`connection with the accompanying drawings, wherein is set 40
`forth by way of illustration and example, an embodiment of
`this invention and various features thereof.
`
`30
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`45
`These and/or other aspects and utilities of the present gen
`eral inventive concept will become apparent and more readily
`appreciated from the following description of the embodi
`ments, taken in conjunction with the accompanying draw
`ings. For the purpose of illustration, forms of the present 50
`general inventive concept which are presently preferred are
`shown in the drawings; it being understood, however, that the
`general inventive concept is not limited to the precise arrange
`ments and instrumentalities shown. In the drawings:
`FIG. 1 is an exemplary embodiment of the general inven- 55
`tive concept where a mobile application is operated on a
`non-certified device in wireless communication with a gate
`way which is then in hardwire communication with FAA
`certified devices such as multi-function flight displays (via
`Ethernet) and/or navigation equipment (via ARINC429 or 60
`RS232).
`FIG. 2 is the end-to-end flight experience employing non
`certified devices enabled by a gateway of the general inven
`tive concept.
`FIG. 3 is an exemplary embodiment of the general inven- 65
`tive concept where a gateway is used in the cockpit of an
`aircraft allowing a pilot to coordinate tasks performed on
`
`US 9,141,830 B2
`
`4
`non-certified devices before and after flight with tasks per
`formed during flight on non-certified devices and interfacing
`with FAA-certified devices.
`FIG. 4 is a detailed view of the gateway shown in FIG. 3.
`FIG. 5 is another exemplary embodiment of a gateway of
`the present general inventive concept.
`FIG. 6 is an embodiment of a gateway of the present gen
`eral inventive concept with a single Ethernet port.
`FIG. 7 is a detailed view of an Ethernet connectivity option
`of a gateway of the present general inventive concept where a
`switch is added to the gateway to provide additional Ethernet
`ports.
`FIG. 8 is an embodiment of a gateway of the present gen
`eral inventive concept configured to include three Ethernet
`ports.
`FIG. 9 is a flow chart showing how a flight planning soft
`ware application interfaces between a non-certified device
`and an FAA-certified device via a gateway of the present
`general inventive concept.
`FIG. 10 is a flow chart showing how a flight planning
`service application functions on a gateway of the present
`general inventive concept.
`FIG. 11 is a flow chart showing how a flight control/radio
`tuning Software application interfaces between a non-certi
`fied device and an FAA-certified device via a gateway of the
`present general inventive concept.
`FIG. 12 is a flow chart showing how a radio tuning software
`service application functions on a gateway of the present
`general inventive concept.
`FIG. 13 is a flow chart showing how a flight log book
`Software application interfaces between a non-certified
`device and an FAA-certified device via a gateway of the
`present general inventive concept.
`FIG. 14 is a flow chart showing one exemplary embodi
`ment of secured access protocols for communication between
`a non-certified mobile computing device and a wireless gate
`way in a system of the present general inventive concept.
`FIG. 15 shows an exemplary embodiment of a system of
`the present general inventive concept.
`
`DETAILED DESCRIPTION
`
`This general inventive concept provides an electronic gate
`way interface module designed to provide telecommunica
`tions connectivity between cockpit avionics and mobile
`devices (i.e., between FAA-certified and non-certified
`devices). One example of the general inventive concept is
`described, in detail, in co-pending U.S. Provisional Patent
`Application Ser. No. 61/674,340, filed Jul. 21, 2012, the
`entire disclosure of which is incorporated herein by reference.
`Referring to FIG. 1, the gateway provides a hardwire tele
`communications link to FAA-certified devices. Such as
`ASPENS EFD, via an Ethernet interface, or such as a navi
`gation system, via an ARINC429 (RS-232) connection. The
`gateway also provides a telecommunications link to non
`certified devices, such as mobile phones, tablets, electronic
`notebooks, laptops, or similar. In FIG. 1, the gateway pro
`vides a wireless link to non-certified devices via WiFi (IEEE
`802.11a/b/g/n). The gateway acts as a wireless access point
`providing a connection point between wireless mobile
`devices and avionics equipment. In some embodiments the
`gateway utilizes standard security protocols and/or security
`certification programs developed to secure wireless computer
`networks, such as WPA, WPA2, WEP, etc. The gateway may
`be a standalone device or part of FAA-certified device includ
`ing software used in that FAA-certified device to provide
`gateway functionality as defined herein.
`
`

`

`5
`The gateway is designed to operate with a pre-defined
`Application Programming Interface (API). Third-party
`software developers use the API specifications to develop
`apps for mobile devices (i.e., non-certified devices) that
`access data and functions on avionics equipment (i.e., FAA
`certified devices) that are connected to the gateway. For
`example, but not by way of limitation, if the gateway is
`connected to ASPENS EFD, navigation and communica
`tions device data are accessible via the EFD. In alternative
`examples, multiple FAA-certified devices are connected to
`and accessible via the gateway. The methods used to acknowl
`edge, confirm and validate are not limited to being resident in
`ASPENS EFD. The methods, hardware and/or software, can
`be included as part of any FAA-certified device that operates
`as the FAA-certified interface
`The gateway, when used in combination with third-party
`non-certified devices and existing and yet-to-be-developed
`third-party software applications, allows users to streamline
`the end-to-end flight experience. With the gateway, users can
`more efficiently coordinate and synchronize efforts on-the
`ground before and after flights. The gateway allows users to
`use information necessary for flight and collected during
`flight as well as analytics available between flights. Referring
`to FIG. 2, before flight, a pilot uses non-certified devices to
`accomplish tasks Such as check the latest weather develop
`ments, plan a flight, finalize a flight route, file and obtain
`clearance, prepare and update charts and flight databases,
`plan for destination logistics, notify others of upcoming
`flight, confirm pilot and aircraft airworthiness, confirm air
`craft availability, and plan for passenger comfort. Referring to
`FIG. 2, during flight, a pilot uses non-certified devices to
`interface with FAA-certified devices, via the gateway, to
`accomplish tasks such as load flight plan and clearance to the
`avionics systems, tune radios and communicate with others,
`review and perform flight procedures, manage charts and
`flight databases, monitor fuel and engine operations, avoid
`weather, terrain, and obstacles, execute checklist, report and
`track position, communicate with people on the ground, and
`keep passengers comfortable. Referring to FIG.2, after flight,
`a pilot uses non-certified devices to accomplish tasks Such as
`close the flight plan, flight log entry, notify others of arrival,
`arrange for ground transportation, review flight and debrief,
`and report any incidents. Referring to FIG. 2, between flights,
`a pilot uses non-certified devices and information gathered
`from avionics devices to accomplish tasks Such as review
`flight trends, share experience, analyze data, maintain air
`craft, maintain and enhance skills, maintain pilot status, and
`critique instructor.
`In some embodiments, the general inventive concept also
`includes a security key feature. The security key feature pro
`vides an option for a subscription arrangement in using the
`gateway. If a user cancels the Subscription, then that user's
`specific security key is deactivated and that user can no longer
`access the gateway. In some embodiments, the security key
`feature is specific to each app (e.g., the app developer is issued
`the security key for a specific app). In other embodiments, the
`security key feature is specific to each user (e.g., each mobile
`device is issued a unique security key regardless of what apps
`are used by that device). If an app developer creates an app
`that somehow damages or improperly interferes with the
`gateway or an FAA-certified device, the relevant security
`keys are deactivated and the problematic app and/or user can
`no longer interface with the gateway. Thus, even if the devel
`oper published a pirate app online, it does not function for any
`user thanks to this security key feature.
`Referring to FIG. 3, a gateway of an embodiment the
`present general inventive concept is installed in the cockpit of
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`US 9,141,830 B2
`
`10
`
`15
`
`6
`an aircraft and interfaces with FAA-certified devices. The
`gateway provides a wireless access point within the cockpit of
`the aircraft Such that non-certified devices can access and
`communicate with FAA-certified devices of the aircraft.
`Alternatively or additionally, the gateway provides a wired
`(e.g., USB) connection for non-certified devices. The pilot
`performs certain tasks before flight, after flight, and between
`flights on a non-certified device. During flight, the pilot uses
`a non-certified device to access information and functions of
`the FAA-certified devices that interface with the gateway.
`For example, and not by way of limitation, in a preferred
`embodiment, the gateway complies with DO-160E environ
`mental conditions requirements. In this example, the gateway
`meets the requirements under a non-interference mode. The
`gateway will not interfere with avionics equipment, but may
`be susceptible to interference from other devices. The gate
`way is not certified as a critical device. The gateway is a
`non-essential, non-critical hardware and software component
`that should not cause interference to the aircraft but whose
`function may be degraded by noise or environmental condi
`tions. Those skilled in the art will recognize that other con
`figurations and alternative embodiments are equally viable
`where the software and/or hardware are fully certified by the
`FAA.
`Referring to FIG. 4, a detailed view of the gateway of FIG.
`3 is provided. As shown in FIG. 4, the gateway includes a
`communication module that provides in-aircraft telecommu
`nications connectivity. As shown in FIG. 4, in-aircraft tele
`communications connectivity is WiFi, 3G/4G cellular, Iri
`dium satellite, or USB. The gateway is connected to a power
`supply. The power supply may be self contained within the
`gateway (e.g., battery operated), connected to any aircraft
`power Supply system (including an FAA-certified device), or
`both (one or the other with backup for redundancy). The
`gateway includes a processor and memory storage, with
`optional additional external memory interface (e.g., a
`memory card).
`According to FIG. 4, the gateway includes several avail
`able interface options for connectivity to FAA-certified
`devices. According to FIG.4, the gateway connects directly to
`ASPENS EFD multi-function flight display or other similar
`device via an Ethernet connection. According to FIG.4, other
`FAA-certified devices are connected to the EFD or other
`similar device and are thus accessible via the gateway-EFD
`(or other similar device) connection. According to FIG. 4.
`Some