Deliverables
D61cThis deliverable reports yearly on the community building activities that were conducted in the respective year Also it describes planned activities for the next period The third report D61c summarizes and finalizes the activities during the course of the project
D2.3.b The first release of this deliverable will specify the requirements for BIG IoT according to the overall project goal and vision, as well as for the use cases defined in Task 2.2. As such, this deliverable will set the scope, the functionalities, and the features of the overall architecture (i.e., the BIG IoT API, the semantic framework, and the marketplace) and provides the guidelines for the technology development in WP3, WP4 and WP5. The second release (D2.3.b) will extend D2.3.a with a refined set of the requirements based on the experiences and results gained with the first version of the BIG IoT technologies and use case implementation. D2.3.b contributes to MS3.
D3.3.a Lead of this deliverable is BOSCH CR in representation of BOSCH SI. This deliverable provides the design and detailed specification of security and privacy mechanisms for smart object platforms and services. This specification is aligned with and contributes to the BIG IoT API design (D3.1). This deliverable will have three versions, starting with D3.3.a that is due in M12. The second and third versions (D3.3.b at M21 and D3.3.c at M30) will build up on their preceding versions and will consider lessons learned from implementing and utilizing the previous version. D3.3.a contributes to MS1.
This deliverable is produced by Task 24 and will provide the final evaluation of the BIG IoT architecture including the BIG IoT API and semantic framework and the marketplace The evaluation will consider the experience gained through the development of the use cases and regional pilots as well as their validation based on user trialsD25 contributes to MS7
D4.1.b This deliverable is a report that specifies in detail the concepts, architecture, design, and interfaces of the software infrastructure underlying the marketplace. The software infrastructure can be used to setup and deploy a marketplace. The deliverable is developed in 3 iterative cycles, starting with D4.1.a that is due in M12. The second version D4.1.b is due at M21 and the third version D4.1.c is due at M30. Each new version will extend the previous version to take into account the progress on related deliverables (e.g., use cases, requirements, BIG IoT API, and high level architecture). D4.1.b contributes to MS3.
D6.2.b This deliverable reports yearly on the activities for dissemination, standardization, and coordination with other EU initiatives that were conducted in the respective year. Also, it describes planned activities for the next period. The third report, D6.2.c, summarizes and finalizes the activities during the course of the project.
D5.4.a The deliverable reports on the demonstration of the three pilots and the assessment of the project results as carried out in Task 5.4. Also this deliverable is produced in an iterative way, aligned with the 3 release cycles. The first version (D5.4.a) and second version (D5.4.b) of this deliverable at M20 and M27 will present intermediary demonstration results and assessments to be fed into the next iteration for specification and implementation. At M36, a final report (D5.4.c) is presented that aggregates and extends its predecessor versions by assessing the final state of pilots and use cases to provide an overall conclusion. While D5.4.a and D5.4.b are independently delivered of any milestones, D5.4c contributes to MS7.
D4.3.b This deliverable will provide the results for the Task 4.3 on semantic orchestration of offerings. Outcome will be the report on research results as well as a prototype implementation that will be contributed to the overall software infrastructure for the marketplace (D4.4). The deliverable is developed in three iterative steps, starting with D4.3.a that is due in M12. The second version D4.3.b is due at M21 and the third version D4.3.c is due at M30. Each new version will extend the previous version to take into account the progress on related deliverables (e.g., use cases, requirements, BIG IoT API, and high level architecture). D4.3.b contributes to MS3.
D53cThis deliverable is a report that describes the conduction and outcome of the integration deployment and testing of the 3 pilots and their use cases realizing services and applications as carried out in Task 53 For each of the 3 releases of D52 integrationdeploymenttesting is carried out and this deliverable is updated by reflecting the continued development The first version D53a is due in M18 the second version D53b is due in M25 and the third version D53c is due in M34D53c contributes to MS6
D4.2.c This deliverable will provide the specification of a semantic model which provides a formal definition of vocabulary terms to annotate the descriptions of offerings of services and platforms exposed through the marketplace. The deliverable is developed in 3 iterative cycles, starting with D4.2.a that is due in M12. The second version D4.2.b is due at M21 and the third version D4.2.c is due at M30. Each new version will extend the previous version to take into account the progress on related deliverables (e.g., use cases, requirements, BIG IoT API, marketplace, and high level architecture). D4.2.c contributes to MS5.
D4.2.a This deliverable will provide the specification of a semantic service model which provides a formal definition of vocabulary terms to annotate the descriptions of offerings of services and platforms exposed through the marketplace. The deliverable is developed in 3 iterative cycles, starting with D4.2.a that is due in M12. The second version D4.2.b is due at M21 and the third version D4.2.c is due at M30. Each new version will extend the previous version to take into account the progress on related deliverables (e.g., use cases, requirements, BIG IoT API, marketplace, and high level architecture). D4.2.a contributes to MS1.
D3.2.c This deliverable provides the design and detailed specification of semantic models for smart object interoperability of smart object platforms and services. This specification is aligned with and contributes to the BIG IoT API design (D3.1). This deliverable will have three versions, starting with D3.2.a that is due in M12. The second and third versions (D3.2.b at M21 and D3.2.c at M30) will build up on their preceding versions and will consider lessons learned from implementing and utilizing the previous version. D3.2.c contributes to MS5.
D3.3.b Lead of this deliverable is BOSCH CR in representation of BOSCH SI. This deliverable provides the design and detailed specification of security and privacy mechanisms for smart object platforms and services. This specification is aligned with and contributes to the BIG IoT API design (D3.1). This deliverable will have three versions, starting with D3.3.a that is due in M12. The second and third versions (D3.3.b at M21 and D3.3.c at M30) will build up on their preceding versions and will consider lessons learned from implementing and utilizing the previous version. D3.3.b contributes to MS3.
D54bThe deliverable reports on the demonstration of the three pilots and the assessment of the project results as carried out in Task 54 Also this deliverable is produced in an iterative way aligned with the 3 release cycles The first version D54a and second version D54b of this deliverable at M20 and M27 will present intermediary demonstration results and assessments to be fed into the next iteration for specification and implementation At M36 a final report D54c is presented that aggregates and extends its predecessor versions by assessing the final state of pilots and use cases to provide an overall conclusionWhile D54a and D54b are independently delivered of any milestones D54c contributes to MS7
D2.4.b Lead of this deliverable is BOSCH CR in representation of BOSCH SI. The first version of this deliverable (D2.4.a) will specify the high level architecture for the first version of the BIG IoT implementations and development of the use cases and regional pilots. It will define the core components and interfaces within the system and to the surrounding software infrastructure. It will define the basic functionality and behaviour of all components, as well as their relations and basic interaction patterns with the overall system. As such, this deliverable will serve as blueprint and architecture guideline for the technical work across all other work packages. The specification will cover the smart objects and their IoT platforms, the BIG IoT interoperation layer consisting of the BIG IoT API as well as the necessary support services and their hosting infrastructure, and the BIG IoT marketplace with its services and applications. The second release, D2.4.b, will extend D2.4.a by refining the BIG IoT architecture for the second version of the BIG IoT implementations. The experiences and findings of developing the first version of BIG IoT will be taken into account to improve the architecture. D2.4.b contributes to MS3.
D3.2.a This deliverable provides the design and detailed specification of semantic models for smart object interoperability of smart object platforms and services. This specification is aligned with and contributes to the BIG IoT API design (D3.1). This deliverable will have three versions, starting with D3.2.a that is due in M12. The second and third versions (D3.2.b at M21 and D3.2.c at M30) will build up on their preceding versions and will consider lessons learned from implementing and utilizing the previous version. D3.2.a contributes to MS1.
D2.2.a This deliverable will define the guiding use cases of the project (as outlined in Section 1.1.3) in full detail. Thus, the deliverable will become the blueprint for the use case development in WP5. For each use case, the deliverable will capture a detailed description of the scenario, its stakeholders, the services and applications offered, the stakeholder benefits, the smart objects and platforms involved, the high level interactions among the smart objects, platforms, services and applications, and specifically, the key functionalities of the BIG IoT architecture. D2.2.a contributes to MS1.
D3.1.b This deliverable provides the design and detailed specification of the BIG IoT API. Outcome of this deliverable will be the central basis for the implementation work of D3.4 as well as an important input to the work on marketplace and software infrastructure in WP4 as well as the realization of use cases in WP5. Following the agile project management approach, this deliverable will have three versions, starting with D3.1.a that is due in M12. The second and third versions (D3.1.b at M21 and D3.1.c at M30) of the BIG IoT API will build up on their preceding versions and their design will consider lessons learned from implementing and utilizing the previous version. D3.1.b contributes to MS3.
D54cThe deliverable reports on the demonstration of the three pilots and the assessment of the project results as carried out in Task 54 Also this deliverable is produced in an iterative way aligned with the 3 release cycles The first version D54a and second version D54b of this deliverable at M20 and M27 will present intermediary demonstration results and assessments to be fed into the next iteration for specification and implementation At M36 a final report D54c is presented that aggregates and extends its predecessor versions by assessing the final state of pilots and use cases to provide an overall conclusionWhile D54a and D54b are independently delivered of any milestones D54c contributes to MS7
D7.1.a The first version of this deliverable, D7.1.a, will give an initial view on the BIG IoT exploitation activities including a market analysis, applicable business models for IoT ecosystem stakeholders, and an initial business plan.
D4.1.c This deliverable is a report that specifies in detail the concepts, architecture, design, and interfaces of the software infrastructure underlying the marketplace. The software infrastructure can be used to setup and deploy a marketplace. The deliverable is developed in 3 iterative cycles, starting with D4.1.a that is due in M12. The second version D4.1.b is due at M21 and the third version D4.1.c is due at M30. Each new version will extend the previous version to take into account the progress on related deliverables (e.g., use cases, requirements, BIG IoT API, and high level architecture). D4.1.c contributes to MS5.
D5.3.a This deliverable is a report that describes the conduction and outcome of the integration, deployment, and testing of the 3 pilots and their use cases realizing services and applications as carried out in Task 5.3. For each of the 3 releases of D5.2, integration/deployment/testing is carried out and this deliverable is updated by reflecting the continued development. The first version, D5.3.a, is due in M18, the second version, D5.3.b, is due in M25, and the third version, D5.3.c, is due in M34. D5.3.a contributes to MS2.
D22c This deliverable will define the guiding use cases of the project as outlined in Section 113 in full detail Thus the deliverable will become the blueprint for the use case development in WP5 For each use case the deliverable will capture a detailed description of the scenario its stakeholders the services and applications offered the stakeholder benefits the smart objects and platforms involved the high level interactions among the smart objects platforms services and applications and specifically the key functionalities of the BIG IoT architectureThe third release D22c will be extended by descriptions of scope and expectations as contribution for the definition of the second Open Call D22c contributes to MS5
D2.2.b This deliverable will define the guiding use cases of the project (as outlined in Section 1.1.3) in full detail. Thus, the deliverable will become the blueprint for the use case development in WP5. For each use case, the deliverable will capture a detailed description of the scenario, its stakeholders, the services and applications offered, the stakeholder benefits, the smart objects and platforms involved, the high level interactions among the smart objects, platforms, services and applications, and specifically, the key functionalities of the BIG IoT architecture. The second release (D2.2.b) will be extended by descriptions of scope and expectations as contribution for the definition of the first Open Call. D2.2.b contributes to MS3.
D2.4.a Lead of this deliverable is BOSCH CR in representation of BOSCH SI. The first version of this deliverable (D2.4.a) will specify the high level architecture for the first version of the BIG IoT implementations and development of the use cases and regional pilots. It will define the core components and interfaces within the system and to the surrounding software infrastructure. It will define the basic functionality and behaviour of all components, as well as their relations and basic interaction patterns with the overall system. As such, this deliverable will serve as blueprint and architecture guideline for the technical work across all other work packages. The specification will cover the smart objects and their IoT platforms, the BIG IoT interoperation layer consisting of the BIG IoT API as well as the necessary support services and their hosting infrastructure, and the BIG IoT marketplace with its services and applications. D2.4.a contributes to MS1.
D5.1.b The deliverable defines prerequisites / assumptions, services and application specification, measures for the technical, organizational and operational set-up of the pilot demonstrations. It further includes the set-up plans for each pilot, Northern Germany, Piedmont, and Barcelona. The deliverable is developed in 3 iterative cycles, starting with D5.1.a that is due in M9. The second version D5.1.b is due at M21 and the third version D5.1.c is due at M30. Each of the 3 iterative versions of this deliverable extent their predecessor version by refining the pilot specifications and adhering to new requirements, updates on use case definitions, etc. D5.1.b contributes to MS3.
D2.3.a The first release of this deliverable will specify the requirements for BIG IoT according to the overall project goal and vision, as well as for the use cases defined in Task 2.2. As such, this deliverable will set the scope, the functionalities, and the features of the overall architecture (i.e., the BIG IoT API, the semantic framework, and the marketplace) and provides the guidelines for the technology development in WP3, WP4 and WP5. D2.3.a contributes to MS1.
D3.1.a This deliverable provides the design and detailed specification of the BIG IoT API. Outcome of this deliverable will be the central basis for the implementation work of D3.4 as well as an important input to the work on marketplace and software infrastructure in WP4 as well as the realization of use cases in WP5. Following the agile project management approach, this deliverable will have three versions, starting with D3.1.a that is due in M12. The second and third versions (D3.1.b at M21 and D3.1.c at M30) of the BIG IoT API will build up on their preceding versions and their design will consider lessons learned from implementing and utilizing the previous version. D3.1.a contributes to MS1.
D7.2.b This deliverable comprises the planning, coordination, conduction and evaluation of the 2 Open Calls. It includes the necessary documents for the management of the 2 Open Calls, such as the announcement and advertisements, a detailed guide for applicants, the application form, etc. The deliverable D7.2.b describes in detail the the planning, coordination, and conduction of the second Open Call.
D43cThis deliverable will provide the results for the Task 43 on semantic orchestration of offerings Outcome will be the report on research results as well as a prototype implementation that will be contributed to the overall software infrastructure for the marketplace D44 The deliverable is developed in three iterative steps starting with D43a that is due in M12 The second version D43b is due at M21 and the third version D43c is due at M30 Each new version will extend the previous version to take into account the progress on related deliverables eg use cases requirements BIG IoT API and high level architecture D43c contributes to MS5
D5.1.a The deliverable defines prerequisites / assumptions, services and application specification, measures for the technical, organizational and operational set-up of the pilot demonstrations. It further includes the set-up plans for each pilot, Northern Germany, Piedmont, and Barcelona. The deliverable is developed in 3 iterative cycles, starting with D5.1.a that is due in M9. The second version D5.1.b is due at M21 and the third version D5.1.c is due at M30. Each of the 3 iterative versions of this deliverable extent their predecessor version by refining the pilot specifications and adhering to new requirements, updates on use case definitions, etc. D5.1.a contributes to MS1.
D23cThe first release of this deliverable will specify the requirements for BIG IoT according to the overall project goal and vision as well as for the use cases defined in Task 22 As such this deliverable will set the scope the functionalities and the features of the overall architecture ie the BIG IoT API the semantic framework and the marketplace and provides the guidelines for the technology development in WP3 WP4 and WP5The third final release D23c will add the requirements for the final version of the BIG IoT technologies use cases and regional pilot implementations It will also include the requirements stemming from the addition of use cases accepted as part of the Open CallsD23c contributes to MS5
D53bThis deliverable is a report that describes the conduction and outcome of the integration deployment and testing of the 3 pilots and their use cases realizing services and applications as carried out in Task 53 For each of the 3 releases of D52 integrationdeploymenttesting is carried out and this deliverable is updated by reflecting the continued development The first version D53a is due in M18 the second version D53b is due in M25 and the third version D53c is due in M34D53b contributes to MS4
D4.2.b This deliverable will provide the specification of a semantic model which provides a formal definition of vocabulary terms to annotate the descriptions of offerings of services and platforms exposed through the marketplace. The deliverable is developed in 3 iterative cycles, starting with D4.2.a that is due in M12. The second version D4.2.b is due at M21 and the third version D4.2.c is due at M30. Each new version will extend the previous version to take into account the progress on related deliverables (e.g., use cases, requirements, BIG IoT API, marketplace, and high level architecture). D4.2.b contributes to MS3.
D3.3.c Lead of this deliverable is BOSCH CR in representation of BOSCH SI. This deliverable provides the design and detailed specification of security and privacy mechanisms for smart object platforms and services. This specification is aligned with and contributes to the BIG IoT API design (D3.1). This deliverable will have three versions, starting with D3.3.a that is due in M12. The second and third versions (D3.3.b at M21 and D3.3.c at M30) will build up on their preceding versions and will consider lessons learned from implementing and utilizing the previous version. D3.3.c contributes to MS5.
D3.1.c This deliverable provides the design and detailed specification of the BIG IoT API. Outcome of this deliverable will be the central basis for the implementation work of D3.4 as well as an important input to the work on marketplace and software infrastructure in WP4 as well as the realization of use cases in WP5. Following the agile project management approach, this deliverable will have three versions, starting with D3.1.a that is due in M12. The second and third versions (D3.1.b at M21 and D3.1.c at M30) of the BIG IoT API will build up on their preceding versions and their design will consider lessons learned from implementing and utilizing the previous version. D3.1.c contributes to MS5.
D5.1.c The deliverable defines prerequisites / assumptions, services and application specification, measures for the technical, organizational and operational set-up of the pilot demonstrations. It further includes the set-up plans for each pilot, Northern Germany, Piedmont, and Barcelona. The deliverable is developed in 3 iterative cycles, starting with D5.1.a that is due in M9. The second version D5.1.b is due at M21 and the third version D5.1.c is due at M30. Each of the 3 iterative versions of this deliverable extent their predecessor version by refining the pilot specifications and adhering to new requirements, updates on use case definitions, etc. D5.1.c contributes to MS5.
D62cThis deliverable reports yearly on the activities for dissemination standardization and coordination with other EU initiatives that were conducted in the respective year Also it describes planned activities for the next period The third report D62c summarizes and finalizes the activities during the course of the project
D7.2.a This deliverable comprises the planning, coordination, conduction and evaluation of the 2 Open Calls. It includes the necessary documents for the management of the 2 Open Calls, such as the announcement and advertisements, a detailed guide for applicants, the application form, etc. The deliverable D7.2.a describes in detail the the planning, coordination, and conduction of the first Open Call.
This deliverable will capture the results of the technology readiness analysis (Task 2.1). In particular, this report will provide an overview and technical analysis of relevant state-of-the-art technologies, highlighting their readiness with respect to the objectives and targets of the project. As such, D2.1 will become the baseline for the technical work carried out in WP3, WP4 and WP5. D2.1 contributes to MS1.
D6.1.a,b,c (M12, M24, M36) This deliverable reports yearly on the community building activities that were conducted in the respective year. Also, it describes planned activities for the next period. The third report, D6.1.c, summarizes and finalizes the activities during the course of the project.
D61bThis deliverable reports yearly on the community building activities that were conducted in the respective year Also it describes planned activities for the next period The third report D61c summarizes and finalizes the activities during the course of the project
D6.2.a This deliverable reports yearly on the activities for dissemination, standardization, and coordination with other EU initiatives that were conducted in the respective year. Also, it describes planned activities for the next period. The third report, D6.2.c, summarizes and finalizes the activities during the course of the project.
D4.1.a This deliverable is a report that specifies in detail the concepts, architecture, design, and interfaces of the software infrastructure underlying the marketplace. The software infrastructure can be used to setup and deploy a marketplace. The deliverable is developed in 3 iterative cycles, starting with D4.1.a that is due in M12. The second version D4.1.b is due at M21 and the third version D4.1.c is due at M30. Each new version will extend the previous version to take into account the progress on related deliverables (e.g., use cases, requirements, BIG IoT API, and high level architecture). D4.1.a contributes to MS1.
D4.3.a This deliverable will provide the results for the Task 4.3 on semantic orchestration of offerings. Outcome will be the report on research results as well as a prototype implementation that will be contributed to the overall software infrastructure for the marketplace (D4.4). The deliverable is developed in three iterative steps, starting with D4.3.a that is due in M12. The second version D4.3.b is due at M21 and the third version D4.3.c is due at M30. Each new version will extend the previous version to take into account the progress on related deliverables (e.g., use cases, requirements, BIG IoT API, and high level architecture). D4.3.a contributes to MS1.
D71cThis third release of this deliverable D71c will present the finalized exploitation activities of the project results
D71bThe second release of this deliverable D71b will detail the exploitation activities and will describe marketing strategy and elaborated business plan for the project outcomes
D3.2.b This deliverable provides the design and detailed specification of semantic models for smart object interoperability of smart object platforms and services. This specification is aligned with and contributes to the BIG IoT API design (D3.1). This deliverable will have three versions, starting with D3.2.a that is due in M12. The second and third versions (D3.2.b at M21 and D3.2.c at M30) will build up on their preceding versions and will consider lessons learned from implementing and utilizing the previous version. D3.2.b contributes to MS3.
D24cLead of this deliverable is BOSCH CR in representation of BOSCH SIThe first version of this deliverable D24a will specify the high level architecture for the first version of the BIG IoT implementations and development of the use cases and regional pilots It will define the core components and interfaces within the system and to the surrounding software infrastructure It will define the basic functionality and behaviour of all components as well as their relations and basic interaction patterns with the overall system As such this deliverable will serve as blueprint and architecture guideline for the technical work across all other work packages The specification will cover the smart objects and their IoT platforms the BIG IoT interoperation layer consisting of the BIG IoT API as well as the necessary support services and their hosting infrastructure and the BIG IoT marketplace with its services and applicationsThe final release D24c will further refine and advance the BIG IoT architecture for the final version of the BIG IoT implementations It will take into account all the experiences gained during the development of version 1 and version 2 of the BIG IoT technologies as well as the use case and pilot developments including the finding from the Open Call projectsD24c contributes to MS5
Searching for OpenAIRE data...
Publications
Author(s): Stefan Schmid, Arne Bröring, Denis Kramer, Sebastian Käbisch, Achille Zappa, Martin Lorenz, Yong Wang, Andreas Rausch, Luca Gioppo
Published in: Interoperability and Open-Source Solutions for the Internet of Things, 10218, 2017, Page(s) 39-55, ISBN 978-3-319-56876-8
Publisher: Springer International Publishing
DOI: 10.1007/978-3-319-56877-5_3
Author(s): Victor Charpenay, Hoan Nguyen, Mohamad Ibrahim, Achille Zappa, Arne Bröring
Published in: The Semantic Web: ESWC 2018 Satellite Events - ESWC 2018 Satellite Events, Heraklion, Crete, Greece, June 3-7, 2018, Revised Selected Papers, 11155, 2018, Page(s) 66-71, ISBN 978-3-319-98191-8
Publisher: Springer International Publishing
DOI: 10.1007/978-3-319-98192-5_13
Author(s): Ovidiu Vermesan
Published in: Advancing IoT Platforms Interoperability, 1, 2018, Page(s) 1-92, ISBN 9788-770220057
Publisher: River Publisher
DOI: 10.13052/rp-9788770220057
Author(s): Ovidiu Vermesan, Joël Bacquet
Published in: Cognitive Hyperconnected Digital Transformation, 1, 2017, Page(s) 1-310, ISBN 9788-793609105
Publisher: River Publisher
DOI: 10.13052/rp-9788793609105
Author(s): Werner Schladofsky, Jelena Mitic, Alfred Paul Megner, Claudia Simonato, Luca Gioppo, Dimitris Leonardos, Arne Bröring
Published in: Interoperability and Open-Source Solutions for the Internet of Things, 10218, 2017, Page(s) 91-106, ISBN 978-3-319-56876-8
Publisher: Springer International Publishing
DOI: 10.1007/978-3-319-56877-5_6
Author(s): Ovidiu Vermesan, Peter Friess
Published in: Digitising the Industry - Internet of Things Connecting the Physical, Digital and Virtual Worlds, 1, 2016, Page(s) 1-364, ISBN 9788-793379824
Publisher: River Publisher
DOI: 10.13052/rp-9788793379824
Author(s): Juan Hernández-Serrano, Jose L. Muñoz, Arne Bröring, Oscar Esparza, Lars Mikkelsen, Wolfgang Schwarzott, Olga León, Jan Zibuschka
Published in: Interoperability and Open-Source Solutions for the Internet of Things, 10218, 2017, Page(s) 107-122, ISBN 978-3-319-56876-8
Publisher: Springer International Publishing
DOI: 10.1007/978-3-319-56877-5_7
Author(s): Xavier Oriol, Ernest Teniente
Published in: Advanced Information Systems Engineering, 10816, 2018, Page(s) 220-235, ISBN 978-3-319-91562-3
Publisher: Springer International Publishing
DOI: 10.1007/978-3-319-91563-0_14
Author(s): Ovidiu Vermesan, Arne Broring, Elias Tragos, Martin Serrano, Davide Bacciu, Stefano Chessa, Claudio Gallicchio, Alessio Micheli, Mauro Dragone, Alessandro Saffiotti, Pieter Simoens, Filippo Cavallo and Roy Bahr
Published in: Cognitive Hyperconnected Digital Transformation Internet of Things Intelligence Evolution, IERC Cluster Book 2017, 2017, Page(s) 97-155, ISBN 9788-793609105
Publisher: River Publisher
Author(s): Arne Broring, Andreas Ziller, Victor Charpenay, Aparna S. Thuluva, Darko Anicic, Stefan Schmid, Achille Zappa, Mari Paz Linares, Lars Mikkelsen, Christian Seidel
Published in: IEEE Pervasive Computing, 17/4, 2018, Page(s) 41-51, ISSN 1536-1268
Publisher: IEEE Computer Society
DOI: 10.1109/mprv.2018.2873566
Author(s): Yong Wang , Andreas Rausch
Published in: The International Journal on Advances in Software, vol. 9, no. 3 & 4, year 2016, 2016, Page(s) pages: 272 - 282, ISSN 1942-2628
Publisher: IARIA
Author(s): Arne Broring, Stefan Schmid, Corina-Kim Schindhelm, Abdelmajid Khelil, Sebastian Kabisch, Denis Kramer, Danh Le Phuoc, Jelena Mitic, Darko Anicic, Ernest Teniente
Published in: IEEE Software, 34/1, 2017, Page(s) 54-61, ISSN 0740-7459
Publisher: Institute of Electrical and Electronics Engineers
DOI: 10.1109/MS.2017.2
Author(s): Lars Mikkelsen, Hans-Peter Schwefel, Tatiana Madsen
Published in: 2018 IEEE 17th International Symposium on Network Computing and Applications (NCA), 2018, Page(s) 1-4, ISBN 978-1-5386-7659-2
Publisher: IEEE
DOI: 10.1109/nca.2018.8548319
Author(s): Yulia Svetashova, Stefan Schmid, Andreas Harth
Published in: 2018 Global Internet of Things Summit (GIoTS), 2018, Page(s) 1-6, ISBN 978-1-5386-6451-3
Publisher: IEEE
DOI: 10.1109/giots.2018.8534561
Author(s): Hoan Nguyen Mau Quoc, Martin Serrano, John G. Breslin, Danh Le Phuoc
Published in: Proceedings of the 8th International Conference on the Internet of Things - IOT '18, 2018, Page(s) 1-8, ISBN 9781-450365642
Publisher: ACM Press
DOI: 10.1145/3277593.3277598
Author(s): Yulia Svetashova
Published in: Proceedings of the Doctoral Consortium at ISWC 2018 co-located with 17th International Semantic Web Conference (ISWC 2018), Vol-2181 urn:nbn:de:0074-2181-7, 2018, Page(s) 73-82
Publisher: CEUR
Author(s): Lars Mikkelsen, Radoslav Buchakchiev, Tatiana Madsen, Hans Peter Schwefel
Published in: 2016 8th International Workshop on Resilient Networks Design and Modeling (RNDM), 2016, Page(s) 302-308, ISBN 978-1-4673-9023-1
Publisher: IEEE
DOI: 10.1109/RNDM.2016.7608302