Efficient service function chaining over a transport network

The method according to 1, wherein the redundant information portion of the source IP address and/or the redundant information portion of the destination IP address is a common prefix of host addresses within an addressing scheme of network hosts.

The method according to 2, wherein the logical address of a next SF in the SFC to which the traffic class is mapped is SFC metadata used for traffic steering between and/or to the SFs.

The method according to 3, wherein the SFC metadata contains a unique logical address that serves as a service function identifier (SF ID) or a block of addresses that serve as an SF ID.

The method according to 4, wherein SF IDs or SF addresses are represented as conventional network addresses and advertised into a routing domain of an underlying transport network for forwarding traffic towards one or more particular SFs.

The method according to 1, wherein a centralized or decentralized control plane or controller for the network or transport network installs routing policies towards one or more SFs to at least one intermediate router, and

• wherein a centralized or decentralized control plane or controller for edge switches, separated or combined with the aforementioned transport network control plane or controller, performs the installing, onto the edge switch, the set of forwarding rules.

The method according to 1, wherein the edge switch is a software switch in a hypervisor.

The method according to 7, wherein the hypervisor is a virtual machine manager (VMM) configured to create and run virtual machines.

The method according to 8, wherein the service function chain includes a plurality of service functions, each service function being a virtual machine (VM) created by the hypervisor.

The method according to 1, wherein at least one branch of an SFC or of different SFCs are tagged for elimination of ambiguous steering decisions.

The method according to 1, wherein the edge switch is an ingress switch of an SFC domain, and wherein the edge switch performs a class matching to match the packet belonging to the traffic class with the traffic class.

The method according to 1, wherein the replacing, by the edge switch, the redundant information portion of the source IP address of the packet belonging to the traffic class and/or the destination IP address of the packet belonging to the traffic class with a logical address of a next SF in the SFC to which the traffic class is mapped so as to provide a modified packet comprises replacing network prefix bits within the source IP address with a logical address of a next SF in an SFC preserving host address.

The method according to 1, wherein an ingress switch provides an SFC identifier (SFC ID) in order to distinguish implicit class matching within an SFC domain.

The method according to 1, wherein the redundant information portion of the source IP address of the packet belonging to the traffic class and/or the destination IP address of the packet belonging to the traffic class is replaced with both the logical address of the next SF in the SFC to which the traffic class is mapped and an SFC identifier (SFC ID).

The method according to 14, wherein the next SF in the SFC preserves the SFC ID and returns it transparently to the edge switch for further forwarding decisions.

The method according to 1, wherein the edge switch performs a header modification if the next SF in the SFC to which the traffic class is mapped is connected to a different switch.

The traffic routing network according to 17, wherein the edge switch is a software switch in a hypervisor.

The traffic routing network according to 18, wherein the hypervisor is a virtual machine manager (VMM) configured to create and run virtual machines.

The traffic routing network according to 19, wherein the service function chain includes a plurality of service functions, each service function being a virtual machine (VM) created by the hypervisor.