Refreshing a session initiation protocol (SIP) session

• US 8,036,215 B2
• Filed: 10/10/2006
• Issued: 10/11/2011
• Est. Priority Date: 10/10/2006
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Bangalore, Manjunath, Kumarasamy, Parameswaran, Parameswaran, Kavithadevi
• Primary Examiner(s): Ton; Dang T
• Assistant Examiner(s): Kaur; Pamit
• Application Number:
  US11/545,208
• Publication Number:
  US 20080086566A1
• Time in Patent Office: 1,827 Days
• Field of Search: 370/395, 370/389, 370/352
• US Class Current: 370/389
• CPC Class Codes: H04L 65/1083 In-session procedures
• CPC Class Codes: H04L 65/1094 Inter-user-equipment sessions transfer or sharing
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/145 avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session

Abstract

In one embodiment, a session is refreshed using a message that is simplified for refresh purposes. The refresh message that is used is a message used for another purpose in a protocol (e.g., SIP). For example, a reINVITE message may be used as a refresh message. If the reINVITE message is used for its intended purpose, the reINVITE message may be used to change the characteristics of a session. This reINVITE message includes an SDP and full header such that the parameters can be properly changed. However, the reINVITE message may be used to refresh a session. This may be referred to as a simple refresh message. But, the simple refresh message does not include an SDP or any other message body. The simple refresh message includes only a reduced header. This reduces time spent building and parsing the simple refresh message.

Claims

1. A method comprising:

determining, during establishment of a SIP (Session Initiation Protocol) session between a first device and a second device, whether a refresh mechanism is supported, by including additional information with existing protocol messages that are used to establish a SIP session;

generating, at the first device, a first new protocol message to initiate a refresh of a session with the second device, where the first new protocol message is a modified version of an existing protocol message that is used for purposes other than a refresh;

sending, from the first device, the first new protocol message to the second device, where the first new protocol message includes information indicating that a refresh of the session is requested; and

determining, at the first device and based on receiving a second new protocol message from the second device in response to the first new protocol message and reading the contents of the second new protocol message, if the session between the first device and the second device is active or inactive.

2. The method of claim 1, wherein the refresh message includes a reduced header that includes fewer fields than if the refresh message is used for the other purpose.

3. The method of claim 1, wherein the refresh message does not include a body.

4. The method of claim 1, wherein the response message is a first type of message if the session is active and a second type of message if the session is inactive.

5. The method of claim 1, further comprising:

sending, during establishment of the SIP session, a first support indication to the refreshee indicating the refresh method is supported, wherein the first support indication is contained in a request message that is used to establish the SIP session; and

receiving a second support indication from the refreshee indicating whether the refreshee supports the refresh method, wherein the second support indication is contained in a response message that is used to respond to the request message to establish the SIP session.

6. A method comprising:

determining, during establishment of a SIP (Session Initiation Protocol) session between a first device and a second device, whether a refresh mechanism is supported, by including additional information with existing protocol messages that are used to establish a SIP session;

receiving, at the second device, a first new protocol message for a session from the first device, where the first new protocol message is a modified version of an existing protocol message that is used for purposes other than a refresh;

determining, at the second device, if the first new protocol message is for a refresh or for another purpose other than a refresh;

if the determination indicates that the first new protocol message is for a refresh, performing the following at the second device;

parsing the first new protocol message to determine an identification of a session to refresh;

examining, based on the identification, whether the session is active or inactive;

generating a second new protocol message in a response to the first new protocol message, where the second new protocol message includes information on the result of the examination and the second new protocol message is a modified version of an existing protocol message that is used for purposes other than a refresh; and

sending, using the second device, the second new protocol message to the first device, the second new protocol message indicating that it is in response to the first new protocol message.

7. The method of claim 6, wherein the message and/or the response message include fewer fields than if the first message is used for a purpose other than a refresh.

8. The method of claim 6, wherein the response message is a first type of message if the session is active and a second type of message if the session is inactive.

9. The method of claim 6, wherein the first message and/or second message do not include a body.

10. The method of claim 6, further comprising:

receiving a negotiation message from the refresher indicating the refresh method is supported; and

sending a response from the refreshee indicating whether the refresh method is supported.

11. The method of claim 6, wherein determining if the first message is a refresh message comprises determining if a refresh tag is included in the first message or determining if the refresh message is received at a predetermined time that a refresh should be performed.

12. An apparatus comprising:

one or more computer processors; and

logic encoded in one or more tangible media for execution by the one or more processors and when executed operable to;

