INTEGRATION WITHIN COGNITIVE SYSTEM
APPLICATIONS
David Moreno Huerta
Atos, Atos and fish symbol, Atos Origin and fish symbol, Atos Consulting, and the fish symbol itself are registered trademarks of Atos Origin SA. March 09
© 2006 Atos Origin. Private for the client. This report or any part of it, may not be copied, circulated, quoted without prior written approval from Atos Origin or the client.
Agenda
1. Overview
2. Cognitive System Application
3. SCOVIS Overview
4. Expected Results
5. Scenario Application
6. Integration process
7. Conclusions
2
Barcelona, January 2009
Overview
» The purpose of this presentation is to give and overview
the integration process for a certain cognitive system
application by explaining “why” we needed to implement
a cognitive system solution and the most important
“how” to implement the most suitable solution for this
one.
» This explanation will be based in the SCOVIS project
challenges.
» We will explain about the approaches achieved until
now and the future implementation activities to deal
with.
» The following slides will be focused to the Smart System
Integration topics
3
Barcelona, January 2009
Cognitive System Application
» What is a Cognitive System??
» Is one that utilizes psychologically plausible
computational representations of human cognitive
processes as a basis for system designs that seek to
engage the underlying mechanisms of human cognition
and will be capable to create new knowledge according
the environment relationship (self-adaptive)
4
Barcelona, January 2009
Cognitive System Application SCOVIS
» Self -configurable COgnitive VIdeo Supervision
» SCOVIS will significantly improve the versatility and the
performance of the current monitoring systems for
security purposes and workflow control in critical
infrastructures.
» It will be based in pattern images recognition in order
to detect abnormal behavior (non acceptable
pattern) within the scenario monitored.
» More details: www.scovis.eu
5
Barcelona, January 2009
SCOVIS in a Nusthell
6
Barcelona, January 2009
Expected Results
» A methodology and an open architecture for largescale camera networks based in:
» A toolkit for weakly supervised learning and object
detection.
» A toolkit for camera network coordination.
» A toolkit for behavior analysis.
» A toolkit for adaptation mechanisms.
» An integrated solution of the all above toolkits and
will demonstrate the benefits of the proposed
synergies.
7
Barcelona, January 2009
SCOVIS Performance
Time t
Time t+∆
∆t
8
Barcelona, January 2009
Scenario Application – “Process for
being monitored” Nissan Factory
9
Barcelona, January 2009
Toolkits to be implemented
Images
patterns
Information
They need
to exchange
their data
10
Barcelona, January 2009
System to be integrated – “What to
integrate???”
HOW TO???
Multimedia
11
Barcelona, January 2009
Knowledge
Behavior Patterns
Integration Issues
» The current solution to implement has multi-platforms
skills
» Independent toolkits need to share their data
» We need to identify a suitable way for sharing all this
data
» This solution need to be as light as possible regarding
the heavy data sharing to process (media files).
» They language communication must be as
standardized as possible: XML patterns
12
Barcelona, January 2009
What to integrate? – Technical
Resources
FRAMEWORK INTEGRATOR
13
Barcelona, January 2009
Analyzing a suitable solution
» Web-Services (too much overhead)
» CORBA (steep learning curve)
» Custom (risky)
SOLUTION:
We need something interoperable and cross-platform
14
Barcelona, January 2009
Possible solution for message
exchange
» JNI seems to be the only solution because
» Java and C++ communication
» JMS (Java Messaging Service)
» JMS has been improved to OpenMQ (Java System
Message Queue 4.3)
» Does not need a Web/Application Server to deploy
like Web Services
» Nice, Documented API
» Good for text messaging (i.e. XML exchange)
15
Barcelona, January 2009
OpenMQ = suitable solution
16
»
Open message queue is an
enterprise quality, production
ready, scalable messaging
server.
»
It provides a complete Java
Message Service (JMS)
implementation for message
oriented system integration
»
Loosely coupled messaging
between enterprise system
components
»
Scalable distribution of
message servers (broker
clustering)
»
Integrated SOAP / HTTP
messaging
»
Java and C Client API
»
Enterprise Administration
Features
Barcelona, January 2009
Conclusions
» OpenMQ will be adapted into our integration process
» Every toolkit will be taken as a black box
» The most important will be the input and output
information between them.
» For the moment it looks like the suitable exchange data
method.
17
Barcelona, January 2009
Thanks!!!!
[email protected]
http://www.es.atosorigin.com/
18
Barcelona, January 2009