Mechanism to coordinate end to end quality of service between network nodes and service provider core

• US 10,567,293 B1
• Filed: 08/23/2018
• Issued: 02/18/2020
• Est. Priority Date: 08/23/2018
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Pularikkal, Gangadharan Byju, Patil, Santosh Ramrao, Grayson, Mark, Anantha, Swaminathan, Chakraborty, Sourav
• Primary Examiner(s): Zaidi, Iqbal
• Application Number:
  US16/111,074
• Publication Number:
  US 20200067844A1
• Time in Patent Office: 544 Days
• Field of Search: 370221-339
• CPC Class Codes: H04L 43/0852 Delays
• CPC Class Codes: H04L 43/0888 Throughput
• CPC Class Codes: H04L 43/0894 Packet rate
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 47/2491 Mapping quality of service [QoS] requirements between different networks
• CPC Class Codes: H04L 47/805 QOS or priority aware
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

Systems, methods, and devices are disclosed for providing a quality of service between nodes. A service provider can receive, from a first node of a customer network to an ingress node of a service provider network, packets bound for a second node on the customer network that is remote from the first node. The packets are mapped to a network segment according to a traffic type based on an identifier associated with the packets that identifies the traffic type of the packets. The packets are sent via their mapped network segment to an egress node with connectivity to the second node of the customer network according to a quality of service associated with the traffic type identified by the identifier.

Claims

1. A computer implemented method for ensuring a minimum quality of service between two network nodes, the method comprising:

receiving, from a first node of a customer network to an ingress node of a service provider network, packets bound for a second node on the customer network remote from the first node;

mapping the packets to a network segment according to a traffic type of a plurality of traffic types sharing portions of a bandwidth with different priority levels for each of the plurality of traffic types, the mapping based on an identifier associated with the packets that identifies the traffic type of the packets, the network segment being a virtual network within a shared physical network infrastructure of the service provider network, the identifier being a scalable group tag identifier configured to apply policies associated with the quality of service, and traffic steering for one or more of specific application flow types or security needs; and

sending the packets, via the network segment, to an egress node with connectivity to the second node according to a quality of service associated with the traffic type identified by the identifier.

2. The method of claim 1, wherein the network segment is comprised of a path of nodes in the service provider network selected to comply with the quality of service associated with the traffic type.

3. The method of claim 1,

wherein,

the traffic type is associated with a type of service, and

the type of service is mapped to logical resources within the network segment.

4. The method of claim 1, wherein the scalable group tag identifier is included within a network service header (NSH) of the packets that identifies the traffic type and quality of service parameters for the packets.

5. The method of claim 1, wherein the quality of service comprises one or more parameters associated with delay, throughput, bandwidth, latency, or loss characteristics associated with the traffic type.

6. The method of claim 1, wherein the scalable group tag identifier is configured to apply the traffic steering for the specific application flow types.

7. The method of claim 1,

wherein,

the quality of service is associated with one or more parameters of a service level agreement, and

a segmentation overlay comprising the network segment is based on the one or more parameters of the service level agreement and the network segment is a desired logical overlay segment associated with a VXLAN Network identifier (VNI).

8. A non-transitory computer-readable medium comprising instructions executable by one or more processors to perform a computer implemented method for ensuring a minimum quality of service between two network nodes, the instructions to:

receive, from a first node of a customer network to an ingress node of a service provider network, packets bound for a second node on the customer network remote from the first node;

map the packets to a network segment according to a traffic type of a plurality of traffic types sharing portions of a bandwidth with different priority levels for each of the plurality of traffic types, the packets being mapped based on an identifier associated with the packets that identifies the traffic type of the packets, the network segment being a virtual network within a shared physical network infrastructure of the service provider network, the identifier being a scalable group tag identifier configured to apply policies associated with the quality of service, and traffic steering for one or more of specific application flow types or security needs; and

send the packets, via the network segment, to an egress node with connectivity to the second node according to a quality of service associated with the traffic type identified by the identifier.

9. The non-transitory computer-readable medium of claim 8, wherein the network segment is comprised of a path of nodes in the service provider network selected to comply with the quality of service associated with the traffic type.

10. The non-transitory computer-readable medium of claim 8,

wherein,

the traffic type is associated with a type of service, and

the type of service is mapped to logical resources within the network segment.

11. The non-transitory computer-readable medium of claim 8, wherein the scalable group tag identifier is included within a network service header (NSH) of the packets that identifies the traffic type and quality of service parameters for the packets.

12. The non-transitory computer-readable medium of claim 8, wherein the quality of service comprises one or more parameters associated with delay, throughput, bandwidth, latency, or loss characteristics associated with the traffic type.

13. The non-transitory computer-readable medium of claim 8, wherein scalable group tag identifier is configured to apply the traffic steering for the specific application flow types.

14. The non-transitory computer-readable medium of claim 8,

wherein,

the quality of service is associated with one or more parameters of a service level agreement, and

a segmentation overlay comprising the network segment is based on the one or more parameters of the service level agreement and the network segment is a desired logical overlay segment associated with a VXLAN Network identifier (VNI).

15. A system for ensuring a minimum quality of service between two network nodes, the system comprising:

one or more processors; and

a communication interface coupled to the one or more processors, the communication interface configured to communicate with a local node and a remote node on a customer network, the one or more processors configured to perform operations comprising;

receiving, from the local node, packets bound for the remote node;

mapping the packets to a network segment according to a traffic type of a plurality of traffic types sharing portions of a bandwidth with different priority levels for each of the plurality of traffic types, the mapping based on an identifier associated with the packets that identifies the traffic type of the packets, the network segment being a virtual network within a shared physical network infrastructure of a service provider network, the identifier being a scalable group tag identifier configured to apply policies associated with the quality of service, and traffic steering for one or more of specific application flow types or security needs; and

sending the packets, via the network segment, to an egress node with connectivity to the remote node according to a quality of service associated with the traffic type identified by the identifier.

16. The system of claim 15, wherein the network segment is comprised of a path of nodes in the service provider network selected to comply with the quality of service associated with the traffic type.

17. The system of claim 15,

wherein,

the traffic type is associated with a type of service, and

the type of service is mapped to logical resources within the network segment.

18. The system of claim 15, wherein the scalable group tag identifier is included within a network service header (NSH) of the packets that identifies the traffic type and quality of service parameters for the packets.

19. The system of claim 15, wherein the quality of service comprises one or more parameters associated with delay, throughput, bandwidth, latency, or loss characteristics associated with the traffic type.

20. The system of claim 15, wherein the egress node has connectivity to an end point node within a mobile radio network.