Packet metadata channels carrying infrastructure metadata in networks

• US 9,300,579 B2
• Filed: 04/15/2013
• Issued: 03/29/2016
• Est. Priority Date: 02/11/2013
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Frost, Daniel C., Spraggs, Simon James Trevor, Fernando, Rex Emmanuel, Bryant, Stewart Frederick, Guichard, Jim, Pignataro, Carlos M., Filsfils, Clarence
• Primary Examiner(s): EBRAHIM, ANEZ C
• Application Number:
  US13/863,013
• Publication Number:
  US 20140226662A1
• Time in Patent Office: 1,079 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 45/50 using label swapping, e.g. multi-protocol label switch [MPLS]
• CPC Class Codes: H04L 45/74 Address processing for routing

Abstract

In one embodiment, an apparatus in a network determines particular metadata to communicate infrastructure information associated with a particular packet to another apparatus in the network. The apparatus sends into the network the particular packet including a metadata channel, comprising said particular metadata, external to the payload of the particular packet. Examples of infrastructure metadata carried in a packet include, but are not limited to, information defining service chaining for processing of the packet, contextual information for processing of the packet, specific handling instructions of the packet, and operations, maintenance, administration (OAM) instrumentation of the packet.

Claims

1. A method, comprising:

receiving, by a first provider edge packet switching device in a provider network, a client packet from a client edge packet switching device in a client network;

determining, by the first provider edge packet switching device, particular metadata provider network signaling information to communicate infrastructure information associated with the client packet to a second provider packet switching device in the provider network, with said particular metadata provider network signaling information for use by at least the second provider packet switching device in processing the client packet, with said particular metadata provider network signaling information including a specific application to apply to the client, packet, contextual information specifying a profile or user name, or instrumentation information for measuring packet loss or latency; and

adding, by the first provider edge packet switching device, to the client packet a metadata component structure including a metadata channel header and a metadata channel, with the metadata channel comprising said particular metadata provider network signaling information, and with the metadata component structure being placed between and external to the header and payload of the client packet;

sending, from the first provider edge packet switching device to the second provider packet switching device through the provider network, the client packet after said adding operation;

receiving, by the second provider packet switching device, the client packet including the metadata component structure including the metadata channel with said particular metadata provider network signaling information;

processing, by the second provider packet switching device, the client packet based on said particular metadata provider network signaling information; and

sending, by the second provider packet switching device, the client packet from the provider network, directly or through another one or more provider packet switching devices in the provider network, wherein the metadata component structure including the metadata channel with said particular metadata provider network signaling information is removed from the client packet by a provider packet switching device of the provider network prior to the client packet exiting the provider network.

2. The method of claim 1, wherein said particular metadata provider network signaling information includes information for measuring packet loss or latency within the provider network.

3. The method of claim 1, wherein said particular metadata provider network signaling information includes the specific application to apply to the packet within the provider network.

4. The method of claim 1, wherein said particular metadata provider network signaling information includes contextual information specifying a profile or user name for processing of the client packet within the provider network.

5. The method of claim 1, wherein the client packet is a Multiprotocol Label Switching (MPLS) packet.

6. The method of claim 1, wherein the client packet is an Internet Protocol (IP) packet.

7. A provider network, comprising:

a first provider edge packet switching device, including one or more first processors;

first memory;

a first plurality of interfaces configured to send and receive packets; and

one or more first packet switching mechanisms configured to packet switch packets among the first plurality of interfaces; and

a second provider packet switching device, including one or more second processors;

second memory;

a second plurality of interfaces configured to send and receive packets; and

one or more second packet switching mechanisms configured to packet switch packets among the second plurality of interfaces;

wherein the first provider edge packet switching device is configured to perform operations including;

receiving a client packet from a client edge packet switching device in a client network;

