Cellco Partnership

Shahid Ahmed

Venkat Gaddam

Sankar Shanmugam

Sm Masudur Rahman

Venkateswara Rao Gaddam

Amit Gupta

Arulvadivel Venugopal

Nanda Kumar

Gayathri Chandrasekaran

S M Masudur Rahman

Rashmi Naik

Patrick Vito Bellone

Peter Kyagaba Kisuule

Zhen Qin

William Cory Hawkins

A method for updating an application program on a wireless terminal in a controlled manner is disclosed. When, a server receives an inquiry from a wireless terminal for updating an application program, the server determines whether there is an updated program available for updating the application program based on information included in the inquiry from the wireless terminal. The server also determines whether updating the application program of the wireless terminal which sent the inquiry is permitted or not at the time of receiving the inquiry based on the information included in the inquiry and criteria information stored in the server. When the server determines that updating the application for the wireless terminal is available and is permitted, the server sends information necessary for updating the application program to the wireless terminal. Then, the wireless terminal updates the application program.

Method for updating an application program on a wireless terminal in a controlled manner

Disclosed procedures automatically identify a carrier-authorized mobile station and verify an account related identifier associated with the device, in response to start-up of an application in the device. Application start-up causes the device to send a request to an application server, with the device's current IP address, MTN and a device identifier such as MEID or ESN. The server queries an AAA system of the network to retrieve the MTN that has been assigned the IP address. If the retrieved MTN matches the MTN passed to the server in the request, the server queries a network database such as DMD for the device identifier associated with the MTN. A match of the device identifier retrieved from the network database with that passed to the server via the request indicates authenticity of the requesting device and its MTN.

Automatic device authentication and account identification without user input when application is started on mobile station

A server system and a mobile device establish a push data framework for communication. The mobile device includes a push client, and runs one or more applications requiring push data communications. The push client transmits a device authentication and application validation request to a push server. Upon the push server successfully authenticating and validating the device and application, the push client receives a session identifier for establishing a persistent communication connection with the push server. Once established, an application server can push data to the mobile device via the persistent communication session. The session identifier remains valid for an extended period of time, and allows the push client to maintain and re-establish push connections with the push server for the duration of the extended period of time.

Method of device authentication and application registration in a push communication framework

A single computer may be configured to function as a multiple client simulator that tests a push engine by simultaneously simulating multiple clients. The multiple client simulator may be configured to open and simultaneously maintain a large number of connections with the push engine. To facilitate this, a virtual interface module may be used to multiply the effective number of IP addresses of the single computer. The default number of ports that are available for each IP address may also be increased, along with the available number of file descriptors.

Multiple client simulator for push engine

A mobile device includes a session maintainer application, a native application and a shell application and a link to a web application. If a user is seeking to access a native application, and an active session has not been established, user login credential is obtained, a session token is obtained upon verification of the user login credential, and the obtained session token is provided to the native application. If the user is seeking to access a web application, and an active session has not been established, a session token is obtained upon verification of the user login credential and the obtained session token is provided to the shell application. If an active session has been established then the obtained session token is automatically provided to the native or shell application when the user subsequently seeks access to the respective application.

Single sign-on for a native application and a web application on a mobile device

A push messaging platform includes a push server system having push engines (PE) for maintaining persistent connections with mobile devices, and push controllers (PC) for maintaining records of mobile devices' connections. The platform provides high scalability by including a load balancer for distributing connection requests received from mobile devices across the PEs, and dispatchers for forwarding each received message to a PC associated with the mobile device identified in the message. The platform provides high availability by using local backup PCs and remote mirror PCs. A global registered process (GRP) on each PC is linked to a process on a backup PC, and the backup process replaces the GRP if the GRP fails. Local registered processes (LRP) on each PC are linked to corresponding processes on a remotely located mirror PC, and the mirror process replaces the LRP if the LRP fails.

Push messaging platform with high scalability and high availability

Computer storage media may have stored thereon a voicemail application. The voicemail application may be configured to determine whether messages in a voicemail box meet a preservation criterion. If the messages do meet the preservation criterion, the voicemail application may be configured to cause a replica of at least one of the messages to be made and stored outside of the voicemail box. After a message is replicated successfully, it may be deleted from the voice mail box.

Automated voicemail preservation and deletion

A persistent connection is used for real-time or near real-time data transfer from a push platform on a network to a mobile station. To establish and maintain the persistent connection between the mobile station and push platform on the network, various protocols are defined over a packet connection between the mobile station and push platform. The real-time or near real-time data is pushed or sent by the push platform to the mobile station, as the data becomes available from a data source. In particular, heartbeat messages are used to determine whether or not the persistent connection is alive and available for real-time or near real-time data transfer. When the persistent connection is lost, the mobile station uses a retry connection scheme based on the number of connection attempts made by the mobile station for establishing a new persistent connection to the push platform.

IP push platform and connection protocol in a push notification framework

A voicemail message system may process voicemail messages sent by mobile communication devices. A network interface may receive the voicemail messages over a network communication system. Each voicemail message may include metadata relating to the voicemail message containing location information indicative of the location of the mobile communication device at approximately the time the message is sent by the mobile communication device. A voicemail message processing system may cause each message which is received by the network interface to be stored in a message storage system, along with its location information. Related mobile communication devices, telephone switches, and recipient phone call devices are also described.

Mobile-originated voicemail messages with location metadata

An application server provides optimized contents or services obtainable over the Internet to wireless mobile communication devices. The application server, which may be operated by wireless communication provider pre-loads templates and mapping information appropriate for diverse wireless communication device models in its memory. The server provides contents or services requested by the wireless communication devices which is optimized according to the pre-loaded configurations and templates. A wireless communication device receives the optimized contents or services and renders the contents or services for display. The pre-loaded configuration and templates specific to each of the wireless communication devices in server memory enables the wireless communication devices to avoid experience disruption of currently running services and reduce any delay in rendering the requested contents or services.

Method and system for providing contents available on the internet to mobile handset

Disclosed procedures automatically identify a carrier-authorized mobile station and verify an account related identifier (e.g. mobile number) associated with the device, in response to start-up of an application in the device. In an example, application start-up causes the device to send a request to an application server, with the device's current IP address, MTN and a device identifier such as MEID or ESN. The server queries a AAA system of the network to retrieve the MTN that has been assigned the IP address. If the retrieved MTN matches the MTN passed to the server in the request, the server queries a network database such as DMD for the device identifier associated with the MTN. A match of the device identifier retrieved from the network database with that passed to the server via the request indicates perfect authenticity of the requesting device and its MTN.

Growing community of inventors

Monmouth Junction, NJ, United States of America

Shahid Ahmed