Techniques for reducing session set-up for real-time communications over a network

• US 20070078986A1
• Filed: 09/13/2005
• Published: 04/05/2007
• Est. Priority Date: 09/13/2005
• Status: Abandoned Application

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Ethier, Randall, Hammer, Michael
• Application Number:
  US11/224,817
• Publication Number:
  US 20070078986A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 41/5003 Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 41/5022 by giving priorities, e.g. assigning classes of service
• CPC Class Codes: H04L 41/5087 wherein the managed service relates to voice services management of VoIP services H04M7/0081
• CPC Class Codes: H04L 41/509 wherein the managed service relates to media content delivery, e.g. audio, video or TV
• CPC Class Codes: H04L 61/2575 using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/612 for unicast
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities

Abstract

Techniques for reducing session set up for real-time communications over a network include determining whether conditions are satisfied for storing session data for a first actual or prospective session and receiving the session data to be stored. The session data indicates multiple properties for real-time communications between a local node and a remote end node connected to a network. If these conditions are satisfied, then the session data is stored. If it is determined that a second session is to be established between the local node and the remote end node, then multiple properties of the second session are determined based on the stored session data. The second session is established using the stored session data instead of at least some negotiations. These techniques reduce the perceived delay from start of setup to commencement of real-time communications, or reduce the resources consumed by the end nodes and network, or both.

Claims

1. A method for reducing session set up for real-time communications over a network, comprising the steps of:

receiving at a local end node session specific data that indicates multiple properties of a first session for real-time communications between the local end node and a remote end node connected to a network;

determining at the local end node whether conditions are satisfied for storing the session specific data; and

if it is determined that conditions are satisfied for storing the session specific data, then;

storing the session specific data;

after storing the session specific data, determining at the local end node whether a second session is to be established between the local end node and the remote end node; and

if it is determined that the second session is to be established, then

determining at the local end node multiple properties of the second session based on the session specific data, and

establishing the second session using the multiple properties of the second session instead of additional traffic over the network to negotiate the multiple properties of the second session.

2. A method as recited in claim 1 wherein the multiple properties include at least one of:

a communication media type supported at the remote end node, selected from a plurality of media types that include voice, video, instant message, text message, application data for each application of a set of one or more applications, and any combination of media types;

a security attribute for a session with the remote end node; and

a quality of network service required for a session with the remote end node using the communication media type.

3. A method as recited in claim 1 wherein the multiple properties include at least one of:

calling party preference data that indicates at least one of a device and network address for a calling party who initiates the second session;

called party preference data that indicates at least one of a device and network address for a calling party who is an invitee to the second session; and

preconditions data that indicates a network resource that should be available to support the second session.

4. A method as recited in claim 1 wherein the multiple properties include at least one of:

firewall transversal data that indicates how to establish the second session with the remote end node behind a firewall process that blocks some network traffic;

NAT traversal data that indicates how to establish the second session with a remote end node when a network address translation (NAT) process operates between the local end node and the remote end node; and

name resolution data that indicates a network address of the remote end node based on a name associated with the remote end node, such as provided by a domain name server (DNS) or an ENUM server.

5. A method as recited in claim 4, said step of receiving session specific data further comprising receiving the name resolution data from one of:

a domain name server (DNS); and

an ENUM server.

6. A method as recited in claim 1 wherein the multiple properties include at least one of:

a MIME type data that indicates a Multipurpose Internet Mail Extensions (MIME) type supported by the remote end node;

event type data that indicates a type of event that sends a notify message which event is supported by the remote end node;

DTMF type data that indicates a method for transporting Dual Tone Multi-Frequency (DTMF) tones during the second session; and

protocol options data that indicates options for a session setup protocol used during the second session.

7. A method as recited in claim 6 wherein the protocol options data that indicates options for a session setup protocol indicates for the Session Initiation Protocol (SIP) at least one of:

an Allow message type;

a Require protocol option; and

a Supported protocol option.

8. A method as recited in claim 1, wherein said step of storing the session specific data further comprises determining a unique identifier for real-time communications with the remote end node, and

storing the unique identifier in association with the session specific data;

and

said step of establishing the second session further comprises communicating with the remote end node a message that includes the unique identifier.

9. A method as recited in claim 8, said step of determining a unique identifier for the remote end node further comprising determining a unique identifier for the remote end node and a first media type for real-time communication between the local end node and the remote end node.

