# US 2026/0089096 A1 · Service Function Proxy for Service Chaining in SRv6 Networks

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

- Number: US 2026/0089096 A1
- Document ID: US20260089096A1
- Status: Published application
- Kind: A1
- Application number: 18/892,887
- Filed: 2024-09-23
- Published: 2026-03-26
- Earliest claimed: 2024-09-23
- Assignees: Ciena Corporation
- Applicants: Ciena Corporation
- Inventors: Ashwath Narasimhan; Muthurajah Sivabalan; Lakshmi Rajasekaran; Jahanzeb Baqai
- Web page: https://patentgrep.com/patent/US20260089096A1

## CPC

- H04L 45/34: {Source routing}
- H04L 45/42: Centralised routing
- H04L 45/00: Routing or path finding of packets in data switching networks (routing or path finding in wireless networks H04W40/00)
- H04L 45/566: {Routing instructions carried by the data packet, e.g. active networks}
- H04L 45/586: of virtual routers
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A node in a Segment Routing Internet Protocol version 6 (SRv6) network with the node configured as a Service Function (SF) Proxy in the SRv6 network, the node includes circuitry configured to, subsequent to installation of a Segment Identifier (SID) for a Service Function Chain (SFC), receive a packet with the SID included therein, remove all Segment Routing (SR) information from the packet, send the packet on an interface associated with an SR-unaware SF, and receive the packet on the interface after processing by the SR-unaware SF, wherein the packet from the interface is associated as returning traffic from the SF.

## Claims

### Claim 1

A node in a Segment Routing Internet Protocol version 6 (SRv6) network with the node configured as a Service Function (SF) Proxy in the SRv6 network, the node comprising circuitry configured to:
subsequent to installation of a Segment Identifier (SID) for a Service Function Chain (SFC), receive a packet with the SID included therein,
remove all Segment Routing (SR) information from the packet,
send the packet on an interface associated with an SR-unaware SF, and
receive the packet on the interface after processing by the SR-unaware SF, wherein the packet from the interface is associated as returning traffic from the SF.

### Claim 2 (depends on 1)

The node of claim 1, wherein the circuitry is further configured to
subsequent to the packet being received on the interface, forward the packet to a next destination using a SR-Policy thereby continuing the SFC until the packet reaches an intended destination.

### Claim 3 (depends on 1)

The node of claim 1, wherein the SID is a unique Flow Identity micro-SID (uSID).

### Claim 4 (depends on 1)

The node of claim 1, wherein the circuitry is further configured to
prior to the installation of the SID, receive the SID via a Layer 3 protocol.

### Claim 5 (depends on 1)

The node of claim 1, wherein the SID identifies one of a Virtual Routing and Forwarding (VRF) endpoint, an Ethernet Virtual Private Network (EVPN) Instance (EVI), or a Layer 2 Virtual Private Network (VPN) (L2-VPN) end point, for the interface.

### Claim 6 (depends on 1)

The node of claim 1, wherein the SR information includes a Segment Routing Header (SRH).

### Claim 7 (depends on 1)

The node of claim 1, wherein the SID is allocated with a unique endpoint behavior different from any endpoint behavior defined in standards.

### Claim 8 (depends on 1)

The node of claim 1, wherein the SID is allocated with a new SRv6 block for SFC proxy using a combination of algorithm and prefix block.

### Claim 9 (depends on 1)

The node of claim 1, wherein the SID is allocated with a combination of a pre-assigned Block Identifier and Reserved End point behaviors.

### Claim 10 (depends on 1)

The node of claim 1, wherein the circuitry is further configured to receive a SRv6 Capabilities Sub-TLV (Type-Length-Value) which includes information describing support for the SID in the SRv6 network.

### Claim 11

A method implemented by a node that is a Service Function (SF) Proxy in a Segment Routing Internet Protocol version 6 (SRv6) network, the method comprising steps of:
subsequent to installing a Segment Identifier (SID) for a Service Function Chain (SFC), receiving a packet with the SID included therein;
removing all Segment Routing (SR) information from the packet;
sending the packet on an interface associated with an SR-unaware SF; and
receiving the packet on the interface after processing by the SR-unaware SF, wherein the packet from the interface is associated as returning traffic from the SF.

### Claim 12 (depends on 11)

The method of claim 11, wherein the steps further include
subsequent to the packet being received on the interface, forwarding the packet to a next destination using a SR-Policy thereby continuing the SFC until the packet reaches an intended destination.

### Claim 13 (depends on 11)

The method of claim 11, wherein the SID is a unique Flow Identity micro-SID (uSID).

### Claim 14 (depends on 11)

The method of claim 11, wherein the steps further include
prior to the installation of the SID, receiving the SID via a Layer 3 protocol.

### Claim 15 (depends on 11)

The method of claim 11, wherein the SID identifies one of a Virtual Routing and Forwarding (VRF) endpoint, an Ethernet Virtual Private Network (EVPN) Instance (EVI), or a Layer 2 Virtual Private Network (VPN) (L2-VPN) end point, for the interface.

### Claim 16 (depends on 11)

The method of claim 11, wherein the SR information includes a Segment Routing Header (SRH).

### Claim 17 (depends on 11)

The method of claim 11, wherein the SID is allocated with a unique endpoint behavior different from any endpoint behavior defined in standards.

### Claim 18 (depends on 11)

The method of claim 11, wherein the SID is allocated with a new SRv6 block for SFC proxy using a combination of algorithm and prefix block.

### Claim 19 (depends on 11)

The method of claim 11, wherein the SID is allocated with a combination of a pre-assigned Block Identifier and Reserved End point behaviors.

### Claim 20 (depends on 11)

The method of claim 11, wherein the steps further include
receiving a SRv6 Capabilities Sub-TLV (Type-Length-Value) which includes information describing support for the SID in the SRv6 network.
