PROJECT PERIODIC REPORT€¦ · 1 PROJECT PERIODIC REPORT Grant Agreement number: 287901 Project...

1

PROJECT PERIODIC REPORT

Grant Agreement number: 287901

Project acronym: BUTLER

Project title: uBiquitous, secure internet-of-things with Location and context-awaReness

Funding Scheme: Collaborative project

Date of latest version of Annex I against which the assessment will be made: 2014-07-09

Periodic report: 1st 2nd 3rd X

Period covered: from October 1st, 2013 to October 31st 2014

Name, title and organisation of the scientific representative of the project's coordinator1:

Bertrand COPIGNEAUX, inno

Tel: +33 4 92 38 84 10

Fax: +33 4 93 65 41 35

E-mail: [email protected]

Project website2 address: http://www.iot-butler.eu/

1 Usually the contact person of the coordinator as specified in Art. 8.1. of the Grant Agreement.

2 The home page of the website should contain the generic European flag and the FP7 logo which are available in electronic format

at the Europa website (logo of the European flag: http://europa.eu/abc/symbols/emblem/index_en.htm logo of the 7th FP: http://ec.europa.eu/research/fp7/index_en.cfm?pg=logos). The area of activity of the project should also be mentioned.

Ref. Ares(2014)4046484 - 03/12/2014

http://www.iot-butler.eu/

http://europa.eu/abc/symbols/emblem/index_en.htm

http://ec.europa.eu/research/fp7/index_en.cfm?pg=logos

287901 BUTLER PPR Y3 01oct13-31oct14

Declaration by the scientific representative of the project coordinator

I, as scientific representative of the coordinator of this project and in line with the obligations as stated in Article II.2.3 of the Grant Agreement declare that: The attached periodic report represents an accurate description of the work carried out in this

project for this reporting period;

The project (tick as appropriate) 3:

X has fully achieved its objectives and technical goals for the period;

□ has achieved most of its objectives and technical goals for the period with relatively minor deviations.

□ has failed to achieve critical objectives and/or is not at all on schedule. The public website, if applicable

X is up to date

□ is not up to date

To my best knowledge, the financial statements which are being submitted as part of this report are in line with the actual work carried out and are consistent with the report on the resources used for the project (section 3.4) and if applicable with the certificate on financial statement.

All beneficiaries, in particular non-profit public bodies, secondary and higher education establishments, research organisations and SMEs, have declared to have verified their legal status. Any changes have been reported under section 3.2.3 (Project Management) in accordance with Article II.3.f of the Grant Agreement.

Name of scientific representative of the Coordinator: Mr Bertrand COPIGNEAUX

Date: 24/ 11 / 2014

For most of the projects, the signature of this declaration could be done directly via the IT reporting tool through an adapted IT mechanism and in that case, no signed paper form needs to be sent

3 If either of these boxes below is ticked, the report should reflect these and any remedial actions taken.


Revision History The following table describes the main changes done in the document since it was created.

Revision Date Description Author (Organisation)

V1.1 October 27th 14 Creation + WP7 contribution Camille Vidaud (inno)

V1.2 November 21st 14 Compilation Camille Vidaud (inno)

V1.3 November 24th 14 Review and final edition Bertrand Copigneaux (inno)


Table of Content

PUBLISHABLE SUMMARY 6

Concept ........................................................................................................................................... 6

Objectives ....................................................................................................................................... 7

Key results ....................................................................................................................................... 8

Main exploitation prospects ............................................................................................................. 9

1. PROJECT OBJECTIVES, WORK PROGRESS AND ACHIEVEMENTS, PROJECT MANAGEMENT 11

1.1. Project objectives for the period ........................................................................................... 11

1.1. Work progress and achievements during the period .............................................................. 12

1.1.1. WP1 Application Use Cases and Requirements for Pervasive Context-Awareness ............................ 12 1.1.2. WP2 Enabling Technologies for Pervasive and Secure Context-Aware Internet of Things ................. 13 1.1.3. WP3 Architecture of Context-Aware Networks .................................................................................. 21 1.1.4. WP4 BUTLER Platform Development and Implementation [TIL] ........................................................ 23 1.1.5. WP5 Integration and Testing ............................................................................................................... 27 1.1.6. WP6 Dissemination, Standardization, Education, Exploitation and IPR Management [FBC] .............. 32

1.2. Project management during the period ................................................................................. 34

1.2.1. Objectives ............................................................................................................................................ 34 1.2.2. Progress towards objectives ................................................................................................................ 35 1.2.3. Deviation from Plan ............................................................................................................................. 36 1.2.4. Changes in the consortium .................................................................................................................. 36 1.2.5. List of project meetings, dates and venues ......................................................................................... 37 1.2.6. Project planning and status ................................................................................................................. 38 1.2.7. Impact of possible deviations from the planned milestones and deliverables ................................... 39 1.2.8. Development of the Project website ................................................................................................... 39 1.2.9. Use of foreground and dissemination activities during this period .................................................... 39

2. DELIVERABLES AND MILESTONES TABLES 40

2.1. Deliverables.......................................................................................................................... 40

2.2. Milestones......................................................................................................................... 2-48

2.3. Explanation of the use of the resources and financial statements ....................................... 2-49


List of Figures Figure 1 - BUTLER work package overview ........................................................................................................ 8 Figure 2 - Interaction between AR, context-awareness and cloud computing for mobileAR applications .... 15 Figure 3 - Component diagram of the framework with clear separation of concerns .................................... 16 Figure 4 - Component diagram shows support for QoC .................................................................................. 16 Figure 5 - BUTLER Smart Platforms ................................................................................................................. 27 Figure 6 - BUTLER trials overview .................................................................................................................... 29 Figure 7 - The BUTLER platform was available for the IOT Week 2014 Hackaton participants ...................... 30 Figure 8 - BUTLER booths in IoT Week and IoT.360 ........................................................................................ 30 Figure 9 - IoT Week 2014 Hackaton................................................................................................................. 33


Publishable summary

Concept BUTLER’s concept is one of active, pervasive, continuous, real-time and progressively personal context-

awareness. Here is an example: “You are getting ready to go to work. You drink the last glass of milk and

push a bottom on the fridge’s touch-screen to indicate that that item is in demand. As you head out through

the door, your personal device running the BUTLER application automatically collects the data (also from

other home servers at the laundry room, bathrooms etc.) and updates your shopping list. On the way to

work, your personal device picks up traffic information from your navigation system (or from the display

system of your subway station) and calculates your time of arrival. Your BUTLER finds in your calendar that

you have a meeting that morning and pro-actively sends an SMS to your colleagues that you will be late.

Later in the day you have an appointment at a client’s location. As you arrive, your BUTLER exchanges with

your clients’ digital business cards. You closed the deal and are heading home! On your way out your

BUTLER informs you of a nearby store. As you enter the unfamiliar shop, your BUTLER downloads the

inventory and finds, in additional to the listed items, that your favourite wine is on a special! The item is

added to your shopping list as a suggestion. Your BUTLER also learns that this store has a particular brand

of milk freshly supplied. At home, your children have just arrived from school and consume several other

items (orange juice, bread, etc.), adding them to the server. Your BUTLER updates your list real time. As you

make the purchase – using your electronic wallet – your wife’s is informed that the shopping is done. She

may save her own trip to the store and go straight home! You get home early too and relax with a glass of

your favourite wine. Your children try the new brand of milk and love it! You add that brand as a preference

to the family’s BUTLER, who will know just where to find it next time…”

The processing power, penetration and multi-functionality required to bring the above vision to reality

already exist. Smartphones today already carry much larger processing power and memory than the NASA

computers equipping the Command and Lunar Modules of the Apollo 11 that landed on the moon in 1962,

and multi-cell processing technology offers a new paradigm to propel further growth powering the future.

The annual sales of smartphones are now exceeding that of PCs (including desktops and laptops). Finally,

not only smartphones are already typically equipped with multiple radio interfaces such as Wi-Fi,

Bluetooth, ZigBee and UWB, but also fourth-generation cellular networks (LTE) are now being deployed

bringing along femtocells, which will boost network penetration and promote the integration of various air

interfaces. This dense and high-capacity communication network will provide ubiquitous and fast Internet

access and interconnectivity amongst powerful smartphones and other devices.

Nevertheless, this digital expansion comes with drawbacks which could limit the potential exploitation if

not properly tackled. Three of them are considered as critical by the project BUTLER:

Information Overload: the sheer amount of information and the means to discover and benefit

from it is becoming been so vast that humans, no matter how technology-savvy, will not be able to

handle on their own.

Privacy and Security: if the probability of success in attacking a secure system is 1/X, in a network

of Y users the potential number of victims is still Y/X. In fact, the lack of privacy and/or security can

also be a serious deterrent to the penetration of future ICT technologies, since maintaining the

identity privacy, knowledge secrecy and asset safety are primary concern of every individual user

and business organization.


Consumption Management: individuals will have to cope with dynamically varying consumption

management (real-time price adjustments and temporarily restricted access to resources) by

adopting efficient and responsible ways to acquire and consume resources. This, in turn, will

require citizens to be timely and well informed about constraints and opportunities, putting further

pressure on the information overload challenge described above.

Objectives These lead to the three challenges that will be addressed by the project BUTLER.

- CHALLENGE 1: Personalized and Dynamic Demands: How to handle large and dynamically varying

demands for personalized services, goods and information with vast heterogeneity of context?

- CHALLENGE 2: Transparency, Privacy and Security in Heterogeneous Systems: how to maintaining

transparency to end-users while ensuring the privacy of users and security of information in such

heterogeneous environments, which in turn calls for universal mechanisms to provide secrecy over

communication channels at lower layers such as the network and physical layers?

- CHALLENGE 3: Collective Behaviour Modelling to Maximize Efficiency: How to optimize the impact that

ICT systems have in influencing human behaviour towards best practices?

BUTLER is an ambitious project with a long-term objective solidified by periodical field trials to make proof-

of-concept of concrete innovation, aimed at the development of pervasive and personalized context-

aware wireless technology. BUTLER holistic view is that of an ICT that becomes part of our daily life and

serves as a personal assistant (i.e., a “butler”) to all our needs. By means of multiple–radio interfaces,

BUTLER’s SmartMobile, SmartObject/Gateway and SmartServer platforms will allow a continuous channel

of access between users and service providers anywhere and anytime. The BUTLER bundle of applications

will therefore be an omnipresent companion ready to provide timely assistance to the users and virtually

limitless opportunities to businesses.

BUTLER addresses context-awareness with an integrated (horizontal) concept that includes location-,

semantic-, user-identity- and history-awareness. It achieves its objective by leveraging on the individual

know-how brought in by its partners on various specific use-cases (vertical), integrating, further developing

and optimizing them for pervasiveness into a unified solution that will serve users transparently throughout

multiple technologies and applications. To this end, BUTLER will tackle the issues of Behaviour Modelling,

Natively Secure Communication, Location-Awareness, Contextualized Services and Integration of Smart

Technologies.

BUTLER’s approach is to develop a natively secure, pervasive, energy-efficient and optimized context-

aware opened architecture, by bundling and integrating IoT technologies and services to transparently

learn and infer the behaviours and needs of users, acting on their behalf of and protecting them so as to

improve their quality-of-life.

BUTLER applications, integrated with the BUTLER Platform components, will be directed to final users

during field trials and will show them examples of how advanced contextualized services on their mobile

phone will help their everyday experience in different environments and use cases. As BUTLER is dealing

with a variety of end user applications implementing technologies that are yet to be adopted by

consumers, it is essential that real final users will be involved to collect feedbacks on the offered

functionalities throughout the project where the end user acceptance plays a major role.

To achieve these objectives the BUTLER project has been organized in seven work packages, focusing on specific tasks:


- Work Package 1 collects the project requirements based on the “Smart Life” use cases identified. It

provides the functional and non functional requirement of the other work package productions and

defines the field trials to set up. The Work Package 1 also identifies the possible business models of

these new “Smart Life” services.

- Work Package 2 focuses on the scientific challenges of the project: how to achieve security and

privacy in IoT? How to determine the context of an application: location, timing, history behavior

and preferences, to offer specific, relevant and targeted services to the users?

- Work Package 3 defines the architecture of the BUTLER Platform, in term of network, data

collection and processing, system management and services. With the goal to define an innovative

architecture that allows easy, seamless, secure and horizontal integration of various context-aware

services from different stakeholders.

- Work Package 4 deals with the implementation of the project reference platforms: “Smart Server”,

“Smart Object” and “Smart Mobile”.

- Work Package 5 focuses on the validation and the integration of the technology developed and the

set up of the proof of concepts and field trials necessary to validate the project platform based on

the specification coming from the Work Package 1.

- Work Package 6 works toward the promotion of the project through the participation to

standardization, dissemination and public awareness activities. It also deals with the exploitation of

the project result and management of the intellectual property created.

- Work Package 7 follows the administration, quality and impact of the project

The following chart sums up the vision of the project organization:

Figure 1 - BUTLER work package overview

Key results

The BUTLER project has been a major contributor to IoT research in Europe, over the three year of the project, the partners have published in more than 85 peer reviewed conferences, 18 peer reviewed


journals, and filled several patents. The project contribution to excellent research has been several times distinguished by “best papers awards” in international research conferences. Among the major contributions of the project, BUTLER has provided an integrated architecture model (Deliverable 3.2) for context-aware IoT applications, cutting across communication layers, integrating location, security and behaviour modelling, and addressing horizontal application domains. This architecture model is building on existing efforts such as FI-WARE and IoT-A and supported by other industry standards body, such as OMA, OAuth, SAML 2.0 or OSGi. The components of this architecture have been developed by the project in a modular approach, some reaching already a high level of technology readiness: The BUTLER gateway (Deliverable 4.3) provides a unifying platform that bridges the communication between the physical and virtual worlds. It provides an abstraction layer in order to access to IoT devices from various manufacturers using different protocols. The abstraction is based on a service oriented approach that allows better management of the dynamicity of the environments, easier and faster application development and other additional features such as service discovery, lookup, run-time binding and management. The project has gone up to the deployment of some of its technologies as field trials on various domains. This includes a large scale deployment in the City of Santander of the “Smart Shopping”] application: a system able to alert merchants about the optimal moments for sending notifications to citizens based on an analysis of city context information: city agenda, parking information, banking information, environmental data... As the project evolved toward field trial and lives deployments, the project has addressed several ethical issues related with the Internet of Things. A comprehensive analysis (Deliverable 1.4) of ethics, privacy and data protection in the IoT has been produced by the project. Together with the project guidelines for end users involvement (deliverable 1.2) and privacy enabling technologies (deliverable 2.1) they provide a complete framework for a responsible, privacy aware and user oriented IoT.

