1 / 20

IEEE P2413 Background, History and Motivation

IEEE P2413 Background, History and Motivation. Outgrowth of multi-year series of IoT Standards workshops and roundtables. Objective: understand requirements by vested stakeholders.

lewisdove
Download Presentation

IEEE P2413 Background, History and Motivation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. IEEE P2413 Background, History and Motivation Outgrowth of multi-year series of IoT Standards workshops and roundtables. Objective: understand requirements by vested stakeholders. IEEE P2413 was initiated through guidance of IEEE-SA’s Industry-Strategic IoT Team. Focus on bridging market needs with developing IoT technology landscape. IEEE-SA Corporate Advisory Group (representing 200+ industry members) provides sponsorship for IEEE P2413. Maintain balanced focus on industry / market / technology and standards eco-system within development framework.

  2. IEEE P2413 Goals and Approach • Goals • Accelerate growth of IoT market by enabling cross-domain interaction and platform unification through increased system compatibility, interoperability, and functional exchangeability • Increase standardization of system architectures to support system benchmarking, safety, and security assessments • Reduce industry fragmentation and create a critical mass of multi-stakeholder activities around the world • Approach • Devise IoT architecture framework that covers architectural needs of various IoT application domains • Leverage the existing body of work

  3. IEEE P2413 Scope • IEEE P2413 will define architecture framework for IoT, including • description of various IoT domains • definitions of IoT domain abstractions • identification of commonalities between different IoT domains.

  4. What is an Architecture Framework? Definition:individual, team, organization, or classes thereof, having an interest in a system / systems Definition:interest in a system / systems relevant to one or more of its stakeholders Definition: work product expressing the architecture of a system from the perspective of specific system concerns Let’s have a look at ISO/IEC/IEEE 42010 Architecture framework • Definition: conventions for construction, interpretation and use of architecture views to frame specific system concerns • Conventions for a type of modelling: class diagrams, sequence diagrams, etc. • Takeaways: • IEEE P2413 will not reinvent existing standards (IETF, IEEE 802.1 …) • To be designed in a way that existing architectures congruent with IEEE 2413 • We will address communalities across application domains

  5. Where does the input come from?*

  6. Comprehensive Approach of IEEE P2413 • Three sample main topics detailed • Networking and communication • Compliance • Dependability and Security • Details provided in backup slides

  7. IEEE P2413 Liaisons • ISO/IEC JTC 1/WG 10 – Internet of Things • ISO/IEC JTC 1/SC 6/WG 7 – Network, Transport and Future Network • oneM2M • ITU-T JCA-IoT "Joint Coordination Activity on Internet of Things • Industrial Internet Consortium (IIC)

  8. IEEE P2413 Conclusions • IEEE P2413 identifies evolving transformational integration and convergence across technology and application domains as main objective • IEEE P2413’s goal is to provide an extensible integrated architectural framework that will continue to evolve and unify standards-creation and architecting efforts • IEEE P2413 will continue to deepen industry engagement by leveraging global IoT workshops, webinars, roundtables, and other tools of the IEEE IoT initiative. • IEEE P2413 is an open community and all are welcome to participate and to share perspectives on addressing and preparing for the inter-connected world of 2020.

  9. IEEE IoT Standards (List)

  10. IEEE IoT Standards (List) To learn more, visit us at: standards.ieee.org/innovate/iot

  11. Accelerating the IoT Network Effect Accelerating the IoT Network Effect Cooperation amongst global standards bodies and consortia is required to enable full IoT commercialization & innovation Global Standards Collaboration

  12. IEEE-SA Internet of Things: Presence http://standards.ieee.org/innovate/iot/

  13. Spanning the IoT Ecosystem

  14. Thank you For more information, please contact Sri Chandrasekaran sri.chandra@ieee.org

  15. Backup Slides

  16. IEEE Internet Initiative (3I) • Cross-organizational, multi-domain community that connects technologists and policymakers from around the world to foster a better understanding of, and to improve decisions affecting, Internet governance, cybersecurity, and privacy issues • Supporting and facilitating the development of open standards to address cybersecurity and privacy challenges • Working to identify societal implications of alternative technology policy solutions; • Monitoring the technology policy landscape; • Supporting, collaborating and partnering with Internet ecosystem entities, and • Connecting stakeholders to a comprehensive framework of conferences, educational programs, and standard. • Focal areas of 3I include • Universal Internet and digital connectivity • Quadruple trust: Protection, Security, Privacy and Safety • Transnational data flows • Internetinitiative.ieee.org

  17. Networking and Communication in IEEE P2413 • Context: development of networking and communication technologies outside of IEEE P2413 scope. However, important to understand approaches of integrating of such technologies into the architectural framework and understanding requirements in this context. • Application-centric communication • Identify communications requirements based upon information flow, frequency, allowed latency, required safety, energy efficiency requirements, etc. driven from the application’s view • Network- and channel-centric communication • Identify and advertise network capabilities to provide awareness of available transport options. Methods: message confirmation, scheduled vs. real time delivery, path/media/channel selection, sporadic network connections etc. towards the applications.

  18. IEEE P2413 and Compliance • Context: compliance has many value-adding touch points with IoT architecture and reference model. Among others, it ensures human and environmental safety, interoperability between systems, adherence with dependability and security, and alignment with regulatory and policy guidelines. • Features targeted: survey of industry and cross-industry compliance requirements, configurability of compliance elements such as rules type and compliance scoring. • Approach: work with standards bodies (e.g., ISO, IEC, IEEE) and regulatory bodies (e.g., EPA, BSEE, FDA), Compliance organization (e.g., ICA, ICPA). • Outcome: • Cross-domain requirements of compliance • Compliance elements for IEEE P2413 • High-level guideline on how to enable IoT-driven compliance in modern IT systems

  19. IEEE P2413 Dependability and Security • Recognize state-of-the-art methodologies: RAMS, etc. • Key principle “security in depth” • IEEE P2413 will gather and document specific architecture needs and requirements to emphasize on IoT-specific topics. Threat-analysis approach for IoT entities and their interactions.

More Related