particular metadata provider network signaling information to communicate infrastructure information associated with the client packet to the second provider packet switching device, with said particular metadata provider network signaling information for use by at least the second provider packet switching device in processing the client packet, with said particular metadata provider network signaling information including a specific application to apply to the client packet, contextual information specifying a profile or user name, or instrumentation information for measuring packet loss or latency;

adding to the client packet a metadata component structure including a metadata channel header and a metadata channel, with the metadata channel comprising said particular metadata provider network signaling information, and with the metadata component structure being placed between and external to the header and payload of the client packet; and

sending the client packet after said adding the metadata component structure to the second provider packet switching device; and

wherein the second provider packet switching device is configured to perform operations including;

receiving the client packet including the metadata component structure including the metadata channel with said particular metadata provider network signaling information;

processing the client packet based on said particular metadata provider network signaling information; and

sending the client packet from the provider network, directly or through another one or more provider packet switching devices in the provider network, wherein the metadata component structure including the metadata channel with said particular metadata provider network signaling information is removed from the client packet by a provider packet switching device of the provider network prior to the client packet exiting the provider network.

8. The provider network of claim 7, wherein said particular metadata provider network signaling information includes information for measuring packet loss or latency.

9. The provider network of claim 7, wherein said particular metadata provider network signaling information includes the specific application to apply to the packet.

10. The provider network of claim 7, wherein said particular metadata provider network signaling information includes contextual information specifying a profile or user name for processing of the client packet.

11. The provider network of claim 7, wherein the client packet is a Multiprotocol Label Switching (MPLS) packet.

12. The provider network of claim 7, wherein the client packet is an Internet Protocol (IP) packet.

13. A method, comprising:

receiving, by a first provider edge packet switching device in a provider network, a client packet from a client edge packet switching device in a client network;

determining, by the first provider edge packet switching device, particular metadata provider network signaling information to communicate infrastructure information associated with the client packet to a second provider packet switching device in the provider network, with said particular metadata provider network signaling information for use by at least the second provider packet switching device in processing the client packet, with said particular metadata provider network signaling information including a specific application to apply to the client packet, contextual information specifying a profile or user name, or instrumentation information for measuring packet loss or latency; and

adding, by the first provider edge packet switching device, to the client packet a metadata component structure including a metadata channel header and a metadata channel, with the metadata channel comprising said particular metadata provider network signaling information, and with the metadata component structure being placed between and external to the header and payload of the client packet; and

sending the client packet after said adding operation from the first provider edge packet switching device to the second provider packet switching device.

14. The method of claim 13, wherein said particular metadata provider network signaling information includes information for measuring packet loss or latency within the provider network.

15. The method of claim 13, wherein said particular metadata provider network signaling information includes the specific application to apply to the packet within the provider network.

16. The method of claim 13, wherein said particular metadata provider network signaling information includes contextual information specifying a profile or user name for processing of the client packet within the provider network.

17. A method, comprising:

receiving, by a second provider packet switching device, a client packet including a metadata component structure including a metadata channel header and a metadata channel, with the metadata channel comprising particular metadata provider network signaling information, and with the metadata component structure being located between and external to the header and payload of the client packet, with said particular metadata provider network signaling information defining to the provider network information for processing the particular packet, with said particular metadata provider network signaling information including a specific application to apply to the client packet, contextual information specifying a profile or user name, or instrumentation information for measuring packet loss or latency;

processing, by the second provider packet switching device, the client packet based on said particular metadata provider network signaling information, including removing said particular metadata provider network signaling information from the client packet; and

sending the client packet without said particular metadata provider network signaling information from the provider network directly or through another one or more provider packet switching devices in the provider network.

18. The method of claim 17, wherein said particular metadata provider network signaling information includes information for measuring packet loss or latency within the provider network.

19. The method of claim 17, wherein said particular metadata provider network signaling information includes the specific application to apply to the packet within the provider network.

20. The method of claim 17, wherein said particular metadata provider network signaling information includes contextual information specifying a profile or user name for processing of the client packet within the provider network.