Main exploitation prospects As presented above, the BUTLER project has developed many exploitable results, and each member of the consortium has clear plans to exploit the result of the project (more than 40 individual exploitable items have been identified, with clear associated plans and TRL ranging from 5 to 9). In addition to these numerous individual opportunities, the project has developed common exploitation plans that will continue the most promising opportunities of the project and that for some of them already reach even beyond the existing consortium. The BUTLER project has initiated the Open Platforms initiative whose objective is to provide a far reaching, open and modular set of technologies for the development of the IoT. The BUTLER project has launched the Open Platforms portal (open-platforms.eu). The objective of the portal is to reference the open technologies that can be used to create Internet of Things applications but also to document their interoperability, relationships, and reference to existing use cases, infrastructures and deployments. This will enable the discovery, support and reuse of IoT component beyond the end of the projects. Newcomers to IoT application development will be able to discover existing models, libraries, tools, use cases, and deployments through complex queries including IPR, TRL, service level, and relationships with other components, effectively mapping the whole IoT Ecosystem. The open approach of a “platform of platforms” proposed here is a guarantee to address not only current foreseen IoT scenarios but also to be able to adapt to emerging needs. The BUTLER project has been joined by other EU project in this initiative, and the Open Platform Initiative has become a part of the IERC, as activity chain 1. Among the BUTLER components that will be part of the Open Platform initiative, some assemble important sub groups of the consortium, committed to an open source approach. They form the core of an open source community that will pursue together the developments of the project. The BUTLER Gateway is among the most comprehensive, assembling at least 7 members of the consortium. Each partner involved in these common initiatives has a clear plan and agenda, and some include the creation of spin-off start-up companies in a short term after the end of the project.

http://open-platforms.eu/


The project has also resulted in reinforced or new link between members of the consortium across the value chain of the Internet of Things, matching devices providers to integrated solution provider that reach the market. These future commercial connections have been enabled by the integration of the research results of the project and by the early deployments in the project trials. Through this process the SMEs of the consortium (ZigPos, TST sistemas, Maya technologies) have been able to develop new solution that will reach the market in a short time frame after the end of the project with direct link with other consortium members.


1. Project objectives, work progress and achievements, project management

1.1. Project objectives for the period Over the first year, the BUTLER project identified an extensive set of use cases for an horizontal Internet of Things scenario, the so called “One Day in 2020” scenario (presented in D1.1). From this deliverable the project extracted technical and non technical functional requirements that served as the basis for an analysis of the necessary enabling technologies of the IoT (presented in deliverable D2.1 for security, D2.2 for geo-temporal contextualization, and D2.3 for behavior modeling). The requirements also enable the definition of a first version of the BUTLER platform architecture (presented in Deliverable 3.1). To assess the feasibility of some of the scenarios a first row of initial Proof of Concept (also presented in deliverable 3.1) was also realized covering the different application domains (Home, City, Health, Transport, and Shopping). Over the second year, the BUTLER project first refined the specification of the project proof of concepts and field trials (presented in Deliverable 1.2), and selected based on the state of the art, the architecture and the defined use cases, the enabling technologies that will be integrated in the project platform (Deliverable 2.4). This was accompanied by further reflection and formalization of the ethics, privacy and data protection linked with the selected use cases (Deliverable 1.4). Based on these analyses and continuing the work of year 1, the project defined the final architecture of the Horizontal platform (presented in D3.2). This enabled the implementation of a first prototype of the project platforms: Smart Server (D4.1) Smart Mobile (4.2) and Smart Object/Gateway (D4.3), following the defined architecture model and using some of the enabling technologies selected. This prototype platform was used to realize a first integrated horizontal proof of concept based on the implemented platform, and following the spirit of the “One day in 2020” scenario (presented at the second review). In parallel the project defined a first draft of an exploitation strategy (D6.5) and continued its efforts on dissemination and standardization (presented in D6.2). The objectives of the third year of the project were thus to:

Finalize a second iteration of the platform in a fully integrated prototype with mature component

implementing the key enabling technologies of the project (security, localization, context

awareness): Described in Deliverable 5.1.

