Method and Apparatus for Cooperation Between Push Devices

• US 20130144954A1
• Filed: 01/30/2013
• Published: 06/06/2013
• Est. Priority Date: 07/30/2010
• Status: Active Grant

• Current Assignee: Apex Net LLC (IP Edge LLC)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: Li, Bojie, Peng, Chenghui
• Granted Patent: US 9,247,018 B2
• Time in Patent Office: Days
• US Class Current: 709/205
• CPC Class Codes: H04L 2101/65 Telephone numbers
• CPC Class Codes: H04L 61/103 across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
• CPC Class Codes: H04L 61/5076 Update or notification mechanisms, e.g. DynDNS
• CPC Class Codes: H04L 63/0892 by using authentication-authorization-accounting [AAA] servers or protocols
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54

Abstract

A method and an apparatus for cooperation between push devices to improve the validity and reachability of Internet Protocol (IP) connections. The method for cooperation between push devices includes: obtaining, by a Push proxy, a Push identifier and an address of a Push client; storing, by the Push proxy, a mapping between the Push identifier and the address of the Push client; and if the address of the Push client changes, updating, by the Push proxy, the corresponding address in the mapping. With the embodiments of the present invention, validity and reachability of IP connections can be improved, and the real-time performance and reliability of Push messages can be improved.

Claims

1. A method for cooperation between push devices comprising:

obtaining, by a push proxy, a push identifier and an address of a push client;

storing, by the push proxy, a mapping between the push identifier and the address of the push client; and

updating, by the push proxy, a corresponding address in the mapping when the address of the push client changes.

2. The method according to claim 1, wherein obtaining, by the push proxy, the push identifier and the address of the push client comprises:

receiving, by the push proxy, a push registration request message sent by the push client, wherein the push registration request message or a data packet header of the push registration request message carries the address of the push client;

parsing the push registration request message or the data packet header of the push registration request message to obtain the address of the push client;

sending the push registration request message to a push server;

receiving a push registration request response message sent by the push server, wherein the push registration request response message carries the push identifier allocated by the push server to the push client; and

parsing the push registration request response message to obtain the push identifier of the push client.

3. The method according to claim 1, wherein obtaining, by the push proxy, the push identifier and the address of the push client comprises:

receiving, by the push proxy, a proxy registration request message sent by the push client, wherein the proxy registration request message or a data packet header of the proxy registration request message carries the push identifier and the address of the push client; and

parsing the proxy registration request message or the data packet header of the proxy registration request message to obtain the push identifier and the address of the push client.

4. The method according to claim 3, wherein the push client obtains the push identifier of the push client by:

sending, by the push client, a push registration request message to a push server;

receiving, by the push client, a push registration request response message sent by the push server, wherein the push registration request response message carries the push identifier allocated by the push server to the push client; and

parsing, by the push client, the registration request response message to obtain the push identifier of the push client.

5. The method according to claim 1, wherein updating, by the push proxy, the corresponding address in the mapping when the address of the push client changes comprises:

receiving, by the push proxy, an address update message sent by a network-side network element, wherein the address update message carries an original address of the push client and a new address after the change which are perceived by the network-side network element, and wherein the network-side network element comprises a data gateway node, a home location register (HLR), a home subscriber server (HSS), or an authentication, authorization and accounting (AAA) server; and

querying the stored mapping between the push identifier and the address of the push client according to the original address and updating the corresponding address in the mapping according to the new address.

6. The method according to claim 5, wherein before the push proxy receives the address update message sent by the network-side network element, the method further comprises sending, by the push proxy, a trigger message to the network-side network element, wherein the trigger message carries the address of the push client and is used to trigger the network-side network element to notify the push proxy when the network-side network element perceives the change of the address of the push client.

7. The method according to claim 6, wherein the push proxy and the network-side network element are located on a same device and the trigger message is sent through an internal trigger mechanism.

8. The method according to claim 1, wherein updating, by the push proxy, the corresponding address in the mapping when the address of the push client changes comprises:

