US10251044B2 - System and method for two-way message transmission on mobile platforms for emergency and non-emergency communications - Google Patents

System and method for two-way message transmission on mobile platforms for emergency and non-emergency communications Download PDF

Info

Publication number
US10251044B2
US10251044B2 US14/507,967 US201414507967A US10251044B2 US 10251044 B2 US10251044 B2 US 10251044B2 US 201414507967 A US201414507967 A US 201414507967A US 10251044 B2 US10251044 B2 US 10251044B2
Authority
US
United States
Prior art keywords
system
platform
single
backend facility
system backend
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
US14/507,967
Other versions
US20150099482A1 (en
Inventor
Anthony Schmitz
Alexandros Tsepetis
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
SWN Communications Inc
Original Assignee
SWN Communications Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US201361888565P priority Critical
Priority to US201361888569P priority
Application filed by SWN Communications Inc filed Critical SWN Communications Inc
Priority to US14/507,967 priority patent/US10251044B2/en
Publication of US20150099482A1 publication Critical patent/US20150099482A1/en
Priority claimed from US15/177,254 external-priority patent/US10270915B2/en
Priority claimed from US15/259,128 external-priority patent/US10257360B2/en
Assigned to SWN Communications, Inc. reassignment SWN Communications, Inc. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: SCHMITZ, ANTHONY F., TSEPETIS, ALEXANDROS
Assigned to ARES CAPITAL CORPORATION reassignment ARES CAPITAL CORPORATION SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: EMERGENCY COMMUNICATIONS NETWORK, LLC, SWN COMMUNICATIONS INC.
Publication of US10251044B2 publication Critical patent/US10251044B2/en
Application granted granted Critical
Application status is Active legal-status Critical
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/18File system types
    • G06F16/1873Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files
    • G06F17/3023
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages
    • H04L51/04Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H04L51/043Real-time or near real-time messaging, e.g. instant messaging [IM] use or manipulation of presence information in messaging
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages
    • H04L51/24Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages with notification on incoming messages
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/04Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12Messaging; Mailboxes; Announcements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W64/00Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1895Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for short real-time information, e.g. alarms, notifications, alerts, updates

Abstract

A method of transmitting emergency and non-emergency communications between a system backend facility (system) and at least one mobile platform (platform), the method comprising establishing a communication link between the system and the platform, providing a single-action voice calling module of the platform for communicating with the system, providing a message reception module of the platform for receiving a message sent from the system, providing a single-action location information transmission module of the platform for sending location information of the platform to the system, providing a single-action location information extraction module of the system for locating at least one recipient associated with the platform based on a predetermined attribute of the platform, and providing a single-action information dispatch module of the system for sending information to the located at least one recipient associated with the platform via the first protocol.

Description

1. FIELD OF DISCLOSURE

The present disclosure relates to the field of communications systems in general and, two-way message transmission on mobile platforms for emergency and non-emergency communications in particular. An end user is provided with an ability to download an application onto a mobile communication device wherein the application allows the end user to receive, interact with, and initiate various types of two-way messaging.

2. BRIEF DESCRIPTION OF RELATED ART

Traditionally, an end user can send and receive messages on a mobile communication device through a limited number of pathways including, for example, SMS (“short message service” for point to point communications). There are inherent limitations of the current SMS systems. As a delivery modality, SMS presents numerous challenges. For example, SMS message transmission may typically carry limited payloads of anywhere from 140 to 1200 characters. Further, SMS is a flat and only text-based modality which is unable to deliver rich text format files in a cost effective manner. Also, certain international markets may prohibit SMS delivery via active censorship. Likewise, SMS does not provide assurance of guaranteed delivery by the underlying carriers or delivery notification. Furthermore, SMS delivery may be a relatively expensive choice of message transmission in both domestic and international markets. Similarly, SMS diagnostics are relatively expensive and time consuming. Accordingly, there is a need for a reliable and cost effective system and method of data transmission which can transmit large payloads, which can support both text-based and non-text based data transmission in both domestic and international markets in spite of active censorship and which can support time and cost effective diagnostic systems. Also, conventional SMS does not provide a secured message transmission for dispatching sensitive information, in contrast, messages sent via SMS are typically sent unencrypted over the wire. Finally, a need for group members to share information via call conferencing exists in the modern business world. Existing SMS systems are unable to provide conference calling capability to the modern business world.

3. SUMMARY OF THE INVENTION

The present invention provides a method of transmitting emergency and non-emergency communications between a system backend facility and at least one mobile platform, the method comprising establishing a communication link between the system and the platform, providing a single-action voice calling module of the platform for communicating with the system, providing a message reception module of the platform for receiving a message sent from the system, providing a single-action location information transmission module of the platform for sending location information of the platform to the system, providing a single-action location information extraction module of the system for locating at least one recipient associated with the platform based on a predetermined attribute of the platform and providing a single-action information dispatch module of the system for sending information to the located at least one recipient associated with the platform via the first protocol.

According to one embodiment, a method of transmitting emergency and non-emergency communications between a system backend facility and at least one mobile platform is provided, the method comprising: establishing a communication link between the system backend facility and the at least one mobile platform via a first protocol providing a single-action voice calling module of at least one mobile platform for communicating with the system backend facility via a first client; providing a message reception module of the at least one mobile platform for receiving a message sent from the system backend facility; providing a single-action location information transmission module of the at least one mobile platform for sending location information of the at least one mobile platform to the system backend facility; providing a single-action location information extraction module of the system backend facility for locating at least one recipient associated with the at least one mobile platform based on a predetermined attribute of the at least one mobile platform to provide a located at least one recipient associated with the at least one mobile platform; and providing a single-action information dispatch module of the system backend facility for sending information to the located at least one recipient associated with the at least one mobile platform via the first protocol.

According to another embodiment, an information transmission system for facilitating communications between a system backend facility and at least one mobile platform is provided, the system comprising: a first protocol to establish a communication link between the system backend facility and at least one mobile platform; a single-action voice calling module of the at least one mobile platform to communicate with the system backend facility via a first client; a message reception module of the at least one mobile platform to receive a message sent from the system backend facility; a single-action location information transmission module of the at least one mobile platform to send location information of at least one mobile platform to the system backend facility; a single-action location information extraction module of the system backend facility to locate at least one recipient associated with the at least one mobile platform based on the a predetermined attribute of the at least one mobile platform; and a single-action information dispatch module of the system backend facility to send information to the located at least one recipient associated with the at least one mobile platform via the first protocol.

4. BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a token screen interface of the disclosed system;

FIG. 2 illustrates an exemplary representation of a login screen of the disclosed system;

FIG. 3 displays a menu screen interface of the disclosed system;

FIG. 4 indicates an alert center interface of the disclosed system;

FIG. 5 shows a details interface of the disclosed system;

FIG. 6 illustrates a lockbox details interface of the disclosed system;

FIG. 7 depicts an incoming call acceptance/rejection interface of the disclosed system;

FIG. 8 shows an incoming call status indicator interface of the disclosed system;

FIG. 9 indicates a graphic representation of a dial pad interface of the disclosed system;

FIG. 10 displays an outgoing call status indicator interface of the disclosed system;

FIG. 11 shows an outgoing call control indicator interface of the disclosed system;

FIG. 12 indicates a device information display interface of the disclosed system; and

FIG. 13 depicts a system diagram of the disclosed invention according to a preferred embodiment of the disclosed invention.

5. DETAILED DESCRIPTION OF THE INVENTION

The disclosed invention herein suggests an alternative method of communication which not only circumvents the aforementioned inherent limitations of the SMS system, but also provides other useful features. The invention that is the subject of this patent application pertains generally to the field of communications systems. The invention relates to an advanced set of use cases using a mobile communication device. In one embodiment of the disclosed invention an end user application is downloaded on a mobile communication device of an end user. The downloaded application residing on the mobile communication device leverages mobile platform technology to allow the end user to engage in two-way message communication by sending and receiving messages via the downloaded application. As would be understood by one of ordinary skill in the art, every aspect of the present invention may be implemented by a computing device and it would likely be more than one computing devices. The term computing device and/or device may include, without limitation, a personal computer, laptop, handheld device, smart phone, iPhone®, Ipad®, Galaxy® or any other device that may be introduced in the future.

The disclosed system may include a modality for two-way text message transmission to one or more mobile platform recipients for emergency and non-emergency communications that utilizes either the Transmission Control Protocol (TCP) or Internet Protocol (IP), or Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), between inter-cooperating processes from the system backend to the mobile application. Furthermore, the disclosed system may include a one-click mobile platform voice calling capability via a Session Initiation Protocol (SIP) or Real-time Transport Protocol (RTP) client to a backend Interactive voice response (IVR) or an inbound call facility or Customer Support staff member. The term single-action would include one-click actions.

