The document provides an overview of the BUTLER project, which aims to design and demonstrate a comprehensive context-aware information system that operates seamlessly across various smart scenarios. The 3-year project will begin with defining vertical and horizontal use cases and requirements. It will then specify and develop the necessary technological enablers and platform architecture in subsequent years, integrating the platform through field trials in the final year. Key scientific advances planned include work on privacy and security, behavioral modeling, geo-temporal contextualization, and contextual networking. The project also outlines plans for standardization contributions and cooperation with other organizations.

1. PROJECT PRESENTATION

2. uBiquitous, secUre inTernet-
of-things with Location and
contEx-awaReness
FP7 call: FP7-ICT-2011-7
Integrated Project
October 2011  September 2014
15 M€
1234 man.months
2

3. High level objective
Design and demonstrate prototype of a
comprehensive, pervasive and effective Context-
Aware information system, which will operate
transparently and seamlessly across various
scenarios towards a unified Smart Life
environment.
3

4. Today: Domain-centric smart solutions
SmartHome SmartTransport SmartShopping
- Monitoring and - Promoting - Managing
controlling carpooling sparkdeals
- Saving Energy - Minimizing taxi - Getting advice on
comfortably delays buying goods
- Interacting with - Avoiding traffic - Retrieving
appliances jams discount
-… -… ! -…
SmartHealth SmartCity
- Monitoring medicine
- Managing parking
intake
space
- Personalized
- Lighting up a city
diabetes assistance
efficiently
- Providing training
- Monitoring Air
tips
Quality
-…
-…
4

5. What should Smart Life be?
5

6. Tomorrow: horizontal smart solutions
SmartLife
6

7. Expectations
Crimes Privacy violation Squandering
Congestion
Stress
Diseases
Latency inefficiency
Pollution
Poverty
SmartHealth
SmartShopping SmartTransport
SmartHome SmartCity
7

8. Awareness
Inversely proportional to the degree of knowledge required
from users
BUTLER’s concept is one of
active, pervasive, continuous,
real-time and progressively
personal context-awareness
8

9. TECHNOLOGICAL CHALLENGES

10. Technological Challenges: Communications
Application Application Application
1 2 °°°° N
Application/Data
Layer ONEM2M/ETSI M2M Service Layer
HTTP CoAP SEP 2.0
ZigBee
Transport Layer TCP TCP/UDP
NWK Layer RPL IPv6
6LoWPAN
3GPP
Bluetooth 4.0
Low Energy
DataLink Layer
RFID/NFC
802.15.4
Wi-Fi
IEEE
PHY Layer
10

11. Integration & Standardization
11

12. Innovation: Technological Enablers
SmartHome SmartTransport SmartShopping
- Monitoring and - Promoting - Managing
controlling carpooling sparkdeals
- Saving Energy - Minimizing taxi - Getting advice on
comfortably delays buying goods
- Interacting with - Avoiding traffic - Retrieving
appliances jams discount
-… -… ! -…
SmartHealth SmartCity
- Monitoring medicine
- Managing parking
intake
space
- Personalized
- Lighting up a city
diabetes assistance
efficiently
- Providing training
- Monitoring Air
tips
Quality
-…
-…
12

13. PROJECT WORKFLOW

14. Year 1 : From Vertical Requirements to a
First Horizontal System Specification
Vertical and Functional and Specification and
horizontal use-cases Non Functional development f1
Requirements
analysis
• Domain specific
enablers
• Generic enablers
o Security
o Localization
Smart o Context,
behavior)
Life
• Initial
architecture
• First proofs of
concept

15. Year 2 : Refined Specification and
Development of the Platform
Vertical and Functional and Specification and
horizontal use-cases Non Functional development f1
Requirements Specification and
analysis development f2
• Domain specific
• Technological
enablers
choices
• Generic enablers
o Security
• Refined
o Localization
specification of
Smart o Context,
Trials
behavior)
Life • Integrated
middleware
• architecture
Initial
Vertical architecture
••First proofs of
2nd proofs of
Scenarios concept
concept

16. Year 3 : Integrating the Platform into
real life field trials
Vertical and Functional and Specification and Integration and
horizontal use-cases Non Functional development f1 testing
Requirements Specification and
analysis development f2
Specification and
• Domain specific
Final field
development f3
enablers
• • Technological
Generic enablers trials
o Security
choices
• Refined
o Localization
Smart •Smart Server
o Context,
specification of
• Trials
behavior)
• •Smart Mobile
Integrated
Life •Smart Object
middleware
architecture
•• 2nd proofs of
Initial Integrated
Vertical architecture
concept platforms
• First proofs of
• Prototyping of
Scenarios concept
enablers
Horizontal • Testing with
measurable
Scenarios goals

17. From Vertical Use Cases to Smart Life Concept
17
SmartMobility SmartHealth SmartHome /
SmartShopping SmartCity
/ Transport / Wellness Office
Horizontal Horizontal Horizontal Horizontal Horizontal
UCs UCs UCs UCs UCs
Aggregate results from Verticals
Smart Live Concept: Horizontal Story Line incl. Personas Customer Insights
Business Requirements IoT Butler
17

18. Project Global Workflow
End-
Users
Use Cases
Partners’
Assets
User
Requirements
State of the
Art
Vertical
PoCs
Technical
Requirement End-
Users
Specify Vertical Field
Trials
Specify (Technical) Horizontal
Architecture
Define
Implement Horizontal Horizontal
Integrate Platform PoC
End-
Validate / Provide feedback Users
Enabling
Technologies
Horizontal
Field Trial
18

19. PLANNED SCIENTIFIC ADVANCES