10. A method as recited in claim 1, wherein:

said step of determining whether conditions are satisfied for storing the session specific data further comprises determining that a remote user of a particular plurality of remote users is present on the network;

said step of receiving session specific data further comprises exchanging network traffic to determine the multiple properties of the first session for real-time communications with the remote end node where the remote user is present, whereby the first session is a prospective session; and

said step of determining whether a second session is to be established further comprises receiving data that indicates an actual session with the remote user is being established, whereby the second session is an actual session.

11. A method as recited in claim 10, said step of exchanging network traffic to determine the multiple properties of the first session further comprising exchanging network traffic at a lower priority than traffic to establish an actual session.

12. A method as recited in claim 10, wherein

said step of storing the session specific data further comprises

determining a unique identifier for real-time communications with the remote end node, and

storing the unique identifier in association with the session specific data;

and

said step of establishing the second session further comprises communicating with the remote end node a message that includes the unique identifier.

13. A method as recited in claim 12, said step of exchanging network traffic to determine the multiple properties of the first session further comprising communicating with the remote end node a message that includes the unique identifier.

14. A method as recited in claim 10, said step of exchanging network traffic for the prospective session further comprising:

determining whether conditions are satisfied for exchanging network traffic for the prospective session; and

if it is determined that conditions are not satisfied for exchanging network traffic for the prospective session, then suspending said step of exchanging network traffic for the prospective session.

15. A method as recited in claim 14, wherein conditions for exchanging network traffic include at least one of:

sufficient resources at local end node for exchanging network traffic for the prospective session;

sufficient resources at remote end node for exchanging network traffic for the prospective session; and

sufficient resources on network for exchanging network traffic for the prospective session.

16. A method as recited in claim 14, wherein conditions for exchanging network traffic include at least one of:

a random time has expired since the local end node has begun communications over the network, to avoid collisions with network traffic for prospective sessions initiated by other network end nodes; and

the current time is not within a predetermined blackout period when prospective sessions are barred by network policy.

17. A method as recited in claim 1, wherein:

the first session is an actual session established between the local end node and the remote end node;

the second session is different from and subsequent to the first session; and

said step of receiving session specific data further comprises receiving data that indicates multiple properties already negotiated for the first session for real-time communications with the remote end node.

18. A method as recited in claim 17, said step of determining whether conditions are satisfied for storing the session specific data further comprises determining that a session start time between requesting the first session and beginning real-time communications exceeds a threshold time.

19. A method as recited in claim 17, wherein

said step of storing the session specific data further comprises

determining a unique identifier for real-time communications with the remote end node, and

storing the unique identifier in association with the session specific data;

and

said step of establishing the second session further comprises communicating with the remote end node a message that includes the unique identifier.

20. A method as recited in claim 19, further comprising the step of communicating with the remote end node a message that includes the unique identifier.

21. A method as recited in claim 1, further comprising:

determining whether conditions are satisfied for deleting the session specific data from storage; and

if it is determined that conditions are satisfied for deleting the session specific data from storage, then deleting the session specific data from storage.

22. A method as recited in claim 21, wherein conditions for deleting the session specific data include at least one of:

a number of different, more recent sessions with stored session specific data equals a particular maximum number of different sessions; and

a time when the session specific data was stored exceeds a particular age.

23. A method as recited in claim 21, wherein conditions for deleting the session specific data include at least one of:

a remote user associated with the remote end node in the session data is not present on the network;

the remote user is removed from a plurality of remote users for whom session data is stored; and

the remote user is no longer associated with the remote end node.

24. A method as recited in claim 21, wherein conditions for deleting the session specific data include at least one of:

the remote end node refuses any of the multiple properties of the second session; and

the local end node that was connected to the network at a particular access point for the stored session specific data is now connected to the network at a different access point.

25. A method as recited in claim 1, said step of receiving session specific data further comprising receiving shared session data that indicates one or more properties for real-time communications between the local end node and any end node of a plurality of remote end nodes.

26. An apparatus for reducing session set up for real-time communications over a network, comprising:

means for receiving at a local end node session specific data that indicates multiple properties of a first session for real-time communications between the local end node and a remote end node connected to a network;

means for determining at the local end node whether conditions are satisfied for storing the session specific data;

