PREVENTING UNINTENTIONAL COMMUNICATION

CROSS REFERENCE TO RELATED APPLICATIONS [0001] This patent application claims priority to U.S. Utility patent application with Serial No. 15/345,930, filed November 8, 2016. Application Serial No. 15/345,930 is fully incorporated herein by reference.

BACKGROUND [0002] Modern telecommunication systems include landline telephone systems, Internet, Wi-Fi™, and heterogeneous mixtures of second, third, and fourth generation (2G, 3G, and 4G) cellular-wireless access technologies, all of which can be cross-compatible and can operate collectively to provide voice and/or data communication services. Global Systems for Mobile (GSM) is an example of 2G telecommunications technologies; Universal Mobile Telecommunications System (UMTS) is an example of 3 G telecommunications technologies; and Long Term Evolution (LTE), including LTE Advanced, and Evolved High-Speed Packet Access (HSPA+) are examples of 4G telecommunications technologies.

[0003] Modern computing devices such as cellular phones, desktop and laptop computers, tablets, and the like, operating in such telecommunication systems are generally capable of operating in various communication modes, such as voice call, email, texting, instant messaging, photo sharing, and the like, and may even have several identities or accounts used for each mode. In such a device, each communication mode may have its own address book, which may contain contact information, such as telephone numbers and email address of friends, family, co-workers, stores and businesses, and the like, and some address books may allow a user of the computing device to combine various addresses under one entry. There may also be similar or the same name entries in the address for different individuals. [0004] As a user of the computing device prepares a new communication, a new email for example, he may unintentionally select and include a recipient who may not be appropriate for the communication, especially considering that many of the modern devices may suggest and/or auto-fill the recipient information from the address books which may contain a similar or the same name for different individuals.

BRIEF DESCRIPTION OF THE DRAWINGS

[0005] The detailed description is set forth with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items or features.

[0006] FIG. 1 illustrates an example address book entries which may be utilized by a method, apparatus, and system for preventing unintentional communication.

[0007] FIG. 2 illustrates an example list of context categories and associated entries which may be utilized by a method, apparatus, and system for preventing unintentional communication.

[0008] FIG. 3 illustrates an example process for preventing unintentional communication.

[0009] FIG. 4 illustrates an example process detailing one of the blocks of FIG. 3.

[0010] FIG. 5 illustrates another example process for preventing unintentional communication.

DETAILED DESCRIPTION

[0011] A method, apparatus, and system discussed herein are directed to a computing device, or a user equipment (UE), for preventing unintentional communication. Computing devices may include personal computers such as desktop, laptop, and tablet computers, and personal communication devices such as cellular phones, personal digital assistances, and the like. Appropriateness of an electronic communication initiated by a user is evaluated based on comparing the contexts of the communication and a recipient of the communication before the communication is transmitted, and the user is provided with an opportunity to cancel or edit the communication. The electronic communication may include, a phone call, Short Message System (SMS) message or text message, email, instant message (IM), social media message, and the like, and may be interchangeably referred to as a message.

[0012] After a user enters a command to send a message such as a text or email message or a phone call, to a particular recipient addressed in the message, appropriateness of the message for the particular recipient is evaluated based on the time of the message and/or a comparison of the contexts of the message against the particular recipient, which may have been auto-filled with a name similar to the intended recipient of the message. If a questionable context for the particular recipient is found, the user is notified and provided with an opportunity to cancel or edit before the message is sent. For example, the user would be notified if a message meant for the user's loved one were unintentionally addressed to a business colleague, which may be irrelevant or even inappropriate.

[0013] The contexts of a message may include a time of the day and context categories of words or phrases used in the message. The context categories may comprise, for example, work, business, family, friends, personal, mature, and the like. Recipients may be categorized into, for example, work, family, friends, personal, unknown, and the like. The context categories are compared to the recipient categories before the message is sent, and if a mismatch is detected, the user is given an opportunity to edit or cancel the message before it is sent. For example, if the message were determined to be in the business category having a phrase "proprietary and confidential," and the recipient were determined to be in the family category such as the user's spouse, a notification or a warning may be provided to the user before the message is sent. The user may then edit the message or the recipients before sending it or cancel the message. The context and recipient categories may be pre-installed in the computing device and/or be created by the user, and the user may make entries to each of the categories.

