ROUTING PATH OPTIMIZATION BETWEEN SIP ENDPOINTS

• US 20070253418A1
• Filed: 04/26/2007
• Published: 11/01/2007
• Est. Priority Date: 04/27/2006
• Status: Abandoned Application

• Current Assignee: DSP Group Ltd. (Synaptics Incorporated)
• Original Assignee: DSP Group Ltd. (Synaptics Incorporated)
• Inventors: SHIRI, Effi, ZMORA, Neta
• Application Number:
  US11/740,621
• Publication Number:
  US 20070253418A1
• Time in Patent Office: Days
• US Class Current: 370/392
• CPC Class Codes: H04L 61/2514 between local and global IP addresses
• CPC Class Codes: H04L 61/2564 for a higher-layer protocol, e.g. for session initiation protocol [SIP]
• 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 61/2578 without involvement of the NAT server
• 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]
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066

Abstract

Methods and systems for optimized routing of real time media session data between session initiation protocol SIP endpoints. In one embodiment of the invention, first and second SIP endpoints each provide notification of network address translation NAT topology thereof and based on the NAT topologies of the two endpoints an SIP server decides whether to route media between the two endpoints via a direct path or via a media relay.

Claims

1. A method for optimally routing media between Session Initiation Protocol (SIP) endpoints, comprising:

during setup of a session between a first and a second SIP endpoints, retrieving a Network Address Translator (NAT) topology associated with said first SIP endpoint and a NAT topology associated with said second SIP endpoint, wherein an indication of said first associated topology and an indication of said second associated NAT topology had been previously provided by said first and second SIP endpoints respectively; and

if a combination of said NAT topology associated with said first endpoint and said NAT topology associated with said second endpoint corresponds to a direct media path, deciding that media will be directly routed between said first and second SIP endpoints during said session.

2. The method of claim 1, wherein at least one of said indications was provided in an SIP Register message.

3. The method of claim 1, wherein said NAT topology associated with said first endpoint and said NAT topology associated with said second endpoint are each from a group comprising:

full cone NAT, address restricted NAT, port restricted NAT, symmetric NAT, and no NAT.

4. The method of claim 1, further comprising:

if said combination corresponds to a relayed media path, deciding that media will be routed between said first and second endpoints via a media relay during said session.

5. The method of claim 1, wherein said combination corresponding to a direct media path includes any a combination which is not included in a group comprising:

symmetric NAT associated with each of said first and second SIP endpoints; and

symmetric NAT associated with one of said first and second SIP endpoint combined with port restricted NAT associated with the other of said first and second SIP endpoints.

6. The method of claim 1, wherein said plurality of combinations corresponding to a direct media path includes a combination where one of said first and second SIP endpoints is associated with a symmetric NAT and the other of said first and second SIP endpoints is associated with a NAT topology from a group comprising:

address restricted NAT, full cone NAT, and no NAT.

7. The method of claim 1, further comprising:

receiving an Invite message from one of said first or second endpoint which invites the other of said first or second endpoint; and

if said combination corresponds to a direct media path, sending said Invite message to said other endpoint;

otherwise, if said combination corresponds to a relayed media path, sending said Invite message to a media relay.

15. The method of claim 1, further comprising:

said endpoint providing an indication not to use said address and port number included in said SDP for routing media to said endpoint.

16. The method of claim 15, further comprising:

said SIP server forwarding said message to said another endpoint or to said media relay depending on said NAT topologies of said endpoint and said another endpoint;

said another endpoint or said media relay recognizing said indication not to use said address and port number included in said SDP for routing media to said endpoint but to extract an address and port number for routing media to said endpoint from a media packet received from said endpoint.

8. A method for allowing optimal routing of media between Session Initiation Protocol (SIP) endpoints, comprising:

an SIP endpoint determining a Network Address Translator (NAT) topology associated with said endpoint; and

said SIP endpoint providing an indication of said NAT topology in order to allow an SIP server during a setup of a subsequent session between said endpoint and another endpoint to decide based on said indicated NAT topology and a NAT topology associated with and indicated by said another endpoint whether to route media between said endpoint and said another endpoint directly or via a media relay.

