Event-Driven Architecture Masterclass: Engineering a Robust, High-performance...
FP7 iCore project presentation
1. iCore Project Number: 287708
Internet Connected Objects for
Reconfigurable Eco-systems
iCore Presenation
Dr.-Ing Abdur Rahim Biswas/ Prof. Kalus
Moessner
1
iCore + Butler joint workshop
07th October 2011
2. iCore
o
Outline
Empowering IoT through Cognitive Technologies
Consortium
Introduction
iCore framework
Technical approach
Work organization
Applicability
Potential synergies with Butler
iCore + Butler joint workshop
07th October 2011
3. iCore
o
Project Outline/Consortium
Empowering IoT through Cognitive Technologies
Project outline
- Project type: Integrated Project
- Duration: 36 months
- Total cost: €13.4M (59%
industry)
- EC requested funding: €8,5M
- Resources: 1,332 PM (111 FTEs)
Consortium
- Coordinator: CREATE-NET (Italy)
- 20 partners ( including NTT)
- Strong industry participation (12
companies)
- 12 countries (including
China/Japan
- External stakeholders group (use
cases)
3
iCore + Butler joint workshop
07th October 2011
4. Future iCore worlds of IoT
iCore
o
Empowering IoT through Cognitive Technologies
What are “things”?
“Things”= Real objects + Digital devices
Yes
Maybe
GPS
4
iCore + Butler joint workshop
07th October 2011
5. iCore
o
Reusability of IoT
Empowering IoT through Cognitive Technologies
Q1: Can we reuse IoT outside the scope in
which they were originally deployed
“A kitchen knife daily used to cut food.
What about if it could act as a
screwdriver, and it could also be an
envelope opener”.
Q2: Can we combine various objects and
use for new applications
“temperature sensor” ( indoor
temperature monitor/control) +
“humidity sensor” ( adjust cooling) = >
city weather forecasting, city
temperature mapping
5
iCore + Butler joint workshop
07th October 2011
6. …
iCore
o
Virtual representation and cognitive
Empowering IoT through Cognitive Technologies
virtual representation of real and digital objects
……without the virtual mind
6
iCore + Butler joint workshop
07th October 2011
7. iCore
o
iCore concept
Empowering IoT through Cognitive Technologies
Open cognitive framework for the Internet of Things
(IoT) addressing three levels:
i) Virtual Objects (VOs): Virtual representations of
real-world objects
ii) Composite Virtual Objects (CVOs): Cognitive mashups of multiple VOs
iii) Users/stakeholders perspectives
7
iCore + Butler joint workshop
7th October 2011
8. 8
iCore + Butler joint workshop
iCore
o
Overall framework
Empowering IoT through Cognitive Technologies
07th October 2011
9. iCore
o
iCore technical challenges
Empowering IoT through Cognitive Technologies
Addressing interoperability issues through
9
VO/CVOs
Increase the reusability of objects outside the
scope in which they were originally deployed
Increase reliability and availability of services
Increase energy efficiency
Allow Business integration on the view of
multiple stakeholders in the composition of
services
iCore + Butler joint workshop
7th October 2011
10. iCore
o
Technical approach
Empowering IoT through Cognitive Technologies
VO and CVO:
Cognitive mechanisms (self-management and
learning capabilities)
Sensing and context/resources extractions
(computing, storage, profile, etc.)
Offering access to information and knowledge on
the RWO/DWO context from service point of view
Semantic descriptions of the virtual and composite
virtual objects
The possibility of sharing data and resources in the
IoT, which through iCore becomes application domain
and initial context agnostic
07 October 2011
th
10
iCore + Butler joint workshop
12. iCore
o
Technical approach
Empowering IoT through Cognitive Technologies
• Cognitive mechanisms are used to create the service
logic based on the user/application requirements and
preferences
• Service logic instantiates the reconfigurable application
on the CVO fabric
• CVO fabric looks up and discovers appropriate VO/CVO
or deploys mechanism for composition of new CVO
• VO fabric creates and manage the semantic description
of VOs
• Cognitive mechanisms in VO factory are used for
objects awareness and maintain the handled to VO
12
iCore + Butler joint workshop
07th October 2011
13. Technical approach
iCore
o
Empowering IoT through Cognitive Technologies
Alignment with EU IoT activities,
Overall cognitive process optimization,
Architecture reference model
iCore security
Context awareness,
cognitive process
technologies
Service logic
factory
Complex event prosessing, service
Cognitive
composition technologies
management and control
framework
CVO
CVO
User
context
registries
CVO
registries
User level cognitive
processes
CVO level cognitive
processes
Semantic technologies
for maintaining the
handle to Virtual Objects
VO
VO
VO
VO
13
iCore + Butler joint workshop
VO
registries
VO level cognitive
processes
7th October 2011
14. Work organization
iCore
o
Empowering IoT through Cognitive Technologies
WP8 Management and co-ordination
WP7 Dissemination and exploitation
Cluster C: Management and impact generation
WP3
Virtual object management
WP9
Demonstration and Testing
WP4
Composite virtual object
management
WP6
Use case implementation
WP5
User level cognitive mgmt
and control mechanisms
Cluster B: Implementation
WP1 Socio-economic and
technical aspects and evaluation
Cluster D: Use case definition and business relevance
14
WP2
Cognitive
management
and control
framework
for IoT
Cluster A: Technology research design and optimisation
iCore + Butler joint workshop
7th October 2011
15. Vertical iCore frameworks
iCore
o
Empowering IoT through Cognitive Technologies
iCore frameworks can be used by many parties and type of users and
stakeholders ( across vertical application/usage areas)
Stakeholders/service providers roles
•A real world (RO) or digital
world (DW) may be owned
(controlled) by a particular
stakeholders
• Virtual object ( VO) may be
owned or controlled by
particular service provider
• Composite virtual object
(CVO) may be owned
(controlled) by yet another
service provider
15
iCore Negotiation
2nd May 2011
16. iCore application domains
iCore
o
Empowering IoT through Cognitive Technologies
This virtual objects framework will be defined independent of
a particular application domain or use case
Su
ch pp
ai ly
n
bu Sm
si ar
ne t
ss
ity
e
to
ffi
c
su ee
pp tin
or g
t
ar
tC
M
ar
rt
po
ns
iCore + Butler joint workshop
iCore generic
business cases
Sm
16
16
a
Tr
of car
Smart home-Living assistant
Smart office- Easy meeting
Smart business-Supply chain
iCore
Framework
and
mechanisms
Vertical/
Domain specific
Use cases
Sm
Smart city/transport-Personalization
Sm
concept four use cases have been
selected for demonstration
ng t
vi an
Li ist
e
ss
om
A
th
ar
To show the applicability of the
07th October 2011
17. iCore
o
External Stakeholders Group
Empowering IoT through Cognitive Technologies
Stakeholder engagement in use cases:
iCore stakeholders involvement into two fold-
use case definition (TNO, TI, DoComo, WuXI,
Atos, etc); use case implementation -ALU,
CRF, Siemens, Atos, etc.
iCore external stakeholders group to provide
the business and technical requirements for
each of the use cases and later validation of
the use cases
17
iCore Negotiation
2nd May 2011
Editor's Notes
A large number of objects surrounding us, thing and sensor , a kitchen knife, screwdriver, envelope opener has has same feature, so can we use this for reuse this. Or A camera in the meeting room or sound systems can we make meeting of the minutes, etc… Another example, your location application say you are in bed and your multimedia or home light systems combing the time application say you are sleeping. Now it we combine this two application we can enable another applicattion block my credit card
If we want to reuse the objects, we will need to make digital representation of the objects, it it is just extracting the features, capabilities, functinalities of the objects.. … if we want to virtual a wine,, what we need virtual the color, etc.. If we can also virtualise the taste of the wine then maybe you can buy wine in online after tasting Yes, we can virtualze the thhing but problem come on opertion… how to use this virtual objects for particular application, what are the features are need to be virtuallize, how can we adapt and update the feature.. There is need some kind automation, cognitive brain who can observe, learn based on the previous hisotry and make a decision
Patients Want to Home status on Tuesday 6 PM- you want to know if I need to buy some or no, if my family memer is in home, tec.. Here is the application requirments and composition
Creating virtual objects… easy to make talk each others ofcourse there need to be interoperability in one to another VO or CVO
