ccnxcon2012: session 2: network management framework for future internet scenarios
DESCRIPTION
Network Management Framework for Future Internet Scenarios Rui L Aguiar, Daniel Corujo (Instituto de Telecomunicações, Universidade de Aveiro), Ivan Vidal Fernandez, Jaime Garcia (Universidade Carlos III de Madrid)TRANSCRIPT
A Flexible Management Framework for Future
Internet Scenarios
Daniel Corujo, Rui L. Aguiar Universidade de Aveiro / Instituto Telecomunicações. Aveiro, Portugal
Iván Vidal, Jaime Garcia Universidad Carlos III de Madrid / Dept. Ingenieria Telematica. Madrid, Spain
CCNxCon 2012 – INRIA – Sophia-Antipolis, France September 12, 2012
Outline
• Increasing the deployment opportunities of CCN through the provision of intrinsic management mechanisms
• A flexible management framework for Content Centric Networking
• Features and examples
Content Centric Networking
• Provides new functional advantages for a content centered access
• … uses named content instead of host IDs
• … deploys a simple and scalable design
• … coupled with intrinsic support for various mechanisms (e.g., security)
But…
• Management and control mechanisms become needed
• Or the set of application scenarios can become reduced
• Example: How to improve the user experience when reaching for content • …which can have different requirements depending on its
type (e.g., video vs. data)? • …whose requirements can vary depending on the access
technology? • …which can dynamically change its conditions due to several
factors (e.g., mobility, load, etc.)? • …with different stakeholders at play (e.g., policies required)
Management and Control in CCN
• The previous challenges provide similar requirements for management and control • Independently of being considered in current Internet
• Or CCN environments
• So the real challenge we are addressing in our work is: • How can CCN facilitate management and control in a
content centric environment?
Example
• Handovers (i.e., Mobility) in Content Centric Environments
• Managing these kind of procedures requires efficient mechanisms (e.g., timing and delay are key factors)
• As such, we need to go beyond a working underlying network, into an actively efficient one
CCN mechanisms help here!
• CCN can operate independently of such procedures • But we consider that, by reutilizing the way CCN
operates (e.g., taping into its PIT and FIB modules, for example), we can add control optimization possibilities
• How to support this, then?
Management Framework
For Review Only
!"
Operator Core
ContentServer
Oth
er N
etw
ork
Internet
Content Store
Pending Interest Table (PIT)
Forward Information Base (FIB) Index
ptr type
Face 0
Face 1
Face i
Face i
Face N
Management Agent (MA)
Network Interfaces
Other Applications
NDN Fabric
User Equipment
Access Network #1
Access Network #2
a)
b)
Network Manager
Entity (ME)
#"Figure 1 – The NDN Flexible Management Framework: a) Manager Entity interfacing with the NDN fabric; $"b) Deployment of the management framework into an operator network featuring a Manager Entity %"
&"
Page 29 of 34
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960
Management Framework Features
For Review Only
!"
Operator Core
ContentServer
Oth
er N
etw
ork
Internet
Content Store
Pending Interest Table (PIT)
Forward Information Base (FIB) Index
ptr type
Face 0
Face 1
Face i
Face i
Face N
Management Agent (MA)
Network Interfaces
Other Applications
NDN Fabric
User Equipment
Access Network #1
Access Network #2
a)
b)
Network Manager
Entity (ME)
#"Figure 1 – The NDN Flexible Management Framework: a) Manager Entity interfacing with the NDN fabric; $"b) Deployment of the management framework into an operator network featuring a Manager Entity %"
&"
Page 29 of 34
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960
Management Entity (ME): ! Located in the network ! Contains an application
able to interface with the CCN fabric and obtain network-wide optimization information (distributed concepts can be introduced as well)
Management Agent (MA): ! Located in the user
equipment ! Interfaces with internal
NDN structures (i.e., PIT and FIB), network interfaces and applications
Management Framework Features
For Review Only
!"
Operator Core
ContentServer
Oth
er N
etw
ork
Internet
Content Store
Pending Interest Table (PIT)
Forward Information Base (FIB) Index
ptr type
Face 0
Face 1
Face i
Face i
Face N
Management Agent (MA)
Network Interfaces
Other Applications
NDN Fabric
User Equipment
Access Network #1
Access Network #2
a)
b)
Network Manager
Entity (ME)
#"Figure 1 – The NDN Flexible Management Framework: a) Manager Entity interfacing with the NDN fabric; $"b) Deployment of the management framework into an operator network featuring a Manager Entity %"
&"
Page 29 of 34
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960
Interaction ME/MA: ! Allows the network and
any user equipment coordinating management procedures
! Management is regarded as content exchanged through Interest/Data
ME and MA are deployed as application processes: ! The framework can be
decoupled from the underlying network architecture,
! Easy interoperation with any ICN approach
Management Framework Features
• Reliability • Content exchanges between MA and ME should proceed
reliably
• Security • MA and ME must be able to authenticate and determine the
trust that can be established on management data • Due to the existence of broadcast interfaces, confidentiality
and integrity
• Asynchronous Information Exchange • Push and Pull information
Results Using a CCN Management Framework
For Review Only !"
Face 0
Face 1
NDN Network
UE
Contentserver
PoA C
ME
PoA A
NDN fabric
PoA B
MA
#"Figure 3: Validation scenario $"
%"
Page 31 of 34
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960
Results Using a CCN Management Framework
80
120
160
200
240
0 20000 40000 60000 80000 100000 120000 140000 160000
0
1
RTT
(ms)
Activ
e fa
ce
Time (ms)
b)RTT
Average RTTFace
80
120
160
200
240
0
1
RTT
(ms)
Activ
e fa
ce
a)
Usage Scenarios
• Network Management Entity assistance: • Optimal Face selection • Load Balancing • Knowledge of better connectivity alternatives • Policies
• Benefits (case of face selection): • Reduced probing • Avoids face oscillation • Attachment to undetected/different technology point of attachment • Optimizes content reception • Energy conservation (alternative interfaces can be off and then
triggered)
Conclusion
• The Content-centric Management framework provides the means to increase management and control capabilities to optimize CCN behavior in many new kinds of scenarios
• Through our flexible framework, such scenarios can go beyond management and control
• More over, they open up new opportunities to which Future Internet architectures need to be on the look for! • An example of such scenarios can be the Internet of Things!
Speaking of the Internet of Things
• Nowadays, we are witnessing a massive deployment of connectivity capacities to existing and new devices • Enabled by evolutions of consumer electronics and wireless
access networks • This leads to the definition of a new paradigm: the Internet
of Things (IoT) • Support of this paradigm needs consideration in novel
Internet architectures, such as Information-Centric Networking
• IoT deployment challenges: • Addressing, naming, transport, security, interoperability,
scalability, data volume and energy efficiency
Overview of the framework
NDN namespace
Gateway
IoT devices
Clients
Clients
Supported procedures
NDN namespace
Gateway
IoT devices
Clients
Clients
Registration of IoT devices Discovery of IoT devices
Command execution & Content retrieval
Example: executing a command
IoT DeviceClient
name2: thing-name-prefix/client-publisher-ID/ESKdg [command, seq-number']/MACSKdg [Interest]
ESKdg [result]MACSKdg [Data]
SKdg-ID
Interest
Gateway
name1: /uc3m/devices/device/client-ID/ESKcg [command, seq-number]/MACSKcg [Interest]
Interest
DataData
ESKcg [result]Signature
Policy check
Command execution
Longest prefix match to match a device
name1
name2
(1)
(2)
(3)(4)
Example: content retrieval
IoT DeviceClient
ESKdg [content]MACSKdg [Data]
SKdg-ID
Interest
Gateway
name: /uc3m/devices/device/client-ID/ESKcg [sessionKey, SKshared-ID, seq-number]
Interest
Data
Data
SKshared-ID, ESKshared [content]Signature
Content retrieval
Longest prefix match to match a device
/uc3m/devices/device/content
thing-name-prefix/content
Selection of symmetric key SKshared
Interestname
Data
ESKcg [SKshared]Signature
(1)
(2)
(3)
(4)
(5)
(6)
The Infamous Set of Backup Slides!!!
For Review Only
!"Figure 2: Bootstrapping and management data exchange #"
$"
Page 30 of 34
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960
Experiments
For Review Only
!"!#"!$"
Basic NDN with 1 probe per face
Basic NDN with 5 probes per face
Framework-managed NDN
Average RTT (ms) 86.6140 84.685 78.9840
CI (ms) (84.6350, 88. 5930) (83.8573, 85.5127) (78.5232, 79.4448)
Overhead (%) 1.2908 5.7677 0.1121
Losses (%) 1.8102 1.5478 0.3728
Handovers/s 0.0594 0.06 0.0125 "#$%&!'(!)*++#,-!./!&01&,2+&34#%!,&5*%45( %"
Page 34 of 34
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960
Some preliminary results
0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1
0 2000 4000 6000 8000 10000
Rat
io R
x dev
ice/
Txcl
ient
Freshness time (ms)
= 10 req/s = 2 req/s = 1 req/s
= 0.2 req/s = 0.1 req/s