The disclosed system may also include a voice message reception capability on the mobile platform as the result of a message sent to one or more mobile platform recipients. Likewise the disclosed system may comprise a capability for the backend to send a file (or files) to one or more recipients via TCP/IP/SIMPLE protocols. Further, the disclosed system may offer a capability from the mobile platform permitting a mobile user to send a one-click message to the backend with location information and a capability that permits the send word now (SWN) backend to locate and send messages to mobile platform applications based solely on their physical location.

It is noted that the depicted interfaces as described herein may be configured to add and subtract softkey functions or to adjust existing functions in different versions of the application. Features and functionality may be embodied in many different forms and should not be construed to limit the scope of the disclosure related to this invention. Many other functions (not shown) may be added to enhance the functionality of the invention. Conversely, not all of the functions need to be present on a particular version in order for the invention to function. Versions of the invention can include different configurations of functionalities. Additional systems, methods, features and embodiments of the invention will be, or will become, apparent to someone who is skilled in the art of examining the Figures and detailed description set forth below. All such additional systems, methods, features and embodiments are included within this description and are within the scope of the claimed subject matter and are protected by the claims that follow.

Now referring to FIG. 1 depicting a token screen interface of the disclosed system. Interface 100 as shown in FIG. 1 is displayed on a communication device (not shown in FIG. 1). Alternatively, interface 100 may also be any other communication device including but not limited to a smart phone, a tablet, a personal computer, a gaming device and the like. A header 110 may include pertinent information regarding the communication device such as a device identification number 130, a device communication range indicator 140, a time indicator 150, an airplane mode indicator 120, and a power indicator 160. A user may be prompted to enter a validation token at an input field 170 and select a response submission link 180 upon entering the validation token.

