SEAMLESS PUSH SYSTEM AND METHOD FOR SAME

• US 20150163168A1
• Filed: 02/17/2015
• Published: 06/11/2015
• Est. Priority Date: 08/20/2012
• Status: Abandoned Application

• Current Assignee: Fujitsu Limited
• Original Assignee: Fujitsu Limited
• Inventors: NAKAMURA, Yosuke, NIMURA, Kazuaki, ITO, Hidenobu
• Application Number:
  US14/624,099
• Publication Number:
  US 20150163168A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 49/25 Routing or path finding in a switch fabric
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• 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
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04W 4/60 Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Abstract

A seamless push system has a first push gateway within an intranet and which, in response to a transmission request for a push message, transmits the push message to a terminal in a connected state via the intranet, and a second push gateway within the Internet and which is capable of maintaining a connected state with the terminal via the Internet. When the terminal can be connected to the Internet, the second push gateway establishes a connected state from the terminal via the Internet and maintains the connected state, the first push gateway transfers the push message to the second push gateway in response to the transmission request for the push message, and the second push gateway transmits the push message via the Internet to the terminal in the connected state in response to the transfer of the push message.

Claims

1. A seamless push system comprising:

a first push gateway which is provided within an intranet and which, in response to a transmission request for a push message, transmits the push message to a terminal in a connected state via the intranet; and

a second push gateway which is provided within an Internet and which is capable of maintaining a connected state with the terminal via the Internet, wherein

when the terminal is capable of connecting to the Internet,

the second push gateway establishes a connected state from the terminal via the Internet and maintains the connected state,

the first push gateway transfers the push message to the second push gateway in response to the transmission request for the push message, and

the second push gateway transmits the push message via the Internet to the terminal in the connected state in response to the transfer of the push message.

2. The seamless push system according to claim 1, further comprising

an application server which is provided within the intranet and which causes the terminal to download an application in correspondence with an access by the terminal, wherein

the application server transmits, via a private network constructed between a terminal having received the push message and the application server, an application corresponding to the push message to the terminal.

3. The seamless push system according to claim 2, wherein

when the private network is being constructed, the first push gateway establishes a connected state from the terminal via the private network and maintains the connected state, and the first push gateway further transmits a different push message to the terminal via the private network.

4. The seamless push system according to claim 2, wherein

when the terminal is capable of connecting to the intranet, the first push gateway establishes a connected state with the terminal via the intranet and transmits the push message to the terminal via the connected state, and when the terminal is capable of connecting to the Internet, the second push gateway establishes a connected state with the terminal via the Internet and transmits the push message to the terminal via the connected state.

5. The seamless push system according to claim 4, wherein

the terminal includes an application downloading unit which downloads the application from the application server via the private network in response to reception of the push message,

the terminal and the first push gateway store a terminal ID and push transmission destination information corresponding to the downloading unit of the terminal,

the first push gateway and the second push gateway store a terminal ID of the terminal that maintains connected states with the respective push gateways,

when a terminal corresponding to the push transmission destination information is not in a connected state with the first push gateway, in response to receiving the push message together with the push transmission destination information, the first push gateway adds a corresponding terminal ID to the push transmission destination information and transmits the push message and the push transmission destination information to the second push gateway, and

the second push gateway checks whether or not the terminal is in a connected state with the second push gate way based on the transferred terminal ID and, when the terminal is in the connected state with the second push gate way, transmits the push message together with the push transmission destination information to the terminal in the connected state.

6. The seamless push system according to claim 5, wherein

the terminal includes a plurality of the downloading units, and

the terminal hands over the transmitted push message to a downloading unit corresponding to the push transmission destination information among the plurality of downloading units, and the downloading unit having received the push message downloads an application corresponding to the push transmission destination information from the application server.

7. The seamless push system according to claim 1, wherein

when the terminal is capable of connecting to the Internet,

the first push gateway stores the push message of the transmission request in a retransmission queue according to a transmission destination terminal, which is for a push message of the transmission request, not being in a connected state, and further transfers the push message of the transmission request to the second push gateway,

the second push gateway checks whether or not the transmission destination terminal of the push message is in a connected state with the second push gateway in response to the transfer of the push message, transmits the push message via the Internet to a terminal in the connected state with the second push gateway, and transmits a push transmission completion notification to the first push gateway in response to a reception notification of the push message from the terminal, and

