Refreshing a session initiation protocol (SIP) session

• US 20080086566A1
• Filed: 10/10/2006
• Published: 04/10/2008
• 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: Kumarasamy, Parameswaran, Parameswaran, Kavithadevi, Bangalore, Manjunath
• Granted Patent: US 8,036,215 B2
• Time in Patent Office: Days
• US Class Current: 709/227
• 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 information needed for a refresh message, the refresh message useable for a refresh and another purpose, wherein the information used for the refresh is less than the information used for the other purpose;

generating the refresh message to initiate a refresh of a session at a refreshee;

sending a refresh message to the refreshee, wherein the refresh message is used for requesting the session refresh;

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

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

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 a negotiation message to the refreshee indicating the refresh method is supported; and

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

6. A method comprising:

receiving a first message for a session from a refresher;

determining if the message is for a refresh or for another purpose;

if the first message is for a refresh, performing the following;

parsing the first message to determine the session to refresh, wherein the first message useable for a refresh and another purpose, wherein the information used for the refresh is less than the information used for the other purpose;

generating a second message in a response to the first message; and

sending the second message, the second message indicating a result of the refresh performed for the session.

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 processors; and

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

determine information needed for a refresh message, the refresh message useable for a refresh and another purpose, wherein the information used for the refresh is less than the information used for the other purpose;

generate the refresh message to initiate a refresh of a session at a refreshes;

send a refresh message to the refreshee, wherein the refresh message is used for requesting the session refresh;

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.

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;

receive a first message for a session from a refresher;

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

if the first message is for a refresh, the logic when executed is operable to;

parse the first message to determine the session to refresh, wherein the first message useable for a refresh and another purpose, wherein the information used for the refresh is less than the information used for the other purpose;

generate a second message in a response to the first message; and

send the second message, the second message indicating a result of the refresh performed for the session.

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 refresher configured to;

determine information needed for a refresh message, the refresh message useable for a refresh and another purpose, wherein the information used for the refresh is less than the information used for the other purpose;

generate the refresh message to initiate a refresh of a session; and

send a refresh message, wherein the refresh message is used for requesting the session refresh; and

a refreshee configured to;

receive the refresh message for the session from the refresher;

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

if the refresh message is for a refresh, the refresher configured to;

parse the first message to determine the session to refresh;

generate a response message in a response to the first message; and

send the response message, the response message indicating a result of the refresh performed for the session.

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;