determine, during establishment of a SIP (Session Initiation Protocol) session between the apparatus and a second device, whether a refresh mechanism is supported, by including additional information with existing protocol messages that are used to establish a SIP session;

generate, using the one or more computer processors, a first new protocol message to initiate a refresh of a session with the second device, where the first new protocol message is a modified version of an existing protocol message that is used for purposes other than a refresh;

send the first new protocol message to the second device, where the first new protocol message includes information indicating that a refresh of the session is requested; and

determine, using the one or more computer processors and based on receiving a second new protocol message from the second device in response to the first new protocol message and reading the contents of the second new protocol message, if the session between the apparatus and the second device is active or inactive.

13. The apparatus of claim 12, wherein the refresh message includes a reduced header that includes fewer fields than if the refresh message is used for the other purpose.

14. The apparatus of claim 12, wherein the refresh message does not include a body.

15. The apparatus of claim 12, wherein the response message is a first type of message if the session is active and a second type of message if the session is inactive.

16. The apparatus of claim 12, wherein the logic when executed is operable to:

send a negotiation message to the refreshee indicating the refresh method is supported; and

receive a response from the refreshee indicating whether the refreshee supports the refresh method.

17. An apparatus comprising:

one or more processors; and

logic encoded in one or more tangible media for execution by the one or more processors and when executed operable to;

determining, during establishment of a SIP (Session Initiation Protocol) session between a first device and the apparatus, whether a refresh mechanism is supported, by including additional information with existing protocol messages that are used to establish a SIP session;

receive, at the apparatus, a first new protocol message for a session from the first device, where the first new protocol message is a modified version of an existing protocol message that is used for purposes other than a refresh;

determine, using the one or more computer processors, if the first new protocol message is for a refresh or for another purpose other than a refresh;

if the determination indicates that the first new protocol message is for a refresh, the logic when executed is operable to;

parse the first new protocol message to determine an identification of a session to refresh;

examine, using the identification, whether the session is active or inactive;

generate a second new protocol message in a response to the first new protocol message, where the second new protocol message includes information on the result of the examination and the second new protocol message is a modified version of an existing protocol message that is used for purposes other than a refresh; and

send, using the one or more computer processors, the second new protocol message to the first device, the second new protocol message indicating that it is in response to the first new protocol message.

18. The apparatus of claim 17, wherein the message and/or the response message include fewer fields than if the first message is used for the other purpose.

19. The apparatus of claim 17, wherein the response message is a first type of message if the session is active and a second type of message if the session is inactive.

20. The apparatus of claim 17, wherein the first message and/or second message do not include a body.

21. The apparatus of claim 17, wherein the logic when executed is operable to:

receive a negotiation message from the refresher indicating the refresh method is supported; and

send a response from the refreshee indicating whether the refresh method is supported.

22. The apparatus of claim 17, wherein the logic when executed is operable to determine if the first message is a refresh message comprises the logic when executed is operable to determine if a refresh tag is included in the first message or determining if the refresh message is received at a predetermined time that a refresh should be performed.

23. A system comprising:

a first device configured to;

determine, during establishment of a SIP session with a second device, whether a refresh mechanism is supported, by including additional information with existing protocol messages that are used to establish a SIP session;

generate a first new protocol message to initiate a refresh of a session, where the first new protocol message is a modified version of an existing protocol message that is used for purposes other than a refresh; and

send the first new protocol message to the second device, where the first new protocol message includes information indicating that a refresh of the session is requested; and

a second device configured to;

determine, during establishment of a SIP session with a first device, whether a refresh mechanism is supported, by including additional information with existing protocol messages that are used to establish a SIP session;

receive a first new protocol message for a session from the the first device, where the first new protocol message is a modified version of an existing protocol message that is used for purposes other than a refresh;

determine if the first new protocol message is for a refresh or for another purpose;

if the determination indicates that the first new protocol message is for a refresh, parse the first new protocol message to determine an identification of a session to refresh;

examine, based on the identification, whether the session is active or inactive;

generate a second new protocol message in a response to the first new protocol message, where the second new protocol message includes information on the result of the examination and the second new protocol message is a modified version of an existing protocol message that is used for purposes other than a refresh; and

send the second new protocol message to the first device, the second new protocol message indicating that it is in response to the first new protocol message.

24. The system of claim 23, wherein the refresher is configured to:

receive a response message for the refresh that has been performed for the session; and

determine if the session is active or inactive based on the received response message.