Traffic segmentation

• US 8,554,860 B1
• Filed: 09/05/2003
• Issued: 10/08/2013
• Est. Priority Date: 09/05/2003
• Status: Active Grant

• Current Assignee: T-Mobile Innovations LLC (Deutsche Telekom AG)
• Original Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Inventors: Cook, Fred S., Satapathy, Durga P.
• Primary Examiner(s): Whipple, Brian P
• Application Number:
  US10/656,058
• Time in Patent Office: 3,686 Days
• Field of Search: None
• US Class Current: 709/207
• CPC Class Codes: H04L 45/24 Multipath
• CPC Class Codes: H04L 47/12 Avoiding congestion; Recovering from congestion
• CPC Class Codes: H04L 47/2433 Allocation of priorities to traffic types

Abstract

An apparatus and method for forwarding message packets over a network having at least one dedicated priority route. The priority messages are identified and only those priority messages having a length less than or equal to a threshold message length are transmitted over the priority route.

Claims

1. An apparatus for controlling the flow of message packets across a message packet network comprising:

an entry router that provides access to the message packet network, the message packet network having at least one transmission route dedicated to the transmission of priority message packets having a selected message length and application; and

an admission controller connected to said entry router and adapted to receive message packets from a network user;

said admission controller operative to examine the header of each message packet generated by said user and, upon determining that a message packet includes a priority message identifier in said message packet header to compare the length of said priority message packet to a fixed threshold priority message packet length that is selected as a function of said application of said priority message packets, said admission controller being further operable, upon determining that said priority message packet is one of less than and equal to said threshold priority message packet length to forward said priority message packet over said message packet network via said dedicated priority transmission route, said admission controller also being operative, upon determining that said priority message packet is longer than said threshold priority message packet length to remove said priority message identifier from said message packet header and to then forward the resulting message packet over the message packet network via a non-priority message route.

2. The apparatus according to claim 1 wherein said threshold priority message packet length is also a function of an application control message length.

3. The apparatus according to claim 2 wherein said priority message packet is a get request and further wherein said threshold priority message packet length is larger than the length of a HTTP get request and smaller than the length of a next larger control message command to set a message packet length such that other types of control message commands based on the message length are not allowed to be sent over said at least one dedicated transmission route.

4. The apparatus according to claim 2 wherein said backbone network is the internet and said message is a get request and further wherein said threshold priority message packet length is set to a length to only allow the length of a HTTP get request.

5. The apparatus according to claim 3 wherein said admission controller is further operative, upon determining that said priority message packet is longer than said threshold priority message packet length to send an error message to said network user.

6. The apparatus according to claim 3 wherein, subsequent to forwarding said priority message packet over the message packet network, said controller is further operative to assess the user a priority route service charge that is based upon the use of said dedicated priority message route.

7. The apparatus according to claim 5 wherein said message packet network is a backbone network.

8. The apparatus according to claim 7 wherein said backbone network is the internet.

9. A method for controlling the flow of message packets across a message packet network comprising the steps of:

(a) providing an admission controller adapted to receive and screen message packets from a network user, the admission controller connected to the message packet network, the message packet network including at least one transmission route dedicated to transmission of priority message packets having a selected message length and application;

(b) receiving a message packet from a network user for transmission over the message packet network;

(c) examining the message packet header to determine that the message header includes a priority message identifier;

(d) comparing the length of the message packet to a fixed threshold priority message packet length that is selected as a function of said application of said priority message packets; and

(e) forwarding the priority message over the dedicated priority message route only upon determining that the priority message length is one of less than and equal to the threshold priority message packet length and forwarding the message over a non-priority message route upon determining that the message length is greater than the threshold priority message packet length.

10. The method according to claim 9 further including, upon determining in step (c) that the message header does not include a priority message identifier, forwarding the message over the network via the non-priority message route.

11. The method according to claim 10 further including, upon determining in step (d) that the length of the priority message packet is greater than the threshold priority message packet length, removing the priority message identifier from the message header.

12. The method according to claim 11 further including, upon determining in step (d) that the length of the priority message packet is greater than the threshold priority message packet length, sending an error message to the network user.

13. The method according to claim 11 further including, after forwarding a message over the internet via a dedicated priority message route, assessing the user a priority route service charge.

14. The method according to claim 11 wherein, during step (d), the threshold priority message packet length compared to the length of the message packet is also a function of an application control message length.

15. The method according to claim 14 wherein the message packet being compared to the threshold priority message packet length is a get request and further wherein the threshold priority message packet length is larger than the length of a HTTP get request and smaller than the length of a next larger control message command.

16. The method according to claim 14 wherein the message packet being compared to the threshold priority message packet length is a get request and further wherein the threshold priority message packet length also has a length to only allow transmission of messages having the length of a HTTP get request over the priority message transmission route.