[0014] The user may select recipients first, then create a message. As discussed above, some of the recipients may be auto-filled and may not be the intended recipients. As the user creates a message and enters inappropriate words or phrases for the selected recipient, the user may be notified. The user may ignore the notice or edit the message. When the user completes creating the message and selects to send it, the context categories may be compared to the recipient categories before the message is sent, and if a mismatch is detected, the user may be given another opportunity to edit the message before it is sent.

[0015] Alternatively, the user may create a message first, or select to forward an existing message, then select the recipients. Some of the recipients may be auto-filled and may not be the intended recipient. As each recipient is selected, the context categories are compared to the recipient category of the recipient just added, and if a mismatch is detected, the user may be warned and given an opportunity to edit the message or the recipient. The user may ignore the warning or edit the message based on the warning. When the user selects to send the message, the context categories may be compared to the recipient categories before the message is sent, and if a mismatch is detected, the user may be given another opportunity to edit the message before it is sent.

[0016] FIG. 1 illustrates example address book entries 100, which may be utilized by a method, apparatus, and system for preventing unintentional communication. A contact entry 102 may include various fields such as a name field 104 for the name of the individual, a recipient category field 106 for the relationship of the individual to the user, and contact information. The contact information for the associated individual may include a phone number field 108 for phone numbers such as home number 1 10, work number 112, and/or mobile number 114, an email field 1 16 for email addresses such as home email address 118 and/or work email address 120, and an address filed 122 for work address 124 and home address 126. The contact entry 102 shows that it is for "John A. Smith" as shown in the name field 104, and his relationship to the user is "work" as shown in the recipient category field 106. Because the relationship of John A. Smith to the user is work related, work related information, such as the work phone number 112 and the work email address 120, from the contact entry 128 may be selected by default.

[0017] Similarly, a contact entry 128 shows that it is for Jane Smith as shown in the name field 104, and her relationship to the user is "family" as shown in the recipient category field 106. Because the relationship of Jane Smith to the user is family, family information, such as the home phone number 1 10 and the home email address 1 18, from the contact entry 102 may be selected by default. Another contact entry 130 shows that it is for John B. Smith as shown in the name field 104, and her relationship to the user is "friend" as shown in the recipient category field 106. Because the relationship of John B. Smith to the user is friend, the use may assign the mobile phone number 110 and the home email address 118 as default from the contact entry 130. An address book for the contact entries, such as 102, 128, and 130, may be, or may be based on, a corporate directory, a personal directory in the user's computing device, an external personal directory maintained by a network service provider, a public record such as a phonebook, and the like.

[0018] FIG. 2 illustrates an example context list 200 of context categories 202 and associated context entries 204 which may be utilized by a method, apparatus, and system for preventing unintentional communication. In the context list 200, three context categories, work 206, family 208, and mature 210 are shown under the context categories 202. Other categories may be created by the user. Under the context entries, work contexts 212, family contexts 214, and mature contexts 216 are shown. These entries may be made by the user, and some words and phrases may be entered under multiple context categories. For example, if the user's work were related to greeting cards, then the phrase "love you" in the family contexts 214 may be equally applicable for the work contexts 212. Similarly, if the user's work were related to legal or police work, the entries in the mature contexts 216 may be equally applicable for the work contexts 210. Other words and phrases may be applicable for the work context 212, the family context 214, and a friend context (not shown).

[0019] FIG. 3 illustrates an example process 300 for preventing unintentional communication. In block 302, the user may prepare a message, an email message for example, by completing the body of the message and one or more recipients for the message, and may enter a command to send the message in block 304. In block 306, a context category of the message may be determined based on finding any context entries, such as those listed in the work contexts 212, family contexts 214, and mature contexts 216, in the message including the subject and the body of the message. If found, a context category corresponding to the context entry may be assigned to the message. In block 308, a recipient category of each of one or more recipients may be determined based on the relationship of each recipient to the user as indicated in the recipient category field 106.

[0020] In block 310, appropriateness of the message for each recipient may be determined by comparing the context category to the recipient category as determined in blocks 304 and 306, respectively. The message may be determined to be appropriate if the context category matched the recipient category or user- assigned recipient category /categories. For example a work-category message would be appropriate for a work-category recipient but it would not be appropriate for a family-category recipient. A family-category message may be appropriate for both a family-category recipient and a friend-category recipient. If the message were determined to be appropriate for the recipient in block 310, then the message may be sent to the recipient in block 312.

