This document proposes a flexible management framework for Content Centric Networking (CCN) that provides intrinsic management mechanisms. The framework includes a Management Agent located in user equipment that interfaces with CCN structures like the Pending Interest Table and Forwarding Information Base. It also includes a Management Entity located in the network that can obtain optimization information. The framework allows network entities and user equipment to coordinate management procedures like handovers through asynchronous information exchange as content. It provides features like reliability, security, and asynchronous information exchange to support management scenarios for CCN.

1. 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
A Flexible Management
Framework for Future
Internet Scenarios
CCNxCon 2012 – INRIA – Sophia-Antipolis, France
September 12, 2012

2. 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

3. 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)

4. 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)

5. 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?

6. 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

7. 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?

8. Management Framework
Page 29 of 34
1
2
3 !"
4
5
6 NDN Fabric
7 Face 0 Network Interfaces
8
9 Face 1
10 Content Store
ptr type
11
a)
12 Face i
Pending Interest Management
13 Table (PIT) Agent (MA)
14 Face i
15 Forward Information
Base (FIB)
16 Index
17 Face N
18
Fo
Other Applications
19
20
21 User Equipment
22
rR
23
k
or
w
24
et
Content
N
Server Access Network Access Network
er
25
th
#1 #2
O
26
27
ev
b)
28
Internet Network
29 Manager
30 Entity (ME)
ie
31 Operator Core
32
33 #"
w
34
35 $" 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
36
O
37 &"

9. Management Framework
Features
NDN Fabric
Face 0 Network Interfaces Management Agent (MA):
! Located in the user
ptr type
Face 1
equipment
Content Store
a) Face i
! Interfaces with internal
Pending Interest
Table (PIT)
Management NDN structures (i.e., PIT
Agent (MA)
Face i
and FIB), network interfaces
Forward Information
Base (FIB) Index
and applications
Face N
Fo
Other Applications
Management Entity (ME):
User Equipment
! Located in the network
! Contains an application
r or
k
able to interface with the
w
et
Content
N
Access Network
Re
Server Access Network
er
CCN fabric and obtain
th
#1 #2
O
b) network-wide optimization
Internet Network information (distributed
vi
Manager
Entity (ME) concepts can be introduced
Operator Core
as well)
ew
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
O

10. Management Framework
Features
NDN Fabric
Face 0 Network Interfaces
Interaction ME/MA:
! Allows the network and
ptr type
Face 1
any user equipment
Content Store
a)
coordinating
management procedures
Face i
Pending Interest Management
Table (PIT)
! Management is regarded
Agent (MA)
Face i
as content exchanged
Forward Information
Base (FIB) Index
Face N
through Interest/Data
Fo
Other Applications
User Equipment ME and MA are deployed
as application processes:
r or
k
! The framework can be
w
et
Content
N
Access Network
Re
Server Access Network
er
decoupled from the
th
#1 #2
O
b) underlying network
Internet Network architecture,
vi
Manager
Entity (ME) ! Easy interoperation with
Operator Core
any ICN approach
ew
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
O

11. 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

12. of 34
Results Using a CCN
Management Framework
!"
PoA C
ME Face 0
NDN
Network
MA
PoA A
Face 1 UE
NDN fabric
Content
server PoA B
Fo
#"
$" Figure 3: Validation scenario
%"
rR

13. Results Using a CCN
Management Framework
240 1
a)
200
Active face
RTT (ms)
160
120
80
0
240 1
RTT
b) Average RTT
200
Face
Active face
RTT (ms)
160
120
80
0
0 20000 40000 60000 80000 100000 120000 140000 160000
Time (ms)

14. 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)

15. 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!

16. 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

17. Overview of the framework
NDN namespace
Clients
Gateway
Clients IoT devices

18. Supported procedures
Discovery of IoT devices Registration of IoT devices
NDN namespace
Clients
Gateway
Clients IoT devices
Command execution & Content retrieval

19. Example: executing a
command
Client Gateway IoT Device
Interest
(1)
name1
Longest prefix match to
match a device
Policy check
Interest
(2)
name2
Command
execution
Data
Data (3)
(4) ESKdg [result]
ESKcg [result] MACSKdg [Data]
Signature SKdg-ID
name1: /uc3m/devices/device/client-ID/ESKcg [command, seq-number]/MACSKcg [Interest]
name2: thing-name-prefix/client-publisher-ID/ESKdg [command, seq-number']/MACSKdg [Interest]

20. Example: content retrieval
Client Gateway IoT Device
Interest
(1)
/uc3m/devices/device/content
Longest prefix match to
match a device
Interest
(2)
thing-name-prefix/content
Content
retrieval
Data
(3)
ESKdg [content]
Selection of symmetric MACSKdg [Data]
key SKshared SKdg-ID
Data
(4)
SKshared-ID, ESKshared [content]
Signature
Interest
(5)
name
Data
(6)
ESKcg [SKshared]
Signature
name: /uc3m/devices/device/client-ID/ESKcg [sessionKey, SKshared-ID, seq-number]

21. Thank you for
watching!
Questions?
CONTACT US:
DCORUJO@AV.IT.PT

22. The Infamous Set of
Backup Slides!!!

23. 1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
Fo
19
20
21
22
r
23
24
Re
25
26
27
28
vi
29
30
31
ew
32
33
34
35
36
On
37
38
39
40
41
42
43
44
45
ly
46
47
48
49
50 !"
51 #" Figure 2: Bootstrapping and management data exchange

24. Experiments Page 34 of 34
1
2
3 !"
4 #" !
5
6 $" !
7
8 Basic NDN with 1 Basic NDN with 5 Framework-
9 probe per face probes per face managed NDN
10 Average RTT (ms) 86.6140 84.685 78.9840
11 CI (ms) (84.6350, 88. 5930) (83.8573, 85.5127) (78.5232, 79.4448)
12
13
Overhead (%) 1.2908 5.7677 0.1121
14 Losses (%) 1.8102 1.5478 0.3728
15 Handovers/s 0.0594 0.06 0.0125
16 %" "#$%&!'(!)*++#,-!./!&01&,2+&34#%!,&5*%45(
17
18
Fo
19
20
21
22
r
23
24
Re
25
26
27
28
v
29

25. Some preliminary results
1
= 10 req/s
= 2 req/s
0.9 = 1 req/s
= 0.2 req/s
= 0.1 req/s
0.8
0.7
Ratio Rxdevice/Txclient
0.6
0.5
0.4
0.3
0.2
0.1
0
0 2000 4000 6000 8000 10000
Freshness time (ms)