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.