Transcript System Wide Information Management (SWIM)over AMHS

SP/6
System Wide Information Management
(SWIM) over AMHS
Federal Aviation
Administration
Presented by: Vic Patel, FAA
Presentation to: AMHS/SWIM Workshop
Chiang Mai, 05-07 March 2012
Federal Aviation
Administration
0 0
Topics
•
•
•
•
•
•
SWIM
• State of the System, Conceptual Overview
FTI IP Backbone
SWIM Messaging Infrastructure
• NAS Enterprise Messaging System (NEMS)
• Request/Response, Publish/Subscribe, NESG
Options for SWIM in Asia/Pac
• AMHS Network Infrastructure
SWIM Messaging over AMHS
• Typical Web services, Web services with an “HTTP to AMHS
Gateway”
Recommendation for the ATNICG
AMHS - SWIM Workshop, Chiang Mai, March 5 - 7
Federal Aviation
Administration
1 1
System Wide Information Management (SWIM)
SWIM will:
• Implement a Service-Oriented Architecture (SOA) in the NAS
• Lower information costs
“The airport runway is the
Most important mainstream
In any town.”
-Norm Crabtree
• Increase speed to establish new interfaces
• Increase common situational awareness
• Increase NAS agility
AMHS - SWIM Workshop, Chiang Mai, March 5 - 7
Federal Aviation
Administration
2 2
State of the System
Business as Usual
- More point-to-point
unique interfaces
- Costly development,
test, maintenance, CM
- New decisions linked to
old data constructs
- Cumbersome data
access outside the NAS
Today
Host
ETMS
WARP
IDS/
ERIDS
ASDE
ATOP
ERAM
STARS/
ARTS/
TAMR
CIWS
FAA Systems
TMA
TFM
ERAM
InterAgency
- Existing point-to-point
hardwired NAS
- Unique interfaces, custom
designs
Enterprise
Management
SWIM Compliant
Non-Government
Systems
SWIM Compliant
Government
Systems
FTI
LEGEND
DOTS
SWIM Segment 1
SWIM Future Segment
SWIM Adapter
AMHS - SWIM Workshop, Chiang Mai, March 5 - 7
Federal Aviation
Administration
3 3
Conceptual Overview
Conceptual Overview
AMHS - SWIM Workshop, Chiang Mai, March 5 - 7
Federal Aviation
Administration
4 4
FTI IP BACKBONE
Federal Communications Infrastructure (FTI)
FTI provides an IP infrastructure for connectivity of all FAA National
Airspace System (NAS) Automation Systems
It is based on IPv4 with an underlying MPLS network
NAS Automation Systems can get different service levels from
basic communications through enhanced communications (e.g.,
with Security)
There is a NAS Enterprise Security Gateway that provides secured
connectivity between NAS and non-NAS systems
AMHS - SWIM Workshop, Chiang Mai, March 5 - 7
Federal Aviation
Administration
5 5
SWIM Messaging Infrastructure
The SWIM Messaging Infrastructure for the FAA is the NAS Enterprise
Messaging System (NEMS)
NEMS Messaging Nodes (NMN) support two types of messaging models:
Request/Response and Publish/ Subscribe
Request/Response is the predominate method used in Service Oriented
Architectures.
It is a “Pull” exchange model where the client invokes a service and gets a synchronous
response
It is used in both SOAP and REST Web Services
The Publish/ Subscribe model is meant to used for Services that require a
constant, persistent feed of data
The FAA uses Java Messaging Service (JMS) for Publish/Subscribe
It is a “Push” exchange model where the service pushes out data asynchronously
AMHS - SWIM Workshop, Chiang Mai, March 5 - 7
Federal Aviation
Administration
6 6
NAS Enterprise Messaging System (NEMS)
The Request/Response model is suited for Services initiated by the Client
May be implemented as SOAP-based Web service typically using an
HTTP binding
A SOAP request message identifies the service and contains any
parameters for the service
A SOAP response message contains the result of the invoked
service
May also be implemented as a Representational State Transfer (REST)
Web service where a URL is used to initiate a service over HTTP
The URL contains all information to invoke the service
NEMS provides a HTTP proxy capability
AMHS - SWIM Workshop, Chiang Mai, March 5 - 7
Federal Aviation
Administration
7 7
NAS Enterprise Messaging System (NEMS)
The Publish/ Subscribe model is typically used for Services that require a constant,
persistent feed of data
NEMS uses Web Logic JMS, where a JMS client connects to a JMS Broker to
receive messages
Messages are distributed using JMS Topics
A topic is used to distinguish among multiple classes of data products
Each data products may be further marked with tags which permit clients to
distinguish particular data products on a Topic
Note that JMS is not a general purpose messaging protocol like SMTP, XMPP, or
X.400
It is a standard way for Java programs to access a message broker and does not
provide wire-level interoperability
Thus it is not generally suitable for global interoperability
AMHS - SWIM Workshop, Chiang Mai, March 5 - 7
Federal Aviation
Administration
8 8
NAS Enterprise Messaging System (NEMS)
Current Deployment (2012)
NEMS Messaging Nodes (MNM) are
currently deployed at 4 locations in the
NAS
For external connectivity MNM are
deployed in the NAS Enterprise
Security Gateway
The NESG has an External (Untrusted)
DMZ and an Internal (Trusted) DMZ
Each DMZ has a general purpose
Enterprise Service Bus
There is an MNM on each ESB, i.e., in
the External and Internal DMZ
AMHS - SWIM Workshop, Chiang Mai, March 5 - 7
Federal Aviation
Administration
9 9
NAS Enterprise Messaging System (NEMS)
Future Deployment (2018)
In the future NEMS Messaging Nodes
(MNM) will be deployed at:
21 ARTCCs (including SLC),
Atlantic City, and
Atlanta
AMHS - SWIM Workshop, Chiang Mai, March 5 - 7
Federal Aviation
Administration
10 10
Options for SWIM in Asia/Pac
SWIM in Asia/Pac could be done in several ways
Over the CLNP Sub-network
An IPv4 to CLNP gateway would be needed
However, CLNP is planned to eventually be replaced
Over the planned IP Sub-network
If IPv6 (following ICAO Montreal in Doc 9896) then a IPv4 to IPv6
gateway would be needed
Over AMHS
For SOAP and REST Request/Response an HTTP Gateway would be
needed
For JMS Pub/Sub a JMS Gateway would be needed
AMHS - SWIM Workshop, Chiang Mai, March
5 -- 7SWIM Workshop, Chiang
AMHS
Mai, March 5 - 7
Federal Aviation
Administration
11 11
AMHS Network Infrastructure
AMHS
System
AMHS
System
IPv4
Network
AMHS
System
IPv6
Network
OSI
Network
AMHS - SWIM Workshop, Chiang Mai, March 5 - 7
AMHS
System
Federal Aviation
Administration
12 12
SWIM Messaging over AMHS
SWIM Messaging over AMHS could be implemented through the
introduction of a SWIM/AMHS Gateway.
This would provide Inter-Regional connectivity since AMHS is the next
generation Messaging System for Aviation
The SWIM/AMHS Gateway should definitely exchange SOAP and REST
Request/Response exchanges over HTTP.
XML encoding should be straight-forward
SOAP will attachments will require additional investigation
In the future, the SWIM/AMHS Gateway might also support
Publish/Subscribe exchanges.
Given the limitations of JMS, this requires further investigation.
Note that the Open Geospatial Consortium (OGC) has initiated an
activity to look into Pub/Sub
AMHS - SWIM Workshop, Chiang Mai, March 5 - 7
Federal Aviation
Administration
13 13
Typical Web Services Communications
Web
Service
Client
Web
Service
Provider
Request/
Response
Request/
Response
SOAP, REST
HTTP
TCP/IP Stack
AMHS - SWIM Workshop, Chiang Mai, March 5 - 7
Federal Aviation
Administration
14 14
Web Services with an
“HTTP to AMHS Gateway”
Web
Service
Client
Web
Service
Provider
Request/
Response
Request/
Response
SOAP, REST
HTTP
TCP/IP Stack
SOAP, REST
HTTP to AMHS Gateway
AMHS
ATN/OSI or
ATN/IPS
AMHS - SWIM Workshop, Chiang Mai, March 5 - 7
HTTP
TCP/IP Stack
Federal Aviation
Administration
15 15
Recommendation for ATNICG
The ATNICG Working Group should take SWIM over AMHS (or
ATN) as a Task Item
Initial investigation should be on SOAP and REST over
HTTP
Pub/Sub operations should be deferred
This activity should be coordinated with ACP Working Group I
AMHS - SWIM Workshop, Chiang Mai, March 5 - 7
Federal Aviation
Administration
16 16