Push service without persistent TCP connection in a mobile network
Methods, systems, and articles of manufacture for non-TCP push service in a mobile network comprise receiving, at a push server, registration information for a mobile device from a push client via a first internal interface without persistent TCP connection. The registration information includes a private IP address for the mobile device and a mobile device session identifier associated with an instance of an application client on the mobile device. A push trigger associated with an event of an application server is received at the push server via a second interface exposed outside of a service provider firewall. The push trigger includes a push trigger session identifier. When the push trigger session identifier matches the mobile device session identifier, the push trigger is determined to be associated with the instance of the application client on the mobile device and is transmitted to the push client without persistent TCP connection.
1. A method comprising:
receiving, at a push server, registration information for a mobile device from a push client via a first internal interface without persistent Transmission Control Protocol (TCP) connection, the registration information including a private Internet Protocol (IP) address for the mobile device and a mobile device session identifier associated with an instance of an application client on the mobile device;
receiving, at the push server, a push trigger associated with an event of an application server via a second interface exposed outside of a service provider firewall, wherein the push trigger includes a push trigger session identifier identifying the instance of the application client on the mobile device;
determining that the push trigger is associated with the instance of the application client on the mobile device when the push trigger session identifier matches the mobile device session identifier; and
transmitting the push trigger to the instance of the application client on the mobile device by mapping the push trigger session identifier to the private IP address of the mobile device.
2. The method of claim 1 , wherein the push trigger is transmitted to the push client via one of the first internal interface without persistent TCP connection or over a cellular network.
3. The method of claim 1 , wherein a connection between the push server and the push client via the first internal interface is a User Datagram Protocol (UDP)-based connection.
4. The method of claim 1 , wherein a connection between the push server and the push client via the first internal interface is a non-persistent TCP connection.
5. The method of claim 1 , further comprising:
transmitting the mobile device session identifier from the application client to the application server via an interface supporting an application specific TCP connection.
6. The method of claim 5 , wherein the mobile device is set to an idle state after the mobile device session identifier is transmitted to the application server and there is no application data to transmit.
7. The method of claim 5 , wherein the mobile device is set to a non-idle state when a paging message associated with the push trigger is received at the push client.
8. The method of claim 1 , further comprising:
receiving the push trigger at the push client; and
communicating the push trigger to the application client.
9. The method of claim 7 , further comprising:
receiving the push trigger at the application client; and
establishing an application specific TCP-based connection between the application client and the application server to receive data associated with the push trigger.
10. The method of claim 1 , further comprising transmitting, from the push server, the registration information when the mobile device moves from a first access network to a second access network if the private IP address or the session identifier changes between the first and second access networks.
11. The method of claim 1 , wherein a TCP connection via the internal first interface with the push client is originated by the push server to deliver the push trigger and then terminated after the push trigger is delivered.
12. An apparatus comprising:
a push server for:
receiving registration information for a mobile device from a push client via a first internal interface without persistent TCP connection, the registration information including a private IP address for the mobile device and a mobile device session identifier associated with an instance of an application client on the mobile device; and
receiving a push trigger associated with an event of an application server via a second interface exposed outside of a service provider firewall, wherein the push trigger includes a push trigger session identifier identifying the instance of the application client on the mobile device;
a data storage device storing computer program instructions; and
a processor communicatively coupled to the data storage device, the processor configured to execute the computer program instructions, which, when executed on the processor, cause the processor to perform a method comprising:
determining that the push trigger is associated with the instance of the application client on the mobile device when the push trigger session identifier matches the mobile device session identifier; and
transmitting the push trigger to the instance of the application client on the mobile device by mapping the push trigger session identifier to the private IP address of the mobile device.
13. The apparatus of claim 12 , wherein the method further comprises transmitting the push trigger to the push client via one of the first internal interface without a persistent TCP connection or over a cellular network.
14. The apparatus of claim 12 , wherein a connection between the push server and the push client via the first internal interface is a UDP-based connection.
15. The apparatus of claim 12 , wherein a connection between the push server and the push client via the first internal interface is a non-persistent TCP connection.
16. The apparatus of claim 12 , wherein the method further comprises transmitting the mobile device session identifier from the application client to the application server via an interface supporting an application specific TCP connection.
17. The apparatus of claim 16 , wherein the mobile device is set to an idle state after the mobile device session identifier is transmitted to the application server and there is no application data to transmit.
18. The apparatus of claim 17 , wherein the mobile device is set to a non-idle state when a paging message associated with the push trigger is received at the push client.
19. The apparatus of claim 12 , wherein the method further comprises communicating the push trigger to the application client when the push trigger is received at the push client.
20. The apparatus of claim 19 , wherein the method further comprises establishing an application specific TCP-based connection between the application client and the application server to receive data associated with the push trigger when the push trigger is received at the application client.
21. The apparatus of claim 12 , wherein the method further comprises transmitting, from the push server, the registration information when the mobile device moves from a first access network to a second access network if the private IP address or the session identifier changes between the first and second access networks.
22. The apparatus of claim 12 , wherein a TCP connection via the internal first interface with the push client is originated by the push server to deliver the push trigger and then terminated after the push trigger is delivered.
23. A non-transitory computer-readable medium having computer program instructions stored thereon, which, when executed on a processor, cause the processor to perform a method comprising:
receiving, at a push server, registration information for a mobile device from a push client via a first internal interface without persistent TCP connection, the registration information including a private IP address for the mobile device and a mobile device session identifier associated with an instance of an application client on the mobile device;
receiving, at the push server, a push trigger associated with an event of an application server via a second interface exposed outside of a service provider firewall, wherein the push trigger includes a push trigger session identifier identifying the instance of the application client on the mobile device;
determining that the push trigger is associated with the instance of the application client on the mobile device when the push trigger session identifier matches the mobile device session identifier; and
transmitting the push trigger to the instance of the application client on the mobile device by mapping the push trigger session identifier to the private IP address of the mobile device.