Analyze the benefits of the enabling technologies in the project, and the future necessary

researches to increase their contribution to the Internet of Things: Described in Deliverable 2.5

Provide a final documentation of the platform component and a first assessment of its technical

qualities (Deliverable 5.2)

Implement live field trials of IoT application based on the project platform and on the scenario

presented in year 1 (trials described in Deliverable 5.2, 6.6 and 6.3).

Provide an updated and clarified version of the exploitation strategy of the project (D6.5 v1.5)

Analyze the socio economic context and potential impact of the project (Deliverable 6.6)

Continue and extend dissemination and standardization activities (Deliverable 6.3)

Provide a final exploitation strategy, for the project as a whole, for exploitation of common results

and for individual exploitation by each actor of the project (Deliverable 6.3).


1.1. Work progress and achievements during the period

1.1.1. WP1 Application Use Cases and Requirements for Pervasive Context-

Awareness

Work package closed at the end of second period


1.1.2. WP2 Enabling Technologies for Pervasive and Secure Context-Aware Internet of Things

1.1.2.1. Objectives

Workpackage Planned (M25-M37): 102 Realised: 140 (not final figures) Leader: JacobsUni Participants: JUB, GTO, CEA, OU, ISMB, UL, KUL

Objectives of the last year of the project have been in general the improvement, but mostly evaluation and formulation of future perspectives of enabling technologies. In particular, the following objectives have been closely addressed:

Specification and the implementation of the security protocol (Gemalto)

NARVAL Update (UL)

Analysis of datasets captured by magnetic loops (sensors) in Luxembourg (Smart Transport, car traffic modelling and driver mobility forecasting) (UL)

Contribution to Deliverable D2.5 "IoT Enabling Technologies and Future Developments" (UL)

Deliverable D2.5 lead. (ISMB)

The role of context awareness and cloud computing on resource intense - augmented reality mobile applications (KUL)

Architectural support for HARD-BN (KUL)

Secrecy Analysis of cellular networks and WSNs using stochastic geometry and from an Information Theory point of view. (JUB)

Design of Orthogonal Golomb Rulers with Applications in Wireless Localization. (JUB)

Improvement of the Causal Framework including new means of Information Causality approximations. (JUB)

Prediction of Multi-variate stochastic processes. (JUB)

D2.5 contribution and review. (UOULU)

Design of a threat analysis model for IoT applications. (CEA)

Design and implementation of a “True” Random Number Generator (TRNG). (CEA)

Design of a lightweight bootstrapping protocol at application layer to deploy the constrained nodes at large scale. (CEA)

Integration of the bootstrapping protocol in the Butler open-platform (work in progress). (CEA)

Final refinement of alternative key management techniques adapted to ad hoc/decentralized networks and compliant with low cost/low power devices (i.e., Smart Objects), integrating context and/or physical information to security functions (CEA)

Design of a context-aware decentralized handover decision module for (intra-cluster) access points selection; Integration in a packet-oriented simulator (WSNet Tool) and validations in representative IEEE 802.15.4-based scenarios (CEA).

1.1.2.2. Progress towards objectives In the last year of the project, we have updated the implementation of the security library to provide more flexibility for applications without adding overhead. On partner request, the Security Library has been updated to support HTTP chunked responses. (Gemalto)


Gemalto participated to “Deliverable D2.5 - IoT Enabling Technologies and Future Developments » by describing the BUTLER Security Framework, the Security experimentations and the highlighted issues. In D2.5, Gemalto provided the study of Business and Market challenges and future developments related to the security aspects. (Gemalto) Addition of a new module focusing on interaction between Scilab and Mysql database (UL) Addition of a new module focusing on Geostatistical mapping (Regression, Kriging, Voronoi, Spatio-Temporal Correlation, etc.) (UL) Contributed to the D2.5 deliverable:

o Advanced Achieved o Challenges and future developments o Summary of issues highlighted in 6Lowpan security o Review of the security section (UL)

The third year of BUTLER project was also devoted to writing the deliverable D2.5, with ISMB playing a double role: coordinator of the activity as leader of D2.5, and contents contributor. A first ToC of the document was prepared by ISMB, then presented and discussed with the other involved partners during the plenary meeting held in Bilbao in February 2014. However, most of the effort devoted to the D2.5 preparation was concentrated between May and October 2014. On the one hand t he many Conference Calls organized in June and July allowed to further discuss and iteratively modify the structure of the report. On the other hand, preliminary contents covering approximately 80% of the expected document were inserted. ISMB coordination role emerged in assigning specific responsibilities to the different partners and in harmonizing the received contributions. In particular, ISMB prepared a Latex template of the deliverable and integrated the contributions drafted by the involved partners providing them with proper comments and suggestions for further refinements. At the end of July, the report included two main chapters: Chapter 3, titled ‘Advances Achieved in the Development of Integrated IoT Enabling Technologies’, and Chapter 4, titled ‘Challenges and Future Developments’. Concerning chapter 3, ISMB provided contributions regarding an Internet key exchange mechanism for IPSec in 6LoWPAN, a cooperative NLoS detection scheme and hybrid -cooperative localization algorithms. Even during the months of September and October 2014 ISMB organized several conference calls, one per week on the average, to check the progress of D2.5 status, discuss any item worthy of discussing, assigning new work and responsibilities to the other partners in view of the next conference call. In the second part of October, when most of the technical contributions were finalized and just minor refinements were expected, a review analysis was organized, according to two parallel directions. On the one hand, a general doc ument review was requested to INNO, which was not directly involved in writing technical contributions of D2.5. On the other hand, different partners were asked to review some sections which they had not contributed to. Concerning the technical contents, ISMB provided additional contributions regarding the already mentioned Internet key exchange mechanism for IPSec in 6LoWPAN and cooperative NLoS detection scheme and hybrid-cooperative localization algorithms, both integrated in Chapter 3, although in different sections. Finally, ISMB cooperated in identifying and discussing challenges and future research trends in the same topics (i.e., security and localization as enabling technologies of the Internet of Things). (ISMB) The resource limitations of mobile devices continue to impose constraints on the development of complex mobile applications. Performance and resource efficiency remains achallenge. We have investigated the resource utilization and performance trade-offs when extending an Augmented Reality (AR) application with context-awareness and cloud computing. The hypothesis is that the costs of these enabling technologies are worth the benefits they result in. As the BUTLER architecture supports three different platforms, such an analysis will guide the application developers for deploying their software components effectively and efficiently. We investigated the trade-offs that arise when combining AR, context-awareness and cloud computing with 1) the design


of a framework to reduce the resource load of general image-based AR applications and 2) an experimental quantization of performance and resource utilization trade-offs of a use case application. (KUL)

Figure 2 - Interaction between AR, context-awareness and cloud computing for mobileAR applications

Our measurements show that filtered image datasets obtained through context -awareness, result in lower latency and a reduced memory load when performing all AR computations on the mobile device. However, a cloud computing AR application does not benefit from in-depth context-awareness, as no part of the dataset is stored locally and the latency is approximately constant, relative to the Internet connectivity. A deployment strategy with respect to the Quality of Service (QoS) and Quality of Experience (QoE) requirements from the application's perspective, such as minimum latency and maximum reliability in terms of performance is essential to cater present trade-offs. (KUL) SAMURAI's security is enhanced by upgrading to the next version of Trust Manager. All the external APIs exposed by SAMURAI are protected by the BUTLER Trust Manager(TM) v1.3 whereas for the performance reasons (and lack of any major security threat), all the internal APIs remain unprotected. Other BUTLER SmartServers such as context brokers are considered as trusted entities i.e., they can utilize SAMURAI without getting authorization on behalf of the client applications. Hence, all BUTLER resources are identified with a single token (per resource). Based on our f eedback, now the security filter (TM) is adapted to support both regular events and server sent events, and chunked transfer encoding is made configurable at the method level. (KUL) The BUTLER behavioural SmartServer– SAMURAI–brings together various powerful building blocks for effective modelling and reasoning of user contexts and behaviours. We further investigate the necessity and the means to support dynamic deployment and re-configuration of multiple human activity recognition components based on context and resource availability to achieve optimal resource and recognition trade-offs.The unified framework will have the following key architectural support,

o Modular components with separation of concerns between domain knowledge, Machine Learning techniques, user/app specific models

o Caching with error propagation over time and other correlated contextual information

o Configuration manager with multiple pre-defined workflows to support dynamic performance Vs efficiency tradeoffs and to assist in cold starts. (KUL)


Figure 3 - Component diagram of the framework with clear separation of concerns

Figure 4 - Component diagram shows support for QoC

Product Line Engineering (PLE) inspired representation of domain knowledge provides a user friendly interface for both the developers and end-users to describe not only the relations between various components such as sensors, algorithms and corresponding contexts of interest but also to define various deployment policies. Furthermore, the deployment manager component supports pre-defined workflows to prevent any cold-start problems such as installing and re-booting the middleware, deploying and re-configuring classifier chains, modelling new user context, context value or data source and sharing or re-using models between users. (KUL) Secure communications in Cellular Networks: In cellular networks, the distribution of BSs follow terrain, as well as regulatory (city-plan), demand and space availability conditions, and therefore are far from (statistically) uniform. Furthermore, devices in urban areas served by pico and femto cells may be clustered together, for instance in and around shopping malls and train -stations), while devices in less populated areas served by macro cells are more sparsely located. Such conditions are clearly distinct from the random and uniformly distributed network assumptions that lead to a Poison number of nodes per unit area -- $i.e.$, the PPP model -- commonly adopted in current literature. In response to the limitations of the PPP model, we consider alternative models such as hard core and cluster process models to analyse the secrecy in cellular networks. (JUB) Design of Orthogonal Golomb Rulers with Applications in Wireless Localization: Ort hogonal Golomb rulers (GRs) are useful in a vast number of applications across various areas of engineering such as coding theory, radio astronomy and communications and pulse phase modulation. Yet, the design of


