# US 2010/0061237 A1 · Method and apparatus for managing end-to-end quality of service policies in a communication system

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

- Number: US 2010/0061237 A1
- Document ID: US20100061237A1
- Status: Published application
- Kind: A1
- Application number: 12/621,098
- Filed: 2009-11-18
- Published: 2010-03-11
- Earliest claimed: 2005-03-31
- Assignees: AT&T Intellectual Property I, L.P.
- Inventors: CHENG-HONG HU
- Web page: https://patentgrep.com/patent/US20100061237A1

## CPC

- H04L 47/825: {Involving tunnels, e.g. MPLS}
- H04L 41/0894: Policy-based network configuration management
- H04L 41/5003: Managing SLA; Interaction between SLA and QoS
- H04L 41/5022: by giving priorities, e.g. assigning classes of service
- H04L 47/15: {in relation to multipoint traffic (arrangements for broadcast or multicast in data networks H04L12/18)}
- H04L 47/70: Admission control; Resource allocation
- H04L 47/745: {Reaction in network}
- H04L 47/786: {Mapping reservation between domains}
- H04L 47/808: {User-type aware}
- H04L 41/5009: Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
- H04L 43/00: Arrangements for monitoring or testing data switching networks
- H04L 43/16: Threshold monitoring
- H04L 2012/6464: {Priority}
- H04L 2012/6489: {Buffer Management, Threshold setting, Scheduling, Shaping}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A computer-readable storage medium (102) is provided for managing end-to-end QoS (Quality of Service) policies in a communication network (100). The storage medium includes computer instructions for establishing (302) a plurality of QoS domains (108) between a plurality of packet switching technologies (102, 106. 110) operating with disparate QoS policies, each QoS domain having an ingress and egress boundary, remapping (303) a QoS policy of each packet exchanged between the ingress boundaries of the plurality of QoS domains, and restoring (309) the QoS policy of each packet exchanged between the egress boundaries of the plurality of QoS domains.

## Claims

### Claim 1

A computer-readable storage medium for managing end-to-end QoS (Quality of Service) policies in a communication network, the storage medium comprising computer instructions for:
establishing a plurality of QoS domains between a plurality of packet switching technologies operating with disparate QoS policies, each QoS domain having an ingress and egress boundary;
monitoring traffic metrics of packets received from one or more of the plurality of QoS domains among the plurality of packet switching technologies at an ingress boundary, wherein the traffic metrics comprise a QoS policy for each of the received packets, traffic conditions, and the SLA packet traffic constraints of said plurality of QoS domains at said ingress boundary;
remapping the QoS policy for each of the received packets according to said traffic metrics; and
restoring the QoS policy of each packet exchanged between the egress boundaries of the plurality of QoS domains for the plurality of packet switching technologies.

### Claim 2 (depends on 1)

The storage medium of claim 1, wherein each QoS policy of the plurality of packet switching technologies is managed by a Service Level Agreement (SLA) establishing packet traffic constraints.

### Claim 3 (depends on 2)

The storage medium of claim 2, wherein a portion of the communication network operates according to a Multi-Protocol Label Switching (MPLS) standard, and wherein the remapping step comprises computer instructions for coding an EXP field conforming to the MPLS standard with the remapped QoS policy for each packet destined to be transported by the portion of the communication network operating according to MPLS standard.

### Claim 4 (depends on 3)

The storage medium of claim 3, further comprising the step of discarding packets when traffic conditions exceed the SLA packet traffic constraints.

### Claim 5 (depends on 1)

The storage medium of claim 1, wherein the remapping of the QoS policy for each of the received packets is done according to said traffic metrics by lowering a transmission priority of the QoS policy of a packet when traffic conditions are above average and below peak traffic conditions established by the SLA and wherein storage medium comprises computer instructions for transmitting the packets with remapped QoS policies.

### Claim 6 (depends on 1)

The storage medium of claim 1, wherein the restoring step further comprises computer instructions for:
monitoring traffic conditions of packets received from one or more of the plurality of QoS domains at an egress boundary;
queuing the received packets according to traffic conditions and the QoS policy provided in the remapping step for each of the received packets;
restoring the QoS policy of each packet according to the QoS policy prior to the remapping step; and
transmitting the queued packets with the restored QoS policy.

### Claim 7 (depends on 6)

The storage medium of claim 6, wherein the restoring step further comprises computer instructions for discarding packets with a low QoS transmission priority when traffic conditions exceed a queuing capacity of the storage medium.

### Claim 8 (depends on 1)

The storage medium of claim 1, wherein the plurality of packet switching technologies conform to a MultiProtocol Label Switching (MPLS) standard, and wherein a portion of said packet switching technologies are coupled to at least one among a group of Internet switching services comprising an Asynchronous Transfer Mode Frame Relay (ATMFR), a Virtual Private Network (VPN), a Voice over Internet Protocol (VoIP), a Digital Subscriber Line (DSL), and Ethernet.

