System and method for establishing a session initiation protocol communication session with a mobile terminal

• US 20050201357A1
• Filed: 03/10/2004
• Published: 09/15/2005
• Est. Priority Date: 03/10/2004
• Status: Active Grant

• Current Assignee: Nokia Technologies Oy (Nokia Corporation)
• Original Assignee: Nokia Corporation
• Inventors: Poyhonen, Petteri
• Granted Patent: US 8,989,737 B2
• Time in Patent Office: Days
• US Class Current: 370/352
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 2101/65 Telephone numbers
• CPC Class Codes: H04L 61/106 across networks, e.g. mapping telephone numbers to data network addresses
• CPC Class Codes: H04L 61/2564 for a higher-layer protocol, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 61/2578 without involvement of the NAT server
• CPC Class Codes: H04L 63/029 Firewall traversal, e.g. tunnelling or, creating pinholes
• CPC Class Codes: H04L 65/1045 Proxies, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1073 Registration or de-registration
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04W 60/00 Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
• CPC Class Codes: H04W 76/12 Setup of transport tunnels
• CPC Class Codes: H04W 88/182 Network node acting on behalf of an other network entity, e.g. proxy

Abstract

A system is provided for establishing a communication session with a terminal (i.e., terminating SIP client). The system includes a network node (e.g., SIP proxy) located in a network across which an originating client is capable of communicating. The network node is capable of sending a trigger to the terminal independent of the network. The network node is also capable of receiving a registration message, in response to the trigger, from the terminal across the network. In this regard, the network node is capable of receiving the registration message to thereby identify the terminal across the network such that a communication session is capable of being established with the terminal based upon the identity of the terminal across the network.

Claims

1. A system for establishing a communication session with a terminal, the system comprising:

a network node located in a network across which an originating client is capable of communicating, wherein the network node is capable of receiving a connection request, and thereafter sending a trigger to the terminal independent of the location of the originating client, wherein the network node is also capable of receiving a registration message in response to the trigger to thereby register the terminal with the network node and identify the terminal across the network such that the communication session is capable of being established with the terminal based upon the identity of the terminal across the network.

2. A system according to claim 1, wherein the network node is capable of receiving the connection request from the originating client, and wherein the network node is capable of sending the connection request to the terminal after registering the terminal.

3. A system according to claim 2, wherein the network node is capable of sending the connection request to the terminal through at least one other network node.

4. A system according to claim 1, wherein the network node comprises a Session Initiation Protocol (SIP) proxy.

5. A system according to claim 1, wherein the network node is capable of receiving, and thereafter storing in a buffer, the connection request, and wherein the network node is capable of receiving the registration message and thereafter retrieving the connection request from the buffer, and sending the connection request to the terminal based upon the identity of the terminal across the network.

6. A system according to claim 1, wherein the network node is capable of receiving the registration message from the terminal via at least one of a network address translator (NAT) and a firewall (FW) located between the network node and the terminal, and wherein the network node is capable of sending the trigger in a manner independent of the at least one of the NAT and FW.

7. A system according to claim 1, wherein the network node is also capable of receiving a first registration message from the terminal before sending the trigger to thereby register the terminal with the network node, wherein the first registration message includes an identifier of the terminal independent of the network such that the network node is capable of sending the trigger based upon the identifier of the terminal independent of the network, and wherein the network node is capable of receiving a subsequent registration message in response to the trigger.

8. A system according to claim 1, wherein the network node is located in a network across which an originating client is capable of at least one of directly and indirectly communicating.

9. A system according to claim 8, wherein the network comprises one of a public network and private network.

10. A system of establishing a communication session with a terminal, the system comprising:

a network node located in a network across which an originating client is capable of communicating, wherein the SIP proxy is capable of receiving a registration message to thereby register the terminal with the SIP proxy, wherein the registration message includes an identifier of the terminal independent of the network, wherein the network node is capable of triggering the terminal independent of the network based upon the identifier of the terminal to thereby identify the terminal across the network such that the communication session is capable of being established with the terminal based upon the identity of the terminal across the network.

11. A system according to claim 10, wherein the network node is capable of receiving a connection request from the originating client, wherein the network node is capable of triggering the terminal in response to receiving the connection request, and wherein the network node is capable of sending the connection request to the terminal after identifying the terminal across the network.

12. A system according to claim 11, wherein the network node is capable of sending the connection request to the terminal through at least one other network node.

13. A system according to claim 11, wherein the network node is capable of receiving, and thereafter storing in a buffer, the connection request, and wherein the network node is capable of retrieving the connection request from the buffer and thereafter sending the connection request to the terminal based upon the identity of the terminal across the network to thereby establish the communication session.

14. A system according to claim 10, wherein the network node comprises a Session Initiation Protocol (SIP) proxy.