means for storing the session specific data and determining at the local end node whether a second session is to be established, if it is determined that conditions are satisfied for storing the session specific data;

means for determining at the local end node multiple properties of the second session based on the session specific data and establishing the second session between the local end node and the remote end node using the multiple properties of the second session instead of additional traffic over the network to negotiate the multiple properties of the second session, if it is determined that the second session is to be established.

27. An apparatus for reducing session set up for real-time communications over a network, comprising:

a network interface that is coupled to a network for communicating one or more packet flows therewith;

one or more processors;

a computer-readable medium; and

one or more sequences of instructions held by the computer-readable medium which instructions, when executed by the one or more processors, causes the one or more processors to carry out the steps of;

receiving session specific data that indicates multiple properties of a first session for real-time communications between the apparatus and a remote end node connected to a network;

determining whether conditions are satisfied for storing the session specific data; and

if it is determined that conditions are satisfied for storing the session specific data, then;

storing the session specific data;

after storing the session specific data, determining whether a second session is to be established between the apparatus and the remote end node; and

if it is determined that the second session is to be established, then

determining multiple properties of the second session based on the session specific data, and

establishing the second session using the multiple properties of the second session instead of additional traffic over the network to negotiate the multiple properties of the second session.

28. An apparatus as recited in claim 27 wherein the multiple properties include at least one of:

a communication media type supported at the remote end node, selected from a plurality of media types that include voice, video, instant message, text message, application data for each application of a set of one or more applications, and any combination of media types;

a security attribute for a session with the remote end node; and

a quality of network service required for a session with the remote end node using the communication media type.

29. An apparatus as recited in claim 27 wherein the multiple properties include at least one of:

calling party preference data that indicates at least one of a device and network address for a calling party who initiates the second session;

called party preference data that indicates at least one of a device and network address for a calling party who is an invitee to the second session; and

preconditions data that indicates a network resource that should be available to support the second session.

30. An apparatus as recited in claim 27 wherein the multiple properties include at least one of:

firewall transversal data that indicates how to establish the second session with the remote end node behind a firewall process that blocks some network traffic;

NAT traversal data that indicates how to establish the second session with a remote end node when a network address translation (NAT) process operates between the local end node and the remote end node; and

name resolution data that indicates a network address of the remote end node based on a name associated with the remote end node, such as provided by a domain name server (DNS) or an ENUM server.

31. An apparatus as recited in claim 30, said step of receiving session specific data further comprising receiving the name resolution data from one of:

a domain name server (DNS); and

an ENUM server.

32. An apparatus as recited in claim 27 wherein the multiple properties include at least one of:

a MIME type data that indicates a Multipurpose Internet Mail Extensions (MIME) type supported by the remote end node;

event type data that indicates a type of event that sends a notify message which event is supported by the remote end node;

DTMF type data that indicates a method for transporting Dual Tone Multi-Frequency (DTMF) tones during the second session; and

protocol options data that indicates options for a session setup protocol used during the second session.

33. An apparatus as recited in claim 32 wherein the protocol options data that indicates options for a session setup protocol indicates for the Session Initiation Protocol (SIP) at least one of:

an Allow message type;

a Require protocol option; and

a Supported protocol option.

34. An apparatus as recited in claim 27, wherein

said step of storing the session specific data further comprises

determining a unique identifier for real-time communications with the remote end node, and

storing the unique identifier in association with the session specific data;

and

said step of establishing the second session further comprises communicating with the remote end node a message that includes the unique identifier.

35. An apparatus as recited in claim 34, said step of determining a unique identifier for the remote end node further comprising determining a unique identifier for the remote end node and a first media type for real-time communication between the apparatus and the remote end node.

36. An apparatus as recited in claim 27, wherein:

said step of determining whether conditions are satisfied for storing the session specific data further comprises determining that a remote user of a particular plurality of remote users is present on the network;

said step of receiving session specific data further comprises exchanging network traffic to determine the multiple properties of the first session for real-time communications with the remote end node where the remote user is present, whereby the first session is a prospective session; and

said step of determining whether a second session is to be established further comprises receiving data that indicates an actual session with the remote user is being established, whereby the second session is an actual session.

37. A method as recited in claim 36, said step of exchanging network traffic to determine the multiple properties of the first session further comprising exchanging network traffic at a lower priority than traffic to establish an actual session.

