Quality of service in packet networks
Methods and systems for providing quality of service over IP networks are disclosed. In one aspect, a flow label field of a header may be divided into first and second portions. The first portion defines a quality of service. The second portion identifies a message flow. Once the first portion defining the quality of service is established by the sending node, no nodes in the transmission path may change the quality of service value. Each node may route packets based on the quality of service field, or may modify the traffic class field of the header based on the quality of service and then route the packet based on the traffic class field. The QoS field can be used to complement a DSCP/traffic class field and provide a better mechanism for end-to-end QoS using IPv6. A service provider can use DSCP within its own administrative domain(s), and end users can set and maintain QoS using the methods described herein, thereby providing a framework for end-to-end QoS using IP packets.
1. An apparatus comprising:
a processor, and
memory storing computer-executable instructions that, when executed by the processor, cause the apparatus to:
receive a data packet comprising a header that comprises: a data field indicating a protocol version, a traffic class data field indicating a first traffic class, a data field indicating a flow label, and an immutable data field indicating a quality of service and populated by a source node that generated the data packet;
if the data packet is from inside an administrative domain associated with the apparatus:
send, based at least on the traffic class data field, the data packet to a next hop node; and
if the data packet is from outside the administrative domain associated with the apparatus:
determine a second traffic class for the data packet based on the quality of service,
update the traffic class data field with the second traffic class, and
send, based at least on the updated traffic class data field, the data packet to the next hop node.
2. The apparatus of claim 1 , wherein the determining the second traffic class is based on a mapping of quality of service to traffic class.
3. The apparatus of claim 2 , wherein the mapping is based on the administrative domain associated with the apparatus, and different from a second mapping of quality of service to traffic class associated with a second administrative domain.
4. The apparatus of claim 1 , wherein the header of the data packet further comprises one or more of:
a data field indicating a payload length;
a data field indicating a next header;
a data field indicating a hop limit;
a data field indicating a source address; and
a data field indicating a destination address.
5. The apparatus of claim 1 , wherein the quality of service indicates acceptable levels of two or more of throughput, dropped packets, errors, latency, jitter, and ordered delivery.
6. The apparatus of claim 1 , wherein the data packet comprises an Internet Protocol (IP) data packet.
7. A method comprising:
receiving, by a routing node in a packet switched network, a data packet comprising a header that comprises: a data field indicating a protocol version, a traffic class data field indicating a first traffic class, a data field indicating a flow label, and an immutable data field indicating a quality of service and populated by a source node that generated the data packet;
if the data packet is from a previous hop node within a same administrative domain as the routing node:
sending, based at least on the traffic class data field, the data packet to a next hop node; and
if the data packet is from a previous hop node not within the same administrative domain as the routing node:
determining a second traffic class for the data packet based on the quality of service,
updating the traffic class data field with the second traffic class, and
sending, based at least on the updated traffic class data field, the data packet to the next hop node.
8. The method of claim 7 , wherein the determining the second traffic class is based on a mapping of quality of service to traffic class.
9. The method of claim 8 , wherein the mapping is based on the administrative domain associated with the routing node, and different from a second mapping of quality of service to traffic class based on a second administrative domain not associated with the routing node.
10. The method of claim 7 , wherein the header of the data packet further comprises one or more of:
a data field indicating a payload length;
a data field indicating a next header;
a data field indicating a hop limit;
a data field indicating a source address; and
a data field indicating a destination address.
11. The method of claim 7 , wherein the previous hop node not within the same administrative domain as the routing node comprises a node within a second administrative domain under control of a same network operator as the administrative domain associated with the routing node.
12. The method of claim 7 , wherein the previous hop node not within the same administrative domain as the routing node comprises a node within a second administrative domain under control of a different network operator as the administrative domain associated with the routing node.
13. The method of claim 7 , wherein the data packet comprises an Internet Protocol (IP) data packet.
14. A method comprising:
receiving, by a routing node, a data packet comprising a header that comprises: a traffic class data field indicating a first traffic class, a data field indicating a flow label, and an immutable data field indicating a quality of service and populated by a source node that generated the data packet;
if the data packet is from a previous hop node within a same administrative domain as the routing node:
sending, based at least on the traffic class data field, the data packet to a next hop node; and
if the data packet is from a previous hop node not within the same administrative domain as the routing node:
determining a second traffic class for the data packet based on the quality of service,
updating the traffic class data field with the second traffic class, and
sending, based at least on the updated traffic class data field, the data packet to the next hop node.
15. The method of claim 14 , wherein the determining the second traffic class is based on a mapping of quality of service to traffic class.
16. The method of claim 15 , wherein the mapping is based on the administrative domain associated with the routing node, and different from a second mapping of quality of service to traffic class based on a second administrative domain not associated with the routing node.
17. The method of claim 14 , wherein the quality of service indicates an acceptable level for two or more of throughput, dropped packets, errors, latency, jitter, and ordered delivery.