ENHANCED PAGER NETWORK

• US 20190230622A1
• Filed: 01/23/2018
• Published: 07/25/2019
• Est. Priority Date: 01/23/2018
• Status: Active Grant

• Current Assignee: Statum Systems Inc.
• Original Assignee: Statum Systems Inc.
• Inventors: Okajima, Stephen Michael, Serebrakian, Arman, Nazarian, Ara
• Granted Patent: US 10,893,505 B2
• Time in Patent Office: Days
• CPC Class Codes: G08B 25/08 using communication transmission lines G08B13/19658, G08B21/0286, G08B25/016 take precedence
• CPC Class Codes: G08B 5/224 Paging receivers with visible signalling details
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 68/02 Arrangements for increasing efficiency of notification or paging channel
• CPC Class Codes: H04W 84/022 One-way selective calling networks, e.g. wide area paging

Abstract

Example embodiments involve an enhanced paging system, executed through novel hardware components, to facilitate a client device to pass incoming messages off, through Wi-Fi or cellular data, to a central server. This central server handles a response request, and sends the message to a corresponding pager address found within a pager network, allowing a closed loop two-way communication handled through a graphical user interface which may be displayed at the client device.

Claims

1. A system comprising:

one or more processors; and

a memory storing instructions that, when executed by at least one processor among the one or more processors, cause the system to perform operations comprising;

transmitting message data from a first client device to a pager module, the message data comprising a pager identifier that identifier the pager module, and a user identifier;

receiving the message data at the pager module based on the pager identifier that identifies the pager module;

identifying, at the pager module, a second client device associated with the user identifier of the message data;

forwarding the message data to the second client device; and

causing display of a notification at the second client device in response to the forwarding the message data to the client device.

2. The system of claim 1, wherein the operations cause the system to perform operations further comprising:

pairing the pager module to one or more client devices that include at least the second client device; and

identifying, at the pager module, the second client device from among the one or more client devices based on the user identifier of the message data.

3. The system of claim 1, wherein the instructions cause the system to perform operations further comprising:

associating the pager identifier that identifies the pager to the user identifier within a registry;

loading a device identifier associated with the user identifier into the pager module, in response to the associating the pager identifier to the user identifier within the registry; and

wherein the identifying the second client device associated with the user identifier is based on the devices identifier loaded into the pager module,

4. The system of claim 1, wherein the message data further comprises a device identifier that identifies the first client device, and the instructions cause the system to perform operations further comprising:

receiving a response to the message data at the second client device;

determining a destination of the response based on the device identifier within the message data; and

delivering the response to the first client device from the second client device.

5. The system of claim 1, wherein the message data further comprises message content, and the causing display of the notification at the second client device further comprises:

causing display of the message content at the second client device.

6. The system of claim 1, wherein the message data further comprises an authentication request, and wherein the causing display of the notification at the second client device includes causing display of the authentication request, and wherein the operations cause the system to perform operation further comprising:

receiving authentication data from the second client device; and

authenticating a user in response to the receiving the authentication data from the second client device.

7. The system of claim 1, wherein the forwarding the message data to the second client device includes forwarding the message data to the second client device via Bluetooth.

8. A method comprising:

transmitting message data from a first client device to a pager module, the message data comprising a pager identifier that identifier the pager module, and a user identifier;

receiving the message data at the pager module based on the pager identifier that identifies the pager module;

identifying, at the pager module, a second client device associated with the user identifier of the message data;

forwarding the message data to the second client device; and

causing display of a notification at the second client device in response to the forwarding the message data to the client device.

9. The method of claim 8, wherein the method further comprises:

pairing the pager module to one or more client devices that include at least the second client device; and

identifying, at the pager module, the second client device from among the one or more client devices based on the user identifier of the message data.

10. The method of claim 8, wherein the method further comprises:

associating the pager identifier that identifies the pager to the user identifier within a registry;

loading a device identifier associated with the user identifier into the pager module, in response to the associating the pager identifier to the user identifier within the registry; and

wherein the identifying the second client device associated with the user identifier is based on the devices identifier loaded into the pager module.

11. The method of claim 8, wherein the message data further comprises a device identifier that identifies the first client device, and the method further comprises:

receiving a response to the message data at the second client device;

determining a destination of the response based on the device identifier within the message data; and

delivering the response to the first client device from the second client device.

12. The method of claim 8, wherein the message data further comprises message content, and the causing display of the notification at the second client device further comprises:

causing display of the message content at the second client device.

13. The method of claim 8, wherein the message data further comprises an authentication request, and wherein the causing display of the notification at the second client device includes causing display of the authentication request, and wherein the method further comprises:

receiving authentication data from the second client device; and

authenticating a user in response to the receiving the authentication data from the second client device.

14. The method of claim 8, wherein the forwarding the message data to the second client device includes forwarding the message data to the second client device via Bluetooth.

15. A non-transitory machine-readable storage medium comprising instructions that, when executed by one or more processors of a machine, cause the machine to perform operations comprising:

transmitting message data from a first client device to a pager module, the message data comprising a pager identifier that identifier the pager module, and a user identifier;

receiving the message data at the pager module based on the pager identifier that identifies the pager module;

identifying, at the pager module, a second client device associated with the user identifier of the message data;

forwarding the message data to the second client device; and

causing display of a notification at the second client device in response to the forwarding the message data to the client device.

16. The non-transitory machine-readable storage medium of claim 15, wherein the instructions cause the machine to perform operations further comprising:

pairing the pager module to one or more client devices that include at least the second client device; and

identifying, at the pager module, the second client device from among the one or more client devices based on the user identifier of the message data.

17. The non-transitory machine-readable storage medium of claim 15, wherein the instructions cause the machine to perform operations further comprising:

associating the pager identifier that identifies the pager to the user identifier within a registry;

loading a device identifier associated with the user identifier into the pager module, in response to the associating the pager identifier to the user identifier within the registry; and

wherein the identifying the second client device associated with the user identifier is based on the devices identifier loaded into the pager module.

18. The non-transitory machine-readable storage medium of claim 15, wherein the message data further comprises a device identifier that identifies the first client device, and the instructions cause the machine to perform operations further comprising:

receiving a response to the message data at the second client device;

determining a destination of the response based on the device identifier within the message data; and

delivering the response to the first client device from the second client device.

19. The non-transitory machine-readable storage medium of claim 15, wherein the message data further comprises message content, and the causing display of the notification at the second client device further comprises:

causing display of the message content at the second client device.

20. The non-transitory machine-readable storage medium of claim 15, wherein the message data further comprises an authentication request, and wherein the causing display of the notification at the second client device includes causing display of the authentication request, and wherein the instructions cause the machine to perform operation further comprising:

receiving authentication data from the second client device; and

authenticating a user in response to the receiving the authentication data from the second client device,