Patent Description:
Concurrently filed United States Patent Application entitled SMART POINT OF PRESENCE (SPoP) DEVICES FOR AIRCRAFT-BASED HIGH AVAILABILITY EDGE NETWORK ARCHITECTURE and having internal docket number 124850US03; and.

Embodiments of the inventive concepts disclosed herein are directed generally to computer networking, and particularly to avionics networking configurations incorporating mission-critical subsystems.

Mission systems updates aboard aviation assets may require a long time to build, test, and certify. Current network architectures are optimized, with size, weight, and power (SWaP) considerations in mind, into interwoven "safe flight" and "mission success" systems. While it may be possible to separate architectures into independent, interactive air vehicle systems (AVS) and mission systems (MS) subsystems, the underlying "hub and spoke" network topologies require long wiring runs (doubly so in the case of duplex systems) which translates to increased wire weight, high rewiring costs, and high I/O density at the hubs, which complicate LRU designs and may require additional switches to extend the network topology.

Current interwoven architectures may require lengthy testing in order to achieve airworthiness certification. However, mission systems may be subject to far more rapid change and update cycles than air vehicle systems. While the emergence of autonomous systems may in turn require more redundant systems, legacy input/output (I/O) and power systems will persist as components of the solution space for the foreseeable future, as there is as yet no "one size fits all" I/O or power solution capable of supplanting them.

A high availability aircraft network architecture incorporating smart points of presence (SPoP) is disclosed. In embodiments, the network architecture divides the aircraft into districts, or physical subdivisions. Each district includes one or more mission systems (MS) smart network access point (SNAP) devices for connecting MS components and devices located within its district to the MS network. Similarly, each district includes one or more air vehicle systems (AVS) SNAP devices for connecting AVS components and devices within the district to the AVS network. The MS network and AVS network may be interconnected but configured according to different topologies. Selected MS and AVS SNAP devices may be connected to each other via guarded network bridges to securely interconnect the MS and AVS networks.

In some embodiments, the network architecture includes at least one essential district wherein the MS SNAP device and/or AVS SNAP device are connected to at least one essential (e.g., mission-critical) component.

In some embodiments, the MS network is configured according to a ring or mesh topology, and the AVS network is configured according to a hub-and-spoke or star topology.

In some embodiments, the MS SNAP devices of the MS network are connected via fiber optic network trunk.

In some embodiments, the MS network includes at least one MS SNAP device incorporating an adaptive input/output (I/O) component connecting the MS SNAP device to legacy I/O or power components within the district (e.g., connecting legacy wired devices to the fiber optic MS network) and providing for data exchange between the legacy I/O or power components and the MS network.

In some embodiments, the legacy I/O or power components include components or devices connected via MIL-STD-<NUM> serial data bus, ARINC <NUM> avionics data bus, or Ethernet networking cables or components.

In some embodiments, the adaptive I/O components includes a data concentrator unit (DCU).

In some embodiments, the adaptive I/O component incorporates a cross-domain data guard and multiple levels of security (MLS) encryption/decryption modules.

In some embodiments, the MS SNAP device includes power control components configured for distributing operating power to MS components within the district connected to the MS SNAP device.

In some embodiments, the power control components are selected from a power converter connected to an aircraft power supply, electronic circuit breakers (ECB) configured for providing converted power to MS components, and local batteries for supplying power directly to MS components.

Embodiments of the inventive concepts disclosed herein are directed to a network architecture based on localized smart points of presence (SPoP) and incorporating autonomous, interconnected air vehicle systems (AVS) and mission systems (MS) communications networks which are distinctly separable and protected while remaining highly interactive with each other through a "digital backbone". While in the short term the AVS network, which is associated with a lower change velocity, may remain a traditional hub-and-spoke (e.g., point-to-point, star-topology) network with a high-speed, high-bandwidth network trunk, the MS network (which has a much higher change velocity) may adopting ring or mesh topologies to increase reliability, survivability, availability, and alleviate the need for long wiring runs. In some embodiments, the AVS network may additionally adopt ring/mesh topologies. The MS and AVS network trunks may incorporate copper or other cabling (e.g., to accommodate legacy I/O or power components); alternatively, the network trunks may be fiber optic based.

