IP Library Granted Patent US 9,438,700
Granted Patent B2
US 9,438,700 · App. 13/735,235 · Granted Sep 6, 2016

System and method for servers to send alerts to connectionless devices

Inventors: Rudy G. Bonefas (Bel Air, MD); Richard K. Sobchack (Eldersburg, MD); James M. Zombek (Boca Raton, FL)
Assignee: Telecommunication Systems, Inc.
H04L69/08F02M25/0809H04L12/66H04L67/2823H04L67/327
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 9,438,700
App. No.
13/735,235
Granted
Sep 6, 2016
Kind
B2
Abstract

A method of sending alerts from servers to client devices is provided. The alert can be generated with a server application and may include customer information. The alert may then be sent to a message router. The message router receives a station ID of the client device based on the customer information. A communication type of the client device can be determined based on the station ID and one or more of a plurality of protocol gateways can be selected based on the communication type. The alert can be forwarded to the selected one or more of the plurality of protocol gateways where it may be formatted for the selected client device. The formatted alert may then be forwarded via the network to the selected client device.

Claims (86)

1. A method of sending a message to a client device, comprising:

retrieving, at a message router, identification information associated with a client device from client information, wherein said identification information includes a device address of said client device;

determining a communication type of said client device based on a size and content of said identification information;

selecting at least one protocol gateway based on said communication type; and

forwarding said message to said selected at least one protocol gateway based on said communication type;

wherein said message is formatted by said selected at least one protocol gateway for transmission to said client device.

2. The method of sending a message to a client device according to claim 1 , wherein:

said client information includes at least one of a customer ID and a port number.

3. The method of sending a message to a client device according to claim 1 , wherein:

said step of determining a communication type further comprises searching a user table to obtain said identification information associated with said customer ID.

4. The method of sending a message to a client device according to claim 1 , wherein:

said step of determining a communication type further comprises searching a local cache of said message router for said identification information associated with a customer ID.

5. The method of sending a message to a client device according to claim 1 , wherein:

said step of determining a communication type further comprises searching a local cache of said message router and a device table for said client device associated with said identification information when both said identification information and a port number are provided.

6. The method of sending a message to a client device according to claim 1 , further comprising:

returning an inactive customer message to a server if no identification information is retrieved.

7. The method of sending a message to a client device according to claim 1 , wherein:

said message is segmented with said selected at least one protocol gateway into message segments before sending said message over a network.

8. The method of sending a message to a client device according to claim 7 , wherein:

said segmented message is assembled at said client device.

9. The method of sending a message to a client device according to claim 1 , wherein:

said message includes at least one of an alert message, a compression flag, an encryption flag, and an acknowledgement flag.

10. The method of sending a message to a client device according to claim 1 , further comprising:

returning an acknowledgement to said selected at least one protocol gateway after receiving said formatted message at said client device.

11. The method of sending a message to a client device according to claim 10 , further comprising:

forwarding said acknowledgement from said selected at least one protocol gateway to a server.

12. The method of sending a message to a client device according to claim 1 , wherein:

said client information is a client information object.

13. The method of sending a message to a client device according to claim 1 , wherein:

said client information includes a customer ID and a device ID.

14. The method of sending a message to a client device according to claim 13 , wherein:

said message includes an active device only flag; and

said device ID can be set to all devices.

15. The method of sending a message to a client device according to claim 14 , further comprising:

searching a local cache of said message router for said identification information if said active device only flag is set and said device ID is specified.

16. The method of sending a message to a client device according to claim 1 , further comprising:

searching a user table for said identification information if said identification information is not located in said local cache.

17. The method of sending a message to a client device according to claim 14 , further comprising:

searching only a user table for active client devices associated with said customer ID if said active device only flag is set and said device ID is set to all devices.

18. The method of sending a message to a client device according to claim 14 , further comprising:

searching a local cache of said message router for said identification information if said active device only flag is not set and said device ID is specified.

19. The method of sending a message to a client device according to claim 1 , further comprising:

searching a device table for said identification information if said identification information is not located in a local cache.

20. The method of sending a message to a client device according to claim 14 , further comprising:

searching a device table for a client device associated with said customer ID if said active only flag is not set and said device ID is set to all devices.

21. The method of sending a message to a client device according to claim 1 , further comprising:

providing each identification information retrieved in said step of retrieving identification information to a server.

22. The method of sending a message to a client device according to claim 1 , further comprising:

providing each identification information retrieved by said message router to a server, before forwarding said message to said at least one protocol gateway.

23. A method of sending a message to a client device, comprising:

retrieving, at a message router, identification information from at least one of customer information and device information, wherein said identification information includes a device address of said client device;

determining, at said message router, a communication type associated with said at least one of customer information and device information based on a size and content of said identification information; and

forwarding said message to at least one protocol gateway associated with said determined communication type;

wherein said message is transmitted with said at least one protocol gateway over a network to said client device.