15. A system according to claim 10, wherein the network node is capable of receiving the registration message from the terminal via at least one of a network address translator (NAT) and a firewall (FW) located between the network node and the terminal, and wherein the network node is capable of triggering the terminal in a manner independent of the at least one of the NAT and the FW.

16. A system according to claim 10, wherein the network node is capable of receiving a first registration message to thereby register the terminal with the network node, wherein the network node is also capable of receiving a subsequent registration message from the terminal, in response to triggering the terminal, to thereby identify the terminal across the network, and wherein the network node is capable of identifying the terminal across the network such that a communication session is capable of being established with the terminal based upon the identity of the terminal across the network.

17. A system according to claim 10, wherein the network node is located in a network across which an originating node is capable of at least one of directly and indirectly communicating.

18. A system according to claim 17, wherein the network comprises one of a public network and a private network.

19. A method of establishing a communication session with a terminal, the method comprising:

sending a trigger to the terminal from a network node located in a network across which an originating client is capable of communicating, wherein sending the trigger comprises sending the trigger independent of the network;

receiving a registration message, in response to the trigger, at the network node from the terminal across the network to thereby register the terminal with the network node and identify the terminal across the network; and

establishing a communication session with the terminal based upon the identity of the terminal across the network.

20. A method according to claim 19 further comprising:

receiving a connection request at the network node from the originating client, wherein establishing a communication session includes sending the connection request to the terminal after registering the terminal.

21. A method according to claim 20, wherein sending the connection request comprises sending the connection request from the network node to the terminal through at least one other network node.

22. A method according to claim 20, wherein receiving a connection request comprises receiving, and thereafter storing in a buffer, a connection request, and wherein establishing a communication session comprises retrieving the connection request from the buffer and thereafter sending the connection request to the terminal based upon the identity of the terminal across the network.

23. A method according to claim 19, wherein sending a trigger to the terminal from a network node comprises sending a trigger to the terminal from a network node comprising a Session Initiation Protocol (SIP) proxy.

24. A method according to claim 19, wherein receiving a registration message comprises receiving a registration message at the network node from the terminal via at least one of a network address translator (NAT) and a firewall (FW) located between the network node and the terminal,

and wherein sending a trigger comprises sending a trigger in a manner independent of the at least one of the NAT and FW.

25. A method according to claim 19, wherein receiving a registration message comprises receiving a subsequent registration message, wherein the method further comprises:

receiving a first registration message at the network node from the terminal before sending a trigger to thereby register the terminal with the network node, wherein the first registration message includes an identifier of the terminal independent of the network,

and wherein sending a trigger comprises sending a trigger based upon the identifier of the terminal independent of the network.

26. A method according to claim 19, wherein sending a trigger to the terminal from a network node comprises sending a trigger to the terminal from a network node located in a network across which an originating node is capable of at least one of directly and indirectly communicating.

27. A method according to claim 26, wherein sending a trigger to the terminal from a network node comprises sending a trigger to the terminal from a network node located in one of a public network and a private network.

28. A method of establishing a communication session with a terminal, the method comprising:

receiving a registration message at a network node located in a network across which an originating client is capable of communicating, wherein receiving the registration message comprises receiving the registration message to thereby register the terminal with the network node, and wherein the registration message includes an identifier of the terminal independent of the network; and

triggering the terminal to thereby identify the terminal across the network, wherein triggering the terminal comprises triggering the terminal independent of the network based upon the identifier of the terminal such that a communication session is capable of being established with the terminal based upon the identity of the terminal across the network.

29. A method according to claim 28 further comprising:

receiving a connection request at the network node from the originating node; and

sending the connection request from the network node to the terminal after identifying the terminal across the network.

30. A method according to claim 29, wherein sending the connection request comprises sending the connection request from the network node to the terminal through at least one other network node.

31. A method according to claim 29, wherein receiving a connection request comprises receiving, and thereafter storing in a buffer, a connection request, and wherein sending the connection request comprises retrieving the connection request from the buffer and thereafter sending the connection request to the terminal based upon the identity of the terminal across the network to thereby establish the communication session.

32. A method according to claim 28, wherein receiving a registration message at a network node comprises receiving a registration message at a network node comprising a Session Initiation Protocol (SIP) proxy.

33. A method according to claim 28, wherein receiving a registration message comprises receiving a registration message at a network node from the terminal via at least one of a network address translator (NAT) and a firewall (FW) located between the network node and the terminal,

and wherein triggering the terminal comprises triggering the terminal in a manner independent of the at least one of the NAT and the FW.

34. A method according to claim 28, wherein receiving a registration message comprises receiving a first registration message, wherein the method further comprises:

receiving a subsequent registration message at the network node from the terminal in response to triggering the terminal to thereby identify the terminal across the network; and

