ICN Based Scalable Audio/Video Conferencing over Virtual Service
Edge Router (VSER) Platform
Ravi Ravindran and Asit Chakraborti([email protected]/[email protected])
(Huawei Research Lab, Santa Clara)(ITU/FG-IMT-2020, Turin, Sept-2015)
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.
Agenda
• 5G Requirements
• 5G-ICN Architecture
• VSER Platform
• A/V Conferencing over VSER
• A/V Conferencing Architecture
• Demo Scenario
5G-ICN Architecture
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
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/
SE-RAN & ICN-SAN: Service-Enabled 5G Architecture
Low-Power Wireless RAN(Lo-RAN)
NG C-RAN
Applications,Devices
ICN-BS
ICN-BS
ICN-SR
ICN-SR
SE- RAN Routing, StorageSecurity, MobilityComputing (Level 2)
Service Mobility
ICN Service VirtualizationPlatform
ICN Network Resourcemgmt
ICN Router
Routing, StorageSecurity, MobilityComputing (Level 1)
ICN Service Access Network (SAN)
Internet Core
Data Center
Enterprise
Common Information –Centric Bus(CIBUS)
Pro
ximity
WP
AN
WLA
NW
NA
NW
WA
N
ICN-GW
Device Layer Service Connectivity Layer DC & App layer
ICN-Wifi-AP
• Heterogeneous Radio Access & mobility
• Unified backbone/core transport
• Ubiquitous security
• Context-aware Self-x networking & mgmt
Sensors
ICN Service Router
ICN Router
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
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)
Common Information-Centric BUS (CIBUS) for IoT
Discovery Management Context Processing
Name Management Policy Based Routing, Forwarding and Mobility
LEAN ICN Protocol
Light-weight OS
[ICN Socket]
e.g., Network services discoveryDevice discovery
e.g., Data aggregationData filtering
e.g., Naming mgmtName certificationName resolution
e.g., Self ClusteringContext-supervised routing
Service Mgmt/Control API
DevicesApplicationsServices
Proximity WPAN WLAN WNAN WWAN
802.15.4 5G Cellular802.11 a* BT SigFox
ZigBee
CIBUSMiddleware
Lean ICN stack with Middleware for Embedded Systems.
ICN PDU Structure
[1] IETF/ICNRG, “Elastic ICN Packet Format”, https://tools.ietf.org/html/draft-ravi-elastic-icn-packet-format-00
• 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.
IP Protocol
ICN Protocol
Src-IP Dest-IP ToS TTL …
• Send packet from i/f A to i/f B.
• Shortest Path or TE Path
• Simple Forwarding Plane, Edge Complexity
• Scaling through Address Aggregation
Interest/Get
ID(Content/Service/Device)
Metadata
Security
Response/Put
ID(Content/Service/Device) Signature
• Self-Sustained and elastic unit of Data
• Cache/Processing anywhere in the pipeline.
• Multicasting - Natural
• Multi-homing –Natural
• Significantly better Mobility
• Exploits ubiquitous computing, caching, bandwidth resources.
• Intelligent forwarding Plane
Context
Security Info.
5G-ICN IoT Scenario
• 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
Interest-Notification{/service-id-1 | <emergency-911>|<Context>}
Interest-Notification{/service-id -1| <emergency-911>|<Context>}
ICN
Service-id-1
ICN
Service-id-1
ICN-BS ICN
Service-ID-2
Interest-Notification{/service-id-2 | <emergency-911>|<Context>}
Interest-Notification{/service-id-2 | <emergency-911>|<Context>}
Interest-Notification{/Vehicle-id-x | <emergency-911>|<Context>}
First Responder
IN
Optical BH
First Responder
Emergency Response Service Controller
Virtual Service Edge Router Platform (VSER)
Page 14HUAWEI TECHNOLOGIES CO., LTD.
VSER: Virtual Service Edge Router High Level View
ICN Router
(CCN)
ICN Service Hypervisor
ICN Services
ICN
Se
rvic
e
Man
ag
em
en
t
ICN-UE
ICN A-UNI
ICN Service Gateway
ICN Router
ICNService-1
L3/L2
ICNService-2
…
ASP-1
ASP-2
…
Service Manager
ICN Service Orchestrator(ICN Cloud Controller + ICN Network Controller)
Service Manager
ICN Service Profile
Manager
ICN S-UNI
L3/L2
ICN Router
App SAL
ICN
SAP
ICN Edge-Cloud
ICN Platform API
ICN Service Gateway
SAP
ASP-3Service
Manager
ICNService-1
ICNService-2
VFSR-2
VFSR-1
ICN C-API
VSER Platform Highlights• ICN based Service Edge Router
• ICN Service Virtualization
• ICN Service Function Life Cycle
Orchestration and Management
• Service Function Chaining
• Service Discovery, Service
Contextualization.
• Generalized to any service, real-time
(conferencing, IOT) or non real-time
(content delivery)
• PULL/PUSH, MP-to-MP communication
• Unified control functions interworking
with SDN/NFV
• Service Orchestration by OpenStack and
FloodLight.
• Non-proprietary Platform
• Overlay deployment of ICN
• Optimized software stack including Multi-
threaded CCNx.
VSER
[1] Ravi Ravindran et al, “Towards Software Defined ICN Based Edge Cloud Services” IEEE, CloudNet, 2013
[2] P. Talebifard, R. Ravindran et al, “An Information Centric Networking Approach Towards Contextualized Edge Service “, IEEE, CCNC, 2015
Interest/Data
SF1
SF2
SF3
ICN SF Chaining
Page 15HUAWEI TECHNOLOGIES CO., LTD.
Realizing ICN Enabled Network Slicing Platform
Service-x Controller
(e.g. content distribution)
Internet Core
• Current Network Slicing definition focuses on :
Connectivity, Network and Host level Programmability and Resource Commitment.
• Network Slicing from ICN perspective Includes enabling and enforcing :
Naming, Context Processing, Security (Access/Integrity/Trust), Data , Resource Requirements
(Cache/Storage/Compute), Mobility-As-A-Service, Name based Routing Services
ICN Platform can offer these functions as a service to allow service differentiation
ICN slices are driven over L2, L3(IPv4/v6), Hybrid, Wireless, Optical Technologies with Programmable
Bandwidth/Specturm resources. (ICN is Transport Agnostic)
• Fine granular Slicing can be realized at Service, Control and User Plane level to meet specific application requirements.
• Service naming
•Service Discovery
• Service Configuration
• Service Request/Routing
• Context Expression
• D2D /Multi-homing
• Mobility as a Service
•Edge Service Control Functions
• Context Processing
• Caching/Storage/Data
• Security Services
• Mobility as a Service
• Service-based Spectrum
Management
ASP Service
Service specific
Compute/Cache/Stor
ageSlice
• Edge Cloud Service Orchestration
•Edge Cloud Service State
• Service function
Placement/Composition
• End-to-end Resource Management
• Service Logic Execution
• Service Monitoring (KPI)
VSER
RSU
ICN Enabled
Access Network
Service-y Controller
(e.g. V2V)
ICN Network Abstraction
ICN Network Slice
Service Functions
ASP Service
Video Streaming Service Slice
V2V Slice
Transport Slice Transport SliceTransport Slice
Page 16HUAWEI TECHNOLOGIES CO., LTD.
Audio/Video Conferencing over VSER
Page 17HUAWEI TECHNOLOGIES CO., LTD.
Audio & Video Conferencing Challenges
• Audio 150ms, Video 350ms, Sync +45ms to -125ms
• Difficult with CCN/NDN as is, considering its a PULL based architecture
• Minimize latency means to emulate PUSH model in CCN/NDN without
sacrificing Multicasting, Flow Balance, Caching, Multi-Path Routing
features.
• Scale to any number conferences and video flows
• Avoid any single point of bottleneck
• Random Join/Leave of Participant
• Participant able to choose any participant video at anytime
• Communication should be Authenticated and Private
• Current design suffers from centralized bottlenecks in a client-
server design or clients themselves in a P2P design.
Page 18HUAWEI TECHNOLOGIES CO., LTD.
Serverless Scalable Audio-Video Conferencing
over VSER [1][2]
Conference Controller Functions
• Enable MP-2-MP Connectivity
• Conference Level Virtualization : Multiple Simultaneous Conferences , Service Scaling, Dynamic Name Based Routing,
Conference Monitoring and Management.
• Context level Adaptation
VSER-
NSAP
Edge CloudEdge Cloud
Edge Cloud Edge Cloud
Bandwidth Scales
O(N), where N =#of
Participants
VSER-
NSAP
VSER-
NSAP
VSER-
NSAP
Conference
ControllerInterest {Notify: { VSER://conference-
session/karen/<fingure-print>}Interest {Content: { VSER://conference-
session/karen/<fingure-print>}
Notifications
Content
Interest {Content: {
VSER://conference-
session/karen/<fingure-print>}
Interest {Content: {
VSER://conference-
session/karen/<fingure-print>}
[1] Asit Chakraborti et al, “ICN Based Scalable Audio/Video Conferencing over Virtual Service Edge Router (VSER) Platform ” ICN Sigcomm, 2015
[2] Anil Jangam et al, “Realtime Multi-Party Video Conferencing Service over Information-Centric Network”, Workshop on Mutimedia Streaming in
ICN (MuSIC), 2015
Page 19HUAWEI TECHNOLOGIES CO., LTD.
A/V Conferencing Architecture
• The Producer design is simpler in the sense of generating A/V content and publishing it for
consumption.
• The Consumer design is challenges considering: 1) Lack of knowledge of Names ; 2) Decipher
if content is from Cache or Producer; 3) Pre-fetching to achieve Producer rate ; 4) Flow
Control/Cache recovery Considering Network Conditions
• We address these challenges using VSER Based Notification Mechanism, which guides the
consumers Interest expression process.
Page 20HUAWEI TECHNOLOGIES CO., LTD.
A/V Conferencing Demo Scenario over VSER
• Conference Controller manages states of all the sites, participants and mapping to Proxy SF to handle Media
Notifications.
• Controller is provided ICN Abstraction, to manage Name Based Routing to UEs mapping to different sites.
• Mobility in CCN proposed to be supported using Forwarding-label proposal [1]
L3/L2 Conf. Service
Conf. Service
Conf. Service
VSER-1
Internet
ICN Network Based Conferencing Service
ICN Service Orchestrator
VSER-2
ICN A-UNI
ICN A-UNI
ICN S-UNI
Service function orchestration and
Dynamic CCN FIB Configuration
ICN
Conf. App SAL
• Service Discovery
• Service Request/Response
•Data Request/Response
• Mobility
•Contextualization
Edge
Cloud
Edge
Cloud
Enterprise
Operator1
Parameters (# of sites,
users, devices, etc)
Bandwidth and
Compute Requirements
2
34
[1] IETF/ICNRG, “Forwarding-Label support in CCN Protocol”, https://tools.ietf.org/html/draft-ravi-ccn-forwarding-label-00
Page 21HUAWEI TECHNOLOGIES CO., LTD.
Conclusions
• ICN offers a natural service-centric platform to
enable end-to-end Service Virtualization.
• SE-RAN proposal integrates traditional smart
devices with CIBUS enabling connectivity and
self-organization to all the IoT devices.
• VSER is a ICN based Service-Edge router which
can host arbitrary ICN Service Functions.
• We discussed A/V Conferencing Architecture
and the demo scenario based on VSER.
Thank You..and
