# US 2021/0344586 A1 · Method for Synchronizing Topology Information in SFC Network, and Routing Network Element

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

- Number: US 2021/0344586 A1
- Document ID: US20210344586A1
- Status: Published application
- Kind: A1
- Application number: 17/378,088
- Filed: 2021-07-16
- Published: 2021-11-04
- Earliest claimed: 2016-08-26
- Assignees: Huawei Technologies Co., Ltd.
- Applicants: Huawei Technologies Co., Ltd.
- Inventors: Ling Xu; Jie Dong; Guoyi Chen
- Web page: https://patentgrep.com/patent/US20210344586A1

## CPC

- H04L 45/64: using an overlay routing layer
- H04L 41/12: Discovery or management of network topologies
- H04L 45/033: by updating distance vector protocols
- H04L 45/0377: for service chaining
- H04L 45/60: Router architectures
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method for synchronizing topology information in a service function chain (SFC) network, where the SFC network includes at least one classifier (CF) and at least one service function forwarder (SFF). The method includes that a first network element in the at least two routing network elements establishes a Border Gateway Protocol (BGP) connection to at least one second network element other than the first network element in the at least two routing network elements, where the first network element is any one of the at least two routing network elements, and the first network element sends a first BGP update message to the at least one second network element, where the first BGP update message includes topology information of the first network element such that the at least one second network element obtains the topology information of the first network element.

## Claims

### Claim 1

A method implemented by a first service function forwarder in a service chain network, the method comprising:
sending, to a controller in the service chain network, a message comprising topology information, wherein the topology information comprises a first identifier of the first service function forwarder, a second identifier indicating a service type of a service function node connected to the first service function forwarder, and an Internet Protocol (IP) address of the service function node;
receiving, from the controller, a forwarding entry; and
forwarding, to the service function node according to the forwarding entry, packets.

### Claim 2 (depends on 1)

The method of claim 1, wherein the forwarding entry comprises an IP prefix and next hop information, and wherein the next hop information includes the IP address.

### Claim 3 (depends on 2)

The method of claim 2, wherein the packets comprise a destination IP address that matches the IP prefix.

### Claim 4 (depends on 1)

The method of claim 1, wherein the message further comprises network layer reachability information (NLRI), and wherein the NLRI comprises a type field indicating that the message comprises the topology information.

### Claim 5 (depends on 1)

The method of claim 1, wherein the service type comprises a type of a service that the service function node provides, and wherein the service comprises antivirus protection, a firewall, application caching, application acceleration, or webpage optimization.

### Claim 6 (depends on 1)

The method of claim 1, further comprising receiving, from a classifier in the service chain network, the packets.

### Claim 7 (depends on 1)

The method of claim 1, wherein forwarding the packets comprises forwarding, to the service function node through a second service function forwarder, the packets.

### Claim 8

A method implemented by a controller in a service chain network, the method comprising:
receiving, from a service function forwarder in the service chain network, a message comprising topology information, wherein the topology information comprises a first identifier of the service function forwarder, a second identifier indicating a service type of a service function node connected to the service function forwarder, and an Internet Protocol (IP) address of the service function node;
generating a forwarding entry according to the topology information; and
sending, to the service function forwarder, the forwarding entry.

### Claim 9 (depends on 8)

The method of claim 8, wherein the forwarding entry comprises an IP prefix and next hop information, and wherein the next hop information includes the IP address.

### Claim 10 (depends on 8)

The method of claim 8, wherein the message further comprises network layer reachability information (NLRI), and wherein the NLRI comprises a type field indicating that the message comprises the topology information.

### Claim 11 (depends on 8)

The method of claim 8, wherein the service type comprises a type of a service that the service function node provides, and wherein the service comprises antivirus protection, a firewall, application caching, application acceleration, or webpage optimization.

### Claim 12

A first service function forwarder in a service chain network and comprising:
a memory configured to store instructions; and
a processor coupled to the memory and configured to execute the instructions to cause the first service function forwarder to:
send, to a controller in the service chain network, a message comprising topology information, wherein the topology information comprises a first identifier of the first service function forwarder, a second identifier indicating a service type of a service function node connected to the first service function forwarder, and an Internet Protocol (IP) address of the service function node;
receive, from the controller, a forwarding entry; and
forward, to the service function node according to the forwarding entry, packets.

### Claim 13 (depends on 12)

The first service function forwarder of claim 12, wherein the forwarding entry comprises an IP prefix and next hop information, and wherein the next hop information includes the IP address.

### Claim 14 (depends on 13)

The first service function forwarder of claim 13, wherein the packets comprise a destination IP address that matches the IP prefix.

### Claim 15 (depends on 12)

The first service function forwarder of claim 12, wherein the message further comprises network layer reachability information (NLRI), and wherein the NLRI comprises a type field indicating that the message comprises the topology information.

### Claim 16 (depends on 12)

The first service function forwarder of claim 12, wherein the service type comprises a type of a service that the service function node provides, and wherein the service comprises antivirus protection, a firewall, application caching, application acceleration, or webpage optimization.

### Claim 17 (depends on 12)

The first service function forwarder according to claim 12, wherein the processor is further configured to receive, from a classifier in the service chain network, the packets.

### Claim 18

A controller in a service chain network and comprising:
a memory configured to store instructions; and
a processor coupled to the memory and configured to execute the instructions to cause the controller to:
receive, from a service function forwarder in the service chain network, a message comprising topology information, wherein the topology information comprises a first identifier of the service function forwarder, a second identifier indicating a service type of a service function node connected to the service function forwarder, and an Internet Protocol (IP) address of the service function node;
generate a forwarding entry according to the topology information; and
send, to the service function forwarder, the forwarding entry.

### Claim 19 (depends on 18)

The controller according to claim 18, wherein the forwarding entry comprises an IP prefix and next hop information, and wherein the next hop information includes the IP address.

### Claim 20 (depends on 18)

The controller according to claim 18, wherein the message further comprises network layer reachability information (NLRI), and wherein the NLRI comprises a type field indicating that the message comprises the topology information.