the first push gateway changes the push message in the retransmission queue to an already transmitted message in response to the push transmission completion notification.

8. The seamless push system according to claim 7, wherein

the second push gateway checks whether or not a transmission destination terminal of the push message is in a connected state with the second push gateway in response to the transfer of the push message and does not store the transferred push message in a database when the transmission destination terminal of the push message is not in the connected state with the second push gateway,

the second push gateway transmits, when the terminal subsequently establishes a connected state with the second push gateway via the Internet, a retransmission inquiry with respect to the terminal having established the connection to the first push gateway, and

the first push gateway transmits a push message for the terminal having established the connection, which is stored in the retransmission queue, to the second push gateway in response to the retransmission inquiry.

19. The seamless push system according to claim 8, wherein

the first push gateway accesses the second push gateway and establishes a connected state with the second push gateway, the second push gateway repetitively replies to the first push gateway to maintain the connected state with the second push gateway, and

the second push gateway transmits the push transmission completion notification or the retransmission inquiry to the first push gateway via the maintained connected state.

20. The seamless push system according to claim 7, wherein

the second push gateway transmits the push completion notification in a response to the transfer of the push message.

21. The seamless push system according to claim 20, wherein

the second push gateway checks whether or not a transmission destination terminal of the push message is in a connected state with the second push gateway in response to the transfer of the push message and does not store the transferred push message in a database when the transmission destination terminal of the push message is not in the connected state with the second push gateway, and transmits the fact that the transmission destination terminal is not in the connected state with the second push gateway in a response to the transfer of the push message,

the first push gateway transmits a connection inquiry command that inquires whether or not the terminal has subsequently established the connected state with the second push gateway via the Internet to the second push gateway,

the second push gateway transmits, when the terminal subsequently establishes the connected state with the second push gateway via the Internet, the connected state in a response to the connection inquiry command, and

the first push gateway transmits a push message for the terminal having established the connection which is stored in the retransmission queue to the second push gateway in response of the connected state.

22. The seamless push system according to claim 20, wherein

the second push gateway transmits the push message to the transmission destination terminal that is in the connected state with the second push gateway in response to the transfer of the push message and transmits a timeout in a response to transfer of the push message when a reception confirmation is not obtained from the transmission destination terminal,

the first push gateway subsequently transmits a transmission result inquiry command that inquires about the reception confirmation from the transmission destination terminal to the second push gateway,

the second push gateway transmits reception of the reception confirmation in a response to the transmission result inquiry command when the reception confirmation is received from the transmission destination terminal, and

the first push gateway changes the push message in the retransmission queue to an already transmitted message in response to the reception of the reception confirmation.

23. The seamless push system according to claim 1, further comprising

a transmission destination information generating server provided so as to be shared by a plurality of first push gateways, wherein

in response to a request for generating transmission destination information that is transmitted by the plurality of first push gateways in correspondence to a request from the terminal, the transmission destination information generating server generates unique transmission destination information with no overlap among the plurality of first push gateways and sends back the unique transmission destination information to the first push gateway having transmitted the request for generating transmission destination information.

9. A method of transmitting a push message by using a push system including:

a first push gateway which is provided within an intranet and which, in response to a transmission request for a push message, transmits the push message to a terminal in a connected state via the intranet; and

a second push gateway which is provided within an Internet and which is capable of maintaining a connected state with the terminal via the Internet,

the push method comprising;

when the terminal is capable of connecting to the Internet,

operating the second push gateway to be in a connected state from the terminal via the Internet and maintain the connected state;

operating the first push gateway to transfer the push message to the second push gateway in response to the transmission request for the push message; and

operating the second push gateway to transmit the push message via the Internet to the terminal in the connected state in response to the transfer of the push message.

10. The method according to claim 9, wherein the push system further includes an application server which is provided within the intranet and which causes the terminal to download an application in correspondence with an access by the terminal,

the method further comprising

operating the application server to transmit, via a private network constructed between a terminal having received the push message and the application server, an application corresponding to the push message to the terminal.

11. The method according to claim 9, further comprising, when the private network is being constructed, operating the first push gateway to be in a connected state from the terminal via the private network and maintain the connected state, and operating the first push gateway to further transmit a different push message to the terminal via the private network.

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

