Source: https://patents.google.com/patent/US20140143202A1/en
Timestamp: 2018-11-19 06:21:26
Document Index: 580554087

Matched Legal Cases: ['arty 1', 'arty 2', 'arty 1', 'arty 2', 'arty 1', 'arty 2', 'arty 1', 'arty 1', 'arty 2', 'arty 1', 'arty 1', 'arty 1', 'arty 2', 'arty 1', 'arty 1', 'arty 1', 'arty 1', 'arty 2', 'arty 1', 'arty 1', 'arty 1', 'arty 2']

US20140143202A1 - Regulated Texting Solution for Mobile Devices - Google Patents
US20140143202A1
US20140143202A1 US13683454 US201213683454A US2014143202A1 US 20140143202 A1 US20140143202 A1 US 20140143202A1 US 13683454 US13683454 US 13683454 US 201213683454 A US201213683454 A US 201213683454A US 2014143202 A1 US2014143202 A1 US 2014143202A1
US13683454
US9442925B2 (en )
FIGS. 2 a-2 k illustrate an example set of data messages that the system of FIG. 1 may consolidate;
FIGS. 3 a-3 d illustrate an example set of consolidated data messages that may result after the system of FIG. 1 consolidates the example set of data messages illustrated in FIGS. 2 a-2 k; and
Consolidation server processor 62 receives communication 25 containing data messages 18 a-18 i and stores data messages 18 a-18 i in consolidation server memory 64. Consolidation server processor 62 may then group data messages 18 a-18 i in accordance with consolidation server criteria 66. For instance, consolidation server criteria 66 may instruct consolidation server processor 62 to group together all data messages which were sent between a certain user and a certain outside party within a certain 24 hour period. Upon grouping the messages as instructed by consolidation server criteria 66, consolidation server processor 62 then combines the grouped data messages 18 into a consolidated message 68. An example of the grouping and combining process will be shown in FIGS. 2 a through 2 k along with FIGS. 3 a through 3 d. In some embodiments, consolidation server processor 62 may retain characters from data messages 18 a-18 i in their original form. In other embodiments, consolidation server processor 62 may perform character encoding on the contents of data messages 18 a-18 i. The grouping and consolidating process may occur daily in some embodiments. However, any frequency of the grouping and consolidating process is envisioned by this disclosure.
FIGS. 2 a through 2 k illustrate an example set of data messages 18 that may be sent or received by device 10 and later stored in aggregation server memory 54 or in consolidation server memory 64. Each data message 18 in FIGS. 2 a-2 k contains certain information regarding the recipient, the sender, and date and time the message was transmitted. Each data message 18 also contains a message body. In FIG. 2 a, the sender is User 1, the recipient is Outside Party 1, the date was Jan. 1, 2012. In FIG. 2 b, the sender was User 1, the recipient was Outside Party 2 and the date was Jan. 1, 2012. In FIG. 2 c, the sender was User 1, the recipient was Outside Party 1, and the date was Jan. 1, 2012. In FIG. 2 d, the sender was Outside Party 2, the recipient was User 1, and the date was Jan. 1, 2012. In FIG. 2 e, the sender was User 1, the recipient was Outside Party 1, and the date was Jan. 3, 2012. In FIG. 2 f, the sender was User 1, the recipient was Outside Party 2, and the date was Jan. 1, 2012. In FIG. 2 g, the sender was Outside Party 1, the recipient was User 1, and the date was Jan. 1, 2012. In FIG. 2 h, the sender was Outside Party 1, the recipient was User 1, and the date was Jan. 3, 2012. In FIG. 2 i, the sender was Outside Party 2, the recipient was User 1, and the date was Jan. 1, 2012. In FIG. 2 j, the sender was Outside Party 1, the recipient was User 1, and the date was Jan. 2, 2012. In FIG. 2 k, the sender was User 1, the recipient was Outside Party 1, and the date was Jan. 2, 2012.
As illustrated in FIGS. 2 a-2 k, it is difficult to understand the context of the conversation between User 1 and Outside Party 1, especially as separated from the conversation between User 1 and Outside Party 2. Further, it is difficult to determine in which order the communications were sent and received, which communications are part of a string of conversation between each party, and what constitutes the context of each conversation. It is even more difficult in real-world situations in which the numbers of users and outside parties may reach greater numbers than can be illustrated here.
FIGS. 3 a-3 d illustrate the consolidated messages 68 that may be created from the data messages 18 illustrated in FIGS. 2 a-2 k if certain consolidation server criteria 66 is utilized. In this example, the consolidation server criteria 66 instructs the consolidation server processor 62 to group those data messages 18 illustrated in FIGS. 2 a-2 k that share a common sender and receiver and have been sent or received within a single twenty-four-hour period ending at midnight. For instance, in FIG. 3 a, the consolidated server processor 62 has grouped those data messages 18 sent and received by User 1 and Outside Party 1 during the twenty-four-hour period corresponding to Jan. 1, 2012. The consolidation server processor 62 inserts the date, the parties to the conversation, the time of each communication, and the message body into consolidated message 68 as illustrated in FIG. 3 a. Specifically, the consolidation server processor 62 chooses the first data message 18 between Outside Party 1 and User 1 that was sent on Jan. 1, 2012, in this case, the data message 18 illustrated in FIG. 2 a. The consolidation server processor 62 inserts an identifier associated with the sender (e.g., a phone number, email address, name, etc.) the time the message was transmitted, and the message body. The consolidation server processor 62 then finds the next message in chronological order that was sent between Outside Party 1 and User 1 on Jan. 1, 2012, in this case, the data message 18 illustrated in FIG. 2 c. The consolidation server processor 62 then inserts an identifier associated with that sender (e.g., a phone number, email address, name, etc.) the time that message was transmitted, and the message body. Finally, the consolidation server processor 62 finds the final data message 18 that was sent between Outside Party 1 and User 1 on Jan. 1, 2012, in this case, the data message illustrated in FIG. 2 g. The consolidation server processor 62 inserts an identifier associated with the sender (e.g., a phone number, email address, name, etc.) the time the message was transmitted, and the message body. Thus, the consolidated message 68 illustrated in FIG. 3 a contains data from the data messages 18 illustrated in FIG. 2 a, FIG. 2 c, and FIG. 2 g.
Similarly, FIG. 3 b illustrates a series of related communications between Outside Party 2 and User 1 on Jan. 1, 2012. Again, the consolidation server criteria 66 instructs the consolidation server processor 62 to group those data messages 18 illustrated in FIGS. 2 a-2 k that share a common sender and receiver and have been sent or received within a single twenty-four-hour period ending at midnight. In the same way, the consolidation server processor 62 groups the appropriate data messages 18 as directed by consolidation server criteria 66. The data messages from FIGS. 2 a-2 k that are grouped for FIG. 3 b are FIG. 2 b, FIG. 2 d, FIG. 2 f, and FIG. 2 i.
FIG. 3 c, on the other hand, groups those messages that were sent between Outside Party 1 and User 1 on Jan. 2, 2012. Again, the consolidation server criteria 66 instructs the consolidation server processor 62 to group those data messages 18 illustrated in FIGS. 2 a-2 k that share a common sender and receiver and have been sent or received within a single twenty-four-hour period ending at midnight. The messages from FIGS. 2 a-2 k that are grouped for FIG. 3 c are FIGS. 2 j and 2 k.
Finally, FIG. 3 d illustrates a series of related communications between Outside Party 1 and User 1 on Jan. 3, 2012. Again, the consolidation server criteria 66 instructs the consolidation server processor 62 to group those data messages 18 illustrated in FIGS. 2 a-2 k that share a common sender and receiver and have been sent or received within a single twenty-four-hour period ending at midnight. The consolidation server processor 62 groups the appropriate data messages as directed by consolidation server criteria 66. The data messages from FIGS. 2 a-2 k that are grouped for FIG. 3 d are FIGS. 2 e and 2 h.
As illustrated by FIGS. 3 a-3 d, the grouping and consolidating process substantially improves the readability of the conversations between User 1 and Outside Party 1 and User 1 and Outside Party 2. The context of each conversation can be easily seen, allowing for much more efficient monitoring and compliance checking. Certain embodiments may reduce the expenditure of time and resources in communications monitoring or other areas. The consolidation server criteria used in FIGS. 2 a-2 k and FIGS. 3 a-3 d are for illustrative purposes and are not the only consolidation server criteria considered in accordance with the present disclosure.
At step 416, consolidation server processor 62 consolidates the first data message 18 with the second data message 18 into a consolidated data message 68. In some embodiments, the messages may be consolidated according to the format illustrated in FIGS. 3 a-3 d. Any other suitable format is also envisioned by this disclosure. The consolidated server processor 62 may additionally inject certain headers into the consolidated data message; these headers may contain data associated with the sender field, receiver field, timestamp field, or data body of the first or second data message 18. These headers may be used for sorting and searching purposes.
a memory operable to store a plurality of data messages, each of the plurality of data messages comprising a user field, an outside party field, and a timestamp field, and the plurality of data messages comprising:
a third data message, the user field associated with the first user, the outside party field associated with the first outside party, and the timestamp field associated with a third timestamp; and
group the first data message with the third data message based at least in part upon the user field and the outside party field and if the first timestamp and the third timestamp are within a predetermined time interval; and
combine the first data message and the third data message into a consolidated data message.
storing a plurality of data messages, each of the plurality of data messages comprising a user field, an outside party field, and a timestamp field, and the plurality of data messages comprising:
grouping the first data message and the third data message based at least in part upon the user field and the outside party field and if the first timestamp and the third timestamp are within a predetermined time interval; and
combining the first data message and the third data message into a consolidated data message.
an application stored in a memory on a device such that when executed by a processor on the device is operable to:
create a copy of the data message, the copy of the data message comprising a user field, an outside party field, and a timestamp field;
a server, comprising a server processor and a server memory, the server processor operable to:
group a plurality of messages from the copies of data messages based at least in part upon the user field, the outside party field, and the timestamp field of each of the copies of data messages;
combine the plurality of messages into a consolidated data message.
US13683454 2012-11-21 2012-11-21 Regulated texting solution for mobile devices Active 2034-07-09 US9442925B2 (en)
US13683454 US9442925B2 (en) 2012-11-21 2012-11-21 Regulated texting solution for mobile devices
US20140143202A1 true true US20140143202A1 (en) 2014-05-22
US9442925B2 US9442925B2 (en) 2016-09-13
US13683454 Active 2034-07-09 US9442925B2 (en) 2012-11-21 2012-11-21 Regulated texting solution for mobile devices
US10116606B2 (en) * 2017-02-16 2018-10-30 International Business Machines Corporation Determining a number of users allowed to access message based on message objective
US8666382B2 (en) 2010-04-28 2014-03-04 Tango Networks, Inc. Controlling mobile device calls, text messages and data usage while operating a motor vehicle
US9442925B2 (en) 2016-09-13 grant