System and Method for Message Dispatching and Communication

• US 20150100628A1
• Filed: 12/12/2014
• Published: 04/09/2015
• Est. Priority Date: 03/13/2012
• Status: Active Grant

• Current Assignee: Semotus Inc.
• Original Assignee: Semotus Inc.
• Inventors: LaPine, Anthony, LaPine, Pamela
• Granted Patent: US 9,674,123 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/245 Query processing
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 51/56 Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 69/162 involving adaptations of sockets based mechanisms secure socket layer H04L63/168
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04M 2203/2011 Service processing based on information specified by a party before or during a call, e.g. information, tone or routing selection
• CPC Class Codes: H04M 2203/2027 Live party detection
• CPC Class Codes: H04M 3/42382 Text-based messaging services in telephone networks such as PSTN/ISDN, e.g. User-to-User Signalling or Short Message Service for fixed networks
• CPC Class Codes: H04M 3/5158 in combination with automated outdialling systems devices for signalling identity of wanted subscriber H04M1/26
• CPC Class Codes: H04M 3/53366 Message disposing or creating aspects
• CPC Class Codes: H04M 7/129 Details of providing call progress tones or announcements

Abstract

A system for secure delivery of messages over disparate networks with disparate protocols, comprising a server computer comprising program code stored in a memory and adapted to manage message delivery received from at least one accredited client computing device, the server computer having at least a plurality of special TCP sockets allowing a plurality of persistent connections, the connections being adapted to deliver messages under different carrier protocols, using at least one of SNPP, WCTP, SMTP, CAP, and OAI carrier types protocols, and the connections being adapted to facilitate the sending of multiple messages in a short time.

Claims

1. A system for secure delivery of messages over disparate networks with disparate protocols, the system comprising:

a server computer comprising program code stored in a memory and adapted to manage message delivery received from at least one accredited client computing device, the server computer having at least a plurality of special TCP sockets allowing a plurality of persistent connections, the connections being adapted to deliver messages under different carrier protocols, using at least one of SNPP, WCTP, SMTP, CAP, and OAI carrier types protocols, and the connections being adapted to facilitate the sending of multiple messages in a short time.

2. The system of claim 1, wherein the message protocol delivers one message to multiple recipients as one message protocol transmission.

3. The system of claim 1, further comprising a meta information database MIDB comprising program code stored in a memory and adapted to allow queuing operations on at least the messages in transmission and previously transmitted within a certain period.

4. The system of claim 3, wherein the MIDB is optimized for multiple queue tasks performed concurrently, allowing scaling to very large peak message volumes, with less degradation of performance.

5. The system of claim 1 further comprising a plurality of software drivers comprising program code stored in a memory and adapted to support workflow type configurations, wherein at least a portion of the plurality of software drivers are made available as plug and play drivers, and further wherein at least a portion of the plurality of drivers are configured alone or jointly to meet a desired workflow as needed for a specific type of workflow delivery defines for a specific message or group of messages.

6. The system of claim 1, wherein the server computer is adapted to facilitate voice type configurations, wherein for voice delivery a sequence of beeps is sent to the receiving end, and wherein after each beep the line is observed for silence, and if the recording stops, or the human finished their greeting, the message is played back.

7. The system of claim 6, further comprising a plurality of fast database computers each comprising program code stored in a memory and adapted to store and provide data to other components of the system, wherein a plurality of TTS output files are cached in the fast database, and wherein for each message a check is made if the message or its sub module are present in the converted format, and wherein, in cases it is available, the already converted file is used in lieu of sending the message to the TTS engine.

8. The system of claim 7, wherein the system keeps two independent databases, a first database being adapted to store and provide a job queue and a second database being adapted to store and provide a dispatch queue, and wherein whenever a job is send to the system, it is first queued in the job queue, and when it gets ready for dispatch, then it is moved from job queue to the dispatch queue, said job queue having two tables, and said dispatch queue having three tables, and wherein a job is then moving the data in the 2 tables (of job queue) to the 3 tables (of dispatch queue) is such a way that the job dispatcher module does not process the job whose move is in-progress, thus avoiding the need to table lock to lock down read access until the write on the tables get finished.

9. A method for secure delivery of messages over disparate networks with disparate protocols, comprising the steps of:

configuring, at a server computer, message manager software program code;

installing, on a user'"'"'s mobile device, a client application;

connecting, via the client application, to the server computer;

registering the client application with the message manager software;

logging the user into the message manager software; and

delivering at least a message to the user'"'"'s client application.

10. The method of claim 9, further comprising the step of configuring the user'"'"'s client application from the server computer.

11. The method of claim 9, further comprising the step of establishing a plurality of access rules for client applications connected to the server computer.