# US 2015/0103827 A1 · Configurable Service Proxy Mapping

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

- Number: US 2015/0103827 A1
- Document ID: US20150103827A1
- Status: Published application
- Kind: A1
- Application number: 14/052,968
- Filed: 2013-10-14
- Published: 2015-04-16
- Earliest claimed: 2013-10-14
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Paul Quinn; James Guichard; Surendra Kumar
- Web page: https://patentgrep.com/patent/US20150103827A1

## CPC

- H04L 45/74: Address processing for routing
- H04L 49/354: for supporting virtual local area networks [VLAN]
- H04L 49/70: {Virtual switches}
- H04L 67/63: Routing a service request depending on the request content or context
- 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

Presented herein are techniques in which a service proxy in a service node is configured to receive a packet encapsulated in a service header that includes a variable set of context headers. The service proxy is configured to use the context headers in the service header to map data in the packet to a local identifier that is associated with one of a plurality of service-functions hosted by the service node. The service proxy is further configured to forward the data in the packet to the service-function associated with the local identifier.

## Claims

### Claim 1

A method comprising:
receiving, at a service node in a network comprising a plurality of service nodes each configured to host one or more service-functions for application to traffic that passes through the respective service nodes forming a service path, a packet encapsulated in a service header that includes a variable set of context headers;
at the service node, evaluating the context headers in the packet based on one or more policies to determine a local identifier associated with a first service-function of a plurality of service-functions hosted by the service node; and
forwarding data in the packet to the first service-function associated with the local identifier.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving the packet at a configurable service proxy in the service node.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
receiving, at the service node, an identification of which context headers for evaluation in received packets.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
receiving, at the service node, an identification of the one or more policies for evaluating the context headers.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
prior to forwarding the data in the packet to the first service-function associated with the local identifier, removing the context headers from the data.

### Claim 6 (depends on 1)

The method of claim 1, where evaluating the context headers in the packet based on one or more policies to determine a local identifier comprises:
determining a virtual local area networks (VLAN) associated with the first service-function.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
receiving modified data from the first service-function associated with the local identifier;
encapsulating the modified data with the service header; and
determining, based on the set of context headers, how to forward the packet.

### Claim 8 (depends on 1)

The method of claim 1, wherein each context header carries service related information of a different scope that is relevant to one or more service-functions in the service path.

### Claim 9 (depends on 1)

The method of claim 1, further comprising generating the service header that includes the variable set of context headers, at a controller that is in communication with the plurality of service nodes.

### Claim 10

An apparatus comprising:
a network interface in a service node in a network comprising a plurality of service nodes each configured to host one or more service-functions for application to traffic that passes through the respective service nodes forming a service path;
a memory; and
a processor configured to:
receive a packet encapsulated in a service header that includes a variable set of context headers,
evaluate the context headers in the packet based on one or more policies to determine a local identifier associated with a first service-function of a plurality of service-functions hosted by the service node,
forward data in the packet to the first service-function associated with the local identifier.

### Claim 11 (depends on 10)

The apparatus of claim 10, wherein the network interface, memory, and processor are part of a configurable service proxy device in the service node.

### Claim 12 (depends on 10)

The apparatus of claim 10, wherein the processor is configured to:
receive an identification of which context headers for evaluation in received packets.

### Claim 13 (depends on 10)

The apparatus of claim 10, wherein the processor is configured to:
receive an identification of the one or more policies for evaluating the context headers.

### Claim 14 (depends on 10)

The apparatus of claim 10, wherein the processor is configured to:
prior to forwarding the data in the packet to the first service-function associated with the local identifier, remove the context headers from the data.

### Claim 15 (depends on 10)

The apparatus of claim 10, where to evaluate the context headers in the packet based on one or more policies to determine a local identifier, the processor is configured to:
determine a virtual local area networks (VLAN) associated with the first service-function.

### Claim 16 (depends on 10)

The apparatus of claim 10, wherein the processor is configured to:
receive modified data from the first service-function associated with the local identifier;
encapsulate the modified data with the service header; and
determine, based on the set of context headers, how to forward the packet.

### Claim 17 (depends on 10)

The apparatus of claim 10, wherein each context header carries service related information of a different scope that is relevant to one or more service-functions in the service path.

### Claim 18

One or more computer readable storage media encoded with software comprising computer executable instructions and when the software is executed operable to:
receive, at a service node in a network comprising a plurality of service nodes each configured to host one or more service-functions for application to traffic that passes through the respective service nodes forming a service path, a packet encapsulated in a service header that includes a variable set of context headers;
at the service node, evaluate the context headers in the packet based on one or more policies to determine a local identifier associated with a first service-function of a plurality of service-functions hosted by the service node; and
forward data in the packet to the first service-function associated with the local identifier.

### Claim 19 (depends on 18)

The computer readable storage media of claim 18, further comprising instructions operable to:
receive the packet at a configurable service proxy in the service node.

### Claim 20 (depends on 18)

The computer readable storage media of claim 18, further comprising instructions operable to:
receive, at the service node, an identification of which context headers for evaluation in received packets.

### Claim 21 (depends on 18)

The computer readable storage media of claim 18, further comprising instructions operable to:
receive, at the service node, an identification of the one or more policies for evaluating the context headers.

### Claim 22 (depends on 18)

The computer readable storage media of claim 18, further comprising instructions operable to:
prior to forwarding the data in the packet to the first service-function associated with the local identifier, remove the context headers from the data.

### Claim 23 (depends on 18)

The computer readable storage media of claim 18, where the instructions operable to evaluate the context headers in the packet based on one or more policies to determine a local identifier comprise instructions operable to:
determine a virtual local area networks (VLAN) associated with the first service-function.

### Claim 24 (depends on 18)

The computer readable storage media of claim 18, further comprising instructions operable to:
receive modified data from the first service-function associated with the local identifier;
encapsulate the modified data with the service header; and
determine, based on the set of context headers, how to forward the packet.

### Claim 25 (depends on 18)

The computer readable storage media of claim 18, wherein each context header carries service related information of a different scope that is relevant to one or more service-functions in the service path.