38. An apparatus as recited in claim 36, wherein

said step of storing the session specific data further comprises

determining a unique identifier for real-time communications with the remote end node, and

storing the unique identifier in association with the session specific data;

and

said step of establishing the second session further comprises communicating with the remote end node a message that includes the unique identifier.

39. An apparatus as recited in claim 38, said step of exchanging network traffic to determine the multiple properties of the first session further comprising communicating with the remote end node a message that includes the unique identifier.

40. An apparatus as recited in claim 36, said step of exchanging network traffic for the prospective session further comprising:

determining whether conditions are satisfied for exchanging network traffic for the prospective session; and

if it is determined that conditions are not satisfied for exchanging network traffic for the prospective session, then suspending said step of exchanging network traffic for the prospective session.

41. An apparatus as recited in claim 40, wherein conditions for exchanging network traffic include at least one of:

sufficient resources at the apparatus for exchanging network traffic for the prospective session;

sufficient resources at remote end node for exchanging network traffic for the prospective session; and

sufficient resources on network for exchanging network traffic for the prospective session.

42. An apparatus as recited in claim 40, wherein conditions for exchanging network traffic include at least one of:

a random time has expired since the apparatus has begun communications over the network, to avoid collisions with network traffic for prospective sessions initiated by other network end nodes; and

the current time is not within a predetermined blackout period when prospective sessions are barred by network policy.

43. An apparatus as recited in claim 27, wherein:

the first session is an actual session established between the apparatus and the remote end node;

the second session is different from and subsequent to the first session; and

said step of receiving session specific data further comprises receiving data that indicates multiple properties already negotiated for the first session for real-time communications with the remote end node.

44. An apparatus as recited in claim 43, said step of determining whether conditions are satisfied for storing the session specific data further comprises determining that a session start time between requesting the first session and beginning real-time communications exceeds a threshold time.

45. An apparatus as recited in claim 43, wherein

said step of storing the session specific data further comprises

determining a unique identifier for real-time communications with the remote end node, and

storing the unique identifier in association with the session specific data;

and

said step of establishing the second session further comprises communicating with the remote end node a message that includes the unique identifier.

46. An apparatus as recited in claim 45, said one or more sequences of instructions further causing the one or more processors to carry out the step of communicating with the remote end node a message that includes the unique identifier.

47. An apparatus as recited in claim 27, said one or more sequences of instructions further causing the one or more processors to carry out the steps of:

determining whether conditions are satisfied for deleting the session specific data from storage;

if it is determined that conditions are satisfied for deleting the session specific data from storage, then deleting the session specific data from storage.

48. An apparatus as recited in claim 47, wherein conditions for deleting the session specific data include at least one of:

a number of different, more recent sessions with stored session specific data equals a particular maximum number of different sessions; and

a time when the session specific data was stored exceeds a particular age.

49. An apparatus as recited in claim 47, wherein conditions for deleting the session specific data include at least one of:

a remote user associated with the remote end node in the session data is not present on the network;

the remote user is removed from a plurality of remote users for whom session data is stored; and

the remote user is no longer associated with the remote end node.

50. An apparatus as recited in claim 47, wherein conditions for deleting the session specific data include at least one of:

the remote end node refuses any of the multiple properties of the second session; and

the apparatus that was connected to the network at a particular access point for the stored session specific data is now connected to the network at a different access point.

51. An apparatus as recited in claim 27, said step of receiving session specific data further comprising receiving shared session data that indicates one or more properties for real-time communications between the apparatus and any end node of a plurality of remote end nodes.

52. A computer-readable medium carrying one or more sequences of instructions for reducing session set up for real-time communications over a network, wherein execution of the one or more sequences of instructions by one or more processors causes the one or more processors to perform the steps of:

receiving session specific data that indicates multiple properties of a first session for real-time communications between a processor of the one or more processors and a remote end node connected to a network;

determining whether conditions are satisfied for storing the session specific data; and

if it is determined that conditions are satisfied for storing the session specific data, then;

storing the session specific data;

after storing the session specific data, determining whether a second session is to be established between the processor and the remote end node; and

if it is determined that the second session is to be established, then

determining multiple properties of the second session based on the session specific data, and

establishing the second session using the multiple properties of the second session instead of additional traffic over the network to negotiate the multiple properties of the second session.