swim-suit information models & services [email protected]
TRANSCRIPT
OverviewOverview
• This presentation refers to work in progress– It shows some directions the work on
the SWIM-SUIT prototype will go– It is the intention to raise some
questions related to FAA SWIM and to start discussion on topics being presented
15/05/2008 AP4/SWIM TIM, Brussels 2
OutlineOutline
• Information Models• Services
15/05/2008 AP4/SWIM TIM, Brussels 3
15/05/2008 AP4/SWIM TIM, Brussels 4
Information ModelsInformation Models
• Specification of Information Models– Goal of SWIM-SUIT project:
Reuse & Adaptation of suitable Information Models
• Usage of scenarios to identify requirements for prototype– Information to be contained in SWIM-SUIT
model– Technology to be used for data transport
including wire representation / serialization / marshalling
15/05/2008 AP4/SWIM TIM, Brussels 5
Information DomainsInformation Domains
• Information Model for Prototype limited to– Flight Data– Surveillance Data
Flight Model (FOIPS)
ATM Information Reference Model
Aero. Model (AIXM)
Services Services Services Services Services
Met. Model (WXXM)
Surv . Data (ASTERIX)
Cap.& Dem. Data
Services
ATFCM Scenario Domain
Models
ATM Reference Model
Flight Model
ATM Information Reference Model
Aero. Model
Services Services Services Services Services Services Services Services Services Services
Met. Model
Surv . Data
Cap.& Dem. Data
Services Services
ATFCM Scenario Domain
Models
ATM Reference Model
15/05/2008 AP4/SWIM TIM, Brussels 6
Information ModelsInformation Models
• Tasks– Create catalogue of available information
models• FOIPS / ICOG2• AICM4.5• ASTERIX Cat. 62• OATA
– Selection of information model and adoption for SWIM-SUIT
– Identify missing data items in available models– Create SWIM-SUIT information model
SWIM-SUIT Information SWIM-SUIT Information ModelModel
• Focus on Flight Data and Surveillance Data
• Reuse & Adapt ICOG2 Information Model– Rational Rose Model & Generated XML
Schemas– References to Environmental Data (AIXM)
• Experiment with non-conventional encoding of surveillance data– ASTERIX Cat.62 or XML
15/05/2008 AP4/SWIM TIM, Brussels 7
OutlineOutline
• Information Models• Services
15/05/2008 AP4/SWIM TIM, Brussels 8
15/05/2008 AP4/SWIM TIM, Brussels 9
Link to SWIM-SUIT Link to SWIM-SUIT ArchitectureArchitecture
• SWIM ATM Application services (access to added-value ATM functionality, e.g. CDM services)
• SWIM ATM Information Access Services (i.e. the “SWIM Virtual Information pool”)
• SWIM Core Technical Services (possibly based on standard IT middleware technologies)
• SWIM network (i.e. the physical pan-European network)SWIM Network
SWIM Core Technical Services
SWIM ATM Info Access Services
SWIM ATM Application Services
SWIM-SUIT Prototype scope
SWIM-SUIT ServicesSWIM-SUIT Services
• Communication patterns– Publish/Subscribe
• FOIPS Role Model– Example for domain specific Work Flow– Contributor, Manager, Publisher, User
– Request/Reply
15/05/2008 AP4/SWIM TIM, Brussels 10
SWIM-SUIT Architectural SWIM-SUIT Architectural IssuesIssues
• Data Transport vs. Data Storage• Core Technical Services affecting all
Service Layers– Lifecycle– Security
• Implemented by external system vs. Policy based
• Design issue– Evolution
• Protocol transparency15/05/2008 AP4/SWIM TIM, Brussels 11
Core Technical ServicesCore Technical Services
• Security– Authentication
– PKI & Identity Management
– Session Context / Key• Lifecycle
– Repository / Directory (LDAP)– User names, public keys, roles– Services
– Trader– Topic lookup
15/05/2008 12AP4/SWIM TIM, Brussels
15/05/2008 AP4/SWIM TIM, Brussels 13
Prototype Security Prototype Security AspectsAspects
• Security Aspects– Description of how SWIM-SUIT services
fulfils established security requirements• Authentication• Authorization• Access Control
– Description of how SWIM-SUIT information model fulfils defined security requirements• Encryption• Digital Signatures
SecuritySecurity
The SWIM-SUIT prototype• shall ensure that only authenticated external
systems can request information from SWIM-SUIT services.
• shall restrict access of external systems.• shall provide means to ensure information
integrity.• shall provide means to ensure information
confidentiality (fully or partial).• shall support a restricted form of PKI (local
certificate store should be sufficient).• should provide enforcement of appropriate
security policies.
15/05/2008 14AP4/SWIM TIM, Brussels
Model Driven SecurityModel Driven Security
• Models for security of prototype– Trust relationships– Policies for information flow, access
control, etc.
15/05/2008 15AP4/SWIM TIM, Brussels
Security Framework Security Framework (optional)(optional)
• shall allow to specify security policies• shall support policy enforcement
points (=agents)• shall automatically generate low-
level rules for enforcement points• shall detect policy violations
15/05/2008 16AP4/SWIM TIM, Brussels
LifecycleLifecycle
The SWIM-SUIT prototype • shall utilize a service for storage of user data
and meta information.• shall provide a trader service to register
interest for entities fulfilling specified selection criteria (e.g. XQuery expressions).
• shall provide indications that the set of entities has changed that is relevant to a trader user (= trader service)
• shall provide mechanisms/services to map entity identities to the underlying publish/subscribe infrastructure and its descriptors (= mapping service)
15/05/2008 17AP4/SWIM TIM, Brussels
LifecycleLifecycle
• Trader Service– Register queries to be updated when
objects become relevant based on specified criteria• Initial information about objects that fulfil
criteria but are not updated at the moment (bootstrapping)
• Mapping Service– Map object identities to technical
infrastructure (topics, etc.)
15/05/2008 18AP4/SWIM TIM, Brussels
15/05/2008 AP4/SWIM TIM, Brussels 19
Evolution supportEvolution support
• Ensure support of evolution of both Services and Information Models– Show evolution paths using typical
examples for• Services• Information Model(s)
Questions?Questions?
Thank you for your attention!
15/05/2008 AP4/SWIM TIM, Brussels 20