After providing a valid token the user is prompted to provide user credentials at a login screen of the disclosed system, as displayed in FIG. 2. As described above, a header 210 on the interface 200 may include pertinent information regarding the communication device. The user is prompted to provide an alphanumeric user identification string 220 and an alphanumeric password string 230 before selecting a sign in link 240. When the user provides a valid user identification string 220 and a valid password string 230, an interface 300 illustrated in FIG. 3 is displayed to the user. Alternatively, if the user is unable to provide either a valid user identification string 220 or a valid password string 230, the user may select forgot password link 250 to get further assistance for resolving login issues.

FIG. 3 depicts a menu screen interface of the disclosed system. Interface 300 as shown in FIG. 3 is displayed on a communication device, not shown in FIG. 3. A menu 320 is displayed on the interface 300 which may contain a home link 310 which points to the alert center, and a return to main menu option 330 to return to the main menu page. Further, the menu 320 may include an alert center option 340, a lock box option 350, a contact customer support option 370, a settings option 390, and an about option 392. The disclosed system has an ability to attach different types of files to an outgoing message for example, a zip file 360, a text file 380 and an image file 394 can be attached to a message as shown in FIG. 3. In one embodiment of the disclosed system, a vanish option may be selected for delivering a confidential message. The vanish option may cause the confidential message to vanish upon the recipient viewing the confidential message effectuating a secured dispatch of the confidential information. This feature may be helpful in protecting confidential information dispatched to the recipient's lost or stolen computing devices.

After performing desired operations on the interface 300, a user may select a log out option 396 to terminate the session. Alternatively, if the user selects the alert center option 340 on the interface 300, then an interface 400 which is displayed in FIG. 4 is displayed to the user. Similarly, if the user selects the lockbox option 350 on the interface 300, then interface 600 which is displayed in FIG. 6 is displayed to the user. Likewise, if the user selects the about option 392 on the interface 300, then an interface 1200 which is displayed in FIG. 12 is displayed to the user.

FIG. 4 depicts an alert center interface 400 of the disclosed system. The alert center interface 400 may be displayed when a user selects the alert center option 340 in FIG. 3 via a single-action (which may include a one-click or screen stroke). An example of the alert center is depicted in FIG. 4. The alert center interface 400 illustrates an alert center listing with an emergency manager, a lockbox Item, an outgoing call, as well as an incoming call instance. The alert center interface 400 as shown in FIG. 4 is displayed on a communication device. At the top, a return to main menu option 410 is provided to return to the main menu page and an alert center option 420 are displayed on the interface 400. The alert center interface 400, when selected, may display notifications such as an incoming call notification 430, and an outgoing call notification 480, each of these notifications may contain additional information regarding the notifications such as caller identification information 432, call date information 434, call time information 436 and call duration information 438.

Additionally, the alert center interface 400 may display notifications pertaining to a set of received files such as HTML files 470 and 490 along with a zip file 440, a text file 450, and an image file 460. Each of the received file notifications may contain additional information regarding the received files such as file receipt date information 454, file receipt time information 456 and file lock information 452.

FIG. 5 depicts a detail interface of a preferred embodiment of the disclosed system. The disclosed system may allow a message sender to send one or more files to one or more recipients via the TCP/IP or SIMPLE protocol. An interface 500 may display a header 510 to display pertinent information regarding the communication device. The name of a received file 530 is displayed on the interface 500.

A link 550 may be the place where the received file 530 is stored by the system. There may also be an icon depicting a file. A user may select to view the received file 530 by selecting the link 550 (or the icon depicting the file). Alternatively, the user may select to delete the received file 530 by selecting a delete option 540. Notably, the delete option 540 may be selected by a user either before or after reviewing the received file 530. In other words, the user has an ability to delete the received file 530 without having to review the received file 530. After performing desired operations on the received file 530, the user may select return to main menu option 520 to return to the alert center interface 400 depicted in FIG. 4.

When the user selects to view the file by selecting the link 550, then an interface 600 shown in FIG. 6 is displayed. FIG. 6 illustrates a lockbox details interface according to one embodiment of the disclosed system. The interface 600 may display a header 610 to display pertinent information regarding the communication device. The name of a received file 630 may be displayed on the interface 600. The file 640 may also be displayed on the interface 600. The user may select return to main menu option 620 to return to the alert center interface 400 depicted in FIG. 4. At this point, if the vanish option is turned on, the confidential message would vanish upon the recipient viewing the confidential message effectuating a secured dispatch of the confidential information. This feature may be helpful in protecting confidential information dispatched to the recipient's lost or stolen computing devices.

As depicted in FIG. 6, a file recipient may view the received files using the reader associated with the attendant Multi-purpose Internet Mail Extensions (MIME) type. In a preferred embodiment of the disclosed system, version control may be maintained between a system backend and a file repository situated on the communication device. Reporting may be provided by the system backend indicating information including but not limited to a name of the file, a name of the recipient receiving the file, name of the sender, time of file dispatch and time of file receipt.