[0021] If the message were determine not to be appropriate for at least one of the recipients in block 310, then the message may be halted and a notice may be provided to the user, notifying that the message may not be appropriate for the recipient in block 314. In block 316, the user may select to edit the message and/or the recipient, or select not to edit the message and confirm to send the message. If the user selects not to edit and confirms to send the message, the message may be sent in block 312. If the user selects to edit the message, then the process may loop back to block 302. As shown in FIG. 1, the contact entries may include similarly named individuals, each having a different relationship with the user, and the user may unintentionally select an unintended recipient. With an auto-fill feature, the user may easily select an unintended recipient from a list suggested by the computing device.

[0022] FIG. 4 illustrates an example process 400 detailing block 310 of FIG. 3. In block 402, whether the message category matches the recipient category may be determined, and if they match, the process may proceed to block 312 and the message may be sent. If they do not match, a historical pattern of the pairing of this particular message category, or the context entry in the particular message category, with the recipient, not the recipient category, may be evaluated in block 404 to determine whether an exception is warranted. For example, the user may frequently use "love you," which is one of the family context 214 listed under the family context category 208, in messages to his co-worker John A. Smith whose contact information is shown in the contact entry 102. Normally, a use of a family context in a work category message may cause a notification, however, if the user and John A. Smith worked for the same greeting card company and it were a normal part of their business to use the phrase "love you," the user may wish to suppress the notice. Yet, the user may not wish to enter "love you" under the work category. By evaluating how often this particular paring, "love you" with the co-worker John A. Smith occurred, and determining how often the user selected to ignore the notice of this paring, the pairing of "love you" with John A. Smith may be determined to be appropriate. A predestined number of the pairing occurrences, or a percentage of overruling or ignoring the notice of inappropriateness of the pairing may be set, and above which the paring may be presumed to be appropriate and the notice may no longer be provided for the pairing. If it is determined that an exception is warranted in block 404, the process may proceed to block 312 and the message may be sent. If the historical patter does not warrant an exception, the process proceeds to block 314.

[0023] FIG. 5 illustrates another example process 500 for preventing unintentional communication. In block 502, the user accidentally, or intentionally, may attempt to make a phone call to a callee. A completion of the phone call may be halted in block 504, and the time of day of the phone call initiation may be determined in block 506. In block 508, a recipient category of the callee may be determined, and appropriateness of the phone call may be evaluated in block 510. If the phone call were determined to be appropriate in block 510, then the process may proceed to block 512 and the phone call may be completed. However, if the phone call were determined to be inappropriate in block 510, the phone call may be halted and a notice may be issued to the user in block 514. If the user overrides the notice in 516, the telephone call may be completed in block 512. If the user does not override the notice in 516, the telephone call may be terminated in block 518.

[0024] For example, a telephone call at 8 pm to a callee who is under the friend recipient category may be appropriate, but to a callee who is under the work recipient category may be inappropriate. However, a telephone call at 8 pm to a callee who is under the work recipient category, but based on the contact entry information, known to be currently in the business hours, may be appropriate.

[0025] Some or all operations of the methods described above can be performed by execution of computer-readable instructions stored on a non- transitory computer storage medium, as defined below. The term "computer- readable instructions" as used in the description and claims, include routines, applications, application modules, program modules, programs, components, data structures, algorithms, and the like. Computer-readable instructions can be implemented on various system configurations, including single-processor or multiprocessor systems, minicomputers, mainframe computers, personal computers, hand-held computing devices, microprocessor-based, programmable consumer electronics, combinations thereof, and the like.

[0026] The computer storage media may include volatile memory (such as random access memory (RAM)) and/or non-volatile memory (such as read-only memory (ROM), flash memory, etc.). The computer storage media may also include additional removable storage and/or non-removable storage including, but not limited to, flash memory, magnetic storage, optical storage, and/or tape storage that may provide non-volatile storage of computer-readable instructions, data structures, program modules, and the like.

[0027] The non-transitory computer storage medium is an example of computer-readable media. Computer-readable media includes at least two types of computer-readable media, namely computer storage media and communications media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any process or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, phase change memory (PRAM), static random- access memory (SRAM), dynamic random-access memory (DRAM), other types of random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non- transmission medium that can be used to store information for access by a computing device. In contrast, communication media may embody computer- readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transmission mechanism. As defined herein, computer storage media do not include communication media.

[0028] The computer-readable instructions stored on one or more computer storage media that, when executed by one or more processors, perform operations described above with reference to FIGs. 1-5. Generally, computer- readable instructions include routines, programs, objects, components, data structures, and the like that perform particular functions or implement particular abstract data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement the processes. CONCLUSION

[0029] Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claims.