Referring to <FIG> and <FIG>, the aircraft <NUM> is shown. The aircraft <NUM> may include, but is not limited to, fixed-wing craft, rotorcraft, or unmanned aircraft systems (UAS) piloted by one or more remote operators, or capable of partially or fully autonomous operation.

In embodiments, the aircraft <NUM> may be compartmentalized and/or categorized into districts, each district corresponding to a physical subdivision of the aircraft and incorporating any and all network components physically located within the said district. Each district may include one or more district service access points (DSAP) through which any network components within the district may be connected to, and may exchange data with, an MS or AVS network.

In embodiments, the aircraft <NUM> may be broken down into essential districts <NUM> and non-essential districts <NUM>. Essential districts <NUM> may include AVS essential districts and MS essential districts; AVS essential districts may support equipment and/or services directed to aviation functions, while MS essential (and non-essential) districts may support mission-related equipment and/or services. For example, AVS network components or services may include, but are not limited to, flight control and/or air vehicle computers, human/machine interfaces (HMI), autonomous command and control (C2) and payload systems, communications antennas and tuners, standby instrumentation, landing gear and lighting control systems, vehicle management sensors (e.g., engine, transmission, fuel), and onboard navigational instruments (e.g., radar altimeter (radalt), VOR/ILS, air data computers (ADC), embedded GPS/inertial (EGI) positioning systems). MS network components and services may include, but are not limited to, mission computers and/or display systems (e.g., including DVE processing systems and/or 3D sensors), flight/mission data recorders, weather sensors and/or receivers, head-mounted display (HMD) systems and head trackers, weapons and targeting systems, survivability components and countermeasures, and tactical communications systems (e.g., LOS/BLOS radio systems, SATCOM radio systems, tactical data links). "Essential" equipment or services may refer to any mission-critical network component incorporating dual redundancies (e.g., to avoid a single point of failure and ensure high availability) and/or any network component operating or operable on local battery power (as described in greater detail below). Similarly, non-essential network components include any network components that are not essential, e.g., without which mission objectives may be fulfilled via alternative means.

In embodiments, essential districts <NUM> may include both essential and non-essential components, while non-essential districts <NUM> support solely non-essential components. Referring in particular to <FIG>, the aircraft <NUM> may incorporate an AVS network <NUM> having a star topology (e.g., hub-and-spoke) comprising a number of smart network access point (SNAP) devices <NUM>, each SNAP device connected to a central/hub SNAP device 204a via AVS network trunk <NUM> (e.g., fiber optic, copper/wired or cable connection) and serving as a DSAP for any AVS network components or devices within its district. Similarly, the aircraft <NUM> may incorporate an MS network <NUM> comprising a group of SNAP devices <NUM> connected in a ring topology via an MS network trunk <NUM> (e.g., fiber optic trunk cable). For example, the AVS network <NUM> and MS network <NUM> may be independent and isolated from each other but directly connected via one or more network bridges <NUM> (e.g., dual redundant guard/network bridge). In embodiments, each district (essential districts <NUM> and non-essential districts <NUM>) may include at least one SNAP device <NUM>, e.g., at least one AVS SNAP device of the AVS network <NUM> and at least one MS SNAP device of the MS network <NUM>. For example, some districts may include multiple SNAP devices, e.g., if the quantity of network components and/or devices within its district so requires.

By moving hub-and-spoke connections of the AVS network <NUM> to the district level, the length (and weight) of cabling or wiring may be minimized while maintaining high availability. Similarly, a next-generation or high change velocity MS network <NUM> may be retrofitted to an existing hub-and-spoke AVS network <NUM>, allowing for high flexibility of functionality by supporting the addition of new SNAP devices <NUM> between existing MS SNAP devices in an MS network having a ring topology (e.g., or a mesh topology). Further, SNAP devices <NUM> may provide conversion support for legacy I/O and/or power components at the district level, compartmentalizing I/O and power needs within a district and providing for easier portability of features from one SNAP device to another. The replacement of legacy I/O and power components may be incentivized by the removability of conversion support features when they are no longer needed, further improving SWaP considerations. At a high level, rapid change and deployment of new MS features may be provided while preserving certified airworthy AVS features, eliminating the need for additional recertification testing.