receiving, by the push proxy, an address update message sent by the push client, wherein the address update message carries the push identifier of the push client and a new address after the change and the new address after the change is perceived by the push client; and

querying the stored mapping between the push identifier and the address of the push client according to the push identifier of the push client and updating the corresponding address in the mapping according to the new address.

9. The method according to claim 1, further comprising:

receiving, by the push proxy, a push message sent by the push server, wherein the push message carries the push identifier of the push client;

obtaining, by the push proxy, the address of the push client from the stored mapping between the push identifier and the address of the push client according to the push identifier of the push client; and

sending the push message to the push client according to the address of the push client.

10. The method according to claim 9, wherein before the push message is sent to the push client, the method further comprises converting a format of the push message to adapt to an interface of the push client.

11. The method according to claim 1, further comprising:

receiving, by the push proxy, an address release message sent by a network-side network element, wherein the address release message carries an address of the push client to be released, and the address of the push client to be released is perceived by the network-side network element, and wherein the network-side network element comprises a data gateway node, an HLR, an HSS, or an AAA server; and

querying the stored mapping between the push identifier and the address of the push client according to the address, and marking the corresponding address in the mapping as unobtained or as a special value.

12. The method according to claim 1, further comprising:

receiving, by the push proxy, a deregistration request message sent by the push client, wherein the deregistration request message carries at least the push identifier of the push client; and

sending, by the push proxy, a deregistration request response message to the push client, and deleting the stored mapping between the push identifier and the address of the push client.

13. The method according to claim 1, further comprising:

receiving, by the push proxy, a deregistration request message sent by the push client, wherein the deregistration request message carries at least the push identifier of the push client;

sending the deregistration request message to a push server; and

receiving a deregistration request response message sent by the push server and sending it to the push client, and deleting the stored mapping between the push identifier and the address of the push client.

14. A method for cooperation between push devices comprising:

obtaining, by a push proxy, a push identifier, an intra-network identifier, and an address of a push client;

storing, by the push proxy, a mapping between the push identifier, the intra-network identifier, and the address of the push client; and

updating, by the push proxy, a corresponding address in the mapping when the address of the push client changes.

15. The method according to claim 14, wherein obtaining, by the push proxy, the push identifier, the intra-network identifier, and the address of the push client comprises:

receiving, by the push proxy, a push registration request message sent by the push client, wherein the push registration request message or a data packet header of the push registration request message carries the address of the push client;

parsing the push registration request message or the data packet header of the push registration request message to obtain the address of the push client;

querying a network-side network element according to the address to obtain the intra-network identifier of the push client, wherein the network-side network element comprises a data gateway node, a home location register (HLR), a home subscriber server (HSS), or an authentication, authorization and accounting (AAA) server;

sending the push registration request message to a push server;

receiving a push registration request response message sent by the push server, wherein the push registration request response message carries the push identifier allocated by the push server to the push client; and

parsing the push registration request response message to obtain the push identifier of the push client.

16. The method according to claim 14, wherein obtaining, by the push proxy, the push identifier, the intra-network identifier, and the address of the push client comprises:

receiving, by the push proxy, a proxy registration request message sent by the push client, wherein the proxy registration request message or a data packet header of the proxy registration request message carries the push identifier, the intra-network identifier, and the address of the push client; and

parsing the proxy registration request or its data packet header to obtain the push identifier, the intra-network identifier, and the address of the push client.

17. The method according to claim 14, wherein obtaining, by the push proxy, the push identifier, the intra-network identifier, and the address of the push client comprises:

receiving, by the push proxy, a push client network entry notification sent by a network-side network element, wherein the push client network entry notification carries the address and the intra-network identifier of the push client, and wherein the network-side network element comprises a data gateway node, an HLR, an HSS, or an AAA server;

querying authentication information of the push client and an address of a push server locally or obtaining authentication information of the push client and an address of a push server from a user information database according to the intra-network identifier, and sending a push registration request message to the push server;

receiving a push registration request response message sent by the push server, wherein the push registration request response message carries the push identifier allocated by the push server to the push client; and

