Standard for an Architectural

Framework for the Internet of Things

(IoT)

IEEE P2413

September 2016
2
What we talk about when we talk
about CPS/IoT
What is our goal (“satellite view”)?

How? ß “Informization” of physical interaction

mechanical mechanical
sensor actor
brake pedal brake

electronic electronic actor

sensor
brake pedal brake

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

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 P2413.
Maintain balanced focus on industry / market / technology
and standards eco-system within development framework.
Motivation and Goals of P2413

q  P2413 - Standard for an Architectural Framework for the Internet of

Things (IoT)
-  Promotes cross-domain interaction
-  Descriptions of various IoT domains, definitions of IoT domain
abstractions, and identification of commonalities between different
IoT domains
-  Quality "quadruple" that includes protection, security, privacy, and
safety
q  Motivated by the need to promote cross-domain interaction, aid system
interoperability and functional compatibility, and further fuel the growth
of the IoT market
q  Aims to provide an architecture framework which captures the
commonalities across different domains and provides a basis for
instantiation of concrete IoT architectures

Motivation, Approach, Content Development and Status 03.08.2016 5

Approach and Dependencies

q  P2413 is a top down approach

q  Follows the recommendations for architecture descriptions
defined in ISO/IEC/IEEE 42010 Systems and software
engineering - Architecture description (2011)
q  ISO/IEC/IEEE 42010
-  Provides a core ontology for the description of architectures
-  Specifies provisions that enforce desired properties of
architecture frameworks
-  Can be used to establish a coherent practice for developing
architecture frameworks
-  Can be used to assess conformance of an architecture
framework

Motivation, Approach, Content Development and Status 03.08.2016 6

Definition: individual, Definition: interest in a
team, organization, or Definition: work product expressing
system / systems
What is an Architecture Framework?
classes thereof, having relevant to one or
the architecture of a system from
the perspective of specific system
an interest in a system / more of its
systems concerns
stakeholders
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 2413 no new architecture and 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 (see next slides)
Where does the input come from?*
Hospitals & Doctors
Consumer equipment providers

Insurance companies
Consumers Healthcare
Appliances
Home & providers
Media Building
ICT infrastructure
providers
Facility
Regulators management

Shared
Logistics Retail Retail stores
Logistics Concerns
companies

Application
Public transport developers
companies Mobility/
Transpor- Energy
tation
Utilities
City authorities Manufactur-
ing

Manufacturing industries Automation equipment providers

*due to the diversity of IoT application areas only

selected domains and stakeholders are shown
8
 ISO/IEEE/IEC 42010 Architecture Framework

q  Architectures are
abstract notions

q  Architecture descriptions
are concrete artifacts
that can be shared and
analyzed

q  Architecture frameworks are principles,

conventions and practices for the
description of architectures established
within a specific domain of application
and/or community of stakeholders

Motivation, Approach, Content Development and Status 03.08.2016 9

P2413 Architecture Framework

Motivation, Approach, Content Development and Status 03.08.2016 10

Basic Document Structure
Part 1 IoT: Vertical Application Domains Informative

Provides descriptions of IoT behaviors in the context of vertical

application domains

Part 2 IoT: Modeling the Horizontal

Discussion of the core characteristics across IoT domains

Part 3 Architecture Framework Normative

IEEE/IEC/ISO 42010:2011 conformant description of the P2413

IoT Architecture Framework

Part n Using the IoT Architecture Framework Informative

Annex Further elaborates the P2413 IoT Architecture Framework to

develop a domain specific IEEE/IEC/ISO 42010:2011 conformant
architectural description

Motivation, Approach, Content Development and Status 03.08.2016 11

Architecture Framework Dev Process

Motivation, Approach, Content Development and Status 03.08.2016 12

 IEEE P2413 Membership
1.  BroadBand Tower, Inc. 14. Korea Electronics Technology
Institute (KETI)
2.  Cisco Systems
15. Mitsubishi Electric
3.  Emerson
16. NIST
4.  EPRI
17. Qualcomm Inc.
5.  Finger Food Studios
18. Rockwell Automation
6.  Hitachi, Ltd.
19. Schneider Electric
7.  Honeywell International
20. Senslytics
8.  Huawei Technologies
21. Siemens AG
9.  Industrial Technology Research
Institute (ITRI) 22. SIGFOX
10. Infocomm Development 23. STMicroelectronics
Authority (IDA)
24. Toshiba Corporation
11. Intel
25. Wipro
12. IoTecha
26. Yokogawa Electric Corporation
13. Kaspersky Lab
27. ZTE

13
 IEEE P2413 Working Group Meetings
1.  10-11 July 2014, Hosted by Siemens in Munich, Germany
2.  16-17 September 2014, Hosted by STMicroelectronics in Santa Clara, CA USA
3.  Teleconference, 28 October 2014
4.  Teleconference, 17 December 2014
5.  22-23 January 2015 in Taipei, Hosted by Institute for Information Industry (III).
6.  27-28 April 2015 in Grenoble, Hosted by Schneider Electric
7.  27-30 July 2015, Hollywood Beach, Florida USA
8.  2-6 November 2015, Grenoble
9.  1-3 February 2016 in Washington DC USA
10.  11-14 April 2016 in Tokyo Japan, Hosted by Renesas
11.  Teleconference, May 2016
12.  7-10 June 2016 in Santa Clara, CA USA
13.  27-30 September 2016 in Barcelona Spain
14.  24-27 January 2017, Shinagawa, Tokyo (hosted by Hitachi)
15.  27-30 March 2017, Las Vegas, Nevada, USA

14
 IEEE P2413 Liaisons
Established Liaisons
1.  ISO/IEC JTC 1/WG 10 "Working Group on Internet of Things”
2.  IEEE 802.24 "Smart Grid Technical Advisory Group”
3.  IEC SG8 "Industry 4.0 - Smart Manufacturing”
4.  ITU-T JCA-IoT "Joint Coordination Activity on Internet of Things”
5.  Industrial Internet Consortium (IIC)
6.  IEEE P42010
7.  OPC Foundation
8.  IVI
Liaisons in Progress
1.  ISO/IEC JTC 1/SC 6/WG 7 "Network, transport and future network”
2.  oneM2M
3.  Kantara Initiative
4.  AIOTI
5.  Open Fog Consortium (OFC)

15
P2413 – Conclusions
•  P2413 identifies evolving transformational integration and
convergence across technology and application domains as
main objective

•  P2413’s goal is to provide an extensible integrated

architectural framework that will continue to evolve and unify
standards-creation and architecting efforts.

•  P2413 will continue to deepen industry engagement by

leveraging global IoT workshops, webinars, roundtables, and
other tools of the IEEE IoT initiative.

•  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.
Thank you!

Join the IEEE P2413 Working Group

http://grouper.ieee.org/groups/2413/

For additional information, please contact:

Oleg Logvinov
P2413 Chair
oleg.logvinov.us@ieee.org
or
Soo Kim
IEEE-SA Project Manager
s.h.kim@ieee.org

17