FIG. 7 depicts an incoming call acceptance/rejection interface according to one embodiment of the disclosed system. FIG. 7 illustrates the voice message reception capability of the disclosed system. The interface 700 may display a header 710 to display pertinent information regarding the communication device 101, not shown in FIG. 7. An incoming call pop up window 720 may be displayed on the interface 700. The incoming call pop up window 720 may additionally display call identification information such as a calling number 730 initiating an incoming call for the called party. The called party may select to answer the incoming call by selecting an answer option 750 or reject the incoming call by selecting by selecting a decline option 740.

In a preferred embodiment of the disclosed system, the system may send a voice message to one or more recipient applications on the mobile platform via SIP/RTP. If, as part of that message, the recipient is invited to join a conference call they can use Dual-tone multi-frequency signaling (DTMF) tones to acknowledge the invitation and be connected to a conference bridge. In addition, recipients can use DTMF tones to answer multiple choice questions sent by the message sender. If the called party selects the answer option 750 then an interface 800 illustrated in FIG. 8 is displayed.

FIG. 8 depicts an incoming call status indicator interface of the disclosed system. The interface 800 may display a header 810 to display pertinent information regarding the communication device. Dashboard 820 displayed on the interface 800 depicts the details of an ongoing phone call. For example, phone number of a calling party 840 may be displayed on the interface. Similarly, a status of an ongoing call 850 may also be displayed on the interface 800. As displayed in FIG. 8 telephone number 1111111111 is a coordinator of the present call. Phone number 9610009 is in the connected state. A user of the device may use features on the phone such as keypad 860 to enter information. The mute button 870 may allow the user to mute the speakers of the device while volume 880 can be used to increase or decrease the call volume. Ultimately, the user may end the phone call by selecting end option 890.

FIG. 9 indicates a graphic representation of a dial pad interface of the disclosed system. Interface 900 illustrates an outbound voice calling capability according to a preferred embodiment of the disclosed invention. The interface 900 may display a header 910 to display pertinent information regarding the communication device. The input display area 920 on the interface 900 depicts an input provided by the user of the phone (also referred to as communication device). The claims refer to a mobile platform, which would typically be an application installed on the communication device. Interface 900 depicts the input 930 as number 56, which may be provided by the user of the device. Numeric keys 940 may be selected by the user to provide input 930. Likewise, alphabetic keys may also be used by the user of the device to provide input 930. The process of providing input may be aborted by the user of the device by selecting cancel option 960.

FIG. 10 displays an outgoing call status indicator interface of the disclosed system. The interface 1000 may display a header 1010 to display pertinent information regarding the communication device. A call dashboard 1020 may be displayed on the interface 1000 indicating the details of an ongoing phone call. For example, phone number of a call party 1030 may be displayed on the interface 1000. Similarly, a status of an ongoing call 1040 may also be displayed on the interface 1000. As displayed in FIG. 10, telephone number 955003 is in the connected state. A user of the device may not use the features on the phone such as mute option 1050, pause option 1060, and volume option 1070 since the features are currently disabled. Ultimately, the user may end the phone call by selecting end call option 1080.

FIG. 11 shows an outgoing call control indicator interface of the disclosed system. The interface 1100 may display a header 1110 to display pertinent information regarding the communication device. A call dashboard 1120 may be displayed on the interface 1100 indicating the details of an ongoing phone call. For example, phone number 1130 of a call party may be displayed on the interface 1100. Similarly, a status of an ongoing call 1140 may also be displayed on the interface 1100. As displayed in FIG. 11, the telephone number 955003 is in the connected state. A user of the device may use features on the phone such as mute option 1150 to mute speakers of the device. The conversation between the user of the device and the phone number 955003 may be paused by selecting the pause option 1160. The volume option 1170 can be used to increase or decrease the call volume. Ultimately, the user may end the phone call by selecting end call option 1180.

FIG. 12 depicts a device information display interface of the disclosed system. Interface 1200 as shown in FIG. 12 is displayed on a communication device. A menu 1220 is displayed on the interface 1200 which may contain a home link 1210 which points to the alert center, and a return to main menu option 1230 which can be selected to return to the main menu page. Further, the menu 1220 may include an alert center option 1240, a lock box option 1250, a contact customer support option 1270, a setting option 1290, and an about option 1292. The return to main menu option 1230 displays different types of files that can be attached to an outgoing message for example, a zip file 1260, a text file 1280 and an image file 1294.

After performing desired operations on the interface 1200, a user may select a log out option 1298 to terminate the session. Alternatively, if the user selects the alert center option 1240 on the interface 1200, then an interface 400 which is displayed in FIG. 4 is displayed to the user. Similarly, if the user selects the lockbox option 1250 on the interface 1200, then a lockbox interface is displayed to the user. Likewise, if the user selects the about option 1292 on the interface 1200, then a window 1297 is displayed an interface 1200 which indicates the sip number 1295 of the device and the version number 1296 of the software on the device.

In one embodiment the disclosed system may include the capability to send a one-click instant message to the service backend indicating complete location information. This capability is typically used during a crisis or emergency situation. When location information is transmitted, the location information may subsequently be identified and displayed in a map with a push pin indicating who instantiated the one-click instant message and from which location the one-click instant message was initiated. In addition to the SIP/RTP, an audio channel will be initiated to a hard coded emergency response number for immediate audio transmittal. Need to review the language in this last sentence.