parsing the push registration request response message to obtain the push identifier of the push client.

18. The method according to claim 14, wherein updating, by the push proxy, the corresponding address in the mapping when the address of the push client changes comprises:

receiving, by the push proxy, an address update message sent by a network-side network element, wherein the address update message carries the intra-network identifier of the push client and a new address of the push client after the change, and the new address of the push client after the change is perceived by the network-side network element, and wherein the network-side network element comprises a data gateway node, an HLR, an HSS, or an AAA server; and

querying the stored mapping between the push identifier, the intra-network identifier, and the address of the push client according to the intra-network identifier, and updating the corresponding address in the mapping according to the new address.

19. The method according to claim 14, further comprising:

receiving, by the push proxy, a push message sent by push server, wherein the push message carries the push identifier of the push client;

obtaining, by the push proxy, the intra-network identifier of the push client from the stored mapping between the push identifier, the intra-network identifier, and the address of the push client according to the push identifier of the push client; and

converting the push message into a Short Message Service (SMS) message or a Wireless Application Protocol (WAP) Push message, and sending the converted message to an SMS Center (SMSC) or a WAP Push proxy gateway, wherein the converted message carries the intra-network identifier corresponding to the push identifier.

20. An apparatus for cooperation between push devices comprising:

a first obtaining module configured to obtain a push identifier and an address of a push client;

a first storing module configured to store a mapping between the push identifier and the address of the push client; and

a first updating module configured to update a corresponding address in the mapping when the address of the push client changes.

21. The cooperation apparatus according to claim 20, wherein the first obtaining module comprises:

a first receiving unit configured to receive a push registration request message sent by the push client, wherein the push registration request message or a data packet header of the push registration request message carries the address of the push client;

a first parsing unit configured to parse the push registration request message or the data packet header of the push registration request message to obtain the address of the push client; and

a first sending unit configured to send the push registration request message to a push server,

wherein the first receiving unit is further configured to receive a push registration request response message sent by the push server,

wherein the push registration request response message carries the push identifier allocated by the push server to the push client, and

wherein the first parsing unit is further configured to parse the push registration request response message to obtain the push identifier of the push client.

22. The cooperation apparatus according to claim 20, wherein the first obtaining module comprises:

a second receiving unit configured to receive a proxy registration request message sent by the push client, wherein the proxy registration request message or a data packet header of the proxy registration request message carries the push identifier and the address of the push client; and

a second parsing unit configured to parse the proxy registration request message or the data packet header of the proxy registration request message to obtain the push identifier and the address of the push client.

23. The cooperation apparatus according to claim 20, wherein the first updating module comprises:

a first processing unit configured to receive an address update message sent by a network-side network element, wherein the address update message carries an original address of the push client and a new address of the push client after the change which are perceived by the network-side network element, and wherein the network-side network element comprises a data gateway node, a home location register (HLR), a home subscriber server (HSS), or an authentication, authorization and accounting (AAA) server; and

a second processing unit configured to query the stored mapping between the push identifier and the address of the push client according to the original address, and update the corresponding address in the mapping according to the new address.

24. The cooperation apparatus according to claim 23, wherein the second processing unit is further configured to send a trigger message to the network-side network element, and wherein the trigger message carries the address of the push client and is used to trigger the network-side network element to notify the first processing unit when the network-side network element perceives the change of the address of the push client.

25. The cooperation apparatus according to claim 20, wherein the first updating module comprises:

a third processing unit configured to receive an address update message sent by the push client, wherein the address update message carries the push identifier of the push client and a new address after the change, wherein the new address after the change is perceived by the push client; and

a fourth processing unit configured to query the stored mapping between the push identifier and the address of the push client according to the push identifier of the push client, and update the corresponding address in the mapping according to the new address.

26. The cooperation apparatus according to claim 20, further comprising:

a first controlling module configured to receive a push message sent by the push server, wherein the push message carries the push identifier of the push client;

