civil-military swim interoperability - · pdf filepresentation on. civil-military swim ......
TRANSCRIPT
Jorge PEREIRAHead Civil-Military CNS Unit, CMAC Division, Directorate Single SkyEUROCONTROL
Presentation on
Civil-Military SWIM Interoperability
2nd Military CNS Information days
2
One Sky two Infrastructures ?
3
Interoperability Options have to be studied
MILITARY INFRASTRUCTURE
ATM(SWIM)
X
4
Communication versus SWIM Middleware
Layer 1: Physical
Layer 2: Data Link
Layer 3: Network
Layer 4: Transport
Layer 5: Session
Layer 6: Presentation
Layer 7: Application
Physical / Link
TransportTransfer
Physical / LinkA/A, A-G, G-G
TransportTransfer
(TCP/UDP/IP, TP4…)
Application
CommunicationApplication N
TPSM
TPEt
c…
ApplicationCPDLC, SDPSFPPS, ODS,AMHS, VCS?…
Net
wor
k Su
perv
isio
nV
oice
Communications: SESAR Project 15.2.10
SWIM: SESAR Projects 14.1.3, 14.2.2, etc.
5
Objectives/Activities:
Refine and verify a secure terrestrial communications network for all voice and data exchange applications including SWIM
Work ongoing with focus on SESAR VPN
Interoperability with military systems over PENS is a key aspect (protocols, ICD, addressing scheme, directory service, security, multicast VoIP, etc.)
OSI Layers: Physical, Data Link, Network
Supports FMTP, AMHS, AFTN, Flight/Traj. Data, Meteo, AIS, Voice, Radar data, etc.
Military Application considered: Airspace management System (LARA)
WP15.2.10 Terrestrial COM Infrastructure – SWIM Backbone
6
Project 15.2.10 Terrestrial COM Infrastructure – SWIM BackboneActivities:
Work ongoing with focus on PENS SESAR VPN, PENS end-to-end performances, security and use of IP multicast for ATC communications
Final goal is to validate an all-IP terrestrial communications network for all voice and data exchange applications including SWIM
Military Interoperability will be vital !
National Expert (MEPS) will attend next meeting.
Status:
SESAR VPN Infrastructure Tests covered FMTP, AMHS, VoIP, TCP, UDP and LARA. LARA (WA2) trials completed in February 2012
A report with test results was delivered (D3)“LARA application tests: The overall test result is really good and the application was running stable on the network. The
interchange of the data between Maastricht and Madrid was also fast and we had no visible faults”
Current activities focus on security (SRA and coordination with 14.2.2), IP multicast, VoIP
Surveillance multicast tests are being coordinated
Indra(PM), Enav, Aena, DFS, Frequentis, Selex, DSNA, Eurocontrol, Selex. 15.2.10 will offer the network backbone for SWIM as part of a wider all-IP solution for ATM. Military participation is key !
7
SWIM Application InterfaceSWIM Application InterfaceProprietaryProprietary
SWIM InterfaceSWIM InterfaceStandardStandardServices Services -- ISRMISRM
SWIM SWIM –– Service Oriented ArchitectureService Oriented Architecture
PAO Leiden - 3.12.1999 8
NMNMNOPNOP
AirportAirport
SWIM infrastructure
WSWSClientsClients(AOC,GA(AOC,GAAIS, AIS, ……))
ATCATC(MUAC)(MUAC)
ATCATC(Thales)(Thales)
ATCATC((IndraIndra))
EADEAD
SWIM infrastructure
Different types of SWIM Different types of SWIM usage / needsusage / needs
Map SWIM needs with Map SWIM needs with potential set of supporting potential set of supporting technologies & services technologies & services optionsoptions
SWIM Step1 profilesSWIM Step1 profilesFO/IOP ProfileFO/IOP ProfileNOP/B2B ProfileNOP/B2B ProfileEAD/B2B ProfileEAD/B2B Profile
Multi TechnologiesMulti Technologies
SWIM SWIM –– One Solution does not fit AllOne Solution does not fit All
9/
Civil-Military SWIM Interoperability Study
Characteristics of Military ATM and AD/C2 systems and the justification for their interoperability with SWIM
Target SWIM Interoperability Concept and Architecture
Detailed technical civil- military SWIM Interoperability Requirements
Prototyping and V & V Plan
D1
D2
D3
D4
Study supporting Eurocontrol input to SESAR SWIM Design. Awarded
to Helios, UvE
Ltd and Object Security. June 2011 to Sept 2012. Dissemination workshop
on 5 Sept 2012.
10/
Military EntitiesCivil Entities
Civil Airspace Users
ANSP
Airline Operations
Airport
Remote Sensors
CFMU
Military Airspace Users
Military ATC
ARS
CAOC WOC SQOC
Airbase
AOCC
SAMOC
Remote Sensors
AirspaceManagement & coordination
Control
GAT flight plan
AirspaceManagement & coordination AMC
Surveillance Data
10
Interaction Between Military and Civil ATM and AD C2 Entities
11/
What is SWIM in this context?
11
12/
Interoperability of the SWIM middleware
12
SWIM Middleware
13
Civil-Military Interoperability Through Model Driven Development
Proxy Provider
Flight
Surveillance
Airport
Environment
Capacity
AIM
Flow
Weather
System #1 System #2
Federated technical service
SWIM service
SWIMservices
SWIM services
System #7
System #8
System #4
System #6
System #5
System #3
14/
Civil-Military Interoperability
From the IOR model, we learned that military systems can be integrated into SWIM like civil systems
Very similar information flows
Concept of SWIM Nodes can be applied
There are some important specific requirements
Information format details
Security
We expect a lot of detail technical problems with practical integration
But this is not in the scope of this study
15/
Security
The big difference: Security!
For the military, security is most important
Without sufficient security, the military will not be willing to connect to SWIM
Trust is the main question!
The military will not trust others to protect key assets
But without a sufficient level of trust, integration of military systems into SWIM is not possible
16/
Military Security Requirements
The military has strong security requirements for SWIM and also for the civil systems connected to SWIM which communicate with the military
Confidentiality, integrity and availability
But are these additional security requirements?
We believe no!
SWIM needs to be able to enforce the standard security requirements anyway
No penetration and no disclosure of classified information have to be based on the military's own abilities
17/
Characteristics of Military ATM and AD/C2 systems justify the need for interoperability
with SWIM
A civil-military interoperability concept accommodating SOA will be based on gateways providing the functionality of a SWIM
node
The architectural implementation is complex
and needs to be
assessed in a realistic environment
Applying the concepts of Model-Driven Development
to SWIM
should be considered from a Requirements Engineering Management perspective
As a preliminary finding no additional military security requirements
(for penetration, confidentiality, integrity,
availability) up and above the SWIM standard security requirements and own military abilities are identified. This statement needs to be verified upon full definition of the SWIM standard security requirements.
Civil-Military SWIM Interoperability Study - Draft Conclusions (1) -
18/
A SWIM middleware prototype
would be required to be built and tested for a selected set of SWIM services to verify the proof of principle of civil-military interoperability
When used, the application of MDD in the definition and introduction of new SWIM services
will be validated
Validation & Verification
should include a demonstration of the implementation of a SWIM middleware prototype in a real-world operational environment
V & V should also confirm a concept for potential security accreditation
Civil-Military SWIM Interoperability Study - Draft Conclusions (2) -
Next Steps:- Address prototyping and validation- Progress security work- Verify adequacy of information formats
19/
Can we think out of the box !Can we think out of the box !