FIG. 13 depicts a system diagram of the disclosed invention. The information transmission system 1300 shown in FIG. 13 is an information transmission system for facilitating communications between a system backend facility 1320 and at least one mobile platform 1310. The system comprises a first protocol 1318 for establishing a communication link between the system backend facility 1320 and the at least one mobile platform 1310. In one embodiment the first protocol 1318 may be a transmission control protocol (TCP), and the system backend facility 1320 may be an interactive voice response (IVR) system. In another embodiment, the first protocol 1318 may be a Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE) protocol and the system backend facility 1320 may comprise a customer service representative.

A single-action voice calling module 1312 is also part of the at least one mobile platform 1310. The single-action voice calling module 1312 is configured to communicate with the system backend facility 1320 via a first client 1326. In one embodiment of the disclosed invention the first client 1326 may employ a session initiation protocol (SIP). Further, a message reception module 1314 is also contained in the at least one mobile platform 1310 and is configured to receive a message sent from the system backend facility 1320.

A single-action location information transmission module 1316 of the at least one mobile platform 1310 is configured to send location information of the at least one mobile platform 1310 to the system backend facility 1320. The system backend facility 1320 may comprise a single-action location information extraction module 1324 for locating at least one recipient associated with the at least one mobile platform 1310 based on a predetermined attribute of the at least one mobile platform 1310.

A single-action information dispatch module 1322 of the system backend facility 1320 is configured to send information to the located at least one recipient associated with the at least one mobile platform 1310 via the first protocol 1318. In one embodiment of the disclosed invention, the single-action information dispatch module 1322 may be configured to transmit a set of emergency and non-emergency communications between the system backend facility 1320 and at least one mobile platform 1310. In another embodiment of the disclosed invention, the single-action information dispatch module 1322 may be configured to transmit a two-way text message communication between the system backend facility 1320 and at least one mobile platform 1310.

In yet another embodiment, the first protocol 1318 may be configured to establish a communication link between a set of inter-cooperating processes from the system backend facility 1320 and at least one mobile platform 1310. Additionally, the first protocol 1318 may be configured to establish a communication link between the system backend facility 1320 and a mobile application residing on at least one mobile platform 1310. The single-action information dispatch module 1322 may be configured to transmit a two-way data message communication between the system backend facility 1320 and the at least one mobile platform 1310.

In one embodiment of the disclosed invention, the backend facility 1320 may send messages to mobile platform recipients based on their physical location. A user (which may be located at the backend facility 1320) may draw a shape on a map interface. For example, the user may circle (using their finger on a computing tablet) a geographical area. The mobile platform application would have the ability to respond to backend originated location queries to determine a recipient's eligibility for receiving a message from the backend facility 1320. If a recipient who receives a location query is within the map boundary defined by the user at the backend facility 1320, then the recipient may receive the message.

The disclosed system may allow a message sender to send a message to one or more message recipients via the TCP/IP/SIMPLE protocols to an application on the mobile platform. The transmitted message may contain an unlimited text character count. The disclosed system may provide 100% support of rich text/html messages in addition to guaranteed end message delivery with real-time receipt and integrated diagnostics. Furthermore, the disclosed system may provide an ability to circumvent any censorship constraints that are prevalent in different parts of the world. The disclosed system may reduce cost and expense associated with message transmission. Additionally, the message recipient may view/download file attachments and respond to the alert with a DTMF answer to a multiple choice question.

Claims (17)

