# US 9,438,700 B2 · System and method for servers to send alerts to connectionless devices > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 9,438,700 B2 - Document ID: US9438700B2 - Status: Granted - Kind: B2 - Application number: 13/735,235 - Filed: 2013-01-07 - Published: 2013-08-15 - Granted: 2016-09-06 - Earliest claimed: 2000-01-31 - Assignees: TeleCommunication Systems, Inc. - Applicants: TeleCommunication Systems, Inc. - Inventors: Rudy G. Bonefas; Richard K. Sobchack; James M. Zombek - Web page: https://patentgrep.com/patent/US9438700B2 ## CPC - F02M 25/0809: {Judging failure of purge control system} - H04L 12/66: Arrangements for connecting between networks having differing types of switching systems, e.g. gateways - H04L 67/565: Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561) - H04L 67/63: Routing a service request depending on the request content or context - F02M: SUPPLYING COMBUSTION ENGINES IN GENERAL WITH COMBUSTIBLE MIXTURES OR CONSTITUENTS THEREOF - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## 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 ### Claim 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. ### Claim 2 (depends on 1) 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. ### Claim 3 (depends on 1) 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. ### Claim 4 (depends on 1) 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. ### Claim 5 (depends on 1) 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. ### Claim 6 (depends on 1) 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. ### Claim 7 (depends on 1) 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. ### Claim 8 (depends on 7) The method of sending a message to a client device according to claim 7, wherein: said segmented message is assembled at said client device. ### Claim 9 (depends on 1) 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. ### Claim 10 (depends on 1) 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. ### Claim 11 (depends on 10) 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. ### Claim 12 (depends on 1) The method of sending a message to a client device according to claim 1, wherein: said client information is a client information object. ### Claim 13 (depends on 1) 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. ### Claim 14 (depends on 13) 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. ### Claim 15 (depends on 14) 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. ### Claim 16 (depends on 1) 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. ### Claim 17 (depends on 14) 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. ### Claim 18 (depends on 14) 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. ### Claim 19 (depends on 1) 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. ### Claim 20 (depends on 14) 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. ### Claim 21 (depends on 1) 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. ### Claim 22 (depends on 1) 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. ### Claim 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. ### Claim 24 (depends on 23) 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. ### Claim 25 (depends on 23) 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. ### Claim 26 (depends on 24) The method of sending a message to a client device according to claim 24, wherein: said client application assembles said message segments. ### Claim 27 (depends on 23) 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. ### Claim 28 (depends on 27) 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. ### Claim 29 (depends on 23) 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. ### Claim 30 (depends on 29) 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. ### Claim 31 (depends on 23) 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. ### Claim 32 (depends on 23) 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. ### Claim 33 (depends on 32) 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. ### Claim 34 (depends on 23) 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. ### Claim 35 (depends on 23) 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. ### Claim 36 (depends on 23) 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.