IP Library Granted Patent US 12706836
Granted Patent B2
US 12706836 · App. 18/194,037 · Granted Aug 11, 2026

Network service chains using sustainability

Inventors: Carlos Pignataro (Cary, NC); Nagendra Kumar Nainar (Morrisville, NC); Sri Gundavelli (San Jose, CA)
Assignee: Cisco Technology, Inc.
H04L45/302H04L67/63
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12706836
App. No.
18/194,037
Granted
Aug 11, 2026
Kind
B2
Abstract

Network energy efficiency and green power selection may be optimized by employing graph-oriented service chains configured to share sustainability attributes and metadata augmentation. More specifically, network Service Function Chain (SFC) creation can include a set of power and energy-specific and sustainable attributes. In general, the goal of SFC is to enable the creation of a service path that matches the specific needs of an application or service. SFCs are composed of a sequence of network functions, such as firewalls, load balancers, intrusion detection systems, and other services. Each network function performs a specific task on the network traffic, and the packets are passed from one function to the next until they reach their destination. Overall, SFCs are a powerful tool for managing complex network environments, enabling network administrators to deploy and manage network services more efficiently and effectively.

Claims (83)

1 . A device, comprising:

one or more processors;

a communications interface;

a non-transitory computer-readable storage media, that when executed by the one or more processors, directs the device to:

initiate a call for a service function by an application;

create an identifier for a service function path and a field suitable for storing a node index associated with a node sequence within a path;

generate a first header comprising the identifier for the service function path, the node index, and green metadata;

compile the first header and a first payload into a first packet;

receive the first packet at a first destination point;

determine a service function to be performed;

determine a second destination point where the service function is to be performed, using the green metadata; and

transmit the first packet to a network; and

a service function forwarder configured to:

analyze the first packet to determine a first service function to be performed based on the identifier for the service function path and the node index;

forward the first packet to the first service function; and

cause the first service function to perform a service, decrement the node index, and

re-encapsulate the first packet.

2 . The device of claim 1 , wherein the node index is a Service Index (SI).

3 . The device of claim 2 , wherein the identifier for the service function path is a Service Function Path Identifier (SFP-ID).

4 . The device of claim 3 , wherein the device is further directed to:

receive a second packet from the network;

process the second packet; and

read the SFP-ID, the SI, and the green metadata associated with the second packet.

5 . The device of claim 4 , wherein the device is further directed to:

determine if all services have been performed;

determine if the device is the device of origin; and

return a second payload to the application.

6 . The device of claim 1 , wherein the green metadata comprises at least one of: geolocation of Network Entities (NEs), power modes of NEs, energy types powering NEs, efficiency of NEs, or battery levels of NEs.

7 . The device of claim 1 , wherein:

the first header is a Network Service Header (NSH); and

the green metadata comprises, at least in part, an application identification (APP-ID).

8 . A device, comprising:

one or more processors;

a communications interface;

a non-transitory computer-readable storage media, that when executed by the one or more processors, directs the device to:

receive a first packet via the communications interface at a first destination point;

process the first packet to extract a first header and a first payload;

determine that the first packet is a service function request;

read an identifier for a service function path, a node index, and green metadata from the first header; and

determine a second destination point where the service function is to be performed, using the green metadata; and

a service function forwarder configured to:

analyze the first packet to determine a first service function to be performed based on the identifier for the service function path and the node index;

forward the first packet to the first service function; and

cause the first service function to perform a service, decrement the node index,

and re-encapsulate the first packet.

9 . The device of claim 8 , wherein the node index is a Service Index (SI).

10 . The device of claim 9 , wherein the identifier for the service function path is a Service Function Path Identifier (SFP-ID).

11 . The device of claim 10 , wherein the device is further directed to:

determining from the SFP-ID and the SI what service function (SF) is to be performed; and

determining from the green metadata where a service function is to be performed.

12 . The device of claim 11 , wherein the device is further directed to:

performing the SF on the first payload to generate a second payload;

decrement the SI;

generating a second header from the SFP-ID, the decremented SI, and the green metadata;

compiling the second header and the second payload into a second packet; and

transmitting the second packet to a network.

13 . The device of claim 12 , wherein the green metadata comprises at least one of: geolocation of Network Entities (NEs), power modes of NEs, energy types powering NEs, efficiency of NEs, or battery levels of NEs.

14 . The device of claim 11 , wherein Network Entities (Nes) comprise at least one of: servers, routers, switches, disk arrays, wireless LAN controllers, wireless access points, cellular access points, or client computers.

15 . A method, comprising:

initiating a call for a service function by an application;

creating a Service Function Path Identifier (SFP-ID) and a Service Index (SI);

generating a first header comprising the SFP-ID, the SI, and green metadata;

compiling the first header and a first payload into a first packet;

receiving the first packet at a first destination point;

determining a service function to be performed;

determining a second destination point where the service function is to be performed; and

transmitting the first packet to a device over a network

utilizing a service function forwarder to:

analyze the first packet to determine a first service function to be performed based on the identifier for the service function path and the node index;

forwarding the first packet to the first service function; and

causing the first service function to perform a service, decrement the node index, and

re-encapsulate the first packet.

16 . The method of claim 15 , wherein the method further comprises:

receiving a second packet from the network;

processing the second packet; and

reading the SFP-ID, the SI, and the green metadata associated with the second packet.

17 . The method of claim 16 , wherein the method further comprises:

determining if all services have been performed;

determining if the device is the device of origin; and

returning a second payload to the application.

18 . The method of claim 16 , wherein the green metadata comprises at least one of: geolocation of Network Entities (NEs), power modes of NEs, energy types powering NEs, efficiency of NEs, or battery levels of NEs.

19 . The method of claim 18 , wherein the NEs comprise at least one of: servers, routers, switches, disk arrays, wireless LAN controllers, wireless access points, cellular access points, or client computers.

20 . The method of claim 15 , wherein the first header comprises at least one of: a Network Service Header (NSH), a Segment Routing IPV6 (SRv6) header, or a Multi-Protocol Label Switching (MPLS) header.