The invention claimed is:
1. A cost effective method of transmitting emergency and non-emergency, text based and non-text based full duplex communications between a system backend facility and a plurality of mobile platforms (platforms), the method comprising:
establishing a communication link between the system backend facility and the platforms via a first protocol;
communicating a message to the system backend facility via a first client by executing a set of single-action voice calling instructions at the platforms;
receiving communication from the system backend facility by executing a set of message reception instructions at the platforms;
designating, by the system backend, an emergency area on a map and transmitting a message to a selective set of platforms by executing the single-action information dispatch instructions, wherein the selective set of platforms have confirmed their presence within the designated emergency area in response to receiving location queries from the system backend;
sending location information of the platform to the system backend facility by executing a set of single-action location information transmission instructions at the platform;
identifying at least one recipient associated with the platform based on the respective location of the platform by executing a set of single-action location information extraction instructions at the system backend facility; and
displaying an invitation to join a conference call on each identified recipient's mobile platform by executing the single-action information dispatch instructions.
2. The method of claim 1, further comprising the steps of:
transmitting, by executing the single-action information dispatch instructions, emergency and non-emergency voice communications between the system backend facility and the platform;
transmitting, by executing the single-action information dispatch instructions, a two-way text message communication between the system backend facility and the platform; and
transmitting, by executing the single-action information dispatch instructions, a two-way data message communication between the system backend facility and the platform.
3. The method of claim 1, wherein the first protocol is at least one of: a transmission control protocol (TCP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE) protocol, and a session initiation protocol (SIP).
4. The method of claim 1, wherein the first protocol is configured to establish a communication link between a set of inter-cooperating processes from the system backend facility and the platform.
5. The method of claim 1, further comprising the step of:
establishing a communication link between the system backend facility and a mobile application residing on the platform.
6. The method of claim 1, further comprising the step of:
transmitting, by executing the single-action information dispatch instructions, a set of messages to the at least one recipient associated with the platform solely based on the physical location of the platform.
7. The method of claim 1, further comprising availing guaranteed end message delivery with real-time receipt and integrated diagnostics.
8. A cost effective information transmission system for facilitating text based and non-text based communications between a system backend facility and at least one mobile platform, the system comprising a logic circuit configured to execute instructions to perform the following operations:
establish a communication link between the system backend facility and the platform via a first protocol;
communicate a message to the system backend facility via a first client by executing a set of single-action voice calling instructions at the platform;
receive communication from the system backend facility by executing a set of message reception instructions at the platform;
send location information of the platform to the system backend facility by executing a set of single-action location information transmission instructions at the platform;
identify at least one recipient associated with the platform based on the location of the at least one mobile platform by executing a set of single-action location information extraction instructions at the system backend facility; and
securely dispatch the message to the identified at least one recipient via the first protocol platform by executing a set of single-action information dispatch instructions at the system backend facility.
9. The system of claim 8, wherein the single-action information dispatch instructions are operable to transmit a set of emergency and non-emergency communications between the system backend facility and the platform.
10. The system of claim 8, wherein the single-action information dispatch instructions are operable to transmit a two-way text message communication between the system backend facility and the-platform.
11. The system of claim 8, wherein the single-action information dispatch instructions are operable to transmit a two-way data message communication between the system backend facility and the platform.
12. The system of claim 8, wherein the first protocol is a transmission control protocol (TCP), and the system backend facility is an interactive voice response (IVR) system.
13. The system of claim 8, wherein the first protocol is a Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE) protocol and the system backend facility comprises a customer service representative.
14. The system of claim 8, wherein the first client employs a session initiation protocol (SIP).
15. The system of claim 8, wherein the first protocol is configured to establish a communication link between a set of inter-cooperating processes from the system backend facility and the platform.
16. The system of claim 15, wherein the predetermined attribute is the physical location of the at least one recipient and wherein the system is configured to transmit a set of messages to the at least one recipient associated with the platform solely based on the physical location of the platform.
17. The system of claim 8, wherein the first protocol is configured to establish a communication link between the system backend facility and a mobile application residing on the platform.
US14/507,967 2013-10-09 2014-10-07 System and method for two-way message transmission on mobile platforms for emergency and non-emergency communications Active US10251044B2 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US201361888565P true 2013-10-09 2013-10-09
US201361888569P true 2013-10-09 2013-10-09
US14/507,967 US10251044B2 (en) 2013-10-09 2014-10-07 System and method for two-way message transmission on mobile platforms for emergency and non-emergency communications

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US14/507,967 US10251044B2 (en) 2013-10-09 2014-10-07 System and method for two-way message transmission on mobile platforms for emergency and non-emergency communications
US15/177,254 US10270915B2 (en) 2013-10-09 2016-06-08 System and method to improve management during a conference call
US15/259,128 US10257360B2 (en) 2013-10-09 2016-09-08 System and method to improve management during a conference call

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US14/305,181 Continuation-In-Part US9820119B2 (en) 2013-10-09 2014-06-16 Method and systems for lockbox secured file transmission

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US15/177,254 Continuation-In-Part US10270915B2 (en) 2013-10-09 2016-06-08 System and method to improve management during a conference call
US15/259,128 Continuation-In-Part US10257360B2 (en) 2013-10-09 2016-09-08 System and method to improve management during a conference call

Publications (2)

Publication Number Publication Date
US20150099482A1 US20150099482A1 (en) 2015-04-09
US10251044B2 true US10251044B2 (en) 2019-04-02

Family

ID=52777343

Family Applications (3)

Application Number Title Priority Date Filing Date
US14/305,181 Active 2035-08-13 US9820119B2 (en) 2013-10-09 2014-06-16 Method and systems for lockbox secured file transmission
US14/305,160 Active 2034-10-02 US9485643B2 (en) 2013-10-09 2014-06-16 Method and systems for secure message transmission
US14/507,967 Active US10251044B2 (en) 2013-10-09 2014-10-07 System and method for two-way message transmission on mobile platforms for emergency and non-emergency communications

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US14/305,181 Active 2035-08-13 US9820119B2 (en) 2013-10-09 2014-06-16 Method and systems for lockbox secured file transmission
US14/305,160 Active 2034-10-02 US9485643B2 (en) 2013-10-09 2014-06-16 Method and systems for secure message transmission

Country Status (1)