### Claim 9

A provider edge for managing end-to-end QoS (Quality of Service) policies in a communication network, comprising:
a packet router at the provider edge; and
a processor for controlling operations of the packet router, wherein the processor is programmed to:
establish a plurality of QoS domains between a plurality of packet switching technologies operating with disparate QoS policies, each QoS domain having an ingress and egress boundary;
monitor traffic metrics of packets received from one or more of the plurality of QoS domains among the plurality of packet switching technologies at an ingress boundary;
remap the QoS policy for each of the received packets according to said traffic metrics; and
transmit the packets with remapped QoS policies.

### Claim 10 (depends on 9)

The provider edge of claim 9, wherein each QoS policy of the plurality of packet switching technologies is managed by a Service Level Agreement (SLA) establishing packet traffic constraints.

### Claim 11 (depends on 10)

The provider edge of claim 10, wherein a portion of the communication network operates according to a Multi-Protocol Label Switching (MPLS) standard, and wherein the remap step the processor is further programmed to code an EXP field conforming to the MPLS standard with the remapped QoS policy for each packet destined to be transported by the portion of the communication network operating according to MPLS standard.

### Claim 12 (depends on 11)

The provider edge of claim 11, wherein the processor is further programmed to discard packets when traffic conditions exceed the SLA packet traffic constraints.

### Claim 13 (depends on 9)

The provider edge of claim 9, wherein the traffic metrics comprise a QoS policy for each of the received packets, traffic conditions, and the SLA packet traffic constraints of said plurality of QoS domains at said ingress boundary and wherein the processor is programmed to remap the QoS policy for each of the received packets according to said traffic metrics by lowering a transmission priority of the QoS policy of a packet when traffic conditions are above average and below peak traffic conditions established by the SLA.

### Claim 14 (depends on 9)

The provider edge of claim 9, wherein the restore step the processor is further programmed to:
monitor traffic conditions of packets received from one or more of the plurality of QoS domains at an egress boundary;
queue the received packets according to traffic conditions and the QoS policy provided in the remapping step for each of the received packets;
restore the QoS policy of each packet according to the QoS policy prior to the remap step; and
transmit the queued packets with the restored QoS policy.

### Claim 15 (depends on 14)

The provider edge of claim 14, wherein the restoring step the processor is further programmed to discard packets with a low QoS transmission priority when traffic conditions exceed a queuing capacity of the storage medium.

### Claim 16 (depends on 9)

The provider edge of claim 9, wherein the plurality of packet switching technologies conform to a MultiProtocol Label Switching (MPLS) standard, and wherein a portion of said packet switching technologies are coupled to at least one among a group of Internet switching services comprising an Asynchronous Transfer Mode Frame Relay (ATMFR), a Virtual Private Network (VPN), a Voice over Internet Protocol (VoIP), a Digital Subscriber Line (DSL), and Ethernet.

### Claim 17

A method for managing end-to-end QoS (Quality of Service) policies, comprising:
monitoring traffic metrics of packets received from one or more of the plurality of QoS domains among the plurality of packet switching technologies at an ingress boundary;
remapping the QoS policy for each of the received packets according to said traffic metrics and a service level agreement (SLA);
transmitting the packets with remapped QoS policies; and
restoring the QoS policy of each packet exchanged between the egress boundaries of the plurality of QoS domains for the plurality of packet switching technologies.

### Claim 18 (depends on 17)

The method of claim 17, wherein each QoS policy of the plurality of packet switching technologies is managed by a Service Level Agreement (SLA) establishing packet traffic constraints, and wherein the remapping step comprises the steps of:
monitoring traffic metrics of packets received from one or more of the plurality of QoS domains at an ingress boundary, wherein said traffic metrics comprise a QoS policy for each of the received packets, traffic conditions, and the SLA packet traffic constraints of said plurality of QoS domains at said ingress boundary;
discarding packets received when traffic conditions exceed the SLA packet traffic constraints;
remapping the QoS policy for each of the remaining packets according to the traffic metrics; and
transmitting the packets with remapped QoS policies.

### Claim 19 (depends on 17)

The method of claim 17, wherein the method transmits each of the queued packets with their restored QoS policy.

### Claim 20 (depends on 17)

The method of claim 17, wherein the method operates in a communication network, wherein a portion of the communication network operates according to a Multi-Protocol Label Switching (MPLS) standard, and wherein the remapping step further comprises the step of coding an EXP field conforming to the MPLS standard with the remapped QoS policy for each packet destined to be transported by the portion of the communication network operating according to MPLS standard.