9. The method of claim 8, wherein said SIP endpoint determines said associated NAT topology by sending at least one Simple Traversal of User Datagram Protocol through NATs (STUN) binding request and evaluating at least one response or non-response to said sent at least one binding request.

10. The method of claim 8, wherein said indication is provided in an SIP message.

11. The method of claim 10, wherein said SIP message is a Register message.

12. The method of claim 10, wherein said indication is concatenated to a header in said message.

13. The method of claim 8, further comprising:

said endpoint sending a STUN binding request via a port intended for outgoing media and receiving a response including a mapped address attribute;

said endpoint inserting an address and port number from said mapped address attribute in a session description protocol (SDP) of a message intended for said another endpoint.

14. The method of claim 13, wherein said message is selected from a group comprising:

Invite message and 180 Ringing message.

17. The method of claim 8, further comprising:

said endpoint receiving a message and recognizing an indication in said message not to use an address and port number included in an SDP of said message for routing media to another endpoint but to extract an address and port number for routing media to said another endpoint from a media packet received from said another endpoint; and

said endpoint determining based on a NAT topology of said endpoint whether or not to initially send media to said address and port number included in said SDP in order to create a NAT binding for said endpoint.

18. The method of claim 8, wherein said NAT topology associated with said endpoint and said NAT topology associated with said another endpoint are each from a group comprising:

full cone NAT, address restricted NAT, port restricted NAT, symmetric NAT, and no NAT.

19. A system for optimally routing media between Session Initiation Protocol (SIP) endpoints, comprising:

a database configured to store associations between Network Address Translator (NAT) topologies and SIP endpoints, based on notifications received from associated endpoints; and

an SIP server configured to access stored NAT topologies of endpoints participating in a session and to select, based on said accessed NAT topologies, a direct media path or a relayed media path between said participating endpoints.

20. The system of claim 19, including:

means for receiving notifications from endpoints relating to associated NAT topologies and to save associations between notifying endpoints and notified NAT topologies in said database.

21. The system of claim 20, wherein said means includes a registrar and said notifications are included in Register messages sent by associated endpoints.

22. The system of claim 20, wherein said means includes said SIP server and said notifications are included in SIP messages sent by associated endpoints.

23. An SIP endpoint, comprising:

means for determining a Network Address Translator (NAT) topology associated with said endpoint; and

means for providing an indication of said NAT topology in order to allow an SIP server during a setup of a subsequent session between said endpoint and another endpoint to decide based on said indicated NAT topology and a NAT topology associated with and indicated by said another endpoint whether to route media between said endpoint and said another endpoint directly or via a media relay.

24. The endpoint of claim 23, wherein said means for providing an indication includes means for including an indication of said NAT topology in a transmitted SIP message.

25. The endpoint of claim 23, wherein said means for determining includes means for sending Simple Traversal of User Datagram Protocol through NATs (STUN) binding requests and evaluating responses or non-response to said sent binding requests.

26. A network for optimally routing media between Session Initiation Protocol (SIP) endpoints, comprising:

at least one Simple Traversal of User Datagram Protocol through NAT'"'"'s (STUN) server;

at least two SIP endpoints, each configured to use said at least one STUN server to discover a NAT topology associated with said endpoint;

a database configured to store NAT topologies discovered by said at least two endpoints; and

an SIP server configured to access stored NAT topologies associated with endpoints participating in a session and to select, based on said accessed NAT topologies, a direct media path or a relayed media path between said participating endpoints.

27. The network of claim 26, further comprising:

a media relay configured to relay media between said participating endpoints, if a relayed media path was selected.

28. The network of claim 27, wherein said SIP server and said media relay are comprised in a session border controller (SBC).

29. The network of claim 26, further comprising:

a registrar configured to receive registrar messages from SIP endpoints indicating said discovered NAT topologies.

30. The network of claim 26, further comprising:

at least one NAT hiding at least one of said endpoints.

31. The network of claim 26, wherein said network includes an Internet telephony service provider network which provides voice over internet protocol (VoIP) services.