when the terminal is capable of connecting to the Internet,

operating the first push gateway to store the push message of the transmission request in a retransmission queue according to a transmission destination terminal, which is for a push message of the transmission request, not being in a connected state, and further to transfer the push message of the transmission request to the second push gateway;

operating the second push gateway to check whether or not the transmission destination terminal of the push message is in a connected state with the second push gateway in response to the transfer of the push message, and transmit the push message via the Internet to a terminal in the connected state with the second push gateway, and moreover transmit a push transmission completion notification to the first push gateway in response to a reception notification of the push message from the terminal; and

operating the first push gateway to change the push message in the retransmission queue to an already transmitted message in response to the push transmission completion notification.

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

operating the second push gateway to check whether or not a transmission destination terminal of the push message is in a connected state with the second push gateway in response to the transfer of the push message and not to store the transferred push message in a database when the transmission destination terminal of the push message is not in the connected state with the second push gateway;

operating the second push gateway to transmit, when the terminal subsequently establishes a connected state with the second push gateway via the Internet, a retransmission inquiry with respect to the terminal having established the connection to the first push gateway; and

operating the first push gateway to transmit a push message for the terminal having established the connection which is stored in the retransmission queue to the second push gateway in response to the retransmission inquiry.

14. A method of providing an application push service by using a push system including:

a first push gateway which is provided within an intranet and which, in response to a transmission request for a push message, transmits the push message to a terminal in a connected state via the intranet; and

a second push gateway which is provided within an Internet and which is capable of maintaining a connected state with the terminal via the Internet,

the push method comprising;

when the terminal is capable of connecting to the Internet,

operating the second push gateway to be in a connected state from the terminal via the Internet and maintain the connected state;

operating the first push gateway to transfer the push message to the second push gateway in response to the transmission request for the push message; and

operating the second push gateway to transmit the push message via the Internet to the terminal in the connected state in response to the transfer of the push message.

15. A first push gateway which is provided within an intranet and which is capable of communicating with a second push gateway provided within an Internet,

the first push gateway comprising:

a push message request receiving unit which transmits, in response to a transmission request for a push message, the push message to a terminal in a connected state via the intranet;

a terminal connection receiving unit which establishes a connected state with a terminal via the intranet in response to a connection request from the terminal; and

a gateway cooperating unit capable of communicating with the second push gateway, wherein

when a connected state is formed from the terminal in the second push gateway and the connected state is being maintained by the second push gateway,

the first push gateway transfers the push message to the second push gateway in response to a transmission request for the push message and causes the second push gateway to transmit the push message to the terminal in the connected state via the Internet.

16. The first push gateway according to claim 15, wherein

a private network is constructed with an application server within the intranet by a terminal having received the push message, and an application corresponding to the push message is downloaded from the application server to the terminal, and

when the private network is being constructed, a connected state is formed in the first push gateway from the terminal via the private network and the first push gateway maintains the connected state, and the first push gateway further transmits a different push message to the terminal via the private network.

17. The first push gateway according to claim 15, wherein

the first push gateway stores the push message of the transmission request in a retransmission queue according to a transmission destination terminal, which is for a push message of the transmission request, not being in a connected state, and further transfers the push message of the transmission request to the second push gateway,

in the second push gateway, whether or not the transmission destination terminal of the push message is in a connected state with the second push gateway is checked in response to the transfer of the push message, the push message is transmitted via the Internet to a terminal in the connected state with the second push gateway, and a push transmission completion notification is transmitted to the first push gateway in response to a reception notification of the push message from the terminal, and

the first push gateway changes the push message in the retransmission queue to an already transmitted message in response to the push transmission completion notification.

18. The first push gateway according to claim 17, wherein

in the second push gateway, whether or not a transmission destination terminal of the push message is in a connected state with the second push gateway is checked in response to the transfer of the push message and the transferred push message is not stored in a database when the transmission destination terminal of the push message is not in the connected state with the second push gateway,

in the second push gateway, when the terminal subsequently establishes a connected state with the second push gateway via the Internet, a retransmission inquiry with respect to the terminal having established the connection is transmitted to the first push gateway, and

the first push gateway transmits a push message for the terminal having established the connection which is stored in the retransmission queue to the second push gateway in response to the retransmission inquiry.