Referring to <FIG>, the aircraft <NUM>, AVS network <NUM>, and MS network <NUM> are disclosed.

In embodiments, the AVS network <NUM> and MS network <NUM> may be connected via high bandwidth network bridges <NUM> (e.g., dual redundant network trunks) protected on each end by SNAP devices <NUM> and including assured network guards. For example, the network bridges <NUM> may further provide a "digital backbone" for additional shared functionalities (e.g., adaptive cooling/thermal management for dissipation or control of heat generated by components within a district) between the AVS and MS networks.

In embodiments, each SNAP device <NUM> may serve as a district service access point (DSAP) for network components in its district. For example, the SNAP devices <NUM> of the AVS network <NUM> may provide network access to, e.g., communications equipment <NUM>, navigational sensors <NUM>, ARINC <NUM> data buses <NUM> and compatible legacy equipment <NUM>, and AVS displays <NUM>. Similarly, the SNAP devices <NUM> of the MS network <NUM> may provide network access to, e.g., MIL-STD-<NUM> data buses <NUM> and compatible legacy equipment <NUM>; sensor suites <NUM>; MS displays <NUM>; and mission computers <NUM>. In some embodiments, the MS network <NUM> may be configured in a mesh topology rather than the ring topology shown by, e.g., <FIG>, whereby some SNAP devices <NUM> are directly connected (<NUM>) in addition to their ring neighbors on the MS network trunk <NUM>. In embodiments, the SNAP devices <NUM> may provide district-level management for, e.g., power distribution and control; thermal management and adaptive cooling (e.g., management of heat generated by the network components within a district); network access; I/O conversion and distribution; and encryption/decryption. For example, a SNAP device <NUM> may incorporate additional software and/or hardware components depending on the DSAP services provided within its district, as described in greater detail below.

Referring to <FIG>, the aircraft <NUM>, AVS network <NUM>, and MS network <NUM> is disclosed.

In embodiments, the MS network <NUM> (as well as the AVS network <NUM>, not shown here in equivalent detail) may comprise multiple local area networks, connected via MS network trunks 210a-b, for its essential districts <NUM> and non-essential districts <NUM>. For example, the essential district 102a may include both essential and non-essential network components, serviced by essential SNAP devices 204b and non-essential SNAP device 204c. Similarly, the essential district 102b may include essential SNAP device 204b (with network bridging (<NUM>) to AVS SNAP device 204d) and non-essential SNAP device 204c. The non-essential districts 104b-c may each include non-essential SNAP devices 204c (the latter SNAP device of the non-essential district 104c also incorporating network bridging <NUM> to AVS SNAP device 204e), and the non-essential district 104d may include non-essential SNAP device 204c, which may serve as a subnetwork hub for the subnetwork <NUM>.

In embodiments, each MS network trunk 210a-b connecting a local area network within the MS network <NUM> may incorporate backbone rings <NUM>, <NUM>, <NUM>. For example, a data ring <NUM> may provide primary control and data functionality for the MS network <NUM>. A dedicated video/sensor ring <NUM> may provide high-bandwidth raw video (e.g., main cameras/heads-up displays, weather radar, fire control, forward-looking infrared radar (FLIR)). A time ring <NUM> may provide accurate and time-sensitive distribution of precise timing synchronization information throughout the MS network <NUM> and, through the SNAP devices 204b-e, to network components and devices served by the SNAP devices.

Referring now to <FIG>, the SNAP device <NUM> is disclosed.