Country Link
US (3) US9820119B2 (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9756115B2 (en) * 2012-11-08 2017-09-05 Gpvtl Canada Inc. System and method of secure file sharing using P2P
KR20160101604A (en) * 2015-02-17 2016-08-25 삼성전자주식회사 Device for Determining Sameness Between Difference Languages and Method thereof
EP3139259B1 (en) * 2015-03-31 2019-01-09 Huawei Technologies Co., Ltd. Method and device for processing new message associated with application
US10305850B1 (en) * 2016-11-15 2019-05-28 Majid Aziz Enhanced instant messaging social network system

Citations (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020107930A1 (en) 2001-02-06 2002-08-08 International Business Machines Corporation Method of setting destinations of electronic mail
US20030105716A1 (en) 2001-12-03 2003-06-05 Sutton Lorin R. Reducing duplication of files on a network
US6711608B1 (en) 1998-09-23 2004-03-23 John W. L. Ogilvie Method for including a self-removing code in a self-removing message
US20040267707A1 (en) 2003-06-17 2004-12-30 Frederick Hayes-Roth Personal portal and secure information exchange
US20050044159A1 (en) * 2001-10-19 2005-02-24 Aki Niemi Messaging system
US20050091289A1 (en) 2003-10-24 2005-04-28 Microsoft Corporation File sharing in P2P group shared spaces
US20050169248A1 (en) * 2004-02-04 2005-08-04 Nortel Networks Limited Method and apparatus for providing in-band location information in an emergency response network
US20050181775A1 (en) 2004-02-13 2005-08-18 Readyalert Systems, Llc Alert notification service
US7224373B1 (en) 2000-04-07 2007-05-29 Danger, Inc. Adjustable data processing display
US20080140732A1 (en) 2006-12-11 2008-06-12 Bentley System, Inc. Method and system for sharing file based data
US20090182833A1 (en) 2008-01-15 2009-07-16 Swaminathan Balasubramanian Sharing Material in a Master-Slave Configuration Using an Instant Messaging Infrastructure
US20100003949A1 (en) * 2008-07-03 2010-01-07 Embarq Holdings Company, Llc Emergency data message router database
US7729684B1 (en) * 2001-11-01 2010-06-01 Garmin Ltd. Combined global positioning system receiver and radio
US20120054156A1 (en) 2010-08-30 2012-03-01 Nasuni Corporation Versioned file system with fast restore
US20120089569A1 (en) 2010-10-12 2012-04-12 Nasuni Corporation Versioned file system with sharing
US8176562B1 (en) 2007-12-21 2012-05-08 Symantec Corporation Privacy protection during remote administration
US8320875B2 (en) * 2010-10-27 2012-11-27 At&T Mobility Ii Llc Emergency communication recognition
US20120322402A1 (en) * 2006-08-31 2012-12-20 At&T Mobility Ii Llc Interoperability of first responder devices
US20130173530A1 (en) 2009-12-14 2013-07-04 Daj Asparna Ltd. Revision control system and method
US20140351346A1 (en) 2013-05-23 2014-11-27 Dropbox, Inc. Providing information for shared content
US20150081630A1 (en) 2013-09-18 2015-03-19 Facebook, Inc. Generating Offline Content
US20150120842A1 (en) 2013-10-30 2015-04-30 Tina Cummings HUGGINS Method and system for sending email to multiple recipients with recipient selected specific attachments

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5801700A (en) * 1996-01-19 1998-09-01 Silicon Graphics Incorporated System and method for an iconic drag and drop interface for electronic file transfer
US6301567B1 (en) * 1998-10-16 2001-10-09 The Chase Manhattan Bank Lockbox browser system
US6704772B1 (en) * 1999-09-20 2004-03-09 Microsoft Corporation Thread based email
US20030105812A1 (en) * 2001-08-09 2003-06-05 Gigamedia Access Corporation Hybrid system architecture for secure peer-to-peer-communications
US6938042B2 (en) * 2002-04-03 2005-08-30 Laplink Software Inc. Peer-to-peer file sharing
US7945618B2 (en) * 2003-02-10 2011-05-17 Oren Asher Peer-to-peer service designer
JP2005275937A (en) * 2004-03-25 2005-10-06 Fujitsu Ltd P2p network system
JP2005284667A (en) * 2004-03-29 2005-10-13 Konica Minolta Business Technologies Inc Document management program and document management apparatus
US7543023B2 (en) * 2005-03-15 2009-06-02 Microsoft Corporation Service support framework for peer to peer applications
US7779006B2 (en) * 2005-12-09 2010-08-17 Illinois Institute Of Technology Peer-to-peer file sharing
US7509339B2 (en) * 2006-01-03 2009-03-24 International Business Machines Corporation System and method of implementing personalized alerts utilizing a user registry in instant messenger
US8732044B2 (en) * 2006-05-23 2014-05-20 Mastercard International Incorporated Electronic transaction apparatus and method
US9053460B2 (en) * 2006-06-12 2015-06-09 International Business Machines Corporation Rule management using a configuration database
JP4906406B2 (en) * 2006-06-14 2012-03-28 キヤノン株式会社 Information processing method and apparatus
US20080005195A1 (en) * 2006-06-30 2008-01-03 Microsoft Corporation Versioning synchronization for mass p2p file sharing
US8924460B2 (en) * 2008-12-19 2014-12-30 International Business Machines Corporation Method and system of administrating a peer-to-peer file sharing network
US8924443B2 (en) * 2012-10-05 2014-12-30 Gary Robin Maze Document management systems and methods

Patent Citations (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6711608B1 (en) 1998-09-23 2004-03-23 John W. L. Ogilvie Method for including a self-removing code in a self-removing message
US7224373B1 (en) 2000-04-07 2007-05-29 Danger, Inc. Adjustable data processing display
US20020107930A1 (en) 2001-02-06 2002-08-08 International Business Machines Corporation Method of setting destinations of electronic mail
US20050044159A1 (en) * 2001-10-19 2005-02-24 Aki Niemi Messaging system
US7729684B1 (en) * 2001-11-01 2010-06-01 Garmin Ltd. Combined global positioning system receiver and radio
US20030105716A1 (en) 2001-12-03 2003-06-05 Sutton Lorin R. Reducing duplication of files on a network
US20040267707A1 (en) 2003-06-17 2004-12-30 Frederick Hayes-Roth Personal portal and secure information exchange
US20050091289A1 (en) 2003-10-24 2005-04-28 Microsoft Corporation File sharing in P2P group shared spaces
US20050169248A1 (en) * 2004-02-04 2005-08-04 Nortel Networks Limited Method and apparatus for providing in-band location information in an emergency response network
US20050181775A1 (en) 2004-02-13 2005-08-18 Readyalert Systems, Llc Alert notification service
US20120322402A1 (en) * 2006-08-31 2012-12-20 At&T Mobility Ii Llc Interoperability of first responder devices
US20080140732A1 (en) 2006-12-11 2008-06-12 Bentley System, Inc. Method and system for sharing file based data
US8176562B1 (en) 2007-12-21 2012-05-08 Symantec Corporation Privacy protection during remote administration
US20090182833A1 (en) 2008-01-15 2009-07-16 Swaminathan Balasubramanian Sharing Material in a Master-Slave Configuration Using an Instant Messaging Infrastructure
US20100003949A1 (en) * 2008-07-03 2010-01-07 Embarq Holdings Company, Llc Emergency data message router database
US20130173530A1 (en) 2009-12-14 2013-07-04 Daj Asparna Ltd. Revision control system and method
US20120054156A1 (en) 2010-08-30 2012-03-01 Nasuni Corporation Versioned file system with fast restore
US20120089569A1 (en) 2010-10-12 2012-04-12 Nasuni Corporation Versioned file system with sharing
US8320875B2 (en) * 2010-10-27 2012-11-27 At&T Mobility Ii Llc Emergency communication recognition
US20140351346A1 (en) 2013-05-23 2014-11-27 Dropbox, Inc. Providing information for shared content
US20150081630A1 (en) 2013-09-18 2015-03-19 Facebook, Inc. Generating Offline Content
US20150120842A1 (en) 2013-10-30 2015-04-30 Tina Cummings HUGGINS Method and system for sending email to multiple recipients with recipient selected specific attachments

Also Published As

Publication number Publication date
US20150101060A1 (en) 2015-04-09
US9820119B2 (en) 2017-11-14
US20150099482A1 (en) 2015-04-09
US9485643B2 (en) 2016-11-01
US20150100653A1 (en) 2015-04-09

Similar Documents

Publication Publication Date Title
KR100585758B1 (en) Message proof method and proof mark display method for mobile communication device
KR20110076903A (en) Inter-threading indications of different types of communication
US20060217133A1 (en) Multi-modal call management
JP5697110B2 (en) Method and apparatus for providing teleconference service
US8161116B2 (en) Method and system for communicating a data file over a network
EP1675352A1 (en) Systems and method for handling instant messages
US20140194095A1 (en) System and method for message identification and notification
US8942767B2 (en) Communications convergence and user interface systems, apparatuses, and methods
JP5490700B2 (en) System and method for delivering notifications to groups
US20050020289A1 (en) Method for blocking spam messages in a mobile communication terminal
KR100566263B1 (en) System and method for providing messenger service changing information of user's status by using schedule
US7308082B2 (en) Method to enable instant collaboration via use of pervasive messaging
US7764769B2 (en) Integrated call handler and email systems and methods
KR100842548B1 (en) Emergency call system and method thereof
JP4860750B2 (en) SMS2PSTN Integrated Messaging Service Providing System and Method Using Short / Multimedia Message Service Gateway
JP2007052784A (en) Method for transferring system message by session start protocol
US7894805B2 (en) System and method for connecting to an audio conference service using a mobile communications device
KR20060073574A (en) The mobilephone user's schedule management and supplementary service applied system of speech recognition
KR100803251B1 (en) Multi-Modal Community system and control method thereof
CN103078949B (en) Method and system for displaying the telephone number information
JP2008219903A (en) Communication server for handling sound and data connection in parallel and method for using the same
US20150222584A1 (en) Methods and apparatus for message prioritization and gps mapping during instant messaging sessions.
US6542586B1 (en) Text messaging with embedded telephony action keys
US20140025724A1 (en) Personal safety communication system
EP2499850A2 (en) Personal protection system with automatic emergency contact notification based on registered events

Legal Events

Date Code Title Description
AS Assignment

Owner name: SWN COMMUNICATIONS, INC., NEW YORK

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:TSEPETIS, ALEXANDROS;SCHMITZ, ANTHONY F.;SIGNING DATES FROM 20141006 TO 20141007;REEL/FRAME:041935/0842

AS Assignment

Owner name: ARES CAPITAL CORPORATION, NEW YORK

Free format text: SECURITY INTEREST;ASSIGNORS:EMERGENCY COMMUNICATIONS NETWORK, LLC;SWN COMMUNICATIONS INC.;REEL/FRAME:042576/0342

Effective date: 20170601

STCF Information on status: patent grant

Free format text: PATENTED CASE