Software Defined Everything IoT

Transkript

1 Software Defined Everything IoT Architektur der virtuellen Funktionen? Thomas Pfeiffenberger Salzburg Research / ANC Advanced Networking Center

2 CONSUMER IoT Delay Agnostic Web Traffic Clustered SDN Controller IoT EVERYWHERE IPTV Provider WAN C Delay Critical VoIP Traffic District Heating Control Access Edge Core Thomas Pfeiffenberger 2

3 Software Defined Everything IoT Architektur der virtuellen Funktionen? Thomas Pfeiffenberger Salzburg Research / ANC Advanced Networking Center

4 Herausforderungen in der Kommunikationsinfrastruktur end-to-end IP Kommunikation der IoT Geräte Erfordert eine Anpassung der Netzwerkfunktionen an die neuen Anforderungen aus dem IoT BereichManage a large number of devices with variety of IoT protocols Unterschiedliche implementierte IoT Geräte MTU differences, simplified vs. full protocol stack (e.g., CoAP/UDP vs. HTTP/TCP) single stack vs. dual stack processing and communications bandwidth sleep schedule, security protocols, etc. Herausfordernde Interaktion zwischen den Applikationen und der Infrastruktur dynamische Kommunikation Kritische Infrastrukturen unterschiedliche Zugangstechnologien (z.b.: wireless, wired, 5G, Fiber, Thomas Pfeiffenberger 4

5 Fehlende Standards und Frameworks Thomas Pfeiffenberger 5

6 Thomas Pfeiffenberger 6

7 Networking as it is! /Router App App App Operating System Specialized Packet Forwarding Hardware /Router App App App Operating System Specialized Packet Forwarding Hardware App App App /Router App App App Operating Specialized System Packet Forwarding Hardware /Router /Router App App App Operating Specialized System Packet Forwarding Hardware Operating Specialized System Packet Forwarding Hardware Thomas Pfeiffenberger 7

8 SDN Architecture Thomas Pfeiffenberger 8

9 Zusammenspiel SDN App NFV IoT C Thomas Pfeiffenberger 9

10 Offenen Fragen im Zusammenspiel SDN IoT NFV Wie können neue Kommunikationsstrukturen den Anforderungen entsprechen? Wie werden die unterschiedlichen IoT Protokolstacks abgestimme? Wie kann die Funktionalität der IoT Geräte in der SDN Welt abgebildet werden? Wie kann die Network Function Virtualisation NFV von IoT Funktionen abstrahiert werden? Wie kann die SDIoT Infrastrukture die erwartete Anzahl von IoT Geräten verwaltet? Ist SDN/NFV eine Ermöglicher (enabler) für neue IoT Anwendungen und Service! Thomas Pfeiffenberger 10

11 OPOSSUM: IoT enabler Clustered SDN Controller IPTV Provider WAN C Redundant Paths District Heating Control Access Edge Core Ferdinand von Tüllenburg, SDN World Congress 2016, The Hague,

12 OPOSSUM OpenFlow-based communication system for multi-energy domains Thomas Pfeiffenberger Salzburg Research / ANC Advanced Networking Center

13 Was ist SDN? Software defined networking Thomas Pfeiffenberger 13

14 Networking as it is! C /Router App App App Operating Specialized System Packet Forwarding Hardware /Router App App App Operating Specialized System Packet Forwarding Hardware App App App /Router App App App Operating Specialized System Packet Forwarding Hardware /Router /Router App App App Operating Specialized System Packet Forwarding Hardware Operating Specialized System Packet Forwarding Hardware C C Thomas Pfeiffenberger 14

15 SDN architecture App App App Operating System Specialized Packet Forwarding Hardware Control Path (Software) Data Path (Hardware) Thomas Pfeiffenberger 15

16 SDN OF Controller OpenFlow Protocol (SSL/TCP) Control Path OpenFlow Data Path (Hardware) Thomas Pfeiffenberger 16

17 SDN Architecture Thomas Pfeiffenberger 17

18 SDN architecture SDN OF Controller A B Control Plane A B C D Host B Host A E F G Forwarding Plane Thomas Pfeiffenberger 18

19 SDN architecture SDN OF Controller A B Control Plane A B C D Host B Host A E F G Forwarding Plane Thomas Pfeiffenberger 19

20 App App App SDN OF Controller A B Control Plane A B A B C A B D Host B Host A A B E A B F A B G Forwarding Plane Specialized Packet Forwarding Hardware Thomas Pfeiffenberger 20

21 OPOSSUM OpenFlow-based communication system for multi-energy domains Thomas Pfeiffenberger Salzburg Research / ANC Advanced Networking Center

22 OPOSSUM Programm IKT der Zukunft 2013 Fördergeber Bundesministerium für Verkehr, Innovation und Technologie bmvit Laufzeit 36 Monate, Start 1. Oktober 2014 (30.Sept 2017) Projektpartner: Nahwärme Eugendorf GmbH Multikom SRFG Thomas Pfeiffenberger 22

23 Critical infrastructure Reliable Communication 1. Traffic Separation Avoid Mutual Interference Proactive Delay Agnostic Web Traffic Clustered SDN Controller IPTV Provider WAN 2. Managed End-to-End Conn. Reactive Failover Time: < 1s C Delay Critical VoIP Traffic District Heating Control 3. Fast Failover Reactive Failover Time: < 50ms Access Edge Core 4. Controlled Packet Duplication Proactive Failover Time: none Ferdinand von Tüllenburg, SDN World Congress 2016, The Hague,

24 Lesson Learned: A Big Need for Big Tools What we have Different requirements on Reliability What we learned The Devil is in the Detail Things get complex in the brown field Each network is different What we need Description Verification Automation Monitoring What we did The Opossum App for ONOS Can do a lot of other Things The Opossum App for Reliability Configuration Ferdinand von Tüllenburg, SDN World Congress 2016, The Hague,

25 Meet us at: OpenFlow-based communication system for multi-energy domains Thomas Pfeiffenberger 25

26 Aufruf für neu Partner neue Projektidee IKT der Zukunft (Vorstellung ) Einreichung ca Mitte März Fördermöglichkeit durch BMvit Projektidee: Monitoring und Management for critical Infrastructures using P Thomas Pfeiffenberger 26

27 What we can do: Reliable Communication Delay Agnostic Web Traffic Clustered SDN Controller IPTV Provider WAN C Delay Critical VoIP Traffic District Heating Control 1. Traffic Separation Avoid Mutual Interference Proactive Access Edge Core Ferdinand von Tüllenburg, SDN World Congress 2016, The Hague,

28 What we can do: Reliable Communication Primary Path Alternative Path Clustered SDN Controller IPTV Provider WAN C District Heating Control 2. Managed End-to-End Conn. Access Edge Core Reactive Failover Time: < 1s Ferdinand von Tüllenburg, SDN World Congress 2016, The Hague,

29 What we can do: Reliable Communication Clustered SDN Controller IPTV Provider WAN C Alternative Path Primary Path District Heating Control 3. Fast Failover Access Edge Core Reactive Failover Time: < 50ms Ferdinand von Tüllenburg, SDN World Congress 2016, The Hague,

30 What we can do: Reliable Communication Clustered SDN Controller IPTV Provider WAN C Redundant Paths District Heating Control 4. Controlled Packet Duplication Access Edge Core Proactive Failover Time: none Ferdinand von Tüllenburg, SDN World Congress 2016, The Hague,