System and method for pushing content to a terminal utilizing a network-initiated data service technique

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

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Nokia Corporation
• Inventors: Kiss, Krisztian, Asthana, Sarvesh
• Granted Patent: US 8,085,741 B2
• Time in Patent Office: Days
• US Class Current: 370/328
• 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 65/1045 Proxies, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1073 Registration or de-registration
• CPC Class Codes: H04W 68/005 Transmission of information for alerting of incoming communication
• CPC Class Codes: H04W 76/10 Connection setup

Abstract

A system is provided for pushing content to a terminal located within a mobile network or a private network. The system includes a network node, such as a Session Initiation Protocol (SIP) proxy, located across a public network from the network including the terminal. The network node is capable of subscribing to a push service on behalf of the terminal such that the network node is also capable of receiving push content in accordance with the push service. Thereafter, the network node is capable of establishing a network-initiated data session with the terminal. In response to the network-initiated data session, the network node is further capable of registering the terminal such that the terminal is capable of receiving the push content based upon the registration.

Claims

1. A system for pushing content to a terminal located within one of a mobile network and a private network, the system comprising:

a network node located across a public network from the network including the terminal, wherein the network node is capable of subscribing to a push service on behalf of the terminal such that the network node is also capable of receiving push content in accordance with the push service, wherein the network node is thereafter capable of establishing a network-initiated data session with the terminal, and wherein the network node is further capable of registering the terminal in response to the network-initiated data session such that the terminal is capable of receiving the push content based upon the registration.

2. A system according to claim 1, wherein the network node is capable of receiving, and thereafter storing in a buffer, the push content, and wherein the network node is capable of sending the push content to the terminal from the buffer.

3. A system according to claim 1, wherein the network node is capable of registering the terminal such that the terminal is capable of subscribing to the push service based upon the registration, and thereafter receiving the push content based upon the terminal subscribing to the push service.

4. A system according to claim 1, wherein the network node is capable of establishing a network-initiated data session with the terminal by sending a trigger to the terminal independent of the public network to thereby trigger the terminal to register with the network node.

5. A system according to claim 1, wherein the network node is capable of receiving a registration message from the terminal across the public network to thereby identify the terminal across the public network and register the terminal, and wherein the network node is capable of registering the terminal such that the terminal is capable of receiving the push content based upon the identity of the terminal across the public network.

6. A system according to claim 5, wherein the network node is capable of receiving a 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 establishing a network-initiated data session 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 comprises a Session Initiation Protocol (SIP) proxy.

8. A method of pushing content to a terminal located within one of a mobile network and a private network, the method comprising:

subscribing to a push service from a network node located across a public network from the network including the terminal, wherein subscribing to a push service comprises subscribing to a push service on behalf of the terminal;

receiving push content at the network node in accordance with the push service;

establishing, at the network node, a network-initiated data session with the terminal;

registering the terminal with the network node in response to the network-initiated data session; and

sending the push content to the terminal based upon the registration.

9. A method according to claim 8, wherein receiving push content at the network node further comprises storing the push content in a buffer at the network node,

and wherein sending the push content comprises sending the push content to the terminal from the buffer.

10. A method according to claim 8 further comprising:

subscribing to the push service from the terminal based upon the registration,

wherein sending the push content comprises sending the push content to the terminal based upon subscribing to the push service from the terminal.

11. A method according to claim 8, wherein establishing a network-initiated data session with the terminal comprises sending a trigger from the network node to the terminal independent of the public network to thereby trigger the terminal to register with the network node.

12. A method according to claim 8, wherein registering the terminal comprises receiving a registration message at the network node from the terminal across the public network to thereby identify the terminal across the public network,

and wherein sending the push content comprises sending the push content based upon the identity of the terminal across the public network.

13. A method according to claim 12, 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 establishing a network-initiated data session comprises establishing a network-initiated data session in a manner independent of the at least one of the NAT and FW.

14. A method according to claim 8, wherein subscribing to a push service comprises subscribing to a push service from a network node comprising a Session Initiation Protocol (SIP) proxy.

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

a controller capable of instructing a network node to subscribe to a push service on behalf of the terminal such that the network node receives push content in accordance with the push service, the network node being located across a public network from the network including the terminal, wherein the controller is capable of instructing the network node to subscribe to the push service such that the network node also establishes a network-initiated data session with the terminal, wherein the controller is capable of registering the terminal with the network node in response to the network-initiated data session, and thereafter receiving the push content based upon the registration.

16. A terminal according to claim 15, wherein the controller is capable of instructing the network node to subscribe to the push service such that the network node receives, and stores in a buffer, push content such that the controller is capable of receiving the push content from the buffer.

17. A terminal according to claim 15, wherein the controller is capable of subscribing to the push service based upon the registration, and wherein the controller is capable of receiving the push content based upon subscribing to the push service from the terminal.

18. A terminal according to claim 15, wherein the controller is capable of receiving a trigger from the network node to the terminal independent of the public network to thereby establish a network-initiated data session and trigger the terminal to register with the network node.

19. A terminal according to claim 15, wherein the controller is capable of sending a registration message to the network node across the public network to thereby identify the terminal across the public network such that the network node is capable of registering the terminal, and wherein the controller is capable of receiving the push content based upon the identity of the terminal across the public network.

20. A terminal according to claim 19, wherein the controller is capable of sending a 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 instructing the network node to subscribe to the push service such that the network node establishes the network-initiated data session in a manner independent of the at least one of the NAT and FW.

21. A terminal according to claim 15, wherein the controller is capable of instructing a network node comprising a Session Initiation Protocol (SIP) proxy to subscribe to a push service on behalf of the terminal.