110 likes | 250 Views
Architecture of the Flexinet ForCES-based Control Point. Robert Haas, IBM Research, Zurich Research Lab, rha@zurich.ibm.com Toshiaki Suzuki, Hitachi, Central Research Laboratory, toshiaki@crl.hitachi.co.jp IETF ForCES WG meeting, Paris, Aug 1, 2005. FlexiNET: Overview.
E N D
Architecture of the Flexinet ForCES-based Control Point Robert Haas, IBM Research, Zurich Research Lab, rha@zurich.ibm.com Toshiaki Suzuki, Hitachi, Central Research Laboratory, toshiaki@crl.hitachi.co.jp IETF ForCES WG meeting, Paris, Aug 1, 2005.
FlexiNET: Overview • STREP @ “Broadband for all” (Specific Targeted Research Projects) • Started March 01, 2004, duration 2 years • www.ist-flexinet.org • 8 partners • Main objective:to accelerate the introduction of next-generation marketable services, and increase competitiveness in the telecom field by facilitating the broadening of current business models for services provisioning and exploitation. • Get data out of the Network elements (Data Interface and SAN) • Use a service-centric architecture for new applications (Applications Interface) • Move services and switching management towards the network edges (GW) • Add service programmability
FlexiNET: Architecture FlexiNET FWAN Alcatel Teletel APEX Hitachi UoP IBM Alcatel COM Alcatel Teletel
Expandable Function Block Module-2 Module-3 Module-4 Module-1 Module-5 Cache Cache Encrypt. OSPF OSPF lll lll lll lll lll lll High Speed L2 Switch Basic Function Block Manager Packet Forwarding IF IF IF IF IF Prototype Modular Node Modular Node Architecture for High-Performance, Flexible and Reliable Network Modules (Blade Server) ① ② ③ Switch Forwarding (NP) This work was partly supported by National Institute of Information and Communications Technology (NICT).
FlexiNET: FWAN FWAN CE Extensible Function Block Basic Function Block (PC) Host PC CPU RAM(Table) CE FE 100Base-TX (NP Development Kit) I/O RAM(Buffer) Bridge CE PCI NP FE Core CPU RAM (Buffer) Micro Engine Micro Engine GbE Switch RAM (Table) GbE I/O I/O I/O I/O WLAN AP To Generic Application Interface Router To Internet GbE: Gigabit Ethernet
FWAN ForCEG requirements • ForCEG maintains NE-wide consistency while various services configure the FEs. • Services declare their consistency req’s • Checking is done at LFB, FE, and NE levels. • ForCEG demultiplexes responses to the originating service QoS AAA Proxy ForCEG CE CE FE FE FE
FWAN ForCEG architecture • MCP are services such as AAA Proxy, QoS, etc.
Implementation • Dynamic Service Deployment implementation (in progress) based on • OSGi for remote code starting/stopping • Webservices for flexible loose coupling with services • GT4 Resource Discovery • Matchmaking algorithm for optimal resource allocation • ForCEG implementation in Java (in progress) • ForCES CE implementation in Java (in progress)
FWAN ForCEG adaptability • ForCEG offers Service API modules that match Service requirements AND underlying FE capabilities. QoS AAA Proxy API API ForCEG CE CE FE FE FE