In embodiments, the SNAP device <NUM> may include network trunk ports <NUM> capable of accepting network trunk connections (e.g., AVS network trunk (<FIG>, <NUM>), MS network trunk (<FIG>, <NUM>) for incorporation into an AVS network (<FIG>, <NUM>) or MS network (<FIG>, <NUM>). The SNAP device <NUM> may include additional device ports <NUM> for accepting physical links (e.g., coaxial, fiber, copper) to AVS or MS network components or devices within a district served by the SNAP device.

In embodiments, each SNAP device <NUM> may be capable of controlling multiple standard functions, e.g., cybersecurity, trunk networking, power control and distribution, district networking, and adaptive cooling/thermal management. In some embodiments, a SNAP device <NUM> may be required to manage additional functionalities, e.g., power transformation, district-level data concentration, and/or district-level isolated power distribution.

Referring also to <FIG>, an adaptive I/O access point device <NUM> (AIAP, AdAPt) is disclosed. In embodiments, the SNAP device <NUM> may incorporate an AIAP device <NUM> in order to provide network access to, and data exchange with, a fiber optic MS network (<FIG>, <NUM>) or AVS network (<FIG>, <NUM>) and legacy network components or equipment via device ports <NUM>, e.g., legacy equipment (<FIG>: <NUM>, <NUM>) compatible with MIL-STD-<NUM> and/or ARINC <NUM> data buses (<FIG>: <NUM>, <NUM>) or, e.g., discrete or serial interfaces. In some embodiments, the AIAP device <NUM> may incorporate additional components, e.g., for data guard and/or encryption/decryption capabilities, as described in greater detail below.

Referring to <FIG>, the SNAP device <NUM> is disclosed.

Referring in particular to <FIG>, the SNAP device <NUM> may include, in addition to network trunk ports <NUM> and device ports <NUM> (e.g., district switch ports), network bridging ports <NUM> for accepting network bridging (<FIG>, <NUM>), e.g., to an AVS network (<FIG>, <NUM>) if the SNAP device <NUM> is part of an MS network (<FIG>, <NUM>), or to the MS network if the SNAP device is part of the AVS network.

In embodiments, the SNAP device <NUM> may include a ring switch <NUM> and network processors <NUM> for handling data exchanges and component management within the district served by the SNAP device. Referring also to <FIG>, the network processors <NUM> may include time management modules <NUM> (e.g., capable of sending or receiving timing information via the time ring (<FIG>, <NUM>)), device/network management modules <NUM>, cybersecurity management modules <NUM>, power management modules <NUM>, and network endpoints <NUM>. The bridge core <NUM> may connect the network processors <NUM> to the network trunk ports <NUM> and device ports <NUM>. It is contemplated that the SNAP device <NUM> may support a <NUM> Gb MS network <NUM> with a growth path to <NUM> Gb.

Referring also to <FIG>, the SNAP device 204f may be implemented and may function similarly to the SNAP devices <NUM>, 204a-e of <FIG>, except that the SNAP device 204f may incorporate an AIAP device <NUM> via a device port <NUM>.

In embodiments, the SNAP device 204f may (e.g., via power management modules (<FIG>, <NUM>)) control the distribution of operating power to network components and devices within its district. For example, the SNAP device 204f may incorporate power converters <NUM> capable of receiving operating power from an aircraft power supply <NUM> and, via electronic circuit breakers <NUM> (ECB), supplying operating power to the AIAP device <NUM> and/or legacy network components and devices (<NUM>) served by the SNAP device 204f via the AIAP device. For example, the power converters <NUM> may convert received 270V operating power to 28V for distribution to the network components and devices. In some embodiments, the SNAP device 204f may control the distribution of operating power through a local battery <NUM>.

In embodiments, additional functionalities provided by the AIAP device <NUM> (e.g., to legacy network components and devices via AIAP device ports <NUM>) may be managed by local processors <NUM>. Referring also to <FIG>, in embodiments, the AIAP local processors <NUM> may incorporate AIAP device and I/O management modules <NUM>, cybersecurity management modules <NUM>, and an edge I/O core <NUM> for control of, e.g., general computing 736a, data guarding 736b, data relay and routing 736c, data transformation 736d (e.g., between copper/wired and fiber-optic components), data encryption/decryption 736e, and network endpoint services 736f.

Referring to <FIG>, the AIAP device 600a may be implemented and may function similarly to the AIAP device <NUM> of <FIG>, except that the AIAP device 600a appended to the SNAP device <NUM> (e.g., via device port <NUM>) may incorporate a district-level data concentrator unit <NUM> (DCU) and/or district-level Ethernet switch <NUM> (e.g., to provide network access for Ethernet network components to a fiber-optic MS network (<FIG>, <NUM>).

In some embodiments, the SNAP device <NUM> and AIAP device 600a may connect to existing cross-domain guard and/or Multiple Levels of Security (MLS) encryption/decryption equipment to provide added cybersecurity for district-level legacy network components and devices having security classifications different than the MS network <NUM>. Referring to <FIG>, the AIAP device 600b may be implemented and may function similarly to the AIAP devices <NUM>, 600a of <FIG>, except that the AIAP device 600b may incorporate cross-domain guard functionality <NUM> and MLS encryption/decryption <NUM> (e.g., via AIAP cybersecurity management modules (<FIG>, <NUM>)) for providing cybersecurity and data guard services incorporating multiple levels of assurance to legacy network components and devices (<NUM>).

Referring to <FIG>, the AIAP device <NUM> is disclosed.

In embodiments, the AIAP device <NUM> may provide signal conditioning, MLS data guarding, and/or encryption and decryption of data exchanged between legacy components and devices (e.g., connected via AIAP device ports <NUM>) and the MS network (<FIG>, <NUM>), e.g., USB-connected components (<NUM>); Ethernet links and/or networking components (<NUM>); Avionics Full-Duplex Switched Ethernet (AFDX) and other like ARINC <NUM>-compatible components (<NUM>); MIL-STD-<NUM> data buses (<NUM>); ARINC <NUM> data buses (<NUM>); serial connections and/or components (<NUM>; e.g., RS-<NUM>, RS-<NUM>, RS-<NUM>); analog network components (<NUM>); and discrete-port connected components (<NUM>).

For example, as described above if the AIAP device incorporates MLS encryption/decryption (<FIG>, <NUM>) and/or cross-domain guarding (<FIG>, <NUM>) as described above. Further, the AIAP device <NUM> may provide data relay and routing, multiplexing (muxing) and demultiplexing (demuxing) and transformation of exchanged data between network components (e.g., copper-to-fiber, fiber-to-copper, fiber-to-fiber, copper-to-copper).

Referring to <FIG>, an AIAP backplane implementation <NUM> is disclosed. The AIAP backplane implementation <NUM> may include multiple AIAP devices <NUM>.

In embodiments, the AIAP backplane implementation <NUM> may provide access to the MS network (<FIG>, <NUM>) via the AIAP devices <NUM> to fiber-optic and legacy network components and devices, e.g., via fiber-optic connections <NUM> or legacy wired connections (including, but not limited to, Ethernet links and/or cables <NUM>; serial connections <NUM>; ARINC <NUM> data buses <NUM>; and MIL-STD-<NUM> data buses <NUM>). Connected network component and devices may include, but are not limited to, mission computers <NUM>; sensor suites (<FIG>, <NUM>; e.g., flight sensor suites <NUM>, mission sensors <NUM>, cameras/image sensors <NUM>); input devices <NUM>; AFDX and other Ethernet switches <NUM>; flight computers <NUM>; display systems (e.g., flight crew displays <NUM>, mission displays <NUM>).

Claim 1:
An aircraft mission systems (MS) network architecture, comprising:
a plurality of districts (<NUM>), each district associated with a physical subdivision of an aircraft, each district comprising:
at least one first MS smart network access point (SNAP) device (<NUM>) configured to connect a MS network to one or more MS components disposed within the district,
the MS network comprising a plurality of MS SNAP devices communicatively connected in a first topology via a network trunk;
at least one first air vehicle systems (AVS) SNAP device configured to connect an AVS network to one or more AVS components disposed within the district,
the AVS network comprising a plurality of AVS SNAP devices communicatively connected in a second topology via a second network trunk;
and
the MS network including at least one second MS SNAP device communicatively coupled to a second AVS SNAP device of the AVS network via a guarded network bridge.