IP Library › Granted Patent US 12707242

Granted Patent B2

US 12707242 · App. 18/747,944 · Granted Aug 11, 2026

Service plan design, user interfaces, application programming interfaces, and device management

Inventors: Gregory G. Raleigh (Incline Village, NV); Jose Tellado (Mountain View, CA); Jeffrey Green (Sunnyvale, CA); James Lavine (Denver, NC); Russell Bertrand Carter, III (San Jose, CA); Justin James (Poway, CA); Laurent An Minh Nguyen (Los Altos, CA)

Assignee: Headwater Research LLC

H04W4/50 G06F3/0482 G06Q30/02 G06T1/0007 H04M15/00 H04M15/765 H04M15/80 H04W4/24

View Patent ↗

Loading inventors, assignments & file history…

Monitor This Case

Get email alerts when status or documents change.

Order Certified Copies

Most orders are placed with the USPTO same day — all within 24 business hours.

Order via The Patent Place →

Pre-filled with this patent's details

Quick Facts

Patent No.: US 12707242
App. No.: 18/747,944
Granted: Aug 11, 2026
Kind: B2

External Links

USPTO Patent Center↗ Full Patent PDF↗

Abstract

There is provided a network message server configured to establish a secure network data connection between the network message server and a mobile end-user device, the secure network data connection supported by a socket including a socket identifier (ID) having at least one of a port address or a port number, receive a request to transmit data to one of a plurality of mobile applications a the mobile end-user device, the request including a device ID corresponding to the mobile end-user device and one of a plurality of mobile application IDs corresponding to the one of the plurality of mobile applications, and generate a network data message based on the request, the network data message including application data and the one of the plurality of mobile application IDs corresponding to the one of the plurality of mobile applications.

Claims (53)

1 . A network message server comprising:

one or more hardware processors configured to:

establish a first network data connection between the network message server and a network application server;

establish a second network data connection between the network message server and a mobile end-user device, the second network data connection supported by a socket including a socket identifier (ID) having at least one of a port address or a port number;

register, by the network message server, a plurality of mobile application IDs each having a corresponding one of a plurality of mobile applications of the mobile end-user device, wherein each of the plurality of mobile application IDs uniquely identifies the corresponding one of the plurality of mobile applications;

receive, by the network message server from the network application server via the first network data connection, a push request to push an application update to one of the plurality of mobile applications of the mobile end-user device without the mobile end-user device requesting the application update for the one of the plurality of mobile applications, the push request including the device ID corresponding to the mobile end-user device and one of the plurality of mobile application IDs corresponding to the one of the plurality of mobile applications;

generate, by the network message server, a network data message based on the push request, the network data message including the application update and the one of the plurality of mobile application IDs corresponding to the one of the plurality of mobile applications; and

transmit, by the network message server for delivery to the mobile end-user device corresponding to the device ID, via the second network data connection supported by the socket, the network data message including the application update and the one of the plurality of mobile application IDs.

2 . The network message server of claim 1 , wherein the one or more hardware processors are further configured to:

map, by the network message server and in response to the request, the device ID to the mobile end-user device, and the one of the plurality of mobile application IDs to the corresponding one of the plurality of mobile applications; and

cause, by the network message server, the corresponding one of the plurality of mobile applications to be updated using the application update.

3 . The network message server of claim 1 , wherein each of the plurality of mobile application IDs uniquely identifies, in an application layer, the corresponding one of the plurality of mobile applications.

4 . The network message server of claim 1 , wherein the one or more hardware processors are further configured to:

provide, by the network message server to the network application server, the device ID and at least one of the plurality of mobile application IDs.

5 . The network message server of claim 1 , wherein the one or more hardware processors are further configured to:

receive, by the network message server from the network application server, a second push request to push a second application update to a second one of the plurality of mobile applications of the mobile end-user device without the mobile end-user device requesting the application update for the second one of the plurality of mobile applications, the second push request including the device ID corresponding to the mobile end-user device and a second one of the plurality of mobile application IDs corresponding to the second one of the plurality of mobile applications;

generate, by the network message server, a second network data message based on the second push request, the second network data message including the second application update and the second one of the plurality of mobile application IDs corresponding to the second one of the plurality of mobile applications; and

transmit, by the network message server for delivery to the mobile end-user device corresponding to the device ID, via the second network data connection supported by the socket, the second network data message including the second application update and the second one of the plurality of mobile application IDs.