establishing a communication session with the terminal based upon the identity of the terminal across the network.

35. A method according to claim 28, wherein receiving a registration message at a network node comprises receiving a registration message at a network node located in a network across which an originating node is capable of at least one of directly and indirectly communicating.

36. A method according to claim 35, wherein receiving a registration message at a network node comprises receiving a registration message at a network node located in a network comprising one of a public network and a private network.

37. A terminal comprising:

a controller capable of receiving a trigger from a network node located in a network across which an originating client is capable of communicating, wherein the controller is capable of receiving the trigger independent of the network, wherein the controller is capable of sending a registration message, in response to the trigger, to the network node across the network to thereby register the terminal with the network node and identify the terminal across the network such that a communication session is capable of being established with the terminal based upon the identity of the terminal across the network.

38. A terminal according to claim 37, wherein the controller is capable of receiving the trigger in response to the network node receiving a connection request from the originating node such that the network node is capable of sending the connection request to the terminal after registering the terminal.

39. A terminal according to claim 38, wherein the controller is capable of receiving the trigger in response to the network node receiving a connection request from the originating node such that the network node is capable of sending the connection request to the terminal through at least one other network node.

40. A terminal according to claim 38, wherein the controller is capable of receiving the trigger in response to the network node receiving, and thereafter storing in a buffer, a connection request from the network node, and wherein the controller is capable of sending the registration message such that the network node is capable of retrieving the connection request from the buffer and thereafter sending the connection request to the controller based upon the identity of the terminal across the network.

41. A terminal according to claim 37, wherein the controller is capable of receiving a trigger from a network node comprising a Session Initiation Protocol (SIP) proxy.

42. A terminal according to claim 37, wherein the controller is capable of sending the registration message to the network node via at least one of a network address translator (NAT) and a firewall (FW) located between the network node and the terminal, and wherein the controller is capable of receiving the trigger in a manner independent of the at least one of the NAT and the FW.

43. A terminal according to claim 37, wherein the controller is also capable of sending a first registration message to the network node before receiving the trigger to thereby register the terminal with the network node, wherein the first registration message includes an identifier of the terminal independent of the network such that the controller is capable of receiving the trigger based upon the identifier of the terminal independent of the network, and wherein the controller is capable of sending a subsequent registration message in response to the trigger.

44. A terminal according to claim 37, wherein the controller capable of receiving a trigger from a network node located in a network across which an originating client is capable of at least one of directly and indirectly communicating.

45. A terminal according to claim 44, wherein controller capable of receiving a trigger from a network node located in a network comprising one of a public network and private network.

46. A terminal located within one of a mobile network and a private network, the terminal comprising:

a controller capable of sending a registration message to a network node located in a network across which an originating client is capable of communicating, wherein the controller is capable of sending the registration message to thereby register the terminal with the network node, wherein the registration message includes an identifier of the terminal independent of the network, and wherein the controller is capable of being triggered independent of the network based upon the identifier of the terminal to thereby identify the terminal across the network such that a communication session is capable of being established with the terminal based upon the identity of the terminal across the network.

47. A terminal according to claim 46, wherein the controller is capable of being triggered in response to the network node receiving a connection request from the originating client, and wherein the controller is capable of being triggered such that the network node is capable of sending the connection request to the terminal after identifying the terminal across the network.

48. A terminal according to claim 47, wherein the controller is capable of being triggered such that the network node is capable of sending the connection request to the terminal through at least one other network node.

49. A terminal according to claim 47, wherein the controller is capable of being triggered in response to the network node receiving, and thereafter storing in a buffer, the connection request, and wherein the controller is capable of being triggered such that the network node is capable of retrieving the connection request from the buffer and thereafter sending the connection request to the terminal based upon the identity of the terminal across the network to thereby establish the communication session.

50. A terminal according to claim 46, wherein the controller is capable of sending a registration message to a network node comprising a Session Initiation Protocol (SIP) proxy.

51. A terminal according to claim 46, wherein the controller is capable of sending the registration message to the network node via at least one of a network address translator (NAT) and a firewall (FW) located between the network node and the terminal, and wherein the controller is capable of being triggered in a manner independent of the at least one of the NAT and the FW.

52. A terminal according to claim 46, wherein the controller is capable of sending a first registration message to thereby register the terminal with the network node, wherein the controller is also capable of sending a subsequent registration message to the network node in response to being triggered to thereby identify the terminal across the network such that a communication session is capable of being established with the terminal based upon the identity of the terminal across the network.

53. A terminal according to claim 46, wherein the controller is capable of sending a registration message to a network node located in a network across which an originating node is capable of at least one of directly and indirectly communicating.

54. A terminal according to claim 54, wherein the controller is capable of sending a registration message to a network node located in a network comprising one of a public network and a private network.