icn based scalable audio video conferencing over virtual
play

ICN Based Scalable Audio/Video Conferencing over Virtual Service - PowerPoint PPT Presentation

ICN Based Scalable Audio/Video Conferencing over Virtual Service Edge Router (VSER) Platform Ravi Ravindran and Asit Chakraborti (ravi.ravindran@huawei.com/asit.chakraborti@huawei.com) (Huawei Research Lab, Santa Clara) (ITU/FG-IMT-2020, Turin,


  1. ICN Based Scalable Audio/Video Conferencing over Virtual Service Edge Router (VSER) Platform Ravi Ravindran and Asit Chakraborti (ravi.ravindran@huawei.com/asit.chakraborti@huawei.com) (Huawei Research Lab, Santa Clara) (ITU/FG-IMT-2020, Turin, Sept-2015)

  2. Speakers Biography: Dr. Ravi Ravindran is a Senior Staff Researcher at Huawei. He has been conducting advanced telecommunications research for over 15 years. His current area of research focuses on Information-centric Networking and extends to Internet of Things , 5G, NFV and SDN. Specifically, his research focus has been on NSF-funded future Internet proposals such as NDN/CCN, Mobility First, and XIA , in collaboration with standard bodies (IETF/ITU) ,external research groups and academia. Prior to this role, he was part of the CTO office at Nortel, where he was part of the Advanced Technology Group focused on research areas like Control Plane Routing Protocols related to IP/(G)MPLS, Scheduling problems in 4G Wireless, and End-to-End QoE/QoS Engineering for Multimedia. Over the course of his research, he has been part of more than 10 granted patents and over 40 pending filings in various areas of networking technologies. He has over 30 technical publications in conferences and journals. Dr. Ravindran received his Ph.D. in Systems and Computer Engineering from Carleton University in Canada.

  3. Agenda • 5G Requirements • 5G-ICN Architecture • VSER Platform • A/V Conferencing over VSER • A/V Conferencing Architecture • Demo Scenario

  4. 5G-ICN Architecture

  5. 5G Requirements Requirements have been set in [1] • Enable Service Centric Networking – Allow new Business Models – XaaS (Naas/SaaS/PaaS) – Not only Connectivity Services – Service Platform for Users and ASPs – Personalized and Contextualized • Low end-to-end Latency – 1-10ms depending on the application • High Capacity and Data Rate – >1000x Capacity, >10-100x Bandwidth • High Reliability – Security, Mobility, Disaster Scenarios • Heterogeneous Devices and Applications – Traditional and Emerging IoT (M2M)) [1] NGMN White Paper on 5G: https://www.ngmn.org/uploads/media/NGMN_5G_White_Paper_V1_0.pdf

  6. How ICN Meets these Requirements ? • ICN provides a flexible Service-Centric Platform. – Build in Security/Mobility/Muticasting/Compute/Cache • Placement of Compute and Cache/Storage Anywhere – BS, Lamp Posts, Home Gateway, Routers, etc • ICN Provides Information (service/content/host) Packet Abstraction to process/store it anywhere. • Multiple Modes of Communication – D2D/P2MP/MP2MP • Name Based Networking MORE SECURE than Address Based Networking – Security/Context tightly binds to Identity (e.g. Mitigate DDOS) – Many Security risks due to Address Exposure [1] – Receiver oriented communication, Receiver Anonymity. • Scalable and Flexible Name Resolution System – Local and Global • Mobility via Caching and Late-Binding • Service Orchestration via dedicated ASP Controllers working over ICN Network Abstractions. [1] Telit White Paper, “ M2M/IoT Cellular Data Security ” http://www.m2mnow.biz/2015/08/17/35874-telit-white- paper-m2miot-cellular-data-security/

  7. SE-RAN & ICN-SAN: Service-Enabled 5G Architecture Device Layer Service Connectivity Layer DC & App layer ICN Service Virtualization Platform Routing, Storage Security, Mobility ICN Service Router Computing (Level 1) Routing, Storage SE- RAN Security, Mobility ICN Router Computing (Level 2) NG C-RAN Data Center ICN Network Resource ICN-BS mgmt ICN-SR ICN-BS Service Mobility ICN-Wifi-AP Internet Core Low-Power Wireless RAN Applicatio (Lo-RAN) Enterprise ns, ICN Router Devices Proximity Sensors ICN Service Access Network (SAN) WPAN ICN-SR WLAN ICN-GW WNAN WWAN • Heterogeneous Radio Access & mobility • Unified backbone/core transport Common Information – Centric Bus • Ubiquitous security (CIBUS) • Context-aware Self-x networking & mgmt

  8. SE-RAN Functional Features • NG C-RAN – Flat Architecture and Heterogeneous Radio Access – ICN Edge Cloud Intelligence all the way to the BS and UE – Distributed Routing, Storage/Caching, Computing, Mobility Functions – Application/Services Binds to Names – Name Based Routing/Forwarding – Mobility/Migration – Multi-homing/Multicasting – Data based Security and Trust (Enforceable on the Infrastructure) – D2D/P2P/MP2MP – Adaptable and Service Centric (Low Latency, High Throughput etc.) • Common Information-Centric BUS (CIBUS) – Addresses the need for next 50B IoT devices – Middleware over Constrained and Non-Constrained Devices – Enables Self-Organization (Discovery, Routing, Service Point Attachment) – Contextualized Device/Service Discovery – Heterogeneous Radios (WPAN,LORAN, WLAN etc.) – Local/Global Naming Service – Hierarchical Data Processing – Security/Trust Management – PUB/SUB System for Large scale Content Distribution – Open-APIs for Inter IoT system connectivity

  9. ICN Service Access Network (ICN-SAN) • ICN Service Enabled Network Infrastructure – ICN Service Edge Routers • Host Arbitrary Service Functions • Caching/Storage/Computing features – ICN Routers focusing on High Performance Routing/Forwarding • Service Virtualization Platform – ICN-Centric Network Slicing/Virtualization and Resource Management – Fine Grained Cache/Compute/Bandwidth/Spectrum Resource Management for end-to-end Service Delivery – ICN based Network Abstraction • Software-Defined Name Based Routing – Opportunistic Placement of Service Functions and Inter- Connection to Adapt to varying user behavior and dynamics – Service Orchestration involving UE, Servers and VSERs, E- NodeB (end-to-end)

  10. Common Information-Centric BUS (CIBUS) for IoT Services Applications Devices Service Mgmt/Control API Discovery Management Context Processing e.g., Network services discovery e.g., Data aggregation CIBUS Device discovery Data filtering Middleware Name Management Policy Based Routing, e.g., Naming mgmt Forwarding and Mobility Name certification e.g., Self Clustering Name resolution Context-supervised routing [ICN Socket] LEAN ICN Protocol Light-weight OS ZigBee 802.11 a* BT SigFox 802.15.4 5G Cellular Proximity WPAN WLAN WNAN WWAN Lean ICN stack with Middleware for Embedded Systems.

  11. ICN PDU Structure • Name-based Networking Architecture • Application binds to persistent names than temporary location bindings (IP) • Isolates Applications and Services from underlying dynamics such as Mobility, Migration, Disconnection • Elastic Packet Format [1] proposal to have a single protocol for constrained and non-constrained networks unlike IPv6 and 6LowPAN. ICN Protocol Interest/Get Context ID(Content/Service/Device) Security IP Protocol Metadata Response/Put … Src-IP Dest-IP ToS TTL Security Info. ID(Content/Service/Device) Signature • Self-Sustained and elastic unit of Data • Send packet from i/f A to i/f B. • Cache/Processing anywhere in the pipeline. • Shortest Path or TE Path • Multicasting - Natural • Simple Forwarding Plane, Edge Complexity • Multi-homing – Natural • • Significantly better Mobility Scaling through Address Aggregation • Exploits ubiquitous computing, caching, bandwidth resources. • Intelligent forwarding Plane [1] IETF/ICNRG, “ Elastic ICN Packet Format ”, https://tools.ietf.org/html/draft -ravi-elastic-icn-packet-format-00

  12. 5G-ICN IoT Scenario Emergency Response Service Controller Service-id-1 ICN First Responder Interest-Notification {/service- id-2 | <emergency- Service-ID-2 Interest-Notification {/service- First Respond 911>|<Context>} id-1 | <emergency- ICN-BS ICN 911>|<Context>} Optical BH Service-id-1 ICN IN Interest-Notification {/Vehicle- id-x | <emergency- Interest-Notification {/service- 911>|<Context>} id-2 | <emergency- 911>|<Context>} Interest-Notification {/service-id -1| <emergency-911>|<Context>} • Ad Hoc Communication • Here the services are local, achieving latency requirements • Naming/Name resolution has only local significance. • Heterogeneous Backhaul, including High Speed Optical Networks or LEO Satellites [1] • Interest Notification is PUSH primitive being proposed for CCN/NDN [2] [1] Samsung on using Satellite in 5G: http://www.digitaltrends.com/computing/samsungs-space-internet-could-provide-the-whole-world-with- affordable-internet/ [2] Interest Notification, “ Support for Notifications in CCN”, https://tools.ietf.org/html/draft-ravi-ccn-notification-00

  13. Virtual Service Edge Router Platform (VSER)

Recommend


More recommend