Transcript
Interoperability within the IoT
[email protected] Anders P. Mynster,
[email protected] Senior Consultant EMC & Wireless March 2016
ASICs enabling IoT
Technical details for THOR Front-end comply with ISO 14443A-4 and ISO 15693 Ultra low power tag storage mode (< 0.1μA)
Available as Tested Dies (KGD) or in QFN
DES encryption hardware support Can be operated with and without battery power SPI master interface for auxiliary slave openMSP430 CPU
Ultra low power clock optional external crystal
16 bits linear low-offset Sigma-Delta
12 K samples storage capacity Firmware upgradable
External sensor can be attached
Fully configurable temperature logging profile in the range -30°C to + 100ºC with accuracy: ±0.5°C (abs), ±0.1°C (relative)
IoT specific interoperability challenges Levels of interoperability Co-existence Cyber security Standards System guidelines
IoT definitions • The Internet of Things (IoT) is a framework in which all things have a representation and a presence in the Internet. More specifically, the Internet of Things aims at offering new applications and services bridging the physical and virtual worlds, in which Machine-to-Machine (M2M) communications represents the baseline communication that enables the interactions between Things and applications in the cloud. – IEEE Communication society
IoT-A Reference Architecture
Source: Internet of Things – Architecture IoT-A D1.5
IoT system components
ID
RF
RF
IP
Digital
Rule based engine
Device management
Analog Device security Sensor
Event Trigger
Actuator
Thing
Analytics
Api
Storage
App
IoT system example
Nordic IoT centre Road to Manufacturing Solutions Concept validation Services
Concept validation
Feasibility studies
IC Design Services
IC manufacturing
IoT device design
State-of-the-art Pretotyping Context validation Design panel User interactions Regulatory strategy Quality Process Business model Cloud implications Quality Process
Link budget validation Environment evaluation Perceptual evaluation Conformance Req. Spec. Choice of Wireless Tech. System design Requirement Specification Prototyping Sensor hardware Sensor algorithm Energy Harvesting Battery lifetime Risk Assessment
Digital Analog Mixed signal Layout DFT Foundry libraries Optical sensors RF Power management Ultra low power Front-end Back-end
Wafer purchase PCB layout Wafer storage Design for manufacturing Wafer testing EMS Package design Antenna Design Package Evaluation Prototyping Encapsulation Small series IC testing Scale to Volume Storage & shipping Embedded software App development Yield Analysis Cloud implementation Supply chain optimization Supply chain management LAT HTOL
Test & validation Accredited conformance testing ElectroMagnetic Compatibility(EMC) Real-life RF environments Environmental Impact Product Safety Evaluation Approval Management Technical construction file Extreme test Software validation Failure Analysis Troubleshooting
Wireless Technologies Bluetooth Bluetooth ULP RF4CE ZigBee, 2.4 GHz ZigBee, 915 MHz (USA) ZigBee, 868 MHz (EU) ZigBee PRO, 2.4 GHz 802.11 FHSS Wi-Fi classic Wi-Fi 11a Wi-Fi 11b Wi-Fi 11g Wi-Fi 11n Z-Wave(EU) Z-Wave(US) Z-Wave(Far East) Ant Wavenis Wireless USB Wireless M-bus
DSRC 915 MHz DSRC 5.7GHz EnOcean MiWi, 2.4 GHz MiWi, 915 MHz (USA) MiWi, 868 MHz (EU) WAP 6LowPAN/IPv6 SimpliciTI Sensinode Wireless Desktop Protocol Synapse wireless Scatterweb KNX DECT WirelessUSB(cypress) RuBee Cwave(pulse link) TransferJet MediaFLO
Millenial Net Weightless WirelessHD(HR PHY) WirelessHD(LR PHY) WirelessHART ISA-SP100.11a DECT 6.0 Cat-iq GSM (2G) GPRS/EDGE (2.5G)
6LowPAN LoRa LTE-M IEEE 802.11ac KNX-RF SigFox NB-IoT Clean Slate Analog LTE-NB
UMTS/CDMA (3G) HSPA (3.5G) LTE Advanced (4G) UWB-WiMedia NFC (passive +active) NFC active only WiMax(WiBro in Japan) RLAN Ensation TinyMesh
Ingenu HaLowTM TETRA Proprietary UWB-WiMedia
Standards for technical components
Levels of interoperability "the ability of two or more systems or components to exchange data and use information" - 3GPP Technical – M2M, 802.11x, USB, RS485 Syntactical – HTML, XML, HTTPs, MQTT Semantic – the meaning of the data Organisational – meaningful data to support business via API
Source: IERC Semantic interoperability, March 2015
IEEE P2413 – Stakeholder analysis Hospitals & Doctors
Consumer equipment providers
Insurance companies
Consumers
Healthcare
Media
ICT infrastructure providers
Home & Building
Appliances providers
Facility management Regulators Logistics
Logistics companies
Shared Concerns
Retail
Retail stores
Application developers
Public transport companies
Mobility/ Transpor-tation
City authorities Manufacturing industries
Energy
Utilities Manufactur-ing
Automation equipment providers * due to the diversity of IoT application areas only selected domains and stakeholders are shown 17
P2413 - Architecture Framework Dev Process
Standards verticals and horisontals
Nordic IoT centre – the philosophy • Simulations and ideas to be proven in the real world
• Partnership and community driven development • Understanding IoT requirements • Technological foundation • Application centered • Secure solutions • Scalability • Availability
Co-existence ERC/REC 70-03
Radio interference Wireless Camera
WiFi
22
Cyber security
• Eavesdropper is listening in on data or commands to reveal confidential information about the operation of the infrastructure • Fake device is injecting fake measurements and data to disrupt the control processes and cause them to ract inappropriately, dangerously or can be used to mask physical attacks 23
Cyber security – Covering the basics • OWASP IoT top 10 – – – – – – – – – –
Insecure web interface Insufficient Authentication Insecure network services Lack of transport encryption Privacy concerns Insecure cloud interface Insecure mobile interface Insufficient security configurability Insecure software/firmware Poor physical security
Seven strategies
Source: Tripwire - Defending industrial control systems with tripwire based on - Department of Homeland Security (DHS) - National Cybersecurity and Communications Integration Center(NCCIC) - National Security Agency (NSA)
Standards
Source: https://xkcd.com/927/
TR 103 375 on IoT Landscaping •
329 standards identified –
– –
•
Over 70% of standards in – – –
•
allocated to • 7 vertical IoT Domains (LSPs) • 7 Knowledge Areas (AIOTI WG3) 150 Generic Standards • Common to 3+ vertical domains 179 Domain-specific Standards Communication and connectivity Integration/Interoperability IoT Architecture
Common standards mostly in – – – –
Communication and connectivity Integration/Interoperability Device and sensor technology Infrastructure
TR 103 376 IoT Gap Analysis • What gaps are – Missing standards; missing APIs – Duplications requiring harmonization – Missing interoperability profiles
• Technical/Business/Societal gaps – Security & privacy classified as Societal gaps
• Gaps Identification – Survey in the IoT community (215 answers) – Complemented by the STF experts analysis
• Dissemination of STF results – Towards the IoT community e.g., LSPs
• Resolution of gaps – Left to the proper organizations in the IoT commuiity
General requirements for an IoT system • • • • • • • • • •
Regulation Compliance Autonomous Network functionality Auto-configuration Scalability Discoverability Heterogeneity Unique Identification Useability Standardised interfaces Well defined components
Network connectivity Time Awareness Location Awareness Context & Content Awareness Modularity Reliability Security Confidentiality and Privacy Lagacy components Manageability • Risk Management • • • • • • • • •
Source: Study Report on IoT Reference Architectures/Frameworks, ISO/IEC August 2014
Conclusion Consider the application from multiple stakeholders Look at interoperability in the perspective of – – – –
Technical Syntactic Semantic Organisational
Remember that you are not alone in the world – Co-existence – Cyber security
Standard landscape reports – remeber the requirements
Thank you for your attention Anders P. Mynster,
[email protected] Senior Consultant EMC & Wireless November 2016