a second controlling module configured to obtain, according to the push identifier of the push client, the address of the push client from the mapping that is between the push identifier and the address of the push client and is stored by the first storing module, and notify the address to the first controlling module; and

the first controlling module further configured to send the push message to the push client according to the address of the push client.

27. The cooperation apparatus according to claim 26, wherein the first controlling module is further configured to convert a format of the push message to adapt to an interface of the client before sending the push message to the push client.

28. The cooperation apparatus according to claim 20, further comprising:

a third controlling module configured to receive an address release message sent by a network-side network element, wherein the address release message carries an address of the push client to be released, and the address of the push client to be released is perceived by the network-side network element, and wherein the network-side network element comprises a data gateway node, an HLR, an HSS, or an AAA server; and

a fourth controlling module configured to query, according to the address, the mapping that is between the push identifier and the address of the push client and is stored by the first storing module, and mark the corresponding address in the mapping as unobtained or as a special value.

29. The cooperation apparatus according to claim 28, wherein the third controlling module is further configured to receive a deregistration request message sent by the push client, wherein the deregistration request message carries at least the push identifier of the push client, and wherein the fourth controlling module is further configured to send a deregistration request response message to the push client, and delete the mapping that is between the push identifier and the address of the push client and is stored by the first storing module.

30. The cooperation apparatus according to claim 28, wherein the third controlling module is further configured to receive the deregistration request message sent by the push client, wherein the deregistration request message carries at least the push identifier of the push client, and wherein the fourth controlling module is further configured to send the deregistration request message to a push server, receive the deregistration request response message sent by the push server and send the response message to the push client, and delete the mapping that is between the push identifier and the address of the push client and is stored by the first storing module.

31. An apparatus for cooperation between push devices comprising:

a second obtaining module configured to obtain a push identifier, an intra-network identifier, and an address of a push client;

a second storing module configured to store a mapping between the push identifier, the intra-network identifier, and the address of the push client; and

a second updating module configured to update a corresponding address in the mapping when the address of the push client changes.

32. The cooperation apparatus according to claim 31, wherein the second obtaining module comprises:

a third receiving unit configured to receive a push registration request message sent by the push client, wherein the push registration request message or a data packet header of the push registration request message carries the address of the push client;

a third parsing unit configured to parse the push registration request message or the data packet header of the push registration request message to obtain the address of the push client, and query a network-side network element according to the address to obtain the intra-network identifier of the push client, wherein the network-side network element comprises a data gateway node, a home location register (HLR), a home subscriber server (HSS), or an authentication, authorization and accounting (AAA) server; and

a third sending unit configured to send the push registration request message to a push server,

wherein the third receiving unit is further configured to receive a push registration request response message sent by the push server,

wherein the push registration request response message carries the push identifier allocated by the push server to the push client, and

wherein the third parsing unit is further configured to parse the push registration request response message to obtain the push identifier of the push client.

33. The cooperation apparatus according to claim 31, wherein the second updating module comprises:

a fifth processing unit configured to receive an address update message sent by the network-side network element, wherein the address update message carries the intra-network identifier of the push client and a new address of the push client after the change, and the new address of the push client after the change is perceived by the network-side network element, and wherein the network-side network element comprises a data gateway node, an HLR, an HSS, or an AAA server; and

a sixth processing unit configured to query, according to the intra-network identifier, the mapping that is between the push identifier, the intra-network identifier, and the address of the push client and is stored by the second storing module, and update the corresponding address in the mapping according to the new address.

34. The cooperation apparatus according to claim 31, further comprising:

a fifth controlling module configured to receive a push message sent by the push server, wherein the push message carries the push identifier of the push client; and

a sixth controlling module configured to;

obtain, according to the push identifier of the push client, the intra-network identifier of the push client from the stored mapping between the push identifier, the intra-network identifier, and the address of the push client; and

convert the push message into a Short Message Service (SMS) message or a Wireless Application Protocol (WAP) Push message, and send the converted message to an SMS Center (SMSC) or a WAP Push proxy gateway, wherein the converted message carries the intra-network identifier corresponding to the push identifier.