1 / 33

ICN Management

ICN Management. Daniel Corujo dcorujo@av.it.pt Instituto de Telecomunicações Universidade de Aveiro http://atnog.av.it.pt Iván Vidal, Jaime Garcia- Reinoso (UC3M, Spain ) Kostas Pentikousis (HUAWEI). Outline. Draft status Base concepts The API implementation New ideas

cala
Télécharger la présentation

ICN Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ICN Management Daniel Corujo dcorujo@av.it.pt Instituto de Telecomunicações Universidade de Aveiro http://atnog.av.it.pt Iván Vidal, Jaime Garcia-Reinoso (UC3M, Spain) KostasPentikousis (HUAWEI)

  2. Outline • Draft status • Base concepts • The API implementation • New ideas • New ICN deployments

  3. Draft Status • Not many changes • Added information on new software API deployment (more on this in a few slides) • What we need to do • More scenarios • Verify/compare more ICN deployments • Along the methodologies of the Scenarios and Challenges drafts • Determine overlapping mechanisms • Identify new ICN-based mgmt actions • Identify/verify impact over existing IETF groups

  4. What is this draft about? • The dynamics of management • Placed by it’s relevance in today’s Internet • As well as the possibilities of having it in ICN • Right at the start • Aims to go beyond FCAPS • But to allow, leverage, optimize and interact with other mechanisms (e.g., security, mobility, routing…) • Aims to increase the DEPLOYABILITY of ICN • Through multi-area interaction of management/control procedures

  5. Example (Base concepts of our work) • Control aspects of the networking layer • Using the networking layer’s mechanisms themselves • i.e., Interest+Data exchange (for CCN) • Have special consumer/producer applications • In the network and the terminal • They exchange information between themselves • And with other networking entities/mobile applications • AAA, Content Sources, etc. • To optimize their operations • Joint approach with the Universidad Carlos III de Madrid, Spain • Prof. Iván Vidal • Prof. Jaime Garcia-Reinoso • Kostas is joining us in the draft as well!

  6. General Concept and Design [1/3] ME: Management Entity UE: User Equipment PoS: Point of Service

  7. General Concept and Design [2/3] • A ME at the UE can gather information from several sources by: • Interfacing with existing processes in the UE (e.g. applications and link-layer) • Inter-operating with external MEs (eg. located at a PoS) • The ME can integrate different algorithms to take management decisions • Decisions are enforced by interfacing with the CCN fabric (e.g. by accessing the FIB and PIT)

  8. General Concept and Design [3/3] Architecture of the UE in respect to ME<->CCN interfacing

  9. Support Mechanisms • NDN Name broadcasting (through Interests) • /domain/management/mgmt-case/ME • Secure Mgmt. Info. Exchange • Using key exchange or any other security scheme • Asynchronous Information Exchange • Push and Pull information • Sequencing • For enabling the sending of new information instead of using the cached one

  10. Use Case: Face Management • CCN can take advantage of multiple faces at the receiver • Mechanisms for face selection proposed so far are based on probing via the active interfaces • Main advantages of introducing a face management framework: • Management decisions can be based on information available at the network and at the UE (e.g. link-layer status and application policies and requirements). • The framework is flexible to accommodate different algorithms for management decisions • Faces can be activated/deactivated (e.g. for resource saving) • Support of network-controlled management scenarios

  11. Usage Scenario • Network Management Entity assistance • Optimal Face selection • Load Balancing • Knowledge of better connectivity alternatives • Policies • Benefits • 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)

  12. How it looks Network Content Source Network Management Entity MOBILE NODE Point of Attachment

  13. API for CCN management communications Implementation

  14. Implementation:overview • An API has been implemented to: • Support the communication of management operations over a CCN network • Easy the development of management applications, i.e., MAs and MEs • Current version supports all the procedures defined in draft-corujo-icn-mgmt-01: • Discovery procedure (sect. 2.2.1) • Management communications (sect. 2.2.2) • Developed in Java 1.6.0_26 using the CCNx Java API v0.6.1 • Sources available at: https://github.com/ndnflexmanager

  15. Implementation:the discovery procedure • Bootstrapping allows: • Discovery of a ME • To agree a symmetric session key (128 bits) between MA and ME • The session key is securely exchanged using asymmetric encryption (RSA) • To identify the correspondent party as a valid producer of management content

  16. Implementation:management communications (I) • Pull: • Allows the MA (ME) to retrieve a specified content from the ME (MA) • The content name and the content itself are not exposed • Confidentiality is guaranteed using AES and the symmetric session key obtained from bootstrapping

  17. Implementation:management communications (II) • Push: • Allows the MA(ME) to deliver unsolicited content to the ME (MA) • Subject to ME (MA) authorization

  18. Implementation:API main files • Source files: • ManagementAgent.java: • Contains the API to be used by the MA • Provides the implementation of pull/push methods • ManagementEntity.java: • Contains the API to be used by the ME • Provides the implementation of pull/push methods • Interfaces: • MAInterface.java: • Defines the interface to be implemented by the MA • MEInterface.java: • Defines the interface to be implemented by the ME

  19. Implementation: application methods • An MA (ME) using the API must implement the following methods: • handleInterest: • Called by the API when receiving an Interest for content that must be provided by the application • authorizeContent: • Called by the API when receiving a request to push unsolicited content. • handleContent: • Called by the API to provide the application with unsolicited content that has previously been authorized.

  20. Implementation:example of utilization • Included in the Github repository • Source files: • ApplicationMA.java • Example of MA using the API • Operation: • The MA pulls from the ME a list of WLAN networks available in its vicinity • Then it pushes to the ME the SSID of the WLAN network that it has chosen to obtain access connectivity • ApplicationME.java: • Example of ME operating with the previous MA

  21. New Ideas for the draft work (1) • Mobile terminal impact • ICN is focusing a lot on network behavior • I.e., caching and routing • Mobile terminal is only “housing” the applications • How can it actually contribute to the overall mechanism? • How is it impacted by more “exotic” mechanisms?

  22. New Ideas (2) • Large-scale experimentation • Many of us have access to large testbeds • Some of them are even federated or belong to integrated groups • i.e., FIRE • Many question the usefulness of ICN-based mechanisms • So we need to provide meaningful data and results • Compare them with production deployments somehow • Even if it’s in terms of numbers • Issue: • Mobile terminals?

  23. New ICN Deployments • It is important to subject new ICN mechanisms • Management, Mobility, Security, etc. • Over the different ICN deployments available • CCN, NetInf, DONA, etc., etc. • By exposing the mechanisms to different deployments • We determine the key enablers • Enhance the mechanisms • As well as the deployments • Merge ICNRG contributions to IETF under a single (best of) approach • What can be the role of smaller/less-well-known ICN deployments?

  24. Mobile-aware Entity Title Architecture • Objective: • In a nutshell: ICN + SDN + Mobility Management • Leverage Media Independent information and control to: • Optimize and assist mobility and handover procedures • Detect handover candidates • Obtain pre-configuration information to optimize and accelerate the handover process • Allow other kinds of heterogeneous link control procedures: • Load balancing, policing, etc. • ODTONE (http://atnog.av.it.pt/odtone) • Open-source IEEE 802.21 implementation • Media Independent access link control • Provides abstract link events • Provides abstract link commands • Provides abstract Informational Elements

  25. Entity Title Architecture • Concepts and Components • Entity, Title, Workspace, DTSA • With support from the Federal University of Uberlândia, Brazil (OFELIA Project)

  26. Entity Title Architecture

  27. Entity Title Architecture

  28. Entity Title Architecture

  29. Entity Title Architecture

  30. Entity Title Architecture

  31. Entity Title Architecture

  32. Let’s get moving! • Our aim is to progress and contribute to ICN impact • This draft is also yours! • You are most welcome to contribute!

  33. Thank you! • Daniel Corujo dcorujo@av.it.pt • http://atnog.av.it.pt/members/dcorujo • IvánVidal Fernándezividal@it.uc3m.es • Jaime Garcia jgr@it.uc3m.es

More Related