# US 2017/0302623 A1 · Efficient service function chaining over a transport network

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0302623 A1
- Document ID: US20170302623A1
- Status: Published application
- Kind: A1
- Application number: 15/513,222
- Filed: 2014-09-23
- Published: 2017-10-19
- Earliest claimed: 2014-09-23
- Assignees: NEC Corporation
- Applicants: NEC Europe Ltd.
- Inventors: Roberto BIFULCO; Anton MATSIUK
- Web page: https://patentgrep.com/patent/US20170302623A1

## CPC

- H04L 61/35: {involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function}
- H04L 45/64: using an overlay routing layer
- H04L 47/2441: relying on flow classification, e.g. using integrated services [IntServ]
- H04L 41/0266: using meta-data, objects or commands for formatting management information, e.g. using eXtensible markup language [XML]
- H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04L 45/30: Routing of multiclass traffic
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method for operating a network includes implementing at least one service function chain (SFC) including several service functions (SFs) for providing traffic steering; encoding traffic steering information related to the at least one SFC; and using redundant information in an addressing scheme of network hosts for addressing the SFs.

## Claims

### Claim at position 1

1: A method for operating a network, the method comprising:
implementing at least one service function chain (SFC) comprising several service functions (SFs) for providing traffic steering,
encoding traffic steering information related to the at least one SFC, and
using redundant information in an addressing scheme of network hosts for addressing the SFs.

### Claim at position 2 (depends on 1)

2: The method according to claim 1, wherein the redundant information is a common prefix of host addresses within the addressing scheme of network hosts.

### Claim at position 3 (depends on 2)

3: The method according to claim 2, wherein the common prefix is temporarily replaced with SFC metadata used for traffic steering between and/or to the SFs.

### Claim at position 4 (depends on 3)

4: The method according to claim 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.

### Claim at position 5 (depends on 4)

5: The method according to claim 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.

### Claim at position 6 (depends on 1)

6: The method according to claim 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 the edge switches, separated or combined with the aforementioned transport network control plane or controller, distributes forwarding and network header modification policies or rules to at least one edge switch of the network.

### Claim at position 7 (depends on 1)

7: The method according to claim 1, wherein the traffic steering relies on destination-based forwarding.

### Claim at position 8 (depends on 7)

8: The method according to claim 7, wherein source and destination addresses are swapped.

### Claim at position 9 (depends on 1)

9: The method according to claim 1, wherein the traffic steering relies on source-based forwarding.

### Claim at position 10 (depends on 1)

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

### Claim at position 11 (depends on 1)

11: The method according to claim 1, wherein an SFC is mapped with a particular traffic class.

### Claim at position 12 (depends on 1)

12: The method according to claim 1, wherein an ingress switch of an SFC domain performs a class matching regarding an SFC.

### Claim at position 13 (depends on 1)

13: The method according to claim 1, wherein an edge switch replaces network prefix bits within a source address with a logical address of a next SF in an SFC preserving host address.

### Claim at position 14 (depends on 1)

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

### Claim at position 15 (depends on 1)

15: The method according to claim 1, wherein an SFC identifier (SFC ID) is transferred together with an SF ID by borrowing lower bits of a redundant address part or of a block of redundant bits.

### Claim at position 16 (depends on 1)

16: The method according to claim 1, wherein an edge switch performs a header modification if a next SF is connected to a different switch.

### Claim at position 17 (depends on 1)

17: The method according to claim 1, wherein an egress switch is associated with a default SF logical address.

### Claim at position 18

18: A network, wherein at least one service function chain (SFC) comprising several service functions (SFs) is implemented for providing traffic steering, wherein traffic steering information related to the at least one SFC is encoded, the network being configured to:
use redundant information in an addressing scheme of network hosts for addressing the SFs.
