Network Working Group Joachim W. Walewski Internet-Draft Siemens AG Intended status: Informational Alain. Pastor Expires: January 5, 2012 Bell Labs July 4, 2011 The Internet of Things - Use Cases and Requirements draft-walewski-iot-use-case-00.txt Abstract In this document we provide an overview of use-case specific requirements for (future) IoT applications and direct the reader to the pertinent literature. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on January 5, 2012. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Walewski & Pastor Expires January 5, 2012 [Page 1] Internet-Draft iot July 2011 This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Table of Contents 1. List of abbreviations . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Use cases and requirements . . . . . . . . . . . . . . . . . . 3 3.1. Some words on requirements engineering within IoT-A . . . . 3 3.2. Requirements based on stakeholder aspirations . . . . . . . 3 3.2.1. Multidimensional automated, trustworthy and seamless distribution monitoring . . . . . . . . . . . 4 3.2.2. Smart Cities . . . . . . . . . . . . . . . . . . . . . 4 3.2.3. eHealth . . . . . . . . . . . . . . . . . . . . . . . . 4 3.2.4. Electric cars . . . . . . . . . . . . . . . . . . . . . 4 3.2.5. Retail . . . . . . . . . . . . . . . . . . . . . . . . 4 3.2.6. Building automation . . . . . . . . . . . . . . . . . . 4 3.2.7. Use-case independent requirements . . . . . . . . . . . 5 3.3. Requirements based on the state of the art . . . . . . . . 5 3.3.1. Requirements from IoT-A . . . . . . . . . . . . . . . . 5 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 6. Informative References . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 Walewski & Pastor Expires January 5, 2012 [Page 2] Internet-Draft iot July 2011 1. List of abbreviations IoT-A: Internet of Things Architecture; EU research project (2010- 2013). 2. Introduction The Internet of Things is an emerging technology which is characterized by a pronounced heterogeneity and richness of envisioned usage domains. Due to this heterogeneity not all protocols developed for the !otraditional!+/- Internet will be applicable, and suits of new solutions will be required. In order to devise such solutions a thorough study of the application domain, as well as the pertinent requirements is needed. This RFC is intended as a digest for such overviews. 3. Use cases and requirements 3.1. Some words on requirements engineering within IoT-A The majority of the requirements referenced in this RFC were derived within the project Internet-of-Things Architecture (IoT-A), which started in September 2010 and will provide its final reports in August 2013. An important part of the IoT-A research agenda is to compile a comprehensive list of requirements for the IoT. These can loosely be separated into three categories: stakeholder requirements; requirements derived from the state of the art, and requirements provided by the project partners. Requirements from stakeholder outside IoT-A were collected during a stakeholder workshop in October 2010. These use cases were included !oas they are!+/- in a project deliverable [Pastor, 2010]. This deliverable also outlines the requirements-engineering process employed in IoT-A. After this workshop, these requirements were rephrased as system requirements and classified by the labels !otechnical!+/- and !onon-technical!+/-. Furthermore, they were grouped by perspectives and views. A preview of the refined requirements were provided in another project deliverable [Salinas, 2010], and a finalized list was provided in the recently published !oInitial Architectural Reference Model for IoT!+/- [Bauer, 2011]. The latter document also contains a preliminary list of requirements based on project-partner input and the state of the art. 3.2. Requirements based on stakeholder aspirations Walewski & Pastor Expires January 5, 2012 [Page 3] Internet-Draft iot July 2011 3.2.1. Multidimensional automated, trustworthy and seamless distribution monitoring 3.2.1.1. Requirements from IoT-A Stakeholders: Edinburgh Napier University, Lufthansa Cargo, and Siemens IT Solutions Source: [Pastor, 2010], Section 5.1 3.2.2. Smart Cities 3.2.2.1. Requirements from IoT-A Stakeholders: Alcatel Lucent, Centro Ricerche Fiat Source: [Pastor, 2010], section 5.2 and 5.4.1 3.2.3. eHealth 3.2.3.1. Requirements from IoT-A Stakeholders: ETSI Source: [Pastor, 2010], section 5.3.1 3.2.4. Electric cars 3.2.4.1. Requirements from IoT-A Stakeholders: ETSI, Centro Ricerche Fiat Source: [Pastor, 2010], section 5.3.2 and 5.4.2 3.2.5. Retail 3.2.5.1. Requirements from IoT-A Stakeholders: Group Casino Source: [Pastor, 2010], section 5.5 3.2.6. Building automation Stakeholders: Source: Walewski & Pastor Expires January 5, 2012 [Page 4] Internet-Draft iot July 2011 3.2.7. Use-case independent requirements 3.2.7.1. Requirements from IoT-A Stakeholders: European Commission Source: [Pastor, 2010], section 5.6 3.3. Requirements based on the state of the art 3.3.1. Requirements from IoT-A A preliminary list (that is not sorted by usage areas) can be found in Annex A.2 of [Bauer, 2011]. 4. IANA Considerations TBD 5. Security Considerations TBD 6. Informative References [Project Deliverable D1.2] M. Bauer, N. Bui, P. Giacomin, N. Gruschka, S. Haller, and etc., "Project Deliverable D1.2 "C Initial Architectural Reference Model for IoT", Project: http://www.iot-a.eu/ public/public-documents/project-deliverables/1/1/ D1%202_Initial_architectural_reference_model_for_IoT.pdf/ at_download/file, June 2011. [Requirements-List] A. Pastor, E. Ho, A. Salinas Segura, R. Kernchen, and etc., "Project Deliverable D6.1 - Requirements List", Project: http://www.iot-a.eu/public/public-documents/ project-deliverables/1/1/IoT-A_Deliverable_6.1.pdf/ at_download/file, November 2010. [Stakeholder-opinions] A. Salinas Segura, R. Kernchen, and etc., "Project Deliverable D6.6 - Report on Stakeholder opinions", Project: http://www.iot-a.eu/public/public-documents/ project-deliverables/1/1/IoT-A_Deliverable_6.6.pdf/ Walewski & Pastor Expires January 5, 2012 [Page 5] Internet-Draft iot July 2011 at_download/file, Nov. 2010. Authors' Addresses Joachim W. Walewski Siemens AG Otto-Hahn-Ring 6 81739 Munich Phone: +49 (89) 636 45850 Email: joachim.walewski@siemens.com Alain Pastor Bell Labs Route de Villejust 91620 Nozay Email: alain.pastor@alacatel-lucent.com Walewski & Pastor Expires January 5, 2012 [Page 6]