CCNxCon2012: Session 2: Network Management Framework for Future Internet Scenarios

1,139 views

Published on

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)

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,139
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
9
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

CCNxCon2012: Session 2: Network Management Framework for Future Internet Scenarios

  1. 1. Daniel Corujo, Rui L. AguiarUniversidade de Aveiro / Instituto Telecomunicações. Aveiro, PortugalIván Vidal, Jaime GarciaUniversidad 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. 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. 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. 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. 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. 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. 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. 8. Management FrameworkPage 29 of 34123 !"456 NDN Fabric7 Face 0 Network Interfaces89 Face 110 Content Store ptr type11 a)12 Face i Pending Interest Management13 Table (PIT) Agent (MA)14 Face i15 Forward Information Base (FIB)16 Index17 Face N18 Fo Other Applications192021 User Equipment22 rR23 k or w24 et Content N Server Access Network Access Network er25 th #1 #2 O2627 ev b)28 Internet Network29 Manager30 Entity (ME) ie31 Operator Core3233 #" w3435 $" 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 Entity36 O37 &"
  9. 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) ewFigure 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. 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 ewFigure 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. 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. 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. 13. Results Using a CCN Management Framework 240 1 a) 200 Active faceRTT (ms) 160 120 80 0 240 1 RTT b) Average RTT 200 Face Active faceRTT (ms) 160 120 80 0 0 20000 40000 60000 80000 100000 120000 140000 160000 Time (ms)
  14. 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. 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. 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. 17. Overview of the framework NDN namespace Clients Gateway Clients IoT devices
  18. 18. Supported proceduresDiscovery of IoT devices Registration of IoT devices NDN namespace Clients Gateway Clients IoT devices Command execution & Content retrieval
  19. 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. 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. 21. Thank you for watching! Questions?CONTACT US: DCORUJO@AV.IT.PT
  22. 22. The Infamous Set of Backup Slides!!!
  23. 23. 123456789101112131415161718 Fo19202122 r2324 Re25262728 vi293031 ew3233343536 On373839404142434445 ly4647484950 !"51 #" Figure 2: Bootstrapping and management data exchange
  24. 24. Experiments Page 34 of 34123 !"4 #" !56 $" !78 Basic NDN with 1 Basic NDN with 5 Framework-9 probe per face probes per face managed NDN10 Average RTT (ms) 86.6140 84.685 78.984011 CI (ms) (84.6350, 88. 5930) (83.8573, 85.5127) (78.5232, 79.4448)1213 Overhead (%) 1.2908 5.7677 0.112114 Losses (%) 1.8102 1.5478 0.372815 Handovers/s 0.0594 0.06 0.012516 %" "#$%&!(!)*++#,-!./!&01&,2+&34#%!,&5*%45(1718 Fo19202122 r2324 Re25262728 v29
  25. 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)

×