Architecture%20of%20the%20Flexinet%20ForCES-based%20Control%20Point

1
Architecture of the Flexinet ForCES-based Control
Point

• Robert Haas, IBM Research, Zurich Research Lab,
  rha_at_zurich.ibm.com
• Toshiaki Suzuki, Hitachi, Central Research
  Laboratory, toshiaki_at_crl.hitachi.co.jp
• IETF ForCES WG meeting, Paris, Aug 1, 2005.

2
FlexiNET Overview

• STREP _at_ 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

3
FlexiNET Architecture
FlexiNET FWAN
Alcatel Teletel APEX
Hitachi UoP IBM
Alcatel COM
Alcatel Teletel
4
Prototype Modular Node
Modular Node Architecture for High-Performance,
Flexible and Reliable Network
? Scalability Performance is enhanced by the same processing modules
? Flexibility Function is extended by adding new modules
? Reliability Availability is improved by redundant modules
Modules (Blade Server)
?
?
?
Switch
Forwarding (NP)
This work was partly supported by National
Institute of Information and Communications
Technology (NICT).
5
FlexiNET FWAN
FWAN
CE
Extensible Function Block
Basic Function Block
(PC)
Host PC
CPU
RAM(Table)
CE
FE
100Base-TX
(NP Development Kit)
RAM(Buffer)
I/O
Bridge
CE
PCI
NP
Core CPU
FE
RAM (Buffer)
Micro Engine
Micro Engine
GbE
Switch
RAM (Table)
GbE
I/O
I/O
I/O
I/O
WLAN AP
Router
To Internet
To Generic Application Interface
GbE Gigabit Ethernet
6
FWAN ForCEG requirements
QoS
AAA Proxy

• ForCEG maintains NE-wide consistency while
  various services configure the FEs.
• Services declare their consistency reqs
• Checking is done at LFB, FE, and NE levels.
• ForCEG demultiplexes responses to the originating
  service

ForCEG
CE
CE
FE
FE
FE
7
FWAN ForCEG architecture

• MCP are services such as AAA Proxy, QoS, etc.

8
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)

9
End
10
FWAN ForCEG adaptability
QoS
AAA Proxy

• ForCEG offers Service API modules that match
  Service requirements AND underlying FE
  capabilities.

API
API
ForCEG
CE
CE
FE
FE
FE