20. Privacy and Security (1/2)
User shall be able to manage its distributed user profile.
• Control of identity sharing over distributed applications.
• Control of data duplication – when and where
• Implementation of regulation
• Controlling dynamic inference of user data - identity, current
behavior, system computed user profile.
Defining security and privacy requirements to be taken into
account as design level.
• Design and implementation of BUTLER privacy and security
framework.
• Framework integrates user dynamic data (location, behavior, …) in
security protocols
• Application shall integrate such framework

21. Privacy and Security (2/2)
1. Main objective: user controls/manages its profile
Application 1
Static and
Dynamic
Distributed
2. Applications use/update
User Profile
Application 2

22. Behavioural modelling and mining (1/3)
Recognize context-aware intent through external observation
• Behavior
• Decisions
• Typical course of actions
• Corresponding events and context
Extract meaningful information from distributed event streams
• Purposeful and meaningful abstractions for daily life activities
• Interactions between a few individuals and mass behavior
• Algorithms and software components for aggregation,
classification, learning, predicting and anticipating users’
behavior and activities
• Metrics to assess quality or trustworthiness of information

23. Behavioural modelling and mining (2/3)
events events
1. Model
events Actions
Profile &
Preferences
Context Intentions Behavior
3. Anticipate
Tasks 2. Observe and learn

24. Behavioural modelling and mining (3/3)
New event-based modeling abstractions
• Represent both individual and group behavior
• Explore feasibility of hybrid models combining statistical and
relational models, task trees, workflow and markov models,
dynamic bayesian networks, …
• Semantic modeling abstractions to describe domain knowledge in
relevant (patterns of) events
New processing and synthesis techniques
• Context-aware and semantic event pattern recognition
• Causality detection to anticipate human behavior
• Learning and data stream mining based on complex event
processing techniques (CEP)

25. Geo-Temporal Contextualization (1/2)
Aim to develop algorithms for the seamless acquisition of
geo-temporal information in heterogeneous networks, clearly
defined as following objectives.
Objectives
– Identification of the forms of geo-temporal context information
– Tracking and localize the context information securely
– Simultaneous localization and mapping through cooperative P2P links,
with new location-dependent security mechanisms
– Energy/time-efficient indoor localization within heterogeneous
networks
25

26. Geo-Temporal Contextualization (2/2)
Workflow
– Concrete algorithms be developed to enhance acquire geo-temporal
context with the help of objects, topology, etc…
– Development of corresponding algorithms on real platforms
Domain Specific Objectives
– Provide ambient information about metro platforms when the user
reaches the station entrance, for users located on station platforms.
– Schedule planner - plan the user departure according to user's
agenda, traffic conditions and parking availability.
26

27. Contextual networking
Aim is to develop algorithms to provide contextual information at a macro-
perspective, focusing on contextualized networking strategies, behavior
synthesis (crowd management, incentives) and “contextual games” model to
predict users’ behaviors.
Generic workflow
– Cooperate with the other tasks and create the use cases for the
applications and services;
– Create concrete algorithms to be utilized in such use cases;
– Algorithms brought forward to the implementation tasks;
– Results validations by using the prototypes generated in the
implementation tasks
Domain specific objectives
– Shopping environment related modelling of consumer groups
– To be able affect consumer behaviour via context based targeted
advertising and offers
– Other objectives: to be further studied
27

28. STANDARDISATION AND COOPERATION

29. BUTLER cooperation plans Joint
trials
{
BUSINESS
TECHNOS
TRIALS
IMPLEMENTATION
ARCHITECTURE
...

30. Planned contributions and interactions
• Active participation in key standardization group in Europe and
world-wide on M2M service layer
– ETSI TC M2M
– ETSI TC ITS
– M2M Partnership Project (under creation  technically operational in July 2012)
• Promote the BUTLER M2M service layer solutions and building
blocks in the relevant groups
• Deploy a standardized service layer in the projects
development in order to better influence the standards
• Participate in the standardization of verticals like:
– Continua
– BBF (Broadband Forum)
– ETSI TC ERM (TG28, TG34, TGUWB)
30

31. World-Wide M2M partnership project
• World-Wide standardization of a M2M service layer
• Initial cooperation between the following SDO:
– ETSI (Europe)
– ARIB (Japan)
– TTC (Japan)
– ATIS (US)
– TIA (US)
– CCSA (China)
– TTA (Korea)
• Vertical are invited to the work like ITS,
Continua, ESMIG, etc.
31

32. Schedule for M2M Partnership Project
2011 2012
JUL AUG SEP OCT DEC JAN FEB MAR APR MAY JUN JUL AUG SEP OCT
SDO Meeting#01, SDO Meeting#03, Technical Plenary
Virtual meetings
Seoul, 21 Jul Berlin, 15-16 Dec Meeting#1
SDO Meeting#02, Steering Committee Steering Committee
Washington, Meeting#1 Meeting#2
17-18 Aug
Virtual SDO meetings
SDO Meeting#04,
Tokyo, 28-29 Mar
Reach out to verticals
Start of technical work
M1: “Soft Launch”
M2: Final Consensus
M3: Final Draft
M4: Official Signing
M5:
TP start prepared
M6:
WG start prepared
Copied from the ETSI /M2M(12)18_009
32

33. GETTING MORE

34. Connect with BUTLER
• www.iot-butler.eu :
– Learn about BUTLER
– Follow progresses
– Partnerships
• BUTLER on social networks :
– Twitter: https://twitter.com/#!/IoTBUTLER
– LinkedIn: http://www.linkedin.com/groups/BUTLER-
4205902
34