Verizon Patent and Licensing Inc.

Cellco Partnership

Sm Masudur Rahman

Mohammad Raheel Khalid

Sankar Shanmugam

Samir S Vaidya

Venkat Gaddam

Shahid Ahmed

Ji Hoon Kim

Ying Sun

Zulfiqer Sekender

Manuel Enrique Caceres

Yuk Lun Li

Zhengfang Chen

Paul Berman

David B Murray

Cory Michael Bruno

Gayathri Chandrasekaran

Shiva Narayanabhatla

Jeffrey Dietel

Christopher M Perry

Rosemary McNally

Sonal R Gandhi

Erica Ann Martinez

Marlene Kay Tan Enright

Stephen R Szabo

Zhen Qin

William Cory Hawkins

Systems and methods for generating and transmitting multimedia messaging service (MMS) messages are disclosed. In some implementations, a mobile device presents, at a touchscreen, a visual user interface. The visual user interface includes multiple thumbnails and multiple contact blocks. Each thumbnail identifies a file. Each contact block identifies a contact having a messaging address. The mobile device receives, via the touchscreen, a selection of a first thumbnail from the multiple thumbnails. The mobile device receives, via the touchscreen, an indication of dragging the first thumbnail across the visual user interface to a first contact block. The mobile device transmits, responsive to the dragging of the first thumbnail to the first contact block, the file identified in the thumbnail to the messaging address of the contact identified in the first contact block.

Multimedia messaging service communication using a two way push connection

A primary application and a secondary application installed on a mobile communication device are both configured to obtain input from a user of the device through an application session of the primary application. The primary application transmits a notification to cause the secondary application to begin execution in the background. The primary application further transmits a request for user interface (UI) information to the secondary application. Based on UI information received from the secondary application, the primary application generates a graphical user interface (GUI) including an interface for receiving user input relating to the secondary application. The generated GUI is displayed on the device in the application session of the primary application, and user input relating to the secondary application is received in the application session of the primary application. The primary application then transmits to the secondary application user input identified as relating to the secondary application.

Sharing of a user input interface of an application session of one application between two or more applications

A smart hook system for a store display including a hook configured to hang smart items having a resistor and a capacitor for display in a store. The hook at least one resistive electrical contact configured to come into electrical circuit contact with the resistor of the smart items hanging on the hook, and at least one capacitive electrical contact configured to come into electrical contact with the capacitor of the smart items that are hanging on hook. The smart hook also includes a processor configured to measure the resistance and capacitance of the smart items that are hanging on hook, and determine a quantity of the smart items hanging on the hook and identity of the smart items hanging on the hook based on the measured resistance and capacitance.

Smart hook for retail inventory tracking

Systems and methods for setting up carrier applications within a setup wizard are disclosed. In some implementations, a computing device launches an operating system setup wizard. The computing device launches, from the operating system setup wizard, a carrier-specific setup wizard. The computing device presents, from within the carrier-specific setup wizard, a setup interface for each of a plurality of carrier applications.

System and method to integrate/setup multiple branded applications in the setup wizard

Systems and methods for remote authentication using Single Sign-On (SSO) credentials are disclosed. An implementation includes transmitting a request for an identification code from an application to a wireless service provider, the request provided through an encrypted transport protocol, receiving the identification code as a messaging service message from the wireless service provider, securely routing the received identification code to the requesting application, upon receipt of the identification code at the application, retrieving an authentication token for the application through the encrypted transport protocol and providing the authentication token to an application content server to allow content transfer between the application content server and the application.

Remote authentication method with single sign on credentials

An application installed on a mobile device currently activated for service with a mobile wireless communication network captures information uniquely identifying a currently unsubscribed mobile device. The unique information may be captured from the currently unsubscribed mobile device via any of several short range transfer mechanisms. The application transfers the captured information and other information used to activate the currently unsubscribed mobile device to an activation service of the mobile wireless communication network, and the service activates the currently unsubscribed mobile device. In another example, a self-activation portal system determines an identifier of an owner of an account associated with an identifier provided by a user of a mobile device to be activated for use with a mobile wireless service. The system sends a message to the account owner offering options to accept or decline the activation request.

Remote device activation

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

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 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

Growing community of inventors

Edison, NJ, United States of America

Sm Masudur Rahman