sets with multiple mutually orthogonal GRs is a problem that finds no solution in current literature. In this paper we present a genetic algorithm to solve this long-standing problem. Our solution is based on a modification of a classic GR-generation algorithm, which allows the construction of GRs out of constrained sets of marks, such that multiple orthogonal rulers can be obtained iteratively. A complete pseudo-code of the new algorithm is offered, along with examples that not only demonstrate its ability to solve the intended problem but also indicate a gain in efficiency over the classic algorithm even when applied to generate optimal GRs. An application example in wireless localization is also given, in which a Cram´er-Rao lower bounds (CRLBs) analysis of rangebased target localization is used to illustrate the remarkable gains that can be achieved by employing orthogonal Golomb rulers to perform efficient multipoint ranging. (JUB) Our causal modeling framework can be summarized into the following points:

o Estimation of the causality between each two time series X and Y based on a finite number of samples of both processes, i.e. XN and YN.

o Causal Graph Inference based on the information flow estimation in the previous point.

o Improvement of the structure inferred in the previous point. o Estimation of the root and child processes. o Reproduction and evaluation of the data. (JUB)

A threat modelling process composed of 6 steps has been detailed to handle the threat analysis for a given application of an IoT system. The first step consists in the analysis of the system architecture to identify the main components, sub-systems, trust boundaries and path of data flow. The second step consists in identifying the valuable assets to protect. The third step consists in the creation of the security profile of the considered application based on a depth analysis of the applications needs and its interactions. The fourth step consists in identifying the threats that could affect the application keeping in mind the goal of an attacker. To achieve this step, the STRIDE (Spoofing Identity, Tampering of Data, Repudiation, Information disclosure, Denial of service, Elevation of Privilege) classification could be employed. The fifth step consists in an evaluation of the risks that a valuable asset encountered. The last step is the estimation of the risk assessment and the impact. To highlight the threats that present the most significant risk, the DREAD (Damage potential, Reproducibility, Exploitability, Affected users, Discoverability) model could be used. This process should be employed before the development of each application integrated in open-platform. (CEA) According to the recommendations of Gutman to design a secure True Random Number Generator (TRNG), robust to the main attacks known, the CEA has designed an embedded TRNG based on the physical entropy sources studying during year 2. The TRNG has been implemented on a Wismote device over Contiki OS. As result, the random numbers obtained success the Statistical Tests of the NIST. Two categories of Random Number are available at output: The strong Random Numbers needs 300s to be forged. They are “True” Random Numbers used to generate seeds or cryptographic keys. The weak Random Numbers are always available and are used for nonce or padding. (CEA) The CEA has designed a lightweight protocol to bootstrap the nodes (SmartObjects) with the infrastructure at the application layer. This protocol could be used by a manufacturer to secure the data flow coming from its nodes. It is based on the use of an embedded TRNG, making the nodes autonomous to generate their cryptographic features, and the knowledge of an initial secret standing as “the manufacturer confidential public key”. This initial secret is shared by all the nodes of the manufacturer and is used only once during the bootstrapping phase. It enables an easy secure deployment at large scale as all the nodes are flashed with the same image and the same initial features. (CEA) The last objective is to integrate the previous work in the Butler open-platform and to interact with the security at high level (in the WAN). The integration is still under progress. (CEA) Studies regarding symmetric key generation using physical layer signals have been pursued and finalized in the specific context of Ultra-Wideband Impulse-Radio (as one of the candidate technologies for low power, low data rate wireless networks). Relying on the reciprocity and spatial


de-correlation of radio signals (i.e., channel responses in this case), decentralized symmetric keys distribution is achieved through channel probing, quantization and reconciliation. Over the 3rd year, two main improvements of existing UWB-IR key generation schemes have been achieved concerning the quantization and reconciliation phases. Firstly, randomness studies on the initial quant ization scheme for directly sampled UWB-IR signals have been performed and a new quantization scheme solving the deterministic bit pattern flaws has been proposed. Moreover, we investigated the trade -off between reciprocity (i.e., robustness) and randomness for multi-bit quantization of noisy simulated channel estimates. Finally, explicit radiolocation measurements (e.g., the Round -Trip Time of Flight) have been incorporated into the reconciliation scheme with the aim of masking the public exchanges. (CEA) A specific wireless protocol has been defined, adapting automatically and dynamically to its environment thanks to the combination of multiple contextual metrics. This protocol is compliant with a more generic cross-layer network architecture enabling dynamic interoperability and routing between heterogeneous clusters/networks (e.g., in large-scale SmartCities contexts). More precisely, the proposed decision module adapts in real-time the intra-cluster associations depending on the detected local and temporal context patterns (i.e., including nodes activity, mobility, energy autonomy, traffic, etc.) and provides a handover mechanism ensuring the stability of the whole network. The latter is based on Fuzzy logics and normalized quantitative decisions using gr ouped input metrics. This multi-context management decision module has been preliminarily validated in Matlab, before being implemented in an event-driven and packet-oriented simulation tool named WSNet. Results demonstrated the importance of managing mobi lity, showing connectivity gains within representative (large-scale) IEEE 802.15.4 scenarios for instance. Both the number of disconnections and the packet delivery ratio can thus be significantly improved, while maintaining relatively low average end-to-end delays in comparison with the standard (i.e., without context-aware decision module) (CEA).

1.1.2.3. Significant results

End of 2013, Gemalto has deposed a European patent “SYSTEM AND METHOD FOR SECURING MACHINE-TO-MACHINE COMMUNICATIONS - EP-13306900.5" (Gemalto)

Presentation ICACCI'14 "Towards a New Way of Reliable Routing: Multiple Paths over ARCs", Delhi, India, 24-27 September, 2014 (UL)

* Presentation CAE'14 "Scilab Modelling and Simulation of Communication Networks: Car Traffic Analysis in Luxembourg", 30th International CAE conference, Pacengo del Garda, Italy, 27-28 October, 2014 (UL)

* Poster (NARVAL), 30th International CAE conference, CAE'14, Pacengo del Garda, Italy 27 -28 October, 2014 (UL)

Zhoubing Xiong, Francesco Sottile, Roberto Garello and Claudio Pastrone: “A Cooperative NLoS Identification and Positioning Approach in Wireless Networks,” Proc. 2014 IEEE International Conference on Ultra-Wideband (ICUWB 2014), September 1-3, 2014. (ISMB)

Sarmad Ullah Khan, Claudio Pastrone, Luciano Lavagno and Maurizio A. Spirito: “A Secure On-Line Key Establishment Scheme for Mobile Heterogeneous Sensor Networks,” in International Journal of Distributed Sensor Networks, October, 2014. (ISMB)

Sarmad Ullah Khan, Luciano Lavagno, Claudio Pastrone, and Maurizio A. Spirito: “Online Authentication and Key Establishment Scheme for Heterogeneous Sensor Networks,” in International Journal of Distributed Sensor Networks, October, 2014. (ISMB)

