Methods And Systems For Controlling SIP Overload

• US 20120008495A1
• Filed: 02/25/2011
• Published: 01/12/2012
• Est. Priority Date: 02/25/2010
• Status: Active Grant

• Current Assignee: Trustees Of Columbia University In The City Of New York (Columbia University)
• Original Assignee: Trustees Of Columbia University In The City Of New York (Columbia University)
• Inventors: Shen, Qi, Schulzrinne, Henning
• Granted Patent: US 8,804,513 B2
• Time in Patent Office: Days
• US Class Current: 370/230
• CPC Class Codes: H04L 47/193 at the transport layer, e.g. TCP related
• CPC Class Codes: H04L 47/26 using explicit feedback to the source, e.g. choke packets
• CPC Class Codes: H04L 47/267 sent by the destination endpoint network streaming of media packets with control of the source by the destination H04L65/613
• CPC Class Codes: H04L 47/27 Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets
• CPC Class Codes: H04L 47/30 in combination with information about buffer occupancy at either end or at transit nodes
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/80 Responding to QoS

Abstract

Techniques for controlling Session Initiation Protocol (SIP) overload between a sending entity and a receiving entity includes receiving a message at a send buffer at the sending entity and forwarding the message to a receive buffer at the receiving entity if the send buffer is empty of other messages or rejecting the message if the send buffer is not empty of other messages.

Claims

1. A method for controlling Session Initiation Protocol (SIP) overload between a sending entity and a receiving entity comprising:

receiving a message at a send buffer at the sending entity; and

forwarding the message to a receive buffer at the receiving entity if the send buffer is empty of other messages or rejecting the message if the send buffer is not empty of other messages.

2. The method of claim 1, wherein the message is an INVITE message.

3. The method of claim 1, wherein the message is formatted in accordance with TCP.

4. The method of claim 1, wherein the sending entity is a proxy server.

5. The method of claim 1, wherein the receiving entity is a proxy server.

6. The method of claim 1, wherein rejecting the message comprises sending a rejection message.

7. The method of claim 1, further comprising setting the receive buffer size to a size that holds about two or less INVITE messages.

8. The method of claim 1, further comprising setting the receive buffer size to about 2 KB.

9. The method of claim 1, further comprising setting an application buffer size of the receiving entity to a size that holds about two or less INVITE messages.

10. The method of claim 1, further comprising setting an application buffer size of the receiving entity to a size of about 2 KB.

11. The method of claim 1, further comprising receiving the message at the receive buffer of the receiving entity from the send buffer of the sending entity.

12. The method of claim 11, further comprising sending the message from the receive buffer to an application buffer of the receiving entity.

13. The method of claim 12, further comprising receiving the message at the application buffer at the receiving entity.

14. The method of claim 1, wherein the message comprises an INVITE or a non-INVITE message,

wherein if the message is an INVITE, the forwarding comprises forwarding the INVITE to the receive buffer at the receiving entity if the send buffer is empty of other messages or rejecting the INVITE if the send buffer is not empty of other messages, and

wherein if the message is a non-INVITE message, the forwarding comprises forwarding the message to a receive buffer at the receiving entity.

15. A method for controlling Session Initiation Protocol (SIP) overload between a sending entity and a receiving entity comprising:

receiving a message at a send buffer at the sending entity; and

forwarding the message to a receive buffer at the receiving entity if the send buffer does not indicate an overload condition or rejecting the message if the send buffer indicates an overload condition.

16. The method of claim 15, wherein the send buffer indicates an overload condition if the send buffer is not empty of other messages.

17. A system for controlling Session Initiation Protocol (SIP) overload between a sending entity and a receiving entity comprising:

a send buffer for receiving a message at the sending entity; and

a processor, coupled to the send buffer, wherein the processor is adapted to, in response to receiving the message, cause the send buffer to forward the message to a receive buffer at the receiving entity if the send buffer is empty of other messages or rejects the message if the send buffer is not empty of other messages.

18. The system of claim 17, wherein the message is an INVITE message.

19. The system of claim 17, wherein the message is formatted in accordance with TCP.

20. The system of claim 17, wherein the receive buffer has a size that holds about two or less INVITE messages.