Universal port user agent capable of caching route information among sessions and associated method

• US 20060146795A1
• Filed: 12/31/2004
• Published: 07/06/2006
• Est. Priority Date: 12/31/2004
• Status: Abandoned Application

• Current Assignee: UTStarcom Incorporated (UTStarcom Holdings Corp.)
• Original Assignee: UTStarcom Incorporated (UTStarcom Holdings Corp.)
• Inventors: Puthupparambil, Devarajan S., Joseph, Gigo K.
• Application Number:
  US11/027,316
• Publication Number:
  US 20060146795A1
• Time in Patent Office: Days
• US Class Current: 370/352
• CPC Class Codes: H04L 65/103 in the network
• CPC Class Codes: H04L 65/104 in the network
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]

Abstract

An initial call is setup by a universal port user agent by sending an invitation to the proxy server. The proxy server performs a directory lookup from a back end server to obtain route information to a destination. The route information is passed to the universal port user agent in response and is stored in the universal port user agent. When subsequent calls to the same destination are requested, the subsequent calls can be setup using the stored route information. A universal port user agent performs these call setups. The route information memory is managed based on a number of routes stored and the age of the stored routes. In certain embodiments the calls are setup using the Session Initiation Protocol (SIP).

Claims

1. A method of setting up sessions comprising the steps of:

(a) storing route information for a first session to a destination; and

(b) setting up a second session to the same destination using the stored route information.

2. A method according to claim 1, wherein said step (a) of storing route information for a session to a destination comprises the substeps of (a1) performing a directory lookup to determine a route to the destination and (a2) retaining the route for subsequent sessions.

3. A method according to claim 2, wherein said step (a1) of performing a directory lookup performs the directory lookup from a back end server.

4. A method according to claim 1, wherein said step (a) of storing route information retains the route so long as an ok is received from the destination.

5. A method according to claim 1, wherein said step (a) of storing route information also stores the time of the first session.

6. A method according to claim 1, wherein said step (a) of storing route information also stores the address of the destination.

7. A method according to claim 6, wherein said step (a) of storing the route information for the destination stores a DNIS of the destination.

8. A method according to claim 1, further comprising the step of (c) comparing a current condition against a stored past condition associated with the route information to determine whether to continue storing the route information.

9. A method according to claim 8, wherein said step (c) of comparing compares a current time against a stored time of the first session.

10. A method according to claim 8, wherein said step (c) of comparing compares a current count against a stored time of the first session.

11. A method according to claim 1,

wherein said step (a) of storing route information for a session to a destination increments a counter for each stored route;

and

wherein the method further comprises a step of (c) comparing the counter to a maximum number to determine whether to continue storing the route information.

12. A method according to claim 1, wherein said step (a) of storing route information stores the route information in a user agent.

13. A method according to claim 1, wherein the sessions in steps (a) and (b) are implemented in SIP.

14. A method according to claim 1, wherein said step (a) of storing route information stores the route information in a universal port user agent.

15. A method according to claim 1, further comprising the step of (c) When a server is unwilling to use a route of the route information for setup of a subsequent session to a same destination, the server still optimizes its own route query by using the time in the stored route information.

16. A method in a universal port user agent of setting up sessions comprising the steps of:

(a) for a session to a destination, storing route information obtained for the destination; and

(b) setting up a subsequent session to the same destination by using the stored route information.

17. A method according to claim 16, wherein said step (a) of storing route information stores the route information in the universal port user agent.

18. A method according to claim 16, further comprising the step of (c) when a proxy server is unwilling to use a route of the route information for setup of a subsequent session to a same destination, the proxy server still optimizes its own route query by using the time in the stored route information.

19. A method according to claim 16, wherein the sessions in steps (a) and (b) are implemented in SIP.

20. A universal port user agent for enabling setup of sessions, comprising a processor and communication ports to initially connect with a destination phone and store route information and to again connect with the same destination phone using the stored route information.