Service Forwarding Chaining

Network Management is becoming highly complex. Today each domain has a rather static forwarding set of rules and policies. The propagation of the forwarding information is realized through the routing protocol translation at the edge nodes (or SON).
NGNI, OpenSDNCore, Service Forwarding Chaining, Singelweb, infographic
Fraunhofer FOKUS
The number of domains is highly increasing and tends not to be in the same network area (e.g. virtual infrastructures, UEs connected to virtual infrastructures are visible as part of each of the virtual domains).


On the other hand, domains are highly dynamic and can appear virtually anywhere in the network. The current peering based approach produces too many peers to be synchronized resulting in extended signaling and inconsistencies.

One possible solution is to automate the lower level of Network Management and implementing Service Forwarding Chaining:
  •     Abstract from the domain type
  •     Create possible links on demand
  •     Create service chains on-demand
  •     Dynamically adapt to network conditions changes
  •     Orchestration between a reduced number of network controllers
  •     Provide the service chains with high availability and load balancing
  •     Simplifying network management  for individual services
  •     Easy service description only:
  •     Node placement
  •     Routing policies (not rules statically configured!)