Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Project Presentation


Published on

  • Be the first to comment

  • Be the first to like this

Project Presentation

  1. 1. F uture A ctive I P N etworks IST - 10561 Deliverable D12 Project Presentation 31st July 200
  2. 2. Presentation Outline <ul><li>Active Networks Background & Key Issues </li></ul><ul><li>IST Projects Overview </li></ul><ul><li>FAIN IST - 10561 Project </li></ul><ul><li>Summary & Conclusions </li></ul>
  3. 3. Presentation Outline <ul><li>Active Networks Background & Key Issues </li></ul><ul><li>IST Projects Overview </li></ul><ul><li>FAIN IST - 10561 Project </li></ul><ul><li>Summary & Conclusions </li></ul>
  4. 4. Background <ul><li>Active Networks is about programming the network infrastructure as support of customised communication services </li></ul><ul><ul><li>Active = dynamic programmability and control </li></ul></ul><ul><ul><li>Customisation = user/consumer centric network and services </li></ul></ul><ul><li>Store - Compute - Forward </li></ul><ul><li>Expected major impact : rapid service creation and deployment </li></ul>
  5. 5. Main Issues - Previous Attempts - Service Creation <ul><li>Intelligent Networks ( 18 years of R&D) </li></ul><ul><li>TINA ( 7 years of R&D) </li></ul><ul><li>TMN ( 15 years of R&D) </li></ul><ul><li>Very Complex </li></ul><ul><li>User’s control was not included </li></ul><ul><li>Standardisation cycles very long </li></ul><ul><li>Very few new Communication Services </li></ul><ul><li>Management is detached from networks </li></ul>
  6. 6. Active Networks Background <ul><li>Active Networks </li></ul><ul><ul><li>Store - Compute - Forward </li></ul></ul><ul><ul><li>Level of abstraction / standardisation </li></ul></ul><ul><ul><ul><li>Programming model </li></ul></ul></ul><ul><ul><ul><li>Programmability of network resources </li></ul></ul></ul><ul><ul><ul><li>( communication, processing) -middleware </li></ul></ul></ul><ul><ul><ul><li>Programmability at the application layer & down : across the transport, network, data link and physical layers </li></ul></ul></ul>
  7. 7. AN Background <ul><li>Traditional location of intelligence and control </li></ul><ul><ul><li>Internet - in end-systems applications ( end-to-end issues) </li></ul></ul><ul><ul><li>Telecom- in networks, centralised control with the operator </li></ul></ul><ul><li>Technology changes </li></ul><ul><ul><li>Distributed OO, intelligent mobile code/agents </li></ul></ul><ul><li>Convergence </li></ul><ul><ul><li>Signalling controlled by customers </li></ul></ul><ul><ul><li>QoS provision in Internet (intserv, diffserv) </li></ul></ul>
  8. 8. AN Introduction / Issues <ul><li>Applications’ demand for customised communications </li></ul><ul><ul><li>Application is aware of network semantics ( QoS, “real-time” and location) - the network becomes a dedicated resource of applications </li></ul></ul><ul><ul><li>Network is aware of applications </li></ul></ul><ul><li>Management of QoS in IP Networks </li></ul><ul><ul><li>Dynamic management ( in service) </li></ul></ul><ul><ul><li>Distributed between users and owners </li></ul></ul><ul><li>Application and Service models </li></ul><ul><ul><li>What resources ( abstractions, APIs) </li></ul></ul><ul><ul><li>What models for execution, code distribution </li></ul></ul>
  9. 9. AN Introduction / Issues <ul><li>Management Solutions </li></ul><ul><ul><li>From customised Net Management ( static, configurable) towards programmable Net </li></ul></ul><ul><li>Passive Networks </li></ul><ul><ul><li>Store - Forward </li></ul></ul><ul><ul><li>Level of abstraction /standardisation : protocol </li></ul></ul><ul><ul><li>No control by users </li></ul></ul>
  10. 10. Active Management Model <ul><li>Network supports management services </li></ul><ul><ul><li>Dynamically configurable Business Objects communications services </li></ul></ul><ul><ul><li>Dynamically configurable Work Flow management Engines -integration with service & network management, processing management and information management via dynamic brokerage </li></ul></ul><ul><ul><li>The application includes the business level management solution ( owned by the customer) - includes Work Flow components </li></ul></ul>
  11. 11. Active Networks Impact <ul><li>Facilitate the infrastructure innovation ( eliminate standardisation of protocols) </li></ul><ul><li>Customers / Consumers Relationship </li></ul><ul><ul><li>Dynamic network reconfiguration without operator intervention </li></ul></ul><ul><ul><li>Customer control of Network & services </li></ul></ul><ul><li>Network Service Providers </li></ul><ul><ul><li>Partitioning of network resources and services </li></ul></ul><ul><ul><li>Customised management & value added services </li></ul></ul><ul><ul><li>Legacy network infrastructure can co-exist </li></ul></ul><ul><li>Application Developers </li></ul><ul><ul><li>Non-standardised components can be used </li></ul></ul><ul><ul><li>Lightweight applications on top of services offered by the network </li></ul></ul>
  12. 12. Active Network Impact <ul><li>Augmented Performance by Combining Communication & Information Processing Power </li></ul><ul><ul><li>Packet Data Processing on the way to destination and on-the-fly ( by Active Nodes) </li></ul></ul><ul><li>Rapid Deployment of Services </li></ul><ul><ul><li>Service components can be injected at the right-place at right-time </li></ul></ul><ul><li>Flexible Customisation of Services </li></ul><ul><ul><li>Services can be tailored according to packet data as well as packet header </li></ul></ul>
  13. 13. AN Architectures <ul><li>OPENSIG - Programmable Networks in telecom oriented approach </li></ul><ul><ul><li>Opening up the switches </li></ul></ul><ul><ul><li>Modelling communication hardware using open programmable network interfaces </li></ul></ul><ul><ul><li>Emphasis on service creation with QoS </li></ul></ul><ul><ul><li>Open interfaces allow service providers to manipulate the network via middleware toolkits </li></ul></ul><ul><ul><li>IEEE P1520 Project follows this approach ( standardise programming interfaces for ATM switches, IP routers & mobile networks) </li></ul></ul>
  14. 14. AN Architectures <ul><li>DARPA Projects - a diverse approach </li></ul><ul><ul><li>Manly focussed on IP routers / IP networks where control and data paths are combined </li></ul></ul><ul><ul><li>An approach which mode dynamic that OPENSIG’s semi-static network programming interfaces </li></ul></ul><ul><ul><li>Range of approaches: </li></ul></ul><ul><ul><ul><li>A single packet ( capsule) modifies the behaviour seen only by that packet </li></ul></ul></ul><ul><ul><ul><li>A single packet boots a complete software environment seen by all packets arriving at the node. </li></ul></ul></ul><ul><li>MIAM I AC208 Project - Active Connectivity Service - based on Mobile Agents </li></ul>
  15. 15. DARPA Active Networks Architecture Application Application Application Execution Environment (e.g., ALIEN) Execution Environment (e.g., ANTS) Node Operating System (e.g., Nemesis, Scout, Linux, NT) AAs EEs NodeOS
  16. 16. Performance Vs. Flexibility 155 Mb/s 80 Mb/s 100 Mb/s 60 Mb/s 16 Mb/s Flexibility of System as demonstrated P4 PLAN SNAP ALIEN ANTS PAN
  17. 17. Presentation Outline <ul><li>Active Networks Background & Key Issues </li></ul><ul><li>IST Projects Overview </li></ul><ul><li>FAIN IST - 10561 Project </li></ul><ul><li>Summary & Conclusions </li></ul>
  19. 19. Presentation Outline <ul><li>Active Networks Background & Key Issues </li></ul><ul><li>IST Projects Overview </li></ul><ul><li>FAIN IST - 10561 Project </li></ul><ul><li>Summary & Conclusions </li></ul>
  20. 20. FAIN IST- 10561 Project Partners <ul><li>P1 – University College London UK </li></ul><ul><ul><li>P2 – Jozef Stefan Institute Slovenia </li></ul></ul><ul><ul><li>P3 – National Technical University of Athens Greece </li></ul></ul><ul><ul><li>P4 – Universitat Politecnica de Catalunya Spain </li></ul></ul><ul><li>P5 – Deutsche Telekom/ T-Nona Germany </li></ul><ul><li>P6 – France Telecom/CNET France </li></ul><ul><li>P7 – KPN Netherlands </li></ul><ul><li>P8 – Hitachi Europe Ltd. UK </li></ul><ul><li>P9 – Hitachi Ltd. Japan </li></ul><ul><li>P10 – Siemens AG Germany </li></ul><ul><li>P11 – ETH Zurich Switzerland </li></ul><ul><li>P12 – GMD Fokus GmbH Germany </li></ul><ul><ul><li>P13 – IKV++ GmbH Germany </li></ul></ul><ul><ul><li>P14 – INTERGAsys Spain </li></ul></ul><ul><li>P15 – University of Pennsylvania USA </li></ul>
  21. 21. FAIN Project Main Objectives <ul><li>Develop and validate an open, programmable and dependable active network architecture </li></ul><ul><ul><li>Active network, node and management architectures </li></ul></ul><ul><ul><li>Pan-European & International Active Network infrastructure </li></ul></ul><ul><ul><li>2 Active Services : Policy based network management + Dynamic Provisioning of protocols </li></ul></ul><ul><ul><li>Evaluate advantages / limitations Active IP Network Vs IP network </li></ul></ul>
  22. 22. Enterprise Model Consumer Domain FAIN Scope AN Provider Domain AN Solutions Provider Domain Customer / User Mgmt. Service Provider (Active NW) Application Provider Protocol Provider Active Middleware Provider Active Node Vendor Active Network Operator RP1 RP8 RP7 RP6 RP5 RP4 RP3 RP2
  23. 23. Network Architecture AN Operator Domain ... ... FAIN AN Infrastructure AN Solutions Provider Domain Policy Mgmt. Dynamic Protocol Provisioning NW Resource Mgmt. Consumer Domain AN enabled Application (Customer Controlled) AN enabled Application (Appl. Provider Controlled) RP4 Interface RP3 Interface RP6 Interface RP7 Interface Service Creation Environment (Appl. Provider) RP5 Interface FAIN AN Architecture Scope
  24. 24. Node Architecture Active Node Platform Layer Consumer Domain Active Network (AN) Operator Domain A AN Solution Provider Domain FAIN Active Network Node (ANN) Infrastructure Progammable Router (Hardware) Node Kernel High Perfor- mance EE DPE based EE Active Node Excecution Environments Mobile agent EE Resource Access Control ( policy based) Application s Open Router Interface/API RP6, RP7 Interfaces AN Solutions : RP3, RP4 Interfaces AN Operator Domain B RP8 Inter- Domain Interface Security mgmt Network Mgmt. Service Provision Active Node / Network facilities Active software components Service Execution Layer Programmable Element Layer Node API Node OS
  25. 25. Trial Topology
  26. 26. WP1 Structure PMC (Project Management Committee) TMC (Technical Management Committee) WP Leaders WP2/3/4/5 WP1 EU -PO For a & Projects PC
  27. 27. WP1 Objectives and Tasks <ul><li>Objectives: provide the technical, administrative and consortium management for the project. Development of the project exploitation & dissemination plan. </li></ul><ul><li>Tasks: </li></ul><ul><li>T1.1 Project administrative co-ordination </li></ul><ul><li>T1.2 Technical co-ordination </li></ul><ul><li>T1.3 Information exchange and dissemination </li></ul><ul><li>T1.4 Exploitation plan </li></ul><ul><li>Deliverables: </li></ul><ul><li>D12 - Project Presentation - Y1 M3 </li></ul><ul><li>D10 - Technology Implementation Plan- Version1 - Y1M12 </li></ul><ul><li>QPMR ( Quarterly Project Management Reports) - Y1 M3, M6, M9, M12 </li></ul>
  28. 28. WP2 Objectives & Tasks <ul><li>Objective : Requirements & Specification for an active IP Network Architecture </li></ul><ul><li>T2.1 - Business Model </li></ul><ul><li>T2.2 - Use Cases and Network Architecture Requirements </li></ul><ul><li>Deliverables: D1 - Requirement Analysis & AN Architecture - Y1M9 </li></ul>
  29. 29. WP2 Plan
  30. 30. WP3 Objectives & Tasks <ul><li>Objectives : develop/design/prototype the architecture & APIs for IP Active Networks </li></ul><ul><li>T3.1 - Active Node Architecture </li></ul><ul><li>T3.2 - Active Node Design & Specification </li></ul><ul><li>T3.3 - Active Node Platform Implementation </li></ul><ul><li>T3.4 -Active Node Execution - Implementation </li></ul><ul><li>T3.5 - Prototype Integration & Test </li></ul><ul><li>Deliverables: D2 - Initial A N and Active Node Architecture - Y1M9 ( WP3) </li></ul><ul><li>M1 - Initial Implementation & components - Y1M11 (WP3/WP4) </li></ul>
  31. 31. WP3 Plan
  32. 32. WP4 Objectives & Tasks <ul><li>Objective : develop 2 active services: Policy based network management + Dynamic Provisioning of protocols </li></ul><ul><li>T4.1 - Req , Design, Spec. Policy based network management </li></ul><ul><li>T4.2 - Implementation Policy based network management </li></ul><ul><li>T4.3 - Req , Design, Spec.Implementation- Policy based network management </li></ul><ul><li>Deliverables D3 Initial Specification of Case Studies Systems - Y1M9 (WP4) </li></ul><ul><li>M1 - Initial Implementation & components - Y1M11 (WP3/WP4) </li></ul>
  33. 33. WP4 Plan
  34. 34. WP5 Objectives & Tasks <ul><li>Objectives : Develop & Run an A N Testbed & Evaluate advantages / limitations ANs </li></ul><ul><li>T5.1-Trials Set-up </li></ul><ul><li>T5.2-Trial Execution </li></ul><ul><li>T5.3-Trial Evaluation </li></ul><ul><li>T5.4-Interworking & other testbeds </li></ul><ul><li>Deliverable: None </li></ul><ul><li>M1 - Initial Implementation & components - Y1M11 (WP3/WP4) + Draft Reference Configuration - FAIN Testbed- a ppt presentation (WP5) </li></ul>
  35. 35. WP5 Plan
  36. 36. Presentation Outline <ul><li>Active Networks Background & Key Issues </li></ul><ul><li>IST Projects Overview </li></ul><ul><li>FAIN IST - 10561 Project </li></ul><ul><li>Summary & Conclusions </li></ul>
  37. 37. Key Issues & Conclusions <ul><li>Active Network technology is a hot research area </li></ul><ul><li>Proof of concepts results so far </li></ul><ul><li>Interoperability issues in the next steps </li></ul><ul><li>Performance issues and large scale test beds to follow </li></ul><ul><li>Active Management & Management of AN to follow </li></ul><ul><li>Active Networks will speed-up network evolution and eventually impact the creation and management of many new services </li></ul>