6 . The network message server of claim 1 , wherein the one or more hardware processors are further configured to:

7 . The network message server of claim 6 , wherein transmitting the network data message for delivery to the mobile end-user device includes transmitting (i) the network data message, and (ii) the device identifier corresponding to the mobile end-user device, to the network application server corresponding to the network application server ID.

8 . The network message server of claim 6 , wherein the one or more hardware processors are further configured to:

map, by the network message server in response to the request, the network application server ID to the network application server.

9 . The network message server of claim 1 , wherein the plurality of mobile applications include a first mobile application that receives the application update in a first format, and a second mobile application that receives the application update in a second format different from the first format.

10 . The network message server of claim 1 , wherein the one or more hardware processors are further configured to:

buffer, by the network message server, multiple requests, including the request, before transmitting network data messages to mobile end-user devices, including transmitting the network data message to the mobile end-user device.

11 . A method for use by a network message server, the method comprising:

establishing a first network data connection between the network message server and a network application server;

establishing a second network data connection between the network message server and a mobile end-user device, the second network data connection supported by a socket including a socket identifier (ID) having at least one of a port address or a port number;

registering, by the network message server, a device ID for the mobile end-user device;

registering, by the network message server, a plurality of mobile application IDs each having a corresponding one of a plurality of mobile applications of the mobile end-user device, wherein each of the plurality of mobile application IDs uniquely identifies the corresponding one of the plurality of mobile applications;

receiving, by the network message server from the network application server via the first network data connection, a push request to push an application update to one of the plurality of mobile applications of the mobile end-user device without the mobile end-user device requesting the application update for the one of the plurality of mobile applications, the push request including the device ID corresponding to the mobile end-user device and one of the plurality of mobile application IDs corresponding to the one of the plurality of mobile applications;

generating, by the network message server, a network data message based on the push request, the network data message including the application update and the one of the plurality of mobile application IDs corresponding to the one of the plurality of mobile applications; and

transmitting, by the network message server for delivery to the mobile end-user device corresponding to the device ID, via the second network data connection supported by the socket, the network data message including the application update and the one of the plurality of mobile application IDs.

12 . The method of claim 11 , further comprising:

mapping, by the network message server and in response to the request, the device ID to the mobile end-user device, and the one of the plurality of mobile application IDs to the corresponding one of the plurality of mobile applications; and

causing, by the network message server, the corresponding one of the plurality of mobile applications to be updated using the application update.

13 . The method of claim 11 , wherein each of the plurality of mobile application IDs uniquely identifies, in an application layer, the corresponding one of the plurality of mobile applications.

14 . The method of claim 11 , further comprising:

providing, by the network message server to the network application server, the device ID and at least one of the plurality of mobile application IDs.

15 . The method of claim 14 , further comprising:

receiving, by the network message server from the network application server, a second push request to push a second application update to a second one of the plurality of mobile applications of the mobile end-user device without the mobile end-user device requesting the application update for the second one of the plurality of mobile applications, the second push request including the device ID corresponding to the mobile end-user device and a second one of the plurality of mobile application IDs corresponding to the second one of the plurality of mobile applications;

generating, by the network message server, a second network data message based on the second push request, the second network data message including the second application update and the second one of the plurality of mobile application IDs corresponding to the second one of the plurality of mobile applications; and

transmitting, by the network message server for delivery to the mobile end-user device corresponding to the device ID, via the second network data connection supported by the socket, the second network data message including the second application update and the second one of the plurality of mobile application IDs.

16 . The method of claim 11 , further comprising:

registering, by the network message server, a network application server ID for the network application server.

17 . The method of claim 16 , wherein transmitting the network data message for delivery to the mobile end-user device includes transmitting (i) the network data message, and (ii) the device identifier corresponding to the mobile end-user device, to the network application server corresponding to the network application server ID.

18 . The method of claim 16 , further comprising:

mapping, by the network message server in response to the request, the network application server ID to the network application server.

19 . The method of claim 11 , wherein the plurality of mobile applications include a first mobile application that receives the application update in a first format, and a second mobile application that receives the application update in a second format different from the first format.

20 . The method of claim 11 , further comprising:

buffering, by the network message server, multiple requests, including the request, before transmitting network data messages to mobile end-user devices, including transmitting the network data message to the mobile end-user device.