# US 2017/0289032 A1 · Extending nsh services into the vpn l2/l3 domain

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

- Number: US 2017/0289032 A1
- Document ID: US20170289032A1
- Status: Published application
- Kind: A1
- Application number: 15/084,332
- Filed: 2016-03-29
- Published: 2017-10-05
- Earliest claimed: 2016-03-29
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: James N. Guichard; Carlos M. Pignataro; Yixing Ruan; Javed Asghar
- Web page: https://patentgrep.com/patent/US20170289032A1

## CPC

- H04L 12/4641: {Virtual LANs, VLANs, e.g. virtual private networks [VPN] (LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272)}
- H04L 45/306: {Route determination based on the nature of the carried application}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Embodiments of the present disclosure are directed to augmenting a Network Service Header (NSH) metadata of a data packet with a virtual routing and forwarding identifier (VRF-ID) and forgoing augmenting a virtual private network (VPN) label into a multiprotocol label switched (MPLS) metadata of the data packet. A provider edge router can use the VRF-ID to identify a next hop for the data packet as a service to be applied prior to forwarding the data packet to a VPN site.

## Claims

### Claim 1

A method for applying network services to data traffic forwarded between virtual private network (VPN) sites, the method comprising:
on a forwarding edge router in communication with an origin site associated with a VPN, receiving a data packet addressed to a target site associated with the VPN;
determining a set of services to be applied to the data packet according to a service chain, wherein the determining is a function of at least one of the VPN, the origin site and the target site;
augmenting a network service header (NSH) metadata of the data packet with an identifier of a virtual network context;
encapsulating the data packet with Network Service Header (NSH) encapsulation, wherein a header for the encapsulated data packet indicates at least the service chain;
forwarding the encapsulated data packet in accordance with the service chain.

### Claim 2 (depends on 1)

The method of claim 1, forgoing augmentation of the a VPN label into multiprotocol label switched (MPLS) metadata of the data packet.

### Claim 3 (depends on 1)

The method of claim 1, wherein the identifier of the virtual network context comprises a virtual routing and forwarding identifier (VRF-ID) of a VRF associated with the VPN, wherein the VRF-ID identifies a VRF-name and a VRF table indicating one or more services to be applied to the data packet.

### Claim 4 (depends on 1)

The method according to claim 1, wherein the VPN sites are Level 3 VPN (L3VPN) sites.

### Claim 5 (depends on 1)

The method according to claim 1, wherein determining a set of services comprises looking up the set of services to be applied in a Virtual Routing and Forwarding (VRF) table according to at least one of the VPN, the origin site or the target site.

### Claim 6 (depends on 1)

The method according to claim 1, wherein the service chain is used to apply the set of services to the data traffic addressed to more than one the target site.

### Claim 7

A router comprising a hardware processor, the router configured to:
receive a data packet addressed to a target site associated with a VPN;
determine a set of services to be applied to the data packet according to a service chain, wherein the determining is as a function of at least one of the VPN, an origin site and the target site;
augment a Network Service Header (NSH) metadata of the data packet with an identifier of a virtual network context associated with the VPN;
encapsulate the data packet with (NSH) encapsulation, wherein a header for the encapsulated data packet indicates at least the service chain;
forward the encapsulated data packet in accordance with the service chain.

### Claim 8 (depends on 7)

The router of claim 7, wherein the router is a provider edge router.

### Claim 9 (depends on 7)

The router of claim 7, wherein the identifier of the virtual network context comprises a virtual routing and forwarding identifier (VRF-ID) of a VRF associated with the VPN.

### Claim 10 (depends on 7)

The router of claim 7, wherein the VPN is a Level 3 VPN.

### Claim 11 (depends on 7)

The router of claim 7, wherein the router is configured to attach an MPLS label to the data packet, and the router is further configured to forgo augmentation of a VPN label into MPLS metadata of the data packet.

### Claim 12

A method for applying network services to data traffic forwarded between virtual private network (VPN) sites, the method comprising:
on a forwarding edge router in communication with an origin site associated with a VPN, receiving an data packet addressed to a target site associated with the VPN;
determining a service to be applied to the data packet according to a service chain based at least in part on an identifier of a virtual network context in a Network Service Header (NSH) metadata of the data packet, wherein the determining is a function of at least one of the VPN, the origin site and the target site; and
routing the data packet to a service function forwarder associated at the determined service.

### Claim 13 (depends on 12)

The method of claim 12, wherein the router is a receiving edge router in communication with the target site.

### Claim 14 (depends on 12)

The method of claim 12, wherein the router is a virtual penultimate edge router, wherein the virtual penultimate edge router is positioned between the origin site and the target site.

### Claim 15 (depends on 14)

The method of claim 14, further comprising inserting a next hop indication into the NSH metadata at the virtual penultimate edge router, wherein the next hop indication refers to a receiving edge router in communication with the target site.

### Claim 16 (depends on 12)

The method of claim 12, further comprising routing the data packet from the service function forwarder to at least one VPN site based on a destination address.

### Claim 17 (depends on 12)

The method of claim 12, wherein the identifier of the virtual network context comprises a virtual routing and forwarding identifier (VRF-ID) of a VRF associated with the VPN.

### Claim 18

A router comprising a hardware processor, the router configured to:
receive an data packet addressed to a target site associated with the VPN;
determine a service to be applied to the data packet according to a service chain based at least in part on an identifier of a virtual network context in a Network Service Header (NSH) metadata of the data packet, wherein the determining is a function of at least one of the VPN, the origin site and the target site; and
route the data packet to a service function forwarder associated at the determined service.

### Claim 19 (depends on 18)

The router of claim 18, wherein the router is configured to define a virtual penultimate edge router as an end for the service chain, wherein the virtual penultimate edge router is positioned between the origin site and the target site.

### Claim 20 (depends on 18)

The router of claim 18, wherein the router is a virtual penultimate edge router, wherein the virtual penultimate edge router is logically positioned between the origin site and the target site, and wherein the router is configured to:
insert a next hop indication into the NSH metadata at the virtual penultimate edge router, wherein the next hop indication refers to a receiving edge router in communication with the target site.

### Claim 21 (depends on 18)

The router of claim 18, further configured to route the data packet from the service function forwarder to at least one VPN site based on a destination address.

### Claim 22 (depends on 18)

The router of claim 18, wherein the identifier of the virtual network context comprises a virtual routing and forwarding identifier (VRF-ID) of a VRF associated with the VPN.