24. The method of sending a message to a client device according to claim 23 , further comprising:

receiving said message with a transport layer of an application associated with said at least one protocol gateway; and

sending said message from said transport layer to a client application.

25. The method of sending a message to a client device according to claim 23 , wherein:

said message is segmented into message segments with said at least one protocol gateway.

26. The method of sending a message to a client device according to claim 24 , wherein:

said client application assembles said message segments.

27. The method of sending a message to a client device according to claim 23 , wherein:

an acknowledgement is sent from said client device to said at least one protocol gateway once said message is received by said client device.

28. The method of sending a message to a client device according to claim 27 , wherein:

said acknowledgement is sent from said at least one protocol gateway to a server that forwarded said message after receiving said acknowledgement from said client device.

29. The method of sending a message to a client device according to claim 23 , wherein:

said message comprises at least one of an alert message, a client information object including customer ID, device ID, message flag, compression flag, and an encryption flag.

30. The method of sending a message to a client device according to claim 29 , wherein said messages flag specifies at least one of:

whether a server requires an acknowledgement message;

whether said message should be sent only when said client device is currently active; and

whether said at least one protocol gateway should only attempt message delivery once.

31. The method of sending a message to a client device according to claim 23 , wherein:

said message includes an active device only flag and a device ID set to all devices.

32. The method of sending a message to a client device according to claim 23 , wherein said retrieving step comprises:

searching a local cache of said message router for said identification information when an active device only flag is set and a device ID is specified;

searching only a user table for an active client device associated with a customer ID when said active device flag is set and said device ID is set to all devices;

searching a local cache of said message router for said identification information when said active device only flag is not set and said device ID is specified; and

searching a device table for said client device associated with said customer ID when said active device only flag is not set and said device ID is set to all devices.

33. The method of sending a message to a client device according to claim 32 , further comprising:

for said steps of searching a local cache of said message router, searching a database for said identification information if said identification information is not found in said local cache.

34. The method of sending a message to a client device according to claim 23 , further comprising:

providing each of a device ID when said device ID is set to all devices.

35. The method of sending a message to a client device according to claim 23 , further comprising:

sending an inactive message to a server when no device is located and a device ID is set to all devices, otherwise sending a customer not valid message.

36. The method of sending a message to a client device according to claim 23 , wherein:

said message is formatted for said client device with said at least one protocol gateway.

Assignments (5)
SECURITY INTEREST Recorded Nov 16, 2018
From: COMTECH TELECOMMUNICATIONS CORP.; COMTECH EF DATA CORP.; COMTECH XICOM TECHNOLOGY, INC.; COMTECH SYSTEMS, INC.; COMTECH PST CORP.; COMTECH MOBILE DATACOM CORPORATION; ANGELS ACQUISITION CORP.; ARMER COMMUNICATIONS ENGINEERING SERVICES, INC.; COMTECH AEROASTRO, INC.; COMTECH ANTENNA SYSTEMS, INC.; COMTECH COMMUNICATIONS CORP.; COMTECH COMSTREAM, INC.; COMTECH SYSTEMS INTERNATIONAL, INC.; COMTECH TOLT TECHNOLOGIES, INC.; TIERNAN RADYNE COMSTREAM, INC.; COMTECH CPI ELECTRON DEVICES CORP.; COMTECH CPI MICROWAVE CORP.; TELECOMMUNICATION SYSTEMS, INC.; NETWORKS IN MOTION, INC.; SOLVERN INNOVATIONS, INC.; MICRODATA, LLC; MICRODATA GIS, INC.; MAPLE ACQUISITION LLC; NEXTGEN COMMUNICATIONS, INC., A CORPORATION OF MARYLAND; NEXTGEN COMMUNICATIONS, INC., A CORPORATION OF VIRGINIA; OLIVE ACQUISITION LLC
To: CITIBANK, N.A.
Reel/Frame 048104/0080 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 7, 2013
From: BONEFAS, RUDY G.; SOBCHAK, RICHARD K.
To: AETHER SYSTEMS, INC.
Reel/Frame 029576/0319 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 7, 2013
From: AETHER SYSTEMS, INC.
To: TSYS ACQUISITION CORP.
Reel/Frame 029576/0384 →
CHANGE OF NAME Recorded Jan 7, 2013
From: TSYS ACQUISITION CORP.
To: TELECOMMUNICATION SYSTEMS CORPORATION OF MARYLAND
Reel/Frame 029576/0483 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 7, 2013
From: TELECOMMUNICATION SYSTEMS CORPORATION OF MARYLAND
To: TELECOMMUNICATION SYSTEMS, INC.
Reel/Frame 029576/0488 →
Continuity (5)
Continuation 09723285 · Nov 28, 2000
Continuation In Part 09494553 · Jan 31, 2000
Continuation In Part 13735235
Continuation In Part 09694297 · Oct 24, 2000
Related Publication 20130212195A1 · Aug 15, 2013