The results are summarized in the paper submitted to 30th Symposium on Applied Computing (SAC'15). To cloud or not to cloud: A context-aware deployment perspective of augmented reality mobile applications. (KUL)


Contributions to the submitted book chapter on IoT success stories. How existing stand -alone products benefit from IoT platforms: Tecnalia’s experience with the BUTLER platform, Alberto Martínez et al. (KUL)

Satyanarayana Vuppala, W. Liu, T Ratnarajah and Giuseppe Abreu, “Secrecy outage analysis of cognitive wireless sensor networks,” IEEE Fourty-Eigth Asilomar Conference Conference on Signals, Systems, and Computers (ASILOMAR 14), Pacific Grove, CA, Nov. 2014. (Best paper award nominee) (JUB)

W. Liu, Satyanarayana Vuppala, Giuseppe Abreu and T Ratnarajah, “Secrecy Outage in Correlated Nakagami-m Fading Channels,” IEEE Personal Indoor Mobile Radio Communication, Sept. 2014. (Accepted) (JUB)

Satyanarayana Vuppala, Giuseppe Abreu,“Secrecy Outage Analysis in Cellular Networks”,’ submitted to IEEE Wireless Communications Letters. (Accepted) (JUB)

Satyanarayana Vuppala, Giuseppe Abreu,“Asymptotic Secrecy Analysis of Random Networks with Colluding Eavesdroppers”,’ submitted to IEEE/ACM Trans. On Networking. (Submitted) (JUB)

Satyanarayana Vuppala, W. Liu, T Ratnarajah and Giuseppe Abreu, “Secrecy Outage of Nakagami-m MISO Channels with Randomly Located Receivers,” IEEE ICC, London, UK, 2015. (Submitted) (JUB)

Omotayo Oshiga and Giuseppe Thadeu Freitas de Abreu: “ Design of Orthogonal Golomb Rulers with Applications in Wireless Localization,” Proc. IEEE Fourty -Eight Asilomar Conference on Signals, Systems and Computers, (Asilomar 2014), November 2-5, 2014. (JUB)

We submitted a journal paper on the IEEE Transaction on wireless communication describing the robust solution to positioning based on the Edge kernel algorithm. (UOULU)

“The Entropy of Wireless Statistics”, Christine Henenebert, Hicham Hossayni, Cédric Lauradoux, EUCNC’2014, European Conference on Network and Communication, Bologna, Italy, 23-26 june 2014. (CEA)

“Lightweight Handshake for IoT deployment “, Christine Hennebert, Chip -to-Cloud’2014, 23-25 september, Marseille, France. (CEA)

“Security Protocols and Privacy Issues into 6LoWPAN stack: A synthesis”, Christine Hennebert, Jessye Dos Santos, IEEE Journal of IoT, october 2014, vol. 1, issue 5, pp. 1 -15, ISSN 2327-4662, DOI 10.1109 / JIOT.2014.2359538. (CEA)

I. Tunaru, B. Denis, B. Uguen, “Reciprocity-Diversity Trade-off in Quantization for Symmetric Key Generation”, IEEE International Symposium on Personal Indoor, and Mobile Radio Communications 2014 (IEEE PIMRC’14), Washington, Sept. 2014 (CEA)

I. Tunaru, B. Denis, B. Uguen, “Random Patterns of Secret Keys from Sampled IR -UWB Channel Responses”, IEEE International Conference on Ultra Wideband 2014 (IEEE ICUWB’14), Paris, Sept. 2014 (CEA)

I. Tunaru, B. Denis, B. Uguen, “Public Discussion Strategies for Secret Key Generation from Sampled IR-UWB Channel Responses”, IEEE Conference on Communications 2014 (IEEE COMM’14), Bucharest, May 2014 (CEA)

1.1.2.4. Deviations from the Description of Work No deviation.

1.1.2.5. Work package project meetings

F2F / Conference call Dates Location

Butler D2.5 Phone Call June 26th 2014 GoToMeeting

Butler D2.5 Phone Call July 8th 2014 GoToMeeting




Butler D2.5 Phone Call August 28th 2014 GoToMeeting

Butler D2.5 Phone Call September 9th 2014 GoToMeeting

Butler D2.5 Phone Call October 6th 2014 GoToMeeting

Plenary meeting September 23-25th 2014 Santander, Spain


1.1.3. WP3 Architecture of Context-Aware Networks

1.1.3.1. Objectives

Workpackage Planned (M25-M37): 33 Realised: 26 (not final figures) Leader: ERC Participants: TIL, GTO, CEA, ISMB, iHL, SWC, ST-I, KUL, TST & ZPOS

During the third year of the project (year 3), WP3 aims to support the remaining work packages, mainly focusing on architectural aspects. Additionally, the WP3 has provided some architectural conclusions and identified the main challenges to the BUTLER architecture. They have been outlined in section 6 in deliverable D3.2.

1.1.3.2. Progress towards objectives Along the third year, ISMB and ERC provided technical support to the other WPs regarding the architecture. In particular, it has been ensured that the field trials was are aligned with the BUTLER architectural guidelines delivered at M24. Finally, concerning the network layer aspects, ISMB designed the Network Monitoring functional component, whose description has been included in D5.1, and successfully integrated the CoAP SmartObject devices based on the STM32W platform into the SmartGW. During this quarter ISMB and ERC coordinated WP3 contributions for the D2.5 deliverable and also the architecture contributions to D5.2. It is obvious that a 3-year long project does not work in a closed environment, but must be opened to the inputs of the market, the industry and the society. It means that as the project evolves, the environment does it so and therefore, the partners have to be able to scout it in order to align their own developments with the evolution of the technology outlook. Therefore, ERC has come out with some conclusions related to the BUTLER architecture:

The scenarios that BUTLER addresses (as any other in the real life) cannot deal exclusively with IoT, even if they are enabled by devices. Any IoT architecture applied to real scenarios has to deal not only with IoT architectures and standards but also consider functional components supporting functionalities that not specifically related to IoT. Architecture design must take a best-of-breed approach that considers not only IoT inputs.

IoT-A has created an Architectural Reference Model (ARM). Although its blueprints, guidelines and design choices provide a comprehensive set of inputs to any IoT-related project (in fact the ARM has been the main input to the BUTLER architectural work, especially with regard to BUTLER Information Model), the fact that it does not provide an applied architecture makes it difficult to take an off-the-shelf architecture and use it as the basis of BUTLER’s own architecture.

IoT is driven by the emergence of devices. However, the power of IoT lies on the ubiquity of devices and on the information they sense. Therefore, the emphasis put on the connectivity of devices cannot hide that IoT means also Data Management and that any IoT architecture must include a wide set of functional components dealing with data/context management.

The large amount of SmartObjects that can be connected to any IoT environment, and the heterogeneity of the data they sense and generate, joined with the fact that many of the features exposed by any IoT environment rely on almost real-time reaction to events, bring the need to process data streams as they are generated to the table. That is the reason to introduce a Complex Event Processing Functional Component (which has been anticipated by


emerging industry efforts such as FI-WARE) within the Data/Context Management layer, as it supports the functionality of several functional components.

Although it cannot be considered an unexpected finding or conclusion, as it was one of the main requirements and cornerstone of the project, security management must be handled across all the BUTLER architectural layers and not in silos.

1.1.3.3. Significant results Different contributions were provided to deliverables D2.5 and D5.2. They are mainly related to the identification of architectural challenges and to the conclusions that can be extracted from BUTLER. The former has been listed in the previous sections. The challenges can be summarized in three main ones:

The increasing fragmentation of IoT standards, industry efforts and EU projects.

The need to go beyond the mere connectivity of SmartObject and to provide advanced data management functionalities such as big data analytics.

The maturity of standards and initiatives that use semantic technologies to ensure interoperability and are being supported in IoT.

1.1.3.4. Deviations from the Description of Work No deviation from the DoW.



F2F- Plenary Meeting October 16-18th 2013 Torino, Italy

BUTLER Plenary Call October 28th 2013 Gotomeeting (online)

BUTLER Preparation Review November 05th 2013 Gotomeeting (online)

BUTLER WP Leader January 22nd 2014 Gotomeeting (online)

Regular conf calls During the last year Gotomeeting (online)

6th Plenary meeting February 05-07th 2014 Bilbao, Spain


1.1.4. WP4 BUTLER Platform Development and Implementation [TIL]

1.1.4.1. Objectives

Workpackage Planned (M25-M37): 115 Realised: 138 (not final figures) Leader: TIL Participants: inno, ERC, TIL GTO, CEA, ISMB, iHL, ST-I, TST, ZPOS, MAYA & BSAN

1.1.4.2. Objectives BUTLER WP4 is the implementation Work Package in BUTLER. It’s organized around three tasks, each one dedicated to the implementation of one software platform; the three platforms together constitute the BUTLER Horizontal Platform. The objective of this work package for Year 3 is the delivery of improved versions of the three platforms (SmartObject / Gateway, SmartServer and SmartMobile) components to support the execution of the BUTLER trials and final integrated horizontal demonstrators. After the first release (R1.0), used during the 2nd project review, one intermediate release (R2.0) at Month 30 and a final release (R3.0) at Month 36 have been planned, to fulfil trial integration requirements and security requirements. Software components have been made available to all partners to be deployed and used in trials and final demonstrators.

1.1.4.3. Progress towards objectives The activity of the Work Package has been initially focused to the finalization of the first version of the three platforms SmartObject / Gateway, SmartServer and SmartMobile to support their use in the 2nd year demonstration at the BUTLER 2nd review. This activity consisted in bug fixing, optimization and deployment of the components according to the integration requirements that have been raised during the demo preparation activities. Some components have been made available as public endpoints on the Internet, while others have been deployed locally to the demo setup. Activities on the three tasks have been also directed in the finalization of the three deliverables D4.1/2/3 and their revision after the review comments. In addition to the review preparation, a collection of the planned improvements of components for Year 3 have been done and reviewed, setting prioritizations. Improvements include both new features, as required by 3rd year trials, and improvements/bug fixing that emerged from the 2nd year review integration activity. Feature enhancements activities on the components have progressed after the review. A special focus has been put into security integration on the three platforms. After Month 28, Work Package 4 activities have been concentrated in the preparation of the three platforms for supporting the upcoming Year 3 trials and final demonstrators. The three tasks have progressed in parallel towards the implementation and improvements of their specific software modules. At WP-level the activity has been always coordinated to guarantee alignment of the three platforms and guarantee communication with other Work Packages as well as monitoring the progress of implementation activities. Most of the activity consisted in bug fixing, API and functionalities upgrading and alignment to the BUTLER security framework and to new requirements coming from integration activities in Work Package 5. Documentation has also been improved following suggestions from trial project developers. The three platforms components have been published to the Open Platform initiative where the BUTLER project participates.


The progress on software development and APIs refinement has been documented and reflected in Deliverable D5.1, where in Chapters 2-3-4 partners have documented the intermediate release (release R2.0) of the three platforms at Month 31. After Month 31, activities have been concentrated on the improvements of the three platforms to support trials and final demonstrators. Activities consisted in: bug fixing, update of the documentation on the Open Platform web site and finalization of the alignment to the BUTLER security framework. Updated APIs, integrated technologies, software architectures have been continuously documented in Deliverable D5.2, where partners have described the final status of the three platforms at Month 36. Performance evaluation on the software components was started, according to performance metrics documented in Deliverable D5.1. All the development activities have always been kept in synch with the integration activities carried out in Work Package 5. After Month 34, all the remaining effort has been concentrated to the final release (R3.0) of the three platforms until Month 36, and finalization of the documentation on the Open Platform. Performance evaluations have been completed for all platforms, together with the assessment of the software components while they were used in the field trials. Results of such evaluations have been documented in Deliverable D5.2.

1.1.4.4. Significant results

Preparation of platform components for the 2nd BUTLER review

Development of the three platform components for intermediate release of the BUTLER Integrated Platform (R2.0)

Documentation of each component in deliverable D5.1 addressing: improved functionalities offered, updated Software Architecture, review on Enabling Technologies, updated APIs, definition of performance evaluation metrics, deployment in the trials and demonstrators

Synchronization with integration and trial activities in WP5

Inputs and final editing of Deliverable D5.1

Finalization of developments of the three platform components for the final release of BUTLER Integrated Platform (R3.0)

Updated documentation of each component in deliverable D5.2 addressing: final APIs, performance evaluation, quality assessment, deployment in the trials and demonstrators

Documentation of each component and library released by the work package in the Open Platform web site

Specifically, for each task the following significant results have been achieved: Task 4.1 – SmartServer

Revision of SmartServer APIs for inclusion of BUTLER security framework

Deliverable D4.1 final Release and adjustments according to 2nd review comments

Intermediate release of feature enhancements of the SmartServer APIs

Inputs to D5.1 to document improvement over the first release of the SmartServer platforms

Integration of the BUTLER security framework in SmartServer components

Definition of Performance evaluation metrics

Devaluation tests of the platforms

Final release of the SmartServer APIs and publication on the OpenPlatform web site

Inputs to D5.2 to document final improvements and performance evaluation

Publication on the project software repository (GIT) of library components to be integrated in the final release of the BUTLER demonstrators

Task 4.2 – SmartMobile Platform


Deliverable D4.2 final Release and adjustments according to review comments

Design of the new version of the SmartMobile architecture

Improvement of the BUTLER.js library: full support for security and integration of the Authorization Server / Trust Manager, caching of security tokens, notification system, configuration module

Development of the new BUTLER Android component as a Java library, with:

Full support of the trust manager

Integration of the profile server

SmartMobile application delivered as a single APK archive so developers can run their BUTLER services on SmartMobile without installing the full framework (Android, PhoneGap)

Support of native applications within SmartMobile (e.g. app launcher)

Integration of the localization server in SmartMobile (web and native)

Improvement of the notification system, now targeting both web and native clients

Update of BUTLER UI for web apps to support Bootstrap v3.1

Development of a sample SmartMobile application using the full BUTLER architecture (SmartGateway, SmartServer along with the authentication server)

Setting up of training material

Documentation of BUTLER.js and of the BUTLER Android library within the Open Platform web site

Finalization of inputs to D5.1 and D5.2

Performance evaluation tests and feedback collection from application developers Task 4.3 – SmartObject/Gateway

Deployment of SmartGateway instances for the demos and Preparation of the Year -2 Review

Integration of Security Services within the SmartObject Gateway

Deliverable D4.3 final Release

SmartGateway Development: o Addition of different Consumer Protocol Adapters (Northbound): Complete support

for ReSTful HTTP, JSON-RPC, MQTT w/DDX connector o Additions of different Device Protocol Adapters (Southbound): CoAP/6LoWPAN,

ZigBee/SE1.x, Xbee API Mode 1 and Mode 2 o New SmartObjects supported: ST Bluetooth Body Gateway Device (healthcare),

enOcean, KNX, ZigPos Localization device, Maya Smart TV, TSTmote o Enhancements and new features: Securized access (Gemalto’s authorization server),

Subscribe / Unsubscribe to service appearance/disappearance, Subscribe / Unsubscribe to a resource, Long Polling Subscription mode, Reporting (NetworkMonitoring service from ISMB), Device model generalization

Inputs to D5.1 Chapter 4 to document improvements over the first release of the SmartObject Gateway platform

BUTLER Smart Gateway library set-up in open-platform.eu web site

Hackaton session organized by CEA-LETI in which the gateway was delivered to developers

SmartGateway and nodes demo at IoT Week

Inputs to D5.2 to document improvements over the intermediate release of the SmartObject Gateway platform

Performance evaluation tests for the SmartObject Gateway

1.1.4.5. Deviations from the Description of Work Documentation of platform development work in D5.1 had a delay of about 3 months due to more time needed to release some feature improvements, integration of security framework and the need to


document the latest changes of the software to keep the trial developers updated on the latest component APIs and features.



Technical platform session to finalize platform components towards the review demos

October 15-16th 2013 Torino, Italy

Planning for Smart platform activities in Y3 October 17th 2013 Torino, Italy

Finalization of deployment and configuration for the review demos

November 12th 2013 Lucerne

Platform enhancements and new requirements on field trials

January 23rd 2014 Phone conf. call

D5.1 Documenting Platform improvements January 30th 2014 Phone conf. call

6th Plenary meeting February 05-07th 2014 Bilbao, Santander

Periodic meetings to: -Synchronize development activities -Update on documentation of software developments towards D5.1

February 13th 2014 February 18th 2014 February 24th 2014 March 05th 2014 March 13th 2014 March 26th 2014 April 03rd 2014 April 15th 2014

GOTOMEETING

BUTLER SmartOffice platform meeting May 21-22nd 2014 Milano

Periodic meetings to: - synchronize development activities - update on documentation of software developments towards D5.1/D5.2

May & June 2014

Phone conf. call


1.1.5. WP5 Integration and Testing

1.1.5.1. Objectives

Workpackage Planned (M25-M37): 118 Realised: 197 (not final figures) Leader: CEA Participants: inno, ERC, TIL, GTO, CEA, OY, ISMB, iHL, SWC, ST-I, KUL, TST, JacobsUni, ZPOS,

MAYA, TECNALIA & BSAN The main objective of the 3rd period of the project was to finalize the integration of the BUTLER platforms and do their validation via proofs of concept and field trials, while ensuring that the proposed BUTLER architecture responds the requirements that have been identified in the WP1. The following Erreur ! Source du renvoi introuvable. illustrates the target final integrated BUTLER platforms.

Figure 5 - BUTLER Smart Platforms

The BUTLER Smart Object gateway is the interface between the physical and the cyber world, while The BUTLER Smart Server is the interface to the world of digital information, processing and mediating information that is relevant to users and BUTLER applications. The BUTLER Smart Mobile is the interface between the end-users and the BUTLER platform. And finally, the Security and Trust Service ensures that only authorized entities can be integrated in the BUTLER Platform environment and that only authorized applications can access to provided services and resources. The development of the enabling technologies for each of these layers and their integration into a


horizontal BUTLER platform thus provides a reusable and efficient technological platform for the creation and deployment of secure, context-aware IoT applications.

1.1.5.2. Progress towards objectives During this 3rd year the following work progress towards objectives has been achieved: At the Smart Gateway level, several southbound protocol bridges have been performed such as enOcean, KNX, Xbee Mode 1 and Mode 2 for TST devices, Bluetooth Body Area devices, Bluetooth Low Energy. In addition, several northbound bridges have also been integrated to the gateway such as HTTP REST, JSON RPC, HTTP long pulling and MQTT. Besides integration of several smart servers to the gateway has been performed such as the Zigpos localization system, ISMB localization manager, Maya’s smart multimedia server, Gemalto’s security service, etc. ISMB integrated the IPSec and key distribution modules for 6LoWPAN constrained SmartObjects. CEA’s low layer security solution is also integrated with the smart gateway. At the Smart Server level, integration and testing of several smart servers has been done, in particular: integration of ISMB’s localisation server with the Zigpos localisation system, Integration of the DDX server with Tecnalia middleware, development of a context manager module by analyzing the banking information provided by Banco de Santander, a webcam visualization plugin to the Smart TV application from Maya running on televisions, integration of TI’s user profile manager with Gemalto’s Authorization Smart Server and integration of TI’s context manager with ISMB’s location manager Gemalto has deployed its Authorization Server on the internet which has been made available to partners. In cooperation with CEA, Gemalto integrated the Security and Privacy provider library in the Smart Object Gateway. SAMURAI also upgraded the last version of the Trust Manager and the external APIs exposed by SAMURAI are now protected by the BUTLER Trust Manager(TM) v1.3. At the Smart Mobile level, a new notification component for both web and native BUTLER applications has been developed; this allows developpers to notify end-users usong Google or BUTLER js libraries. Moreover, the latest update related to signatures management done on the Trust Manager has also been ported to the SmartMobile components. A server -side component has been integrated to use the BUTLER OAuth2 protocol from regular web applications. Besides that, access to localization servers has been added to SmartMobile. And last, new gateway wrappers have been added to SmartMobile providng access data on specific gateways, such as for example the list of devices connected to a gateway, the list of resources, the access to specific values. Gemalto and INNO also integrated Security and Privacy application library in the Smart Mobile. The integration work has been deployed and validated via several trials. 3rd year work in trials consisted in doing the following developments in addition to their deployments and performance evaluations. Details of those trials have been given in the Deliverable 5.2.


Figure 6 - BUTLER trials overview

Smart office

Deployment of Zolertia sensors with the smart gateway in Inno meeting room and kitchen - set up and integration of smartthing sensors for door state and presence detection - initial deployment of the office social network

Installation of KNX-controlled office lights, curtains, presence sensors and weather station has been complete for the office of 20 people. KNX-adapter component for BUTLER Smart Object Gateway has been prototyped. Gamification of Smart Office Field Trial has been planned through a competition between three different office locations.

Southbound KNX-adapter development for BUTLER Smart Object Gateway has been initialized and tested for stand alone components. A common scenario for Smart Office Field Trial has been identified among three different office locations in France, Italy and Switzerland. Integration of Open Source Social Media Platform into BUTLER applications is currently in progress.

End user engagement in trials, definition of the end user feedback model and process, set up of end user feedback tool (online survey)

Smart Health

Integration of KUL’s context manager, ISMB localisation server and Zigpos localisation system and Ericsson’s DDX server for the smart health trial

Integration of Tecnalia’s fall detection system and medicine rminder system to the multimedia service

Smart transport

2 scenarios have been developped e-ticketing and save child group


Development and deployment of the SmartTransport field trial with the SmartObject Gateway,

Smart shopping in Santander

Creation of the electronic tools that will be used by city merchants for exploiting the benefits of BUTLER Smart Shopping solution (https://butler.tst-sistemas.es). Many merchants are starting to upload their commerce information and brochures into the SmartShopping platform.

Dissemination of project benefits among Santander citizens with updates in local newspapers.

Smart parking in Santander

Development of wrappers in order to offer standard protocols and interfaces according to the project overall architecture (MQTT broker).

Conducting tests with prototypes of a new vehicle detection sensor (an ultrasonic one), a refurbished lighting system (more power efficient and brighter), a more resistant box case and bigger battery packs.

Release of a robust and feasible SmartParking device that pass from a prototype version to a pre-production version, and complies with the BUTLER architecture and the requirements of the field trial

1.1.5.3. Significant results The main results of the WP5 were the tremendous integration work that has been performed with a great cooperation among the partners.. In addition, BUTLER project participated to many European and international events to disseminate the integration work such as IoT Week and IoT.360 where we organized demonstrations, as well as a hackatong

Figure 7 - The BUTLER platform was available for the IOT Week 2014 Hackaton participants

Figure 8 - BUTLER booths in IoT Week and IoT.360

https://butler.tst-sistemas.es/





Dedicated technical integration workshop during the projects F2F meeting

October 15th 2013 Torino

Preparation of review demos November 12th 2013 Lucerne

WP5 conf call January 23rd 2014 GOTOMEETING

6th Plenary meeting February 05-07th 2014

Bilbao, Santander

Regular conf calls on field trials GOTOMEETING

Regular conf calls for D5.1 GOTOMEETING

Smart Health Trial Meeting May 6-7th 2014 Bilbao, Santander

Technical synchronisation meeting May 21-22nd 2014 Milano, Italiy

Several conf calls for IoT Week demo and hackaton preparation

May & June 2014 GOTOMEETING

Individual, partner level calls for trial preparation

May & July 2014 GOTOMEETING

Plenary meeting September 23-25 2014

Santander

Bi-weekly WP5 call (integration, trials, D5.2)

Starting from July 2014

GOTOMEETING


1.1.6. WP6 Dissemination, Standardization, Education, Exploitation and IPR Management [FBC]

1.1.6.1. Objectives

Workpackage Planned (M25-M37): 46 Realised: 72 (not final figures) Leader: FBC Participants: all partners

The objectives of WP6 in the reporting period have been:

Position the BUTLER project as the interface to the Iot research project in the EU in the onM2M group and the ETSI TC smartM2M, support of other project to be present in oneM2M

IERC cluster reorganization towards an integration into the DG Connect strategy, Co-lead of Standardization activities in the IERC cluster

Create awareness of IERC in the relevant standardization groups and transferring results into the IERC group

Participation in relevant standardisation activities like oneM2M, ETSI TC M2M, ETSI TC ITS and ETSI ERM.

To publish relevant research results (see Deliverable 6.3 for list of all publications)

Involve potential additional stack holders in the discussion, extension of the EMG

Analyse the socio economic context and potential impact of the project (see Deliverable 6.6)

To generate 44 international publications

1.1.6.2. Progress towards objectives

oneM2M #7 (FBC, TIL and GEMALTO)

oneM2M #8 (TIL and GEMALTO)



oneM2M #11 ((TIL and GEMALTO)

oneM2M #12 Meetings in Sophia Antipolis(FBC, TIL and GEMALTO) o Finalization of release 1 of oneM2M service layer specification from public consultation


Participation in several other standardisation activities lie ETSI TC ITS, ETSI ERM,

Participation at ITU workshop on short range devices

Finalization of IERC book including BUTLER contributions

BUTLER booth at ICT2013 in Vilnius, Lithuania

Active participation in the IoT week in London with Hackethon, booth and papers

Participation in IoT 360 event in Rome

Scientific Publications: o Overall in period 3: 57 including 11 joined contributions o Journal papers: 8 o Conference papers: 49 o For more details and lists see Deliverable 6.3


1.1.6.3. Significant results ICT2013, 6 -8 November 2013 in Vilnius, Lithuania BUTLER booth and demo IoT week London:

The BUTLER Project was among the lead contributors of the 2014 IoT Week in London, participating to many activities. Two sessions were directly organized by the BUTLER project, and have now produced reports:

The IERC Activity Chain 1 session on Open Platforms which introduced the Open Platforms initiative. This session was divided in two parts: the morning session presented the Open Platforms initiative, and introduced the Open Platforms portal. The objective of the afternoon session was to discuss openly the sustainability and feasibility of open platform for the development of the Internet of Things. The session overall confirmed the choice of the project to use the Open Platforms initiative as it’s main exploitation opportunity but also stressed the need for institutional support for the initiative. Read the full report.

A session on IoT user’s experiences: engagement, expectations and concerns. The workshop tackled these questions with a twofold perspective: A methodological and theoretical perspective: to discuss about evaluation framework and specific methodological tools implemented to engage users and gathering their feedbacks, and a practical perspective: to discuss about feedbacks and lessons learnt from ongoing works and initiatives (including field trials implemented in projects). This session enabled the formulation of several important best practices on user engagement in IoT experimentations. Read the full report

The project participated actively in the IoT Week Hackathon, both by providing technologies and by participating in some of the challenges.

Figure 9 - IoT Week 2014 Hackaton

Several members of the consortium also participated actively in numerous sessions (such as the IERC AC3 session on pilots and deployments, or the IERC AC7 session on Smartness in the IoT)



http://www.iot-week.eu/

http://open-platforms.eu/

http://www.iot-butler.eu/wp-content/uploads/2014/07/AC1-minutes.pdf

http://www.iot-butler.eu/wp-content/uploads/2014/07/IoT-Week-user-engagement.pdf

http://iot-week2014.challengepost.com/

http://www.iot-butler.eu/wp-content/uploads/2014/07/2014-06-19-10.48.15.jpg


No specific work package meetings have taken place in the reporting period. WP6 meetings and presentation have been organized during the regular periodic project meetings.

1.2. Project management during the period

1.2.1. Objectives

Workpackage

Planned (M25-M38): 20 Realised: 32 (not final figures) Leader: inno Participants: ERC, FBC, TST, JacobsUni, Tecnalia

This Work package covers the aspects concerned with the overall project management and follow up which will ensure that the project achieves successfully its stated objectives on time, within budget and with the right level of quality. Main activities include:

Interfacing with European Commission.

Coordination, preparation of progress meetings and committee meetings.

Planning of activities.

Cost and progress reporting.

Identification / avoidance / resolution of conflicts etc.

Set-up the project quality framework allowing deliverables quality supervision, risk analysis and contingency planning, scientific outputs monitoring.

Defining project graphical branding and templates

Set-up and management of an external Member Group and monitoring of projects impact onto different Stakeholders.


1.2.2. Progress towards objectives

Task summary Achievements

Task 7.1: Administrative Project Management

a. Administrative management

2nd amendment accepted on October 24th 2013 The EC agreed our request as follows:

1. The termination of the beneficiaries POLARIUS-UTREMA CASCARD OY Swisscom AG 2. The addition of the beneficiaries MAYAS TECHNOLOGIES SAS (Maya) BANCO SANTANDER SA (BSAN) AYUNTAMIENTO DE SANTANDER (SANTANDER) FUNDACION TECNALIA RESEARCH & INNOVATION (TECNALIA) 3. Modification of Annex I 4. Modification of legal entity details ZIGPOS 5. Change of coordinator’s name: Mr Bertrand Copigneaux

3rd amendment accepted on August 14th 2014

The EC agreed our request for the new duration of the project, 37 months. b. Deliverables M25 to M37 submitted

All the deliverables were submitted.

The interim reports were submitted.

c. Financial management

All the Costs Claim for the 2nd Period accepted by the EC on March 20th 2014.

d. Regular meetings & conference calls

2nd Review held on November 12-13th November 2013, Luzern, Switzerland

1 F2F synchro meeting

3 F2F consortium meetings

e. Survey tools

Alfresco is regularly updated by all the partners to upload the documents and use the calendar.

Gotomeeting frequently used by all the partners.


Task 7.2: Content and Quality Management

a) Feedback of the 2nd Review by the EC The EC allowed the project to continue. The overall assessment said the project is on good progress and all the deliverables were approved. However, the EC requested some recommendations for the last year of the project as follows:

To Improve editorial quality of reports New version of D4.2 (addressed within 2 weeks of the review

meeting and accepted by the EC To Provide security framework documentation / Consider

security testing An overspending of efforts (JacobsUni) Data protection position Starting time on Field trials Exploitation Plan

Task 7.3: Impact Management The project pursued the interactions with external stakeholders through

the External Member Group both with existing and new member of the group. The EMG has been used by Work Package 6 for the exploitation task and for the ethics and privacy analysis. The activity of this task also lead to further interactions with the IERC cluster, especially in Activity Chain 1, with the set up of the Open Platform portal as an initiative for the IoT community (and supporting the common exploitation strategy of the BUTLER project). Finally this task also actively participated to the creation of Deliverable 6.6 analyzing the potential socio economic impacts of the BUTLER project. This included an analysis of the IoT socio economic context and prospective, and a direct analysis of the field trial impacts and potential impacts (in liaison with WP5 and WP6).

1.2.3. Deviation from Plan

No deviation.

1.2.4. Changes in the consortium

The termination of the beneficiaries:

POLARIUS-UTREMA

CASCARD OY

Swisscom AG The addition of the beneficiaries:

MAYAS TECHNOLOGIES SAS (Maya)

BANCO SANTANDER SA (BSAN)

AYUNTAMIENTO DE SANTANDER (SANTANDER)

FUNDACION TECNALIA RESEARCH & INNOVATION (TECNALIA)


1.2.5. List of project meetings, dates and venues

Plenary conference call Dates Location

Regular conf calls with the consortium Year 3 GOTOMEETING

5th Plenary meeting October 16-17th 2013 Torino, Italy

2nd Review meeting November 12-14th 2013 Luzern, Switzerland

6th Plenary meeting February 04-07th 2014 Bilbao, Santander

Synchro meeting May 21-22nd 2014 Milano, Italy

7th Plenary meeting September 23-25th 2014 Bilbao, Santander


1.2.6. Project planning and status


1.2.7. Impact of possible deviations from the planned milestones and deliverables

None

1.2.8. Development of the Project website

The project website was updated to reflect the evolutions of the project:

The deliverables published

The project home page and presentation updated

1.2.9. Use of foreground and dissemination activities during this period

The dissemination activities are covered above in the WP6 activities.


2. Deliverables and milestones tables

2.1. Deliverables

TABLE 1. DELIVERABLES

Del.

no.

Deliverable name Version WP no. Lead

beneficiary

Nature

Dissemination

level4

Delivery date

from Annex I

(proj month)

Actual / Forecast

delivery date

(proj month)

Status

No

submitted/

Submitted

Comments

D1.1 Use cases and

requirements 1 1 SWC R PU 4 4 Submitted

D1.2 Refined Trial

Specification 1 1 iHL R PU 18 20 Submitted

D1.4 Ethics, Privacy and

Data Protection 1 1 inno R PU 20 21 Submitted

Additional

deliverable

requested at

1st

review

4 PU = Public

PP = Restricted to other programme participants (including the Commission Services). RE = Restricted to a group specified by the consortium (including the Commission Services). CO = Confidential, only for members of the consortium (including the Commission Services). Make sure that you are using the correct following label when your project has classified deliverables. EU restricted = Classified with the mention of the classification level restricted "EU Restricted" EU confidential = Classified with the mention of the classification level confidential " EU Confidential " EU secret = Classified with the mention of the classification level secret "EU Secret "


Del.

no.


beneficiary

Nature

Dissemination

level5

Delivery date

from Annex I

(proj month)

Actual / Forecast

delivery date

(proj month)

Status

No

submitted/

Submitted

Comments

D2.1

Requirements,

Specifications and

Security

Technologies for Iot

Context Aware

Networks

1 2 GTO R PU 12 13 Submitted

D2.2

Requirements,

Specifications and

Localisation/Context-

acquisition

Technologies for IoT

Context Aware

1 2 JUB R PU 12 13 Submitted

D2.3

Requirements,

Specifications and

Behaviour Modelling

1 2 KUL R PU 12 13 Submitted

5 PU = Public



and Synthesis

Technologies for IoT

Context Aware

D2.4

Selected

Technologies of the

BUTLER Platforms

1 2 CEA R PU 18 19 Submitted

D2.5

IoT Enabling

Technologies and

Future

Developments

1 2 ISMB R PU 36 37 Submitted

Del.

no.


beneficiary

Nature

Dissemination

level6

Delivery date

from Annex I

(proj month)

Actual / Forecast

delivery date

(proj month)

Status

No

submitted/

Submitted

Comments

D3.1

Architectures of

BUTLER Platforms,

and Initial Proofs of

concept

1 3 CEA R PU 12 14 Submitted

6 PU = Public



D3.2

Integrated System

Architecture & Initial

Pervasive BUTLER

proof of concept

1 3 ERC R PU 24 25 Submitted

Del.

no.


beneficiary

Nature

Dissemination

level7

Delivery date

from Annex I

(proj month)

Actual / Forecast

delivery date

(proj month)

Status

No

submitted/

Submitted

Comments

D4.1

BUTLER SmartServer

Platform & Enabling

Technologies

1 4 TIL R PU 24 25 Submitted

D4.2

BUTLER Smartmobile

Platform & Enabling

Technologies

1 4 inno R PU 24 25 Submitted

D4.3

BUTLER SmartObject

Platform & Enabling

Technologies

1 4 ST-I R PU 24 25 Submitted

7 PU = Public



Del.

no.


beneficiary

Nature

Dissemination

level8

Delivery date

from Annex I

(proj month)

Actual / Forecast

delivery date

(proj month)

Status

No

submitted/

Submitted

Comments

D5.1

BUTLER Platforms

and Pervasive

Functionalities

1 5 TIL R PU

30

34 Submitted

D5.2

BUTLER Final

Platforms and

Quality Assessment

1 5 ZIGPOS R PU

36

38 Submitted

8 PU = Public



Del.

no.


beneficiary

Nature

Dissemination

level9

Delivery date

from Annex I

(proj month)

Actual / Forecast

delivery date

(proj month)

Status

No

submitted/

Submitted

Comments

D6.1

Progress on

Standardization and

Exploitation and

Dissemination Plans

– Part II

1 6 FBC R RE 12 13 Submitted

D6.2

Progress on

Standardization and

Exploitation and

Dissemination Plans

– II

1 6 UL R RE 24 25 Submitted

D6.3

Progress on

Standardization and

Final Exploitation

and Dissemination

Plans

1 6 FBC R RE 36 38 Sumitted

9 PU = Public



D6.4

Dissemination

Strategy and IERC

collaboration plan

1 6 UL R RE 6 8 Submitted

D6.5 Exploitation Plan 1 6 FBC R RE 18 24 Submitted

Additional

deliverable

requested at

1st

review

D6.5 Exploitation Plan 1.5 6 FBC R RE 20 30 Submitted

Revised

version

following

review

comments

D6.6 Socio Economic

Impact 1 6 inno R PU 36 38 38

Del.

no.


beneficiary

Nature

Dissemination

level10

Delivery date

from Annex I

(proj month)

Actual / Forecast

delivery date

Status

No

submitted/

Submitted

Comments

D7.1 Public project 1 7 inno R RE 1 4 Submitted

10

PU = Public PP = Restricted to other programme participants (including the Commission Services). RE = Restricted to a group specified by the consortium (including the Commission Services). CO = Confidential, only for members of the consortium (including the Commission Services). Make sure that you are using the correct following label when your project has classified deliverables. EU restricted = Classified with the mention of the classification level restricted "EU Restricted" EU confidential = Classified with the mention of the classification level confidential " EU Confidential " EU secret = Classified with the mention of the classification level secret "EU Secret "


presentation

according to the EU

specifications

D7.2 Quarterly project

reports 1 7 inno R RE

4,7,10,16,

19,22,28,31,3

4

4,7,10,16,19,22,

28,31,34 Submitted

D7.3 Planning for the next

period 1 7 inno R RE 24 26 Submitted

D7.4 Quality Plan 1 7 inno R RE 1 4 Submitted


2.2. Milestones

TABLE 2. MILESTONES

Milestone

no.

Milestone name Work

package

no

Lead

beneficiary

Delivery date from

Annex I

Achieved

Yes/No

Actual / Forecast

achievement

date

Comments

MS1 Kick-off 1, 2, 3, 4,

5, 6, 7

1 1 YES 1

Project meeting and

website

MS2 Use-cases and requirements 1 16 4 YES 4 Deliverable D1.1

MS3 Initial test of vertical context-aware

approaches

3, 5 9 12 YES 14

Deliverable 3.2, 1st

project review

MS4

Pervasive BUTLER components:

SmartServer, SmartObject &

SmartMobile

2, 3, 4

3

18

YES

20

Deliverable D2.4

MS5 First pervasive BUTLER system

2, 3, 4, 5

5

24

YES 26

Deliverable D3.2, D4.1,

D4.2, D4.3, 1st

horizontal proof of

concept, 2nd Project

Review

MS6 Enabling technologies and holistic

system architecture for the future

2,3 17 36 YES 36 Deliverable D2.5

MS7 Final BUTLER field trial 4,5 9 36

YES 38 Deliverable D5.2, 3

rd

Project Review


2.3. Explanation of the use of the resources and financial statements


Date post:	27-Jul-2020
Category:	Documents
Upload:	others
View:	4 times
Download:	0 times

PROJECT PERIODIC REPORT€¦ · 1 PROJECT PERIODIC REPORT Grant Agreement number: 287901 Project...

Documents