US20170048387A1 - Collaborative phone reputation system - Google Patents
Collaborative phone reputation system Download PDFInfo
- Publication number
- US20170048387A1 US20170048387A1 US15/250,019 US201615250019A US2017048387A1 US 20170048387 A1 US20170048387 A1 US 20170048387A1 US 201615250019 A US201615250019 A US 201615250019A US 2017048387 A1 US2017048387 A1 US 2017048387A1
- Authority
- US
- United States
- Prior art keywords
- computing device
- cellular telephone
- telephone computing
- user
- information
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/436—Arrangements for screening incoming calls, i.e. evaluating the characteristics of a call before deciding whether to answer it
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/66—Substation equipment, e.g. for use by subscribers with means for preventing unauthorised or fraudulent calling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M19/00—Current supply arrangements for telephone systems
- H04M19/02—Current supply arrangements for telephone systems providing ringing current or supervisory tones, e.g. dialling tone or busy tone
- H04M19/04—Current supply arrangements for telephone systems providing ringing current or supervisory tones, e.g. dialling tone or busy tone the ringing-current being generated at the substations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42025—Calling or Called party identification service
- H04M3/42034—Calling party identification service
- H04M3/42042—Notifying the called party of information on the calling party
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42025—Calling or Called party identification service
- H04M3/42034—Calling party identification service
- H04M3/42059—Making use of the calling party identifier
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/436—Arrangements for screening incoming calls, i.e. evaluating the characteristics of a call before deciding whether to answer it
- H04M3/4365—Arrangements for screening incoming calls, i.e. evaluating the characteristics of a call before deciding whether to answer it based on information specified by the calling party, e.g. priority or subject
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/16—Communication-related supplementary services, e.g. call-transfer or call-hold
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/55—Aspects of automatic or semi-automatic exchanges related to network data storage and management
- H04M2203/551—Call history
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/55—Aspects of automatic or semi-automatic exchanges related to network data storage and management
- H04M2203/555—Statistics, e.g. about subscribers but not being call statistics
- H04M2203/556—Statistical analysis and interpretation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2250/00—Details of telephonic subscriber devices
- H04M2250/60—Details of telephonic subscriber devices logging of communication history, e.g. outgoing or incoming calls, missed calls, messages or URLs
Definitions
- Embodiments described herein generally relate to mobile device management and in particular, to a collaborative phone reputation system.
- Telemarketers, surveyors, and other unsolicited people may attempt to contact a person via phone.
- the Federal Trade Commission created the Do Not Call Registry. People could add their own phone numbers to the Registry. Telemarketers were required to reference the Registry and put phone numbers from the Registry on their “do not call” lists. However, even with the Registry in place, unsolicited calls continue to be a problem. As an example, the Registry may restrain telemarketers, but does not address social engineering attacks by criminals trying to trick end-users into giving away personal and financial information.
- FIG. 1 is a schematic drawing illustrating a system, according to an embodiment
- FIG. 2 is a block diagram illustrating control flow, according to an embodiment
- FIG. 3 is a block diagram illustrating a compute device and a server system for implementing a collaborative phone reputation system, according to an embodiment
- FIG. 4 is a flowchart illustrating a method of implementing a collaborative phone reputation system, according to an embodiment
- FIG. 5 is a block diagram illustrating an example machine upon which any one or more of the techniques (e.g., methodologies) discussed herein may perform, according to an example embodiment.
- Systems and methods described herein provide a collaborative phone reputation system.
- a user may avoid having to receive calls from callers who have a poor reputation.
- blacklist is a list of phone numbers that are suspected to be undesirable, such as telemarketers, fraudulent solicitations, scammers, or robodialers.
- blacklist services require manual configuration and ongoing maintenance.
- blacklist services are a simplistic mechanism where either a number is on or not on the list, and if it is on the list, the number is blocked or flagged. What is needed a more dynamic workable solution for tracking undesirable numbers.
- FIG. 1 is a schematic drawing illustrating a system 100 , according to an embodiment.
- the system 100 includes a compute device 102 and a server system 104 , which are communicatively coupled via a network 106 .
- the compute device 102 may be a device such as a smartphone, cellular telephone, mobile phone, laptop computer, tablet computer, music player, wearable device (e.g., watch, glasses-based device, etc.), desktop, laptop, hybrid, in-wall, or other networked device.
- the compute device 102 includes a speaker and a non-audible alert mechanism.
- the non-audible alert mechanism may be a mechanical vibration motor or an electronic display.
- the compute device 102 may alert a user of an incoming call or notification using the audible alert mechanism (e.g., a ringtone), possibly with a non-audible alert (e.g., a vibration).
- the compute device 102 may alert the user with a vibration or vibration pattern, a visual notification, or combinations of non-audible alerts.
- the network 106 may include local-area networks (LAN), wide-area networks (WAN), wireless networks (e.g., 802.11 or cellular network), the Public Switched Telephone Network (PSTN) network, ad hoc networks, personal area networks (e.g., Bluetooth) or other combinations or permutations of network protocols and network types.
- the network 106 may include a single local area network (LAN) or wide-area network (WAN), or combinations of LANs or WANs, such as the Internet.
- the various devices in FIG. 1 may be coupled to the network 106 via one or more wired or wireless connections.
- the server system 104 may provide a collaborative phone reputation system.
- the server system 104 may provide auxiliary services, such as a social network platform, a retail shopping platform, a weather forecast or history, an appointment calendar, email, text messaging, instant messaging, voice over Internet Protocol (VOIP), or the like.
- auxiliary services such as a social network platform, a retail shopping platform, a weather forecast or history, an appointment calendar, email, text messaging, instant messaging, voice over Internet Protocol (VOIP), or the like.
- the compute device 102 may receive an incoming phone call.
- the call agent 108 intercepts the incoming phone call and analyzes it using a variety of mechanisms in order to determine a probability that a phone call is undesirable. Some of the factors the call agent 108 may use are a relationship between the caller and recipient, a context of the recipient, relevant call history, and the phone number reputation score of the calling number.
- the call agent 108 may access a contact list 110 or a call history 112 , to assess the caller's identity or the frequency of conversations with the caller.
- the call agent 108 may identify aspects of the caller or the phone number based on telephone company (“telco”) switches.
- a telco switch may be accessed to determine whether the caller is a commercial line or a residential line.
- the compute device 102 may allow calls that originate from residential lines and block calls that originate from commercial lines.
- Another feature that may be used is an automatic number identification feature of a telecommunications network.
- the call agent 108 may also access one more sensors 114 .
- the sensor 114 may be remote from the compute device 102 or incorporated into the compute device 102 .
- the sensor 114 may be paired with the compute device 102 using a short-range wireless network, such as Bluetooth®.
- the sensor 114 may be one of any type of sensor, including but not limited to, a camera, a posture sensor, a biometric sensor (e.g., heart rate, skin temperature, perspiration, etc.), location sensor (e.g., GPS or GLONASS), a microphone, an accelerometer, motion sensor, ambient light sensor, or the like. While only one sensor 114 is illustrated in FIG.
- the call agent 108 may detect a context or content of a conversation, ambient sounds, motion, or the like to indicate or infer a recipient's reaction or response to parts of the conversation.
- the call agent 108 may also communicate with the server system 104 to obtain a reputation of the calling phone number.
- the server system 104 may maintain a reputation database having phone number reputation data 116 for a plurality of phone numbers.
- the phone number reputation data 116 includes a phone number and one or more reputation scores.
- the reputation scores are a reflection of how desirable it is to receive a call from the phone number. Mass-dialers, such as telemarketers or other robodialing systems, may have phone numbers with relatively low reputations. In contrast, individuals who only call their family members may have relatively high reputations.
- the reputation database includes phone number reputation data 116 for practically all known phone numbers in use.
- the reputation database may be regional, such as only for United States phone number, or international.
- the reputation database may be partitioned by country calling codes, area codes, or other regional phone number partitioning scheme.
- the server system 104 may receive scores from a large number of clients (e.g., compute devices) to modify phone number reputations.
- the server system 104 may perform its own diligence on numbers, such as by performing reverse phone lookups to determine whether a number is associated with a business or individual, and perhaps whether the number is associated with a business known for mass-dialing (e.g., telemarketer).
- the server system 104 may also access another computer system 116 , such as a consumer driven website where people report those who abuse or ignore the FTC Registry.
- the server system 104 may also access another computer system 116 , such as a social media site, to identify reports of various scams or social engineering attempts and determine signatures of phone callers from those reports. Using the direct report information and other derived information, the server system 104 may update one more phone numbers' reputation data.
- the compute device 102 may receive calls, assess the desirability of the call, compute and assign a score to the caller, and report the score to the server system 104 , which may then update its records of reputation data.
- the compute device 102 may obtain the reputation from the server system 104 . This is especially useful when the call is from an unknown number.
- the compute device 102 may also assess how the user reacted to previous instances of receiving calls from unknown numbers (e.g., did the user pick up, send to voicemail, or disconnect?).
- the call agent 108 may also screen calls using a recorded greeting.
- the recorded greeting may be a recording of the user's voice or may be a computer-generated greeting with a simulated or pre-recorded human voice.
- the call agent 108 may answer the call and play the greeting. This is sometimes necessary to provoke a response because some robodialers may remain silent until the recipient talks, and then the robodialer either opens a line to a human operator or begins a recorded message.
- the call agent 108 may analyze the call using various factors, such as is the caller a human or a recording, is the caller voice a recognized voice (e.g., someone the user has talked to before), or what keywords are used in the conversation.
- keywords such as “limited time offer” or “valued customer” may indicate a sales call.
- voice analysis may be used to determine the nationality of the caller. For example, calls with caller ID blocked and having a speaker with a foreign accent may be an indication of a scammer
- Voice analysis may also be used to determine whether the caller is human or not.
- the call agent 108 may look for a typical greeting, such as “Hello” and timing of further conversation. For example, a human will typically greet a person and then wait for a responsive greeting, whereas a computerize voice caller may not wait for a response from the call recipient before continuing with a script. Timing of responses or queries during a conversion, intonation, understanding of call context and content, and other indicia may be used to distinguish a computer-generated caller from a human caller.
- Similar speech and call analysis may be performed in an ongoing call.
- the call agent 108 may monitor an ongoing conversation and identify keywords, context, calling number, caller's speaking accent, or other aspects of the conversation. If the call agent 108 determines that the call is likely a scam, the call agent 108 may trigger a notification to the user.
- the notification may be provided on the compute device 102 or with an auxiliary device (e.g., a wearable device being worn by the user).
- the notification may be of any type of alert including, but not limited to an audible alert, a vibration, a non-audible alert, a flashing screen or light, an electric shock, a message, etc.
- FIG. 2 is a block diagram illustrating control flow 200 , according to an embodiment.
- a call is received at a compute device 102 .
- the call may be a regular phone call, a voice over Internet Protocol (VOIP) call, etc.
- a call agent installed on the compute device 102 determine whether the caller identification exists in a contact list or has a history with the user of the compute device 102 (operation 204 ). If the caller is not in the contact list, then the call agent communicates with the reputation server to determine whether the calling phone number is unknown (operation 206 ). While some phone numbers may be unknown by the reputation server, it may be more likely that the calls have caller ID blocked, in which case there is not a phone number to look up.
- the reputation score is downloaded to the compute device 102 (operation 208 ).
- the compute device 102 may screen the call by playing a greeting (operation 210 ) and analyzing the answer to the greeting (operation 212 ).
- the call agent computes a probabilistic score to determine whether the incoming call is likely desirable. For example, when the caller is known, the call agent may determine the score based on the features of the caller (e.g., name, relationship to user based on social networks, email, text, behavior, history of frequency of previous communications, current user context including location, time, day, etc.) a probabilistic score. When the caller is unknown, then the score may be based on the score from the reputation server or analysis of an answer to a screening greeting. Based on the result, the call agent will either let the call through and the phone ring (operation 216 ) or ignore the call (operation 218 ).
- the features of the caller e.g., name, relationship to user based on social networks, email, text, behavior, history of frequency of previous communications, current user context including location, time, day, etc.
- the cloud e.g., reputation server
- the phone is rung (operation 216 ). If the user answers (decision block 228 ), then the call agent may analyze the user response (operation 230 ). Natural language processing or other speech recognition may be used to monitor the conversation and determine whether the phone number's reputation should be affected. The user may also be warned of the content or likelihood of it being a scam call. For example, in the case of detecting a criminal who is soliciting personal information, the system may be configured to understand content of the call and warn a user via any available mechanism that the call may be malicious (e.g., by buzzing a wearable device).
- the flow 200 moves to operation 232 where the score is updated.
- the score may be updated based on various inputs including the user's response (e.g., answer phone, hit ignore, listens to voicemail, texts the caller in response, etc.), the context or content of the conversation, the context or content of the voicemail, the rating providing be the user, etc.
- the score may be pushed to the reputation server (operation 236 ). This part is important as it allows for crowd-sourcing of the data. As a result, malicious, obnoxious, or irritating callers may be identified faster.
- the scores are compiled to produce a profile for the phone number.
- the profile may include a score and metadata.
- the metadata may include keywords, specific feedback from users, a business name, a business type, voice characteristics, or other information to assist in identifying a caller and/or evaluating the reputation of the phone number.
- the profile may have an aging mechanism, such that as a phone number ages, its reputation score increases. In this way, a phone number with a poor reputation that has not been used for several months or years, may eventually return to a neutral reputation score.
- the profile may be accessible by the owner of the phone number. The owner may use it for their own information or audit purposes. For example, a car dealership may regularly remind customers to make routine repair appointments. The car dealership's phone number may gain a negative reputation over time as people hang up on such reminder calls. The car dealership may be interested in knowing about their reputation in order to improve their business practices.
- Metadata may also be used by users of the reputation server. For example, phone numbers may be filtered (either whitelisted or blacklisted) based on the metadata. A person who receives a call from a bank and ignores it may later provide feedback on the voicemail left, indicating that the voicemail included the terms “credit card.” As a result, when a different user who regularly rejects calls from credit card companies receives a call from the bank, the call agent on the different user's phone may associate the “credit card” metadata tag with the phone number and determine that the different user likely does not want to take the phone call from the bank.
- FIG. 3 is a block diagram illustrating a compute device 102 and a server system 104 for implementing a collaborative phone reputation system, according to an embodiment.
- the compute device 102 may include a call handling module 300 , a scoring module 302 , and an execution module 304 .
- the call handling module 300 may be configured to detect, at the compute device, an incoming call for a user of the compute device 102 .
- the scoring module 302 may be configured to determine a local probabilistic score that the incoming call is desirable for the user.
- the execution module 304 may be configured to perform an action at the compute device 102 based on the local probabilistic score.
- the scoring module 302 is to determine that the incoming call is from a party in a contact list of the user and increase the local probabilistic score based on the determination that the incoming call is from the party in the contact list. In a further embodiment, the scoring module 302 is to increase the local probabilistic score based on a frequency of calls from the party, a modality of calls from the party, or quality of contact of calls from the party.
- the execution module 304 is to notify the user of the incoming call.
- the scoring module 302 is to analyze a user response to the notifying the user of the incoming call and modify the local probabilistic score based on the user response.
- the scoring module 302 is to determine that the incoming call is from a party not in a contact list of the user and decrease the local probabilistic score based on the determination that the incoming call is from the party not in the contact list.
- the incoming call includes an originating phone number
- the scoring module 302 is to obtain a reputation score of the originating phone number and modify the local probabilistic score based on the reputation score.
- the scoring module 302 is to obtain the reputation score from a reputation server.
- the incoming call is anonymized, and the call handling module 300 is to screen the incoming call.
- the scoring module 302 is to modify the local probabilistic score based on the screening.
- the call handling module 300 is to play a pre-arranged greeting and analyze the response to the pre-arranged greeting.
- the local probabilistic score is less than a threshold, and to perform the action at the compute device 102 based on the local probabilistic score, the execution module 304 is to send the incoming call to voicemail to leave a voicemail message. In a further embodiment, the scoring module 302 is to analyze the voicemail message and modify the local probabilistic score based on the analysis of the voicemail message.
- the scoring module 302 is to analyze a user response to the voicemail message and modify the local probabilistic score based on the user response. In a further embodiment, the scoring module 302 is to query the user for feedback on the incoming call, after the user has listened to the voicemail message and modify the local probabilistic score based on the feedback.
- the execution module 304 is to transmit the local probabilistic score to a reputation server.
- the local probabilistic score may be used as crowd-sourced information about the phone number.
- the server system 104 is communicatively coupled to the compute device 102 and the server system 104 may be configured to manage, in a reputation database, a plurality of reputation scores for a corresponding plurality of phone numbers.
- the server system 104 may further be configured to receive a request from the compute device 102 for a reputation score of a particular phone number and transmit the reputation score of the particular phone number to the compute device 102 .
- the server system 104 is to receive local probabilistic scores from a plurality of compute devices for the particular phone number, calculate a reputation score for the particular phone number, and revise the reputation score for the particular phone number in the reputation database.
- the server system 104 is to track usage of a phone number and increase the reputation of the phone number based on the usage. For example, if over time the phone number is not used, the reputation may be increased. As another example, if over time the score received from users indicate that the phone number is being used responsibly, then the phone number's reputation may be increased to reflect this.
- modules may be incorporated or integrated into an application that executes on the compute device 102 .
- the application may execute in the background and collect data from the sensors and populate a database, which may be accessed by one or more other applications. Multiple applications may be developed to use the real-time or historical data for various purposes.
- FIG. 4 is a flowchart illustrating a method 400 of implementing a collaborative phone reputation system, according to an embodiment.
- an incoming call is detected at a compute device for a user of the compute device.
- a local probabilistic score that the incoming call is desirable for the user is determined.
- determining the local probabilistic score comprises determining that the incoming call is from a party in a contact list of the user and increasing the local probabilistic score based on the determination that the incoming call is from the party in the contact list.
- the method 400 includes increasing the local probabilistic score based on a frequency of calls from the party, a modality of calls from the party, or quality of contact of calls from the party.
- performing the action comprises notifying the user of the incoming call.
- the method 400 includes analyzing a user response to the notifying the user of the incoming call and modifying the local probabilistic score based on the user response.
- determining the local probabilistic score comprises: determining that the incoming call is from a party not in a contact list of the user and decreasing the local probabilistic score based on the determination that the incoming call is from the party not in the contact list.
- the incoming call includes an originating phone number
- the method 400 includes obtaining a reputation score of the originating phone number and modifying the local probabilistic score based on the reputation score.
- obtaining the reputation score comprises obtaining the reputation score from a reputation server.
- the incoming call is anonymized, and the method 400 includes screening the incoming call and modifying the local probabilistic score based on the screening.
- screening the incoming call comprises playing a pre-arranged greeting and analyzing the response to the pre-arranged greeting.
- the local probabilistic score is less than a threshold, and performing the action at the compute device based on the local probabilistic score comprises sending the incoming call to voicemail to leave a voicemail message.
- the method 400 includes analyzing the voicemail message and modifying the local probabilistic score based on the analysis of the voicemail message.
- the method 400 includes analyzing a user response to the voicemail message and modifying the local probabilistic score based on the user response. In a further embodiment, the method 400 includes querying the user for feedback on the incoming call, after the user has listened to the voicemail message and modifying the local probabilistic score based on the feedback.
- the method 400 includes transmitting the local probabilistic score to a reputation server.
- Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.
- Modules may be hardware, software, or firmware communicatively coupled to one or more processors in order to carry out the operations described herein.
- Modules may be hardware modules, and as such modules may be considered tangible entities capable of performing specified operations and may be configured or arranged in a certain manner.
- circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
- the whole or part of one or more computer systems may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
- the software may reside on a machine-readable medium.
- the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
- the term hardware module is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein.
- each of the modules need not be instantiated at any one moment in time.
- the modules comprise a general-purpose hardware processor configured using software; the general-purpose hardware processor may be configured as respective different modules at different times.
- Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
- Modules may also be software or firmware modules, which operate to perform the methodologies described herein.
- FIG. 5 is a block diagram illustrating a machine in the example form of a computer system 500 , within which a set or sequence of instructions may be executed to cause the machine to perform any one of the methodologies discussed herein, according to an example embodiment.
- the machine operates as a standalone device or may be connected (e.g., networked) to other machines.
- the machine may operate in the capacity of either a server or a client machine in server-client network environments, or it may act as a peer machine in peer-to-peer (or distributed) network environments.
- the machine may be an onboard vehicle system, set-top box, wearable device, personal computer (PC), a tablet PC, a hybrid tablet, a personal digital assistant (PDA), a mobile telephone, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine.
- PC personal computer
- PDA personal digital assistant
- machine shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.
- processor-based system shall be taken to include any set of one or more machines that are controlled by or operated by a processor (e.g., a computer) to individually or jointly execute instructions to perform any one or more of the methodologies discussed herein.
- Example computer system 500 includes at least one processor 502 (e.g., a central processing unit (CPU), a graphics processing unit (GPU) or both, processor cores, compute nodes, etc.), a main memory 504 and a static memory 506 , which communicate with each other via a link 508 (e.g., bus).
- the computer system 500 may further include a video display unit 510 , an alphanumeric input device 512 (e.g., a keyboard), and a user interface (UI) navigation device 514 (e.g., a mouse).
- the video display unit 510 , input device 512 and UI navigation device 514 are incorporated into a touch screen display.
- the computer system 500 may additionally include a storage device 516 (e.g., a drive unit), a signal generation device 518 (e.g., a speaker), a network interface device 520 , and one or more sensors (not shown), such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor.
- a storage device 516 e.g., a drive unit
- a signal generation device 518 e.g., a speaker
- a network interface device 520 e.g., a Wi-Fi
- sensors not shown, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor.
- GPS global positioning system
- the storage device 516 includes a machine-readable medium 522 on which is stored one or more sets of data structures and instructions 524 (e.g., software) embodying or utilized by any one or more of the methodologies or functions described herein.
- the instructions 524 may also reside, completely or at least partially, within the main memory 504 , static memory 506 , and/or within the processor 502 during execution thereof by the computer system 500 , with the main memory 504 , static memory 506 , and the processor 502 also constituting machine-readable media.
- machine-readable medium 522 is illustrated in an example embodiment to be a single medium, the term “machine-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more instructions 524 .
- the term “machine-readable medium” shall also be taken to include any tangible medium that is capable of storing, encoding or carrying instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present disclosure or that is capable of storing, encoding or carrying data structures utilized by or associated with such instructions.
- the term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media.
- machine-readable media include non-volatile memory, including but not limited to, by way of example, semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
- semiconductor memory devices e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)
- EPROM electrically programmable read-only memory
- EEPROM electrically erasable programmable read-only memory
- flash memory devices e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)
- flash memory devices e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM
- the instructions 524 may further be transmitted or received over a communications network 526 using a transmission medium via the network interface device 520 utilizing any one of a number of well-known transfer protocols (e.g., HTTP).
- Examples of communication networks include a local area network (LAN), a wide area network (WAN), the Internet, mobile telephone networks, plain old telephone (POTS) networks, and wireless data networks (e.g., Wi-Fi, 3G, and 4G LTE/LTE-A or WiMAX networks).
- POTS plain old telephone
- wireless data networks e.g., Wi-Fi, 3G, and 4G LTE/LTE-A or WiMAX networks.
- transmission medium shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.
- Example 1 includes subject matter (such as a device, apparatus, or machine) for implementing a collaborative phone reputation system comprising: a compute device comprising: a call handling module to detect, at the compute device, an incoming call for a user of the compute device; a scoring module to determine a local probabilistic score that the incoming call is desirable for the user; and an execution module to perform an action at the compute device based on the local probabilistic score.
- a compute device comprising: a call handling module to detect, at the compute device, an incoming call for a user of the compute device; a scoring module to determine a local probabilistic score that the incoming call is desirable for the user; and an execution module to perform an action at the compute device based on the local probabilistic score.
- Example 2 the subject matter of Example 1 may include, wherein to determine the local probabilistic score, the scoring module is to: determine that the incoming call is from a party in a contact list of the user; and increase the local probabilistic score based on the determination that the incoming call is from the party in the contact list.
- Example 3 the subject matter of any one of Examples 1 to 2 may include, wherein the scoring module is to increase the local probabilistic score based on a frequency of calls from the party, a modality of calls from the party, or quality of contact of calls from the party.
- Example 4 the subject matter of any one of Examples 1 to 3 may include, wherein to perform the action, the execution module is to notify the user of the incoming call.
- Example 5 the subject matter of any one of Examples 1 to 4 may include, wherein the scoring module is to: analyze a user response to the notifying the user of the incoming call; and modify the local probabilistic score based on the user response.
- Example 6 the subject matter of any one of Examples 1 to 5 may include, wherein to determine the local probabilistic score, the scoring module is to: determine that the incoming call is from a party not in a contact list of the user; and decrease the local probabilistic score based on the determination that the incoming call is from the party not in the contact list.
- Example 8 the subject matter of any one of Examples 1 to 7 may include, wherein to obtain the reputation score, the scoring module is to obtain the reputation score from a reputation server.
- Example 9 the subject matter of any one of Examples 1 to 8 may include, wherein the incoming call is anonymized, and wherein the call handling module is to screen the incoming call; and wherein the scoring module is to modify the local probabilistic score based on the screening.
- Example 10 the subject matter of any one of Examples 1 to 9 may include, wherein to screen the incoming call, the call handling module is to: play a pre-arranged greeting; and analyze the response to the pre-arranged greeting.
- Example 11 the subject matter of any one of Examples 1 to 10 may include, wherein the local probabilistic score is less than a threshold, and wherein to perform the action at the compute device based on the local probabilistic score, the execution module is to send the incoming call to voicemail to leave a voicemail message.
- Example 12 the subject matter of any one of Examples 1 to 11 may include, wherein the scoring module is to: analyze the voicemail message; and modify the local probabilistic score based on the analysis of the voicemail message.
- Example 13 the subject matter of any one of Examples 1 to 12 may include, wherein the scoring module is to: analyze a user response to the voicemail message; and modify the local probabilistic score based on the user response.
- Example 14 the subject matter of any one of Examples 1 to 13 may include, wherein the scoring module is to query the user for feedback on the incoming call, after the user has listened to the voicemail message; and modify the local probabilistic score based on the feedback.
- Example 15 the subject matter of any one of Examples 1 to 14 may include, wherein the execution module is to: transmit the local probabilistic score to a reputation server.
- Example 16 the subject matter of any one of Examples 1 to 15 may include, a server system communicatively coupled to the compute device, the server system to: manage, in a reputation database, a plurality of reputation scores for a corresponding plurality of phone numbers; receive a request from the compute device for a reputation score of a particular phone number; and transmit the reputation score of the particular phone number to the compute device.
- Example 17 the subject matter of any one of Examples 1 to 16 may include, wherein to manage the plurality of reputation scores, the server system is to: receive local probabilistic scores from a plurality of compute devices for the particular phone number; calculate a reputation score for the particular phone number; and revise the reputation score for the particular phone number in the reputation database.
- Example 18 the subject matter of any one of Examples 1 to 17 may include, wherein to manage the plurality of reputation scores, the server system is to: track usage of a phone number; and increase the reputation of the phone number based on the usage.
- Example 19 includes subject matter (such as a method, means for performing acts, machine readable medium including instructions that when performed by a machine cause the machine to performs acts, or an apparatus to perform) for implementing a collaborative phone reputation system comprising: detecting, at a compute device, an incoming call for a user of the compute device; determining a local probabilistic score that the incoming call is desirable for the user; and performing an action at the compute device based on the local probabilistic score.
- a collaborative phone reputation system comprising: detecting, at a compute device, an incoming call for a user of the compute device; determining a local probabilistic score that the incoming call is desirable for the user; and performing an action at the compute device based on the local probabilistic score.
- Example 20 the subject matter of Example 19 may include, wherein determining the local probabilistic score comprises: determining that the incoming call is from a party in a contact list of the user; and increasing the local probabilistic score based on the determination that the incoming call is from the party in the contact list.
- Example 21 the subject matter of any one of Examples 19 to 20 may include, increasing the local probabilistic score based on a frequency of calls from the party, a modality of calls from the party, or quality of contact of calls from the party.
- Example 22 the subject matter of any one of Examples 19 to 21 may include, wherein performing the action comprises notifying the user of the incoming call.
- Example 23 the subject matter of any one of Examples 19 to 22 may include, analyzing a user response to the notifying the user of the incoming call; and modifying the local probabilistic score based on the user response.
- Example 24 the subject matter of any one of Examples 19 to 23 may include, wherein determining the local probabilistic score comprises: determining that the incoming call is from a party not in a contact list of the user; and decreasing the local probabilistic score based on the determination that the incoming call is from the party not in the contact list.
- Example 25 the subject matter of any one of Examples 19 to 24 may include, wherein the incoming call includes an originating phone number, and wherein the method further comprises: obtaining a reputation score of the originating phone number; and modifying the local probabilistic score based on the reputation score.
- Example 26 the subject matter of any one of Examples 19 to 25 may include, wherein obtaining the reputation score comprises obtaining the reputation score from a reputation server.
- Example 27 the subject matter of any one of Examples 19 to 26 may include, wherein the incoming call is anonymized, and wherein the method further comprises: screening the incoming call; and modifying the local probabilistic score based on the screening.
- Example 28 the subject matter of any one of Examples 19 to 27 may include, wherein screening the incoming call comprises: playing a pre-arranged greeting; and analyzing the response to the pre-arranged greeting.
- Example 29 the subject matter of any one of Examples 19 to 28 may include, wherein the local probabilistic score is less than a threshold, and wherein performing the action at the compute device based on the local probabilistic score comprises sending the incoming call to voicemail to leave a voicemail message.
- Example 30 the subject matter of any one of Examples 19 to 29 may include, analyzing the voicemail message; and modifying the local probabilistic score based on the analysis of the voicemail message.
- Example 31 the subject matter of any one of Examples 19 to 30 may include, analyzing a user response to the voicemail message; and modifying the local probabilistic score based on the user response.
- Example 32 the subject matter of any one of Examples 19 to 31 may include, querying the user for feedback on the incoming call, after the user has listened to the voicemail message; and modifying the local probabilistic score based on the feedback.
- Example 33 the subject matter of any one of Examples 19 to 32 may include, transmitting the local probabilistic score to a reputation server.
- Example 34 includes at least one machine-readable medium including instructions, which when executed by a machine, cause the machine to perform operations of any of the Examples 19-33.
- Example 35 includes an apparatus comprising means for performing any of the Examples 19-33.
- Example 36 includes subject matter (such as a device, apparatus, or machine) for implementing a collaborative phone reputation system comprising: means for detecting, at a compute device, an incoming call for a user of the compute device; means for determining a local probabilistic score that the incoming call is desirable for the user; and means for performing an action at the compute device based on the local probabilistic score.
- Example 37 the subject matter of Example 36 may include, wherein the means for determining the local probabilistic score comprise: means for determining that the incoming call is from a party in a contact list of the user; and means for increasing the local probabilistic score based on the determination that the incoming call is from the party in the contact list.
- Example 38 the subject matter of any one of Examples 36 to 37 may include, means for increasing the local probabilistic score based on a frequency of calls from the party, a modality of calls from the party, or quality of contact of calls from the party.
- Example 39 the subject matter of any one of Examples 36 to 38 may include, wherein the means for performing the action comprise means for notifying the user of the incoming call.
- Example 40 the subject matter of any one of Examples 36 to 39 may include, means for analyzing a user response to the notifying the user of the incoming call; and means for modifying the local probabilistic score based on the user response.
- Example 41 the subject matter of any one of Examples 36 to 40 may include, wherein the means for determining the local probabilistic score comprise: means for determining that the incoming call is from a party not in a contact list of the user; and means for decreasing the local probabilistic score based on the determination that the incoming call is from the party not in the contact list.
- Example 42 the subject matter of any one of Examples 36 to 41 may include, wherein the incoming call includes an originating phone number, and wherein the apparatus further comprises: means for obtaining a reputation score of the originating phone number; and means for modifying the local probabilistic score based on the reputation score.
- Example 43 the subject matter of any one of Examples 36 to 42 may include, wherein the means for obtaining the reputation score comprise means for obtaining the reputation score from a reputation server.
- Example 44 the subject matter of any one of Examples 36 to 43 may include, wherein the incoming call is anonymized, and wherein the apparatus further comprises: means for screening the incoming call; and means for modifying the local probabilistic score based on the screening.
- Example 45 the subject matter of any one of Examples 36 to 44 may include, wherein the means for screening the incoming call comprises: means for playing a pre-arranged greeting; and means for analyzing the response to the pre-arranged greeting.
- Example 46 the subject matter of any one of Examples 36 to 45 may include, wherein the local probabilistic score is less than a threshold, and wherein the means for performing the action at the compute device based on the local probabilistic score comprise means for sending the incoming call to voicemail to leave a voicemail message.
- Example 47 the subject matter of any one of Examples 36 to 46 may include, means for analyzing the voicemail message; and means for modifying the local probabilistic score based on the analysis of the voicemail message.
- Example 48 the subject matter of any one of Examples 36 to 47 may include, means for analyzing a user response to the voicemail message; and means for modifying the local probabilistic score based on the user response.
- Example 49 the subject matter of any one of Examples 36 to 48 may include, means for querying the user for feedback on the incoming call, after the user has listened to the voicemail message; and means for modifying the local probabilistic score based on the feedback.
- Example 50 the subject matter of any one of Examples 36 to 49 may include, means for transmitting the local probabilistic score to a reputation server.
- the terms “a” or “an” are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of “at least one” or “one or more.”
- the term “or” is used to refer to a nonexclusive or, such that “A or B” includes “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated.
- embodiments may include fewer features than those disclosed in a particular example
- the following claims are hereby incorporated into the Detailed Description, with a claim standing on its own as a separate embodiment.
- the scope of the embodiments disclosed herein is to be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Security & Cryptography (AREA)
- Telephonic Communication Services (AREA)
- Telephone Function (AREA)
Abstract
Various systems and methods for a collaborative phone reputation system are described herein. A system for implementing a collaborative phone reputation system includes a compute device comprising: a call handling module to detect, at the compute device, an incoming call for a user of the compute device; a scoring module to determine a local probabilistic score that the incoming call is desirable for the user; and an execution module to perform an action at the compute device based on the local probabilistic score.
Description
- This application is a continuation of U.S. application Ser. No. 14/581,446, filed Dec. 23, 2014, which is incorporated herein by reference in its entirety.
- Embodiments described herein generally relate to mobile device management and in particular, to a collaborative phone reputation system.
- Telemarketers, surveyors, and other unsolicited people may attempt to contact a person via phone. In 2003, the Federal Trade Commission created the Do Not Call Registry. People could add their own phone numbers to the Registry. Telemarketers were required to reference the Registry and put phone numbers from the Registry on their “do not call” lists. However, even with the Registry in place, unsolicited calls continue to be a problem. As an example, the Registry may restrain telemarketers, but does not address social engineering attacks by criminals trying to trick end-users into giving away personal and financial information.
- In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. Some embodiments are illustrated by way of example, and not limitation, in the figures of the accompanying drawings in which:
-
FIG. 1 is a schematic drawing illustrating a system, according to an embodiment; -
FIG. 2 is a block diagram illustrating control flow, according to an embodiment; -
FIG. 3 is a block diagram illustrating a compute device and a server system for implementing a collaborative phone reputation system, according to an embodiment; -
FIG. 4 is a flowchart illustrating a method of implementing a collaborative phone reputation system, according to an embodiment; and -
FIG. 5 is a block diagram illustrating an example machine upon which any one or more of the techniques (e.g., methodologies) discussed herein may perform, according to an example embodiment. - Systems and methods described herein provide a collaborative phone reputation system. Using the collaborative phone reputation system, a user may avoid having to receive calls from callers who have a poor reputation.
- In the ten or more years after the FTC Do No Call Registry was established, unsolicited calls continue to be a problem for many people. Some of the problems stem from telemarketing firms that do not abide by the Registry. Other problems stem from the organizations and parties not covered by the Registry, such as charities, political organizations, surveyors, and companies that had an existing relationship with the receiving party. But the biggest threat and challenge comes from criminals conducting social engineering attacks. The problem is exacerbated by the prevalence of mobile phones and the resulting situation where people have a phone on or near them at nearly every hour of the day.
- Some mobile applications and services have attempted to address the problem of unsolicited phone calls by using blacklists. A blacklist is a list of phone numbers that are suspected to be undesirable, such as telemarketers, fraudulent solicitations, scammers, or robodialers. However, many blacklist services require manual configuration and ongoing maintenance. In addition, blacklist services are a simplistic mechanism where either a number is on or not on the list, and if it is on the list, the number is blocked or flagged. What is needed a more dynamic workable solution for tracking undesirable numbers.
-
FIG. 1 is a schematic drawing illustrating asystem 100, according to an embodiment. Thesystem 100 includes acompute device 102 and aserver system 104, which are communicatively coupled via anetwork 106. Thecompute device 102 may be a device such as a smartphone, cellular telephone, mobile phone, laptop computer, tablet computer, music player, wearable device (e.g., watch, glasses-based device, etc.), desktop, laptop, hybrid, in-wall, or other networked device. Thecompute device 102 includes a speaker and a non-audible alert mechanism. The non-audible alert mechanism may be a mechanical vibration motor or an electronic display. When in a normal mode, thecompute device 102 may alert a user of an incoming call or notification using the audible alert mechanism (e.g., a ringtone), possibly with a non-audible alert (e.g., a vibration). When operating in silent mode, thecompute device 102 may alert the user with a vibration or vibration pattern, a visual notification, or combinations of non-audible alerts. - The
network 106 may include local-area networks (LAN), wide-area networks (WAN), wireless networks (e.g., 802.11 or cellular network), the Public Switched Telephone Network (PSTN) network, ad hoc networks, personal area networks (e.g., Bluetooth) or other combinations or permutations of network protocols and network types. Thenetwork 106 may include a single local area network (LAN) or wide-area network (WAN), or combinations of LANs or WANs, such as the Internet. The various devices inFIG. 1 may be coupled to thenetwork 106 via one or more wired or wireless connections. - The
server system 104 may provide a collaborative phone reputation system. In addition, theserver system 104 may provide auxiliary services, such as a social network platform, a retail shopping platform, a weather forecast or history, an appointment calendar, email, text messaging, instant messaging, voice over Internet Protocol (VOIP), or the like. - In use, the
compute device 102 may receive an incoming phone call. Thecall agent 108 intercepts the incoming phone call and analyzes it using a variety of mechanisms in order to determine a probability that a phone call is undesirable. Some of the factors thecall agent 108 may use are a relationship between the caller and recipient, a context of the recipient, relevant call history, and the phone number reputation score of the calling number. Thecall agent 108 may access acontact list 110 or acall history 112, to assess the caller's identity or the frequency of conversations with the caller. Thecall agent 108 may identify aspects of the caller or the phone number based on telephone company (“telco”) switches. For example, a telco switch may be accessed to determine whether the caller is a commercial line or a residential line. Thecompute device 102 may allow calls that originate from residential lines and block calls that originate from commercial lines. Another feature that may be used is an automatic number identification feature of a telecommunications network. - While generally discussed in terms of phone calls, it is understood that the concepts may be applied more generally to any type of communication, such as be text messages or emails in addition to phone calls, if there is a way to map such messages to a phone number, e.g., via an address book or other online directories.
- The
call agent 108 may also access onemore sensors 114. Thesensor 114 may be remote from thecompute device 102 or incorporated into thecompute device 102. Thesensor 114 may be paired with thecompute device 102 using a short-range wireless network, such as Bluetooth®. Thesensor 114 may be one of any type of sensor, including but not limited to, a camera, a posture sensor, a biometric sensor (e.g., heart rate, skin temperature, perspiration, etc.), location sensor (e.g., GPS or GLONASS), a microphone, an accelerometer, motion sensor, ambient light sensor, or the like. While only onesensor 114 is illustrated inFIG. 1 , it is understood that more than onesensor 114 may be implemented and that some sensors may be incorporated into thecompute device 102, while other sensors may be separate from thecompute device 102. Using thesensor 114, thecall agent 108 may detect a context or content of a conversation, ambient sounds, motion, or the like to indicate or infer a recipient's reaction or response to parts of the conversation. - The
call agent 108 may also communicate with theserver system 104 to obtain a reputation of the calling phone number. Theserver system 104 may maintain a reputation database having phonenumber reputation data 116 for a plurality of phone numbers. The phonenumber reputation data 116 includes a phone number and one or more reputation scores. The reputation scores are a reflection of how desirable it is to receive a call from the phone number. Mass-dialers, such as telemarketers or other robodialing systems, may have phone numbers with relatively low reputations. In contrast, individuals who only call their family members may have relatively high reputations. In an example, the reputation database includes phonenumber reputation data 116 for practically all known phone numbers in use. The reputation database may be regional, such as only for United States phone number, or international. The reputation database may be partitioned by country calling codes, area codes, or other regional phone number partitioning scheme. - After the
call agent 108 analyzes an incoming, ongoing, or completed call, thecall agent 108 may score the interaction and push that score to theserver system 104. Theserver system 104 then uses the score to update the reputation of the phone number. If a phone number is being used by a telemarketer, then the phone number's reputation may decline rapidly. If later, the same phone number is assigned to a private party who uses it responsibly, the phone number may gain reputation. This mechanism may also work in the instance when the phone number was with one private party (e.g., a drug dealer) and then later assigned to another private party (e.g., a software engineer), who is able to restore the reputation associated with the phone number. In this way, the phone number is able to be dynamically restored to a reputable level. - The
server system 104 may receive scores from a large number of clients (e.g., compute devices) to modify phone number reputations. In addition, theserver system 104 may perform its own diligence on numbers, such as by performing reverse phone lookups to determine whether a number is associated with a business or individual, and perhaps whether the number is associated with a business known for mass-dialing (e.g., telemarketer). Theserver system 104 may also access anothercomputer system 116, such as a consumer driven website where people report those who abuse or ignore the FTC Registry. Theserver system 104 may also access anothercomputer system 116, such as a social media site, to identify reports of various scams or social engineering attempts and determine signatures of phone callers from those reports. Using the direct report information and other derived information, theserver system 104 may update one more phone numbers' reputation data. - Thus, the
compute device 102 may receive calls, assess the desirability of the call, compute and assign a score to the caller, and report the score to theserver system 104, which may then update its records of reputation data. When thecompute device 102 receives a call, it may obtain the reputation from theserver system 104. This is especially useful when the call is from an unknown number. Thecompute device 102 may also assess how the user reacted to previous instances of receiving calls from unknown numbers (e.g., did the user pick up, send to voicemail, or disconnect?). - The
call agent 108 may also screen calls using a recorded greeting. The recorded greeting may be a recording of the user's voice or may be a computer-generated greeting with a simulated or pre-recorded human voice. Thecall agent 108 may answer the call and play the greeting. This is sometimes necessary to provoke a response because some robodialers may remain silent until the recipient talks, and then the robodialer either opens a line to a human operator or begins a recorded message. When speech is heard in response to the greeting, thecall agent 108 may analyze the call using various factors, such as is the caller a human or a recording, is the caller voice a recognized voice (e.g., someone the user has talked to before), or what keywords are used in the conversation. For example, keywords such as “limited time offer” or “valued customer” may indicate a sales call. Further, voice analysis may be used to determine the nationality of the caller. For example, calls with caller ID blocked and having a speaker with a foreign accent may be an indication of a scammer Voice analysis may also be used to determine whether the caller is human or not. Thecall agent 108 may look for a typical greeting, such as “Hello” and timing of further conversation. For example, a human will typically greet a person and then wait for a responsive greeting, whereas a computerize voice caller may not wait for a response from the call recipient before continuing with a script. Timing of responses or queries during a conversion, intonation, understanding of call context and content, and other indicia may be used to distinguish a computer-generated caller from a human caller. - Similar speech and call analysis may be performed in an ongoing call. For example, the
call agent 108 may monitor an ongoing conversation and identify keywords, context, calling number, caller's speaking accent, or other aspects of the conversation. If thecall agent 108 determines that the call is likely a scam, thecall agent 108 may trigger a notification to the user. The notification may be provided on thecompute device 102 or with an auxiliary device (e.g., a wearable device being worn by the user). The notification may be of any type of alert including, but not limited to an audible alert, a vibration, a non-audible alert, a flashing screen or light, an electric shock, a message, etc. -
FIG. 2 is a block diagram illustratingcontrol flow 200, according to an embodiment. Atstage 202, a call is received at acompute device 102. The call may be a regular phone call, a voice over Internet Protocol (VOIP) call, etc. A call agent installed on thecompute device 102 determine whether the caller identification exists in a contact list or has a history with the user of the compute device 102 (operation 204). If the caller is not in the contact list, then the call agent communicates with the reputation server to determine whether the calling phone number is unknown (operation 206). While some phone numbers may be unknown by the reputation server, it may be more likely that the calls have caller ID blocked, in which case there is not a phone number to look up. If the calling number is not blocked and known by the reputation server, then the reputation score is downloaded to the compute device 102 (operation 208). Alternately, if the phone number is unknown, then thecompute device 102 may screen the call by playing a greeting (operation 210) and analyzing the answer to the greeting (operation 212). - At
decision block 214, the call agent computes a probabilistic score to determine whether the incoming call is likely desirable. For example, when the caller is known, the call agent may determine the score based on the features of the caller (e.g., name, relationship to user based on social networks, email, text, behavior, history of frequency of previous communications, current user context including location, time, day, etc.) a probabilistic score. When the caller is unknown, then the score may be based on the score from the reputation server or analysis of an answer to a screening greeting. Based on the result, the call agent will either let the call through and the phone ring (operation 216) or ignore the call (operation 218). - If the call is ignored (operation 218), then it is determined whether the caller left a voicemail message (decision block 220). If there was a voicemail left, then it is analyzed (operation 222). Keywords or phrases may be identified in the voicemail to determine whether the call was interesting. The keywords, phrases, or other analysis of the voicemail may affect the determination of a score (operation 232). The keywords or phrases may also be pushed to the cloud (e.g., reputation server) to be used as tags or other metadata on phone numbers in the reputation database. If the user listens to the voicemail (decision block 224), then the user may be asked to rate the caller (operation 226). The rating may be used in combination with other factors to determine the score (operation 232).
- Turning to the other decision path, if the probabilistic score is greater than a threshold (decision block 214), then the phone is rung (operation 216). If the user answers (decision block 228), then the call agent may analyze the user response (operation 230). Natural language processing or other speech recognition may be used to monitor the conversation and determine whether the phone number's reputation should be affected. The user may also be warned of the content or likelihood of it being a scam call. For example, in the case of detecting a criminal who is soliciting personal information, the system may be configured to understand content of the call and warn a user via any available mechanism that the call may be malicious (e.g., by buzzing a wearable device). If the user does not answer the phone, then the
flow 200 moves tooperation 232 where the score is updated. The score may be updated based on various inputs including the user's response (e.g., answer phone, hit ignore, listens to voicemail, texts the caller in response, etc.), the context or content of the conversation, the context or content of the voicemail, the rating providing be the user, etc. - If the call is not personal (decision block 234), then the score may be pushed to the reputation server (operation 236). This part is important as it allows for crowd-sourcing of the data. As a result, malicious, obnoxious, or irritating callers may be identified faster.
- At the reputation server, the scores are compiled to produce a profile for the phone number. The profile may include a score and metadata. The metadata may include keywords, specific feedback from users, a business name, a business type, voice characteristics, or other information to assist in identifying a caller and/or evaluating the reputation of the phone number. The profile may have an aging mechanism, such that as a phone number ages, its reputation score increases. In this way, a phone number with a poor reputation that has not been used for several months or years, may eventually return to a neutral reputation score. The profile may be accessible by the owner of the phone number. The owner may use it for their own information or audit purposes. For example, a car dealership may regularly remind customers to make routine repair appointments. The car dealership's phone number may gain a negative reputation over time as people hang up on such reminder calls. The car dealership may be interested in knowing about their reputation in order to improve their business practices.
- Metadata may also be used by users of the reputation server. For example, phone numbers may be filtered (either whitelisted or blacklisted) based on the metadata. A person who receives a call from a bank and ignores it may later provide feedback on the voicemail left, indicating that the voicemail included the terms “credit card.” As a result, when a different user who regularly rejects calls from credit card companies receives a call from the bank, the call agent on the different user's phone may associate the “credit card” metadata tag with the phone number and determine that the different user likely does not want to take the phone call from the bank.
-
FIG. 3 is a block diagram illustrating acompute device 102 and aserver system 104 for implementing a collaborative phone reputation system, according to an embodiment. Thecompute device 102 may include acall handling module 300, ascoring module 302, and anexecution module 304. - The
call handling module 300 may be configured to detect, at the compute device, an incoming call for a user of thecompute device 102. - The
scoring module 302 may be configured to determine a local probabilistic score that the incoming call is desirable for the user. - The
execution module 304 may be configured to perform an action at thecompute device 102 based on the local probabilistic score. - In an embodiment, to determine the local probabilistic score, the
scoring module 302 is to determine that the incoming call is from a party in a contact list of the user and increase the local probabilistic score based on the determination that the incoming call is from the party in the contact list. In a further embodiment, thescoring module 302 is to increase the local probabilistic score based on a frequency of calls from the party, a modality of calls from the party, or quality of contact of calls from the party. - In a further embodiment, to perform the action, the
execution module 304 is to notify the user of the incoming call. In a further embodiment, thescoring module 302 is to analyze a user response to the notifying the user of the incoming call and modify the local probabilistic score based on the user response. - In an embodiment, to determine the local probabilistic score, the
scoring module 302 is to determine that the incoming call is from a party not in a contact list of the user and decrease the local probabilistic score based on the determination that the incoming call is from the party not in the contact list. In a further embodiment, the incoming call includes an originating phone number, and thescoring module 302 is to obtain a reputation score of the originating phone number and modify the local probabilistic score based on the reputation score. In a further embodiment, to obtain the reputation score, thescoring module 302 is to obtain the reputation score from a reputation server. - In another embodiment, the incoming call is anonymized, and the
call handling module 300 is to screen the incoming call. In such an embodiment, thescoring module 302 is to modify the local probabilistic score based on the screening. In a further embodiment, to screen the incoming call, thecall handling module 300 is to play a pre-arranged greeting and analyze the response to the pre-arranged greeting. - In an embodiment, the local probabilistic score is less than a threshold, and to perform the action at the
compute device 102 based on the local probabilistic score, theexecution module 304 is to send the incoming call to voicemail to leave a voicemail message. In a further embodiment, thescoring module 302 is to analyze the voicemail message and modify the local probabilistic score based on the analysis of the voicemail message. - In another embodiment, the
scoring module 302 is to analyze a user response to the voicemail message and modify the local probabilistic score based on the user response. In a further embodiment, thescoring module 302 is to query the user for feedback on the incoming call, after the user has listened to the voicemail message and modify the local probabilistic score based on the feedback. - In an embodiment, the
execution module 304 is to transmit the local probabilistic score to a reputation server. In this way, the local probabilistic score may be used as crowd-sourced information about the phone number. - In an embodiment, the
server system 104 is communicatively coupled to thecompute device 102 and theserver system 104 may be configured to manage, in a reputation database, a plurality of reputation scores for a corresponding plurality of phone numbers. Theserver system 104 may further be configured to receive a request from thecompute device 102 for a reputation score of a particular phone number and transmit the reputation score of the particular phone number to thecompute device 102. - In an embodiment, to manage the plurality of reputation scores, the
server system 104 is to receive local probabilistic scores from a plurality of compute devices for the particular phone number, calculate a reputation score for the particular phone number, and revise the reputation score for the particular phone number in the reputation database. - In an embodiment, to manage the plurality of reputation scores, the
server system 104 is to track usage of a phone number and increase the reputation of the phone number based on the usage. For example, if over time the phone number is not used, the reputation may be increased. As another example, if over time the score received from users indicate that the phone number is being used responsibly, then the phone number's reputation may be increased to reflect this. - Various modules (e.g.,
modules 300 and 302) may be incorporated or integrated into an application that executes on thecompute device 102. The application may execute in the background and collect data from the sensors and populate a database, which may be accessed by one or more other applications. Multiple applications may be developed to use the real-time or historical data for various purposes. -
FIG. 4 is a flowchart illustrating amethod 400 of implementing a collaborative phone reputation system, according to an embodiment. Atblock 402, an incoming call is detected at a compute device for a user of the compute device. - At
block 404, a local probabilistic score that the incoming call is desirable for the user is determined. - At
block 406, an action is performed at the compute device based on the local probabilistic score. - In an embodiment, determining the local probabilistic score comprises determining that the incoming call is from a party in a contact list of the user and increasing the local probabilistic score based on the determination that the incoming call is from the party in the contact list. In a further embodiment, the
method 400 includes increasing the local probabilistic score based on a frequency of calls from the party, a modality of calls from the party, or quality of contact of calls from the party. - In a further embodiment, performing the action comprises notifying the user of the incoming call. In a further embodiment, the
method 400 includes analyzing a user response to the notifying the user of the incoming call and modifying the local probabilistic score based on the user response. - In an embodiment, determining the local probabilistic score comprises: determining that the incoming call is from a party not in a contact list of the user and decreasing the local probabilistic score based on the determination that the incoming call is from the party not in the contact list. In a further embodiment, the incoming call includes an originating phone number, and the
method 400 includes obtaining a reputation score of the originating phone number and modifying the local probabilistic score based on the reputation score. In a further embodiment, obtaining the reputation score comprises obtaining the reputation score from a reputation server. - In an embodiment, the incoming call is anonymized, and the
method 400 includes screening the incoming call and modifying the local probabilistic score based on the screening. In a further embodiment, screening the incoming call comprises playing a pre-arranged greeting and analyzing the response to the pre-arranged greeting. In a further embodiment, the local probabilistic score is less than a threshold, and performing the action at the compute device based on the local probabilistic score comprises sending the incoming call to voicemail to leave a voicemail message. In a further embodiment, themethod 400 includes analyzing the voicemail message and modifying the local probabilistic score based on the analysis of the voicemail message. - In an embodiment, the
method 400 includes analyzing a user response to the voicemail message and modifying the local probabilistic score based on the user response. In a further embodiment, themethod 400 includes querying the user for feedback on the incoming call, after the user has listened to the voicemail message and modifying the local probabilistic score based on the feedback. - In an embodiment, the
method 400 includes transmitting the local probabilistic score to a reputation server. - Embodiments may be implemented in one or a combination of hardware, firmware, and software. Embodiments may also be implemented as instructions stored on a machine-readable storage device, which may be read and executed by at least one processor to perform the operations described herein. A machine-readable storage device may include any non-transitory mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a machine-readable storage device may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media.
- Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules may be hardware, software, or firmware communicatively coupled to one or more processors in order to carry out the operations described herein. Modules may be hardware modules, and as such modules may be considered tangible entities capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on a machine-readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations. Accordingly, the term hardware module is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general-purpose hardware processor configured using software; the general-purpose hardware processor may be configured as respective different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time. Modules may also be software or firmware modules, which operate to perform the methodologies described herein.
-
FIG. 5 is a block diagram illustrating a machine in the example form of acomputer system 500, within which a set or sequence of instructions may be executed to cause the machine to perform any one of the methodologies discussed herein, according to an example embodiment. In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of either a server or a client machine in server-client network environments, or it may act as a peer machine in peer-to-peer (or distributed) network environments. The machine may be an onboard vehicle system, set-top box, wearable device, personal computer (PC), a tablet PC, a hybrid tablet, a personal digital assistant (PDA), a mobile telephone, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein. Similarly, the term “processor-based system” shall be taken to include any set of one or more machines that are controlled by or operated by a processor (e.g., a computer) to individually or jointly execute instructions to perform any one or more of the methodologies discussed herein. -
Example computer system 500 includes at least one processor 502 (e.g., a central processing unit (CPU), a graphics processing unit (GPU) or both, processor cores, compute nodes, etc.), amain memory 504 and astatic memory 506, which communicate with each other via a link 508 (e.g., bus). Thecomputer system 500 may further include avideo display unit 510, an alphanumeric input device 512 (e.g., a keyboard), and a user interface (UI) navigation device 514 (e.g., a mouse). In one embodiment, thevideo display unit 510,input device 512 andUI navigation device 514 are incorporated into a touch screen display. Thecomputer system 500 may additionally include a storage device 516 (e.g., a drive unit), a signal generation device 518 (e.g., a speaker), anetwork interface device 520, and one or more sensors (not shown), such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. - The
storage device 516 includes a machine-readable medium 522 on which is stored one or more sets of data structures and instructions 524 (e.g., software) embodying or utilized by any one or more of the methodologies or functions described herein. Theinstructions 524 may also reside, completely or at least partially, within themain memory 504,static memory 506, and/or within theprocessor 502 during execution thereof by thecomputer system 500, with themain memory 504,static memory 506, and theprocessor 502 also constituting machine-readable media. - While the machine-
readable medium 522 is illustrated in an example embodiment to be a single medium, the term “machine-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one ormore instructions 524. The term “machine-readable medium” shall also be taken to include any tangible medium that is capable of storing, encoding or carrying instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present disclosure or that is capable of storing, encoding or carrying data structures utilized by or associated with such instructions. The term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media. Specific examples of machine-readable media include non-volatile memory, including but not limited to, by way of example, semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. - The
instructions 524 may further be transmitted or received over acommunications network 526 using a transmission medium via thenetwork interface device 520 utilizing any one of a number of well-known transfer protocols (e.g., HTTP). Examples of communication networks include a local area network (LAN), a wide area network (WAN), the Internet, mobile telephone networks, plain old telephone (POTS) networks, and wireless data networks (e.g., Wi-Fi, 3G, and 4G LTE/LTE-A or WiMAX networks). The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software. - Example 1 includes subject matter (such as a device, apparatus, or machine) for implementing a collaborative phone reputation system comprising: a compute device comprising: a call handling module to detect, at the compute device, an incoming call for a user of the compute device; a scoring module to determine a local probabilistic score that the incoming call is desirable for the user; and an execution module to perform an action at the compute device based on the local probabilistic score.
- In Example 2, the subject matter of Example 1 may include, wherein to determine the local probabilistic score, the scoring module is to: determine that the incoming call is from a party in a contact list of the user; and increase the local probabilistic score based on the determination that the incoming call is from the party in the contact list.
- In Example 3, the subject matter of any one of Examples 1 to 2 may include, wherein the scoring module is to increase the local probabilistic score based on a frequency of calls from the party, a modality of calls from the party, or quality of contact of calls from the party.
- In Example 4, the subject matter of any one of Examples 1 to 3 may include, wherein to perform the action, the execution module is to notify the user of the incoming call.
- In Example 5, the subject matter of any one of Examples 1 to 4 may include, wherein the scoring module is to: analyze a user response to the notifying the user of the incoming call; and modify the local probabilistic score based on the user response.
- In Example 6, the subject matter of any one of Examples 1 to 5 may include, wherein to determine the local probabilistic score, the scoring module is to: determine that the incoming call is from a party not in a contact list of the user; and decrease the local probabilistic score based on the determination that the incoming call is from the party not in the contact list.
- In Example 7, the subject matter of any one of Examples 1 to 6 may include, wherein the incoming call includes an originating phone number, and wherein the scoring module is to: obtain a reputation score of the originating phone number; and modify the local probabilistic score based on the reputation score.
- In Example 8, the subject matter of any one of Examples 1 to 7 may include, wherein to obtain the reputation score, the scoring module is to obtain the reputation score from a reputation server.
- In Example 9, the subject matter of any one of Examples 1 to 8 may include, wherein the incoming call is anonymized, and wherein the call handling module is to screen the incoming call; and wherein the scoring module is to modify the local probabilistic score based on the screening.
- In Example 10, the subject matter of any one of Examples 1 to 9 may include, wherein to screen the incoming call, the call handling module is to: play a pre-arranged greeting; and analyze the response to the pre-arranged greeting.
- In Example 11, the subject matter of any one of Examples 1 to 10 may include, wherein the local probabilistic score is less than a threshold, and wherein to perform the action at the compute device based on the local probabilistic score, the execution module is to send the incoming call to voicemail to leave a voicemail message.
- In Example 12, the subject matter of any one of Examples 1 to 11 may include, wherein the scoring module is to: analyze the voicemail message; and modify the local probabilistic score based on the analysis of the voicemail message.
- In Example 13, the subject matter of any one of Examples 1 to 12 may include, wherein the scoring module is to: analyze a user response to the voicemail message; and modify the local probabilistic score based on the user response.
- In Example 14, the subject matter of any one of Examples 1 to 13 may include, wherein the scoring module is to query the user for feedback on the incoming call, after the user has listened to the voicemail message; and modify the local probabilistic score based on the feedback.
- In Example 15, the subject matter of any one of Examples 1 to 14 may include, wherein the execution module is to: transmit the local probabilistic score to a reputation server.
- In Example 16, the subject matter of any one of Examples 1 to 15 may include, a server system communicatively coupled to the compute device, the server system to: manage, in a reputation database, a plurality of reputation scores for a corresponding plurality of phone numbers; receive a request from the compute device for a reputation score of a particular phone number; and transmit the reputation score of the particular phone number to the compute device.
- In Example 17, the subject matter of any one of Examples 1 to 16 may include, wherein to manage the plurality of reputation scores, the server system is to: receive local probabilistic scores from a plurality of compute devices for the particular phone number; calculate a reputation score for the particular phone number; and revise the reputation score for the particular phone number in the reputation database.
- In Example 18, the subject matter of any one of Examples 1 to 17 may include, wherein to manage the plurality of reputation scores, the server system is to: track usage of a phone number; and increase the reputation of the phone number based on the usage.
- Example 19 includes subject matter (such as a method, means for performing acts, machine readable medium including instructions that when performed by a machine cause the machine to performs acts, or an apparatus to perform) for implementing a collaborative phone reputation system comprising: detecting, at a compute device, an incoming call for a user of the compute device; determining a local probabilistic score that the incoming call is desirable for the user; and performing an action at the compute device based on the local probabilistic score.
- In Example 20, the subject matter of Example 19 may include, wherein determining the local probabilistic score comprises: determining that the incoming call is from a party in a contact list of the user; and increasing the local probabilistic score based on the determination that the incoming call is from the party in the contact list.
- In Example 21, the subject matter of any one of Examples 19 to 20 may include, increasing the local probabilistic score based on a frequency of calls from the party, a modality of calls from the party, or quality of contact of calls from the party.
- In Example 22, the subject matter of any one of Examples 19 to 21 may include, wherein performing the action comprises notifying the user of the incoming call.
- In Example 23, the subject matter of any one of Examples 19 to 22 may include, analyzing a user response to the notifying the user of the incoming call; and modifying the local probabilistic score based on the user response.
- In Example 24, the subject matter of any one of Examples 19 to 23 may include, wherein determining the local probabilistic score comprises: determining that the incoming call is from a party not in a contact list of the user; and decreasing the local probabilistic score based on the determination that the incoming call is from the party not in the contact list.
- In Example 25, the subject matter of any one of Examples 19 to 24 may include, wherein the incoming call includes an originating phone number, and wherein the method further comprises: obtaining a reputation score of the originating phone number; and modifying the local probabilistic score based on the reputation score.
- In Example 26, the subject matter of any one of Examples 19 to 25 may include, wherein obtaining the reputation score comprises obtaining the reputation score from a reputation server.
- In Example 27, the subject matter of any one of Examples 19 to 26 may include, wherein the incoming call is anonymized, and wherein the method further comprises: screening the incoming call; and modifying the local probabilistic score based on the screening.
- In Example 28, the subject matter of any one of Examples 19 to 27 may include, wherein screening the incoming call comprises: playing a pre-arranged greeting; and analyzing the response to the pre-arranged greeting.
- In Example 29, the subject matter of any one of Examples 19 to 28 may include, wherein the local probabilistic score is less than a threshold, and wherein performing the action at the compute device based on the local probabilistic score comprises sending the incoming call to voicemail to leave a voicemail message.
- In Example 30, the subject matter of any one of Examples 19 to 29 may include, analyzing the voicemail message; and modifying the local probabilistic score based on the analysis of the voicemail message.
- In Example 31, the subject matter of any one of Examples 19 to 30 may include, analyzing a user response to the voicemail message; and modifying the local probabilistic score based on the user response.
- In Example 32, the subject matter of any one of Examples 19 to 31 may include, querying the user for feedback on the incoming call, after the user has listened to the voicemail message; and modifying the local probabilistic score based on the feedback.
- In Example 33, the subject matter of any one of Examples 19 to 32 may include, transmitting the local probabilistic score to a reputation server.
- Example 34 includes at least one machine-readable medium including instructions, which when executed by a machine, cause the machine to perform operations of any of the Examples 19-33.
- Example 35 includes an apparatus comprising means for performing any of the Examples 19-33.
- Example 36 includes subject matter (such as a device, apparatus, or machine) for implementing a collaborative phone reputation system comprising: means for detecting, at a compute device, an incoming call for a user of the compute device; means for determining a local probabilistic score that the incoming call is desirable for the user; and means for performing an action at the compute device based on the local probabilistic score.
- In Example 37, the subject matter of Example 36 may include, wherein the means for determining the local probabilistic score comprise: means for determining that the incoming call is from a party in a contact list of the user; and means for increasing the local probabilistic score based on the determination that the incoming call is from the party in the contact list.
- In Example 38, the subject matter of any one of Examples 36 to 37 may include, means for increasing the local probabilistic score based on a frequency of calls from the party, a modality of calls from the party, or quality of contact of calls from the party.
- In Example 39, the subject matter of any one of Examples 36 to 38 may include, wherein the means for performing the action comprise means for notifying the user of the incoming call.
- In Example 40, the subject matter of any one of Examples 36 to 39 may include, means for analyzing a user response to the notifying the user of the incoming call; and means for modifying the local probabilistic score based on the user response.
- In Example 41, the subject matter of any one of Examples 36 to 40 may include, wherein the means for determining the local probabilistic score comprise: means for determining that the incoming call is from a party not in a contact list of the user; and means for decreasing the local probabilistic score based on the determination that the incoming call is from the party not in the contact list.
- In Example 42, the subject matter of any one of Examples 36 to 41 may include, wherein the incoming call includes an originating phone number, and wherein the apparatus further comprises: means for obtaining a reputation score of the originating phone number; and means for modifying the local probabilistic score based on the reputation score.
- In Example 43, the subject matter of any one of Examples 36 to 42 may include, wherein the means for obtaining the reputation score comprise means for obtaining the reputation score from a reputation server.
- In Example 44, the subject matter of any one of Examples 36 to 43 may include, wherein the incoming call is anonymized, and wherein the apparatus further comprises: means for screening the incoming call; and means for modifying the local probabilistic score based on the screening.
- In Example 45, the subject matter of any one of Examples 36 to 44 may include, wherein the means for screening the incoming call comprises: means for playing a pre-arranged greeting; and means for analyzing the response to the pre-arranged greeting.
- In Example 46, the subject matter of any one of Examples 36 to 45 may include, wherein the local probabilistic score is less than a threshold, and wherein the means for performing the action at the compute device based on the local probabilistic score comprise means for sending the incoming call to voicemail to leave a voicemail message.
- In Example 47, the subject matter of any one of Examples 36 to 46 may include, means for analyzing the voicemail message; and means for modifying the local probabilistic score based on the analysis of the voicemail message.
- In Example 48, the subject matter of any one of Examples 36 to 47 may include, means for analyzing a user response to the voicemail message; and means for modifying the local probabilistic score based on the user response.
- In Example 49, the subject matter of any one of Examples 36 to 48 may include, means for querying the user for feedback on the incoming call, after the user has listened to the voicemail message; and means for modifying the local probabilistic score based on the feedback.
- In Example 50, the subject matter of any one of Examples 36 to 49 may include, means for transmitting the local probabilistic score to a reputation server.
- The above detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show, by way of illustration, specific embodiments that may be practiced. These embodiments are also referred to herein as “examples.” Such examples may include elements in addition to those shown or described. However, also contemplated are examples that include the elements shown or described. Moreover, also contemplated are examples using any combination or permutation of those elements shown or described (or one or more aspects thereof), either with respect to a particular example (or one or more aspects thereof), or with respect to other examples (or one or more aspects thereof) shown or described herein.
- Publications, patents, and patent documents referred to in this document are incorporated by reference herein in their entirety, as though individually incorporated by reference. In the event of inconsistent usages between this document and those documents so incorporated by reference, the usage in the incorporated reference(s) are supplementary to that of this document; for irreconcilable inconsistencies, the usage in this document controls.
- In this document, the terms “a” or “an” are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of “at least one” or “one or more.” In this document, the term “or” is used to refer to a nonexclusive or, such that “A or B” includes “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.” Also, in the following claims, the terms “including” and “comprising” are open-ended, that is, a system, device, article, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms “first,” “second,” and “third,” etc. are used merely as labels, and are not intended to suggest a numerical order for their objects.
- The above description is intended to be illustrative, and not restrictive. For example, the above-described examples (or one or more aspects thereof) may be used in combination with others. Other embodiments may be used, such as by one of ordinary skill in the art upon reviewing the above description. The Abstract is to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Also, in the above Detailed Description, various features may be grouped together to streamline the disclosure. However, the claims may not set forth every feature disclosed herein as embodiments may feature a subset of said features. Further, embodiments may include fewer features than those disclosed in a particular example Thus, the following claims are hereby incorporated into the Detailed Description, with a claim standing on its own as a separate embodiment. The scope of the embodiments disclosed herein is to be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.
Claims (43)
1. (canceled)
2. A cellular telephone computing device that is capable of communicating, when the cellular telephone computing device is in operation, with a remote server system via at least one wireless network, the server system comprising database storage, the cellular telephone computing device comprising:
a touch screen-based user interface;
a display;
at least one camera;
at least one central processing unit that includes multiple cores;
semiconductor memory that includes flash memory, the semiconductor memory being capable of storing, at least in part, contacts information and client application instructions, the client application instructions being capable of being executed, at least in part, by the at least one central processing unit, the client application instructions when executed, at least in part, by the at least one central processing unit resulting in the cellular telephone computing device being capable of performing operations comprising:
displaying, via the display, at least one visual notification to a user of the cellular telephone computing device of an incoming call at the cellular telephone computing device, the incoming call being associated with a caller telephone number that is absent from the contacts information;
displaying, via the display, at least one other visual notification to the user, the at least one other visual notification being to notify the user that the incoming call possibly is a scam call, the at least one other visual notification being generated based, at least in part, upon reputation data stored, at least in part, in the database storage and to be associated, at least in part, with the telephone number;
receiving, via the touch screen-based user interface, user input that is capable of being in response, at least in part, to the incoming call, the user input being capable of being used to update, at least in part, the reputation data associated, at least in part, with the telephone number;
wherein:
the reputation data is capable of being based, at least in part, upon governmental and other users' report information reporting, at least in part, the telephone number as being associated, at least in part, with scam activity;
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of sensing biometric data and global positioning system-based location data.
3. The cellular telephone computing device of claim 2 , wherein:
the telephone number is also capable of being associated with an incoming text message; and
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of providing, at least in part, at least one further notification to the user that the incoming text message is a scam text message.
4. The cellular telephone computing device of claim 2 , wherein:
the reputation data is based, at least in part, upon reverse telephone number lookup information, country calling code information, area code information, and whether the telephone number is associated with a commercial line or residential line.
5. The cellular telephone computing device of claim 2 , wherein:
the cellular telephone computing device also comprises a vibration-based user alert motor to provide at least one vibration alert to indicate, at least in part, the incoming call to the user.
6. The cellular telephone computing device of claim 2 , wherein:
the report information comprises social media site-related information; and
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of sensing accelerometer information and compass-related information.
7. The cellular telephone computing device of claim 2 , wherein:
the reputation data includes, at least in part, reputation level to be associated with the telephone number; and
the reputation level is capable of being associated, at least in part, with probability that the incoming call is the scam call.
8. A method associated, at least in part, with use of a cellular telephone computing device, the cellular telephone computing device being capable of communicating, when the cellular telephone computing device is in operation, with a remote server system via at least one wireless network, the server system comprising database storage, the cellular telephone computing device comprising semiconductor memory and at least one central processing unit, the semiconductor memory comprising flash memory, the at least one central processing unit comprising multiple cores, the method comprising:
executing, at least in part, by the at least one central processing unit, client application instructions stored, at least in part, in the semiconductor memory, the semiconductor memory also being capable of storing, at least in part, contacts information, the executing, at least in part, of the client application instructions by the at least one central processing unit resulting in the cellular telephone computing device being capable of performing operations comprising:
displaying, via a display of the cellular telephone computing device, at least one visual notification to a user of the cellular telephone computing device of an incoming call at the cellular telephone computing device, the incoming call being associated with a caller telephone number that is absent from the contacts information;
displaying, via the display, at least one other visual notification to the user, the at least one other visual notification being to notify the user that the incoming call possibly is a scam call, the at least one other visual notification being generated based, at least in part, upon reputation data stored, at least in part, in the database storage and to be associated, at least in part, with the telephone number;
receiving, via a touch screen-based user interface of the cellular telephone computing device, user input that is capable of being in response, at least in part, to the incoming call, the user input being capable of being used to update, at least in part, the reputation data associated, at least in part, with the telephone number;
wherein:
the cellular telephone computing device comprises at least one camera;
the reputation data is capable of being based, at least in part, upon governmental and other users' report information reporting, at least in part, the telephone number as being associated, at least in part, with scam activity;
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of sensing biometric data and global positioning system-based location data.
9. The method of claim 8 , wherein:
the telephone number is also capable of being associated with an incoming text message; and
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of providing, at least in part, at least one further notification to the user that the incoming text message is a scam text message.
10. The method of claim 8 , wherein:
the reputation data is based, at least in part, upon reverse telephone number lookup information, country calling code information, area code information, and whether the telephone number is associated with a commercial line or residential line.
11. The method of claim 8 , wherein:
the cellular telephone computing device also comprises a vibration-based user alert motor to provide at least one vibration alert to indicate, at least in part, the incoming call to the user.
12. The method of claim 8 , wherein:
the report information comprises social media site-related information; and
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of sensing accelerometer information and compass-related information.
13. The method of claim 8 , wherein:
the reputation data includes, at least in part, reputation level to be associated with the telephone number; and
the reputation level is capable of being associated, at least in part, with probability that the incoming call is the scam call.
14. At least one non-transitory computer-readable memory storing client application instructions capable of being executed, at least in part, by at least one central processing unit of a cellular telephone computing device, the cellular telephone computing device being capable of communicating, when the cellular telephone computing device is in operation, with a remote server system via at least one wireless network, the server system comprising database storage, the cellular telephone computing device comprising semiconductor memory and at least one central processing unit, the semiconductor memory comprising flash memory, the at least one central processing unit comprising multiple cores, the instructions, when executed, at least in part, by the at least one central processing unit resulting in the cellular telephone computing device being capable of performing operations comprising:
displaying, via a display of the cellular telephone computing device, at least one visual notification to a user of the cellular telephone computing device of an incoming call at the cellular telephone computing device, the incoming call being associated with a caller telephone number that is absent from contacts information stored, at least in part, in the semiconductor memory;
displaying, via the display, at least one other visual notification to the user, the at least one other visual notification being to notify the user that the incoming call possibly is a scam call, the at least one other visual notification being generated based, at least in part, upon reputation data stored, at least in part, in the database storage and to be associated, at least in part, with the telephone number;
receiving, via a touch screen-based user interface of the cellular telephone computing device, user input that is capable of being in response, at least in part, to the incoming call, the user input being capable of being used to update, at least in part, the reputation data associated, at least in part, with the telephone number;
wherein:
the cellular telephone computing device comprises at least one camera;
the reputation data is capable of being based, at least in part, upon governmental and other users' report information reporting, at least in part, the telephone number as being associated, at least in part, with scam activity;
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of sensing biometric data and global positioning system-based location data.
15. The at least one non-transitory computer-readable memory of claim 14 , wherein:
the telephone number is also capable of being associated with an incoming text message; and
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of providing, at least in part, at least one further notification to the user that the incoming text message is a scam text message.
16. The at least one non-transitory computer-readable memory of claim 14 , wherein:
the reputation data is based, at least in part, upon reverse telephone number lookup information, country calling code information, area code information, and whether the telephone number is associated with a commercial line or residential line.
17. The at least one non-transitory computer-readable memory of claim 14 , wherein:
the cellular telephone computing device also comprises a vibration-based user alert motor to provide at least one vibration alert to indicate, at least in part, the incoming call to the user.
18. The at least one non-transitory computer-readable memory of claim 14 , wherein:
the report information comprises social media site-related information; and
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of sensing accelerometer information and compass-related information.
19. The at least one non-transitory computer-readable memory of claim 14 , wherein:
the reputation data includes, at least in part, reputation level to be associated with the telephone number; and
the reputation level is capable of being associated, at least in part, with probability that the incoming call is the scam call.
20. One or more non-transitory computer-readable memories storing client application instructions capable of being executed by a cellular telephone computing device, the cellular telephone computing device being capable of communicating, when the cellular telephone computing device is in operation, with a remote server system via one or more wireless networks, the server system comprising database storage, the cellular telephone computing device comprising semiconductor memory and one or more central processing units, the semiconductor memory comprising flash memory, the one or more central processing units comprising multiple cores, the instructions, when executed, by the cellular telephone computing device resulting in the cellular telephone computing device being capable of performing operations comprising:
displaying, via a display of the cellular telephone computing device, one or more visual notifications to a user of the cellular telephone computing device of an incoming call at the cellular telephone computing device, the incoming call being associated with a caller telephone number that is absent from contacts information stored in the semiconductor memory;
displaying, via the display, one or more other visual notifications to the user, the one or more other visual notifications being to notify the user that the incoming call possibly is a scam call, the one or more other visual notifications being generated based, at least in part, upon reputation data stored, at least in part, in the database storage and to be associated, at least in part, with the telephone number;
receiving, via a touch screen-based user interface of the cellular telephone computing device, user input that is capable of being in response, at least in part, to the incoming call, the user input being capable of being used to update, at least in part, the reputation data associated, at least in part, with the telephone number;
wherein:
the cellular telephone computing device comprises one or more cameras;
the reputation data is capable of being based, at least in part, upon governmental and other users' report information reporting, at least in part, the telephone number as being associated, at least in part, with scam activity;
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of sensing biometric data and global positioning system-based location data.
21. The one or more non-transitory computer-readable memories of claim 20 , wherein:
the telephone number is also capable of being associated with an incoming text message;
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of providing one or more further notifications to the user that the incoming text message is a scam text message;
the reputation data is based, at least in part, upon reverse telephone number lookup information, country calling code information, area code information, and whether the telephone number is associated with a commercial line or residential line;
the cellular telephone computing device also comprises a vibration-based user alert motor to provide at least one vibration alert to indicate, at least in part, the incoming call to the user.
22. The one or more non-transitory computer-readable memories of claim 20 , wherein:
the report information comprises social media site-related information;
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of sensing accelerometer information and compass-related information;
the reputation data includes reputation level to be associated with the telephone number; and
the reputation level is capable of being associated with probability that the incoming call is the scam call.
23. A server system that is capable of communicating with a cellular telephone computing device via at least one wireless network, the server system comprising:
at least one central processing unit;
database storage capable of storing reputation data associated, at least in part, with a caller telephone number, the reputation data being capable of being based, at least in part, upon governmental and users' report information reporting, at least in part, the telephone number as being associated, at least in part, with scam activity;
computer-readable memory capable of storing, at least in part, instructions that when executed, at least in part, by the at least one central processing unit result in the server system being capable of performing operations comprising:
providing, at least in part, other information to the cellular telephone computing device, the other information being based, at least in part, upon the reputation data, the cellular telephone computing device being capable of displaying, via a display of the cellular telephone computing device, at least one visual notification to a user of the cellular telephone computing device of an incoming call at the cellular telephone computing device, the incoming call being associated with the caller telephone number, the caller telephone number being absent from contacts information stored at the cellular telephone computing device, the cellular telephone computing device also being capable of displaying, via the display, at least one other visual notification to the user, the at least one other visual notification being to notify the user that the incoming call possibly is a scam call, the at least one other visual notification being generated based, at least in part, upon the other information;
updating, at least in part, the reputation data, based at least in part upon user input received, at least in part, via a touch screen-based user interface of the cellular telephone computing device, the user input being capable of being in response, at least in part, to the incoming call;
wherein:
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of sensing biometric data and global positioning system-based location data; and
the cellular telephone computing device comprises at least one camera.
24. The server system of claim 23 , wherein:
the telephone number is also capable of being associated with an incoming text message; and
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of providing, at least in part, based at least in part upon the other information, at least one further notification to the user that the incoming text message is a scam text message.
25. The server system of claim 23 , wherein:
the reputation data is based, at least in part, upon reverse telephone number lookup information, country calling code information, area code information, and whether the telephone number is associated with a commercial line or residential line.
26. The server system of claim 23 , wherein:
the cellular telephone computing device also comprises a vibration-based user alert motor to provide at least one vibration alert to indicate, at least in part, the incoming call to the user.
27. The server system of claim 23 , wherein:
the report information comprises social media site-related information; and
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of sensing accelerometer information and compass-related information.
28. The server system of claim 23 , wherein:
the reputation data includes, at least in part, reputation level to be associated with the telephone number; and
the reputation level is capable of being associated, at least in part, with probability that the incoming call is the scam call.
29. A method implemented, at least in part, using a server system, the server system being capable of communicating with a cellular telephone computing device via at least one wireless network, the method comprising:
executing, at least in part, by at least one central processing unit of the server system, instructions stored, at least in part, in computer-readable memory of the server system, the executing, at least in part, of the instructions resulting in the server system being capable of performing operations comprising:
storing, in a database storage of the server system, reputation data associated, at least in part, with a caller telephone number, the reputation data being capable of being based, at least in part, upon governmental and users' report information reporting, at least in part, the telephone number as being associated, at least in part, with scam activity;
providing, at least in part, other information to the cellular telephone computing device, the other information being based, at least in part, upon the reputation data, the cellular telephone computing device being capable of displaying, via a display of the cellular telephone computing device, at least one visual notification to a user of the cellular telephone computing device of an incoming call at the cellular telephone computing device, the incoming call being associated with the caller telephone number, the caller telephone number being absent from contacts information stored at the cellular telephone computing device, the cellular telephone computing device also being capable of displaying, via the display, at least one other visual notification to the user, the at least one other visual notification being to notify the user that the incoming call possibly is a scam call, the at least one other visual notification being generated based, at least in part, upon the other information;
updating, at least in part, the reputation data, based at least in part upon user input received, at least in part, via a touch screen-based user interface of the cellular telephone computing device, the user input being capable of being in response, at least in part, to the incoming call;
wherein:
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of sensing biometric data and global positioning system-based location data; and
the cellular telephone computing device comprises at least one camera.
30. The method of claim 29 , wherein:
the telephone number is also capable of being associated with an incoming text message; and
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of providing, at least in part, based at least in part upon the other information, at least one further notification to the user that the incoming text message is a scam text message.
31. The method of claim 29 , wherein:
the reputation data is based, at least in part, upon reverse telephone number lookup information, country calling code information, area code information, and whether the telephone number is associated with a commercial line or residential line.
32. The method of claim 29 , wherein:
the cellular telephone computing device also comprises a vibration-based user alert motor to provide at least one vibration alert to indicate, at least in part, the incoming call to the user.
33. The method of claim 29 , wherein:
the report information comprises social media site-related information; and
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of sensing accelerometer information and compass-related information.
34. The method of claim 29 , wherein:
the reputation data includes, at least in part, reputation level to be associated with the telephone number; and
the reputation level is capable of being associated, at least in part, with probability that the incoming call is the scam call.
35. At least one non-transitory computer-readable memory storing instructions capable of being executed, at least in part, by at least one central processing unit of a server system, the server system being capable of communicating with a cellular telephone computing device via at least one wireless network, the instructions, when executed, at least in part, by the at least one central processing unit resulting in the server system being capable of performing operations comprising:
storing, in a database storage of the server system, reputation data associated, at least in part, with a caller telephone number, the reputation data being capable of being based, at least in part, upon governmental and users' report information reporting, at least in part, the telephone number as being associated, at least in part, with scam activity;
providing, at least in part, other information to the cellular telephone computing device, the other information being based, at least in part, upon the reputation data, the cellular telephone computing device being capable of displaying, via a display of the cellular telephone computing device, at least one visual notification to a user of the cellular telephone computing device of an incoming call at the cellular telephone computing device, the incoming call being associated with the caller telephone number, the caller telephone number being absent from contacts information stored at the cellular telephone computing device, the cellular telephone computing device also being capable of displaying, via the display, at least one other visual notification to the user, the at least one other visual notification being to notify the user that the incoming call possibly is a scam call, the at least one other visual notification being generated based, at least in part, upon the other information;
updating, at least in part, the reputation data, based at least in part upon user input received, at least in part, via a touch screen-based user interface of the cellular telephone computing device, the user input being capable of being in response, at least in part, to the incoming call;
wherein:
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of sensing biometric data and global positioning system-based location data; and
the cellular telephone computing device comprises at least one camera.
36. The at least one non-transitory computer-readable memory of claim 35 , wherein:
the telephone number is also capable of being associated with an incoming text message; and
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of providing, at least in part, based at least in part upon the other information, at least one further notification to the user that the incoming text message is a scam text message.
37. The at least one non-transitory computer-readable memory of claim 35 , wherein:
the reputation data is based, at least in part, upon reverse telephone number lookup information, country calling code information, area code information, and whether the telephone number is associated with a commercial line or residential line.
38. The at least one non-transitory computer-readable memory of claim 35 , wherein:
the cellular telephone computing device also comprises a vibration-based user alert motor to provide at least one vibration alert to indicate, at least in part, the incoming call to the user.
39. The at least one non-transitory computer-readable memory of claim 35 , wherein:
the report information comprises social media site-related information; and
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of sensing accelerometer information and compass-related information.
40. The at least one non-transitory computer-readable memory of claim 35 , wherein:
the reputation data includes, at least in part, reputation level to be associated with the telephone number; and
the reputation level is capable of being associated, at least in part, with probability that the incoming call is the scam call.
41. One or more non-transitory computer-readable memories storing instructions capable of being executed, at least in part, by one or more central processing units of a server system, the server system being capable of communicating with a cellular telephone computing device via one or more wireless networks, the instructions, when executed, at least in part, by the one or more central processing units resulting in the server system being capable of performing operations comprising:
storing, in a database storage of the server system, reputation data associated with a caller telephone number, the reputation data being capable of being based, at least in part, upon governmental and users' report information reporting, at least in part, the telephone number as being associated with scam activity;
providing, at least in part, other information to the cellular telephone computing device, the other information being based, at least in part, upon the reputation data, the cellular telephone computing device being capable of displaying, via a display of the cellular telephone computing device, one or more visual notifications to a user of the cellular telephone computing device of an incoming call at the cellular telephone computing device, the incoming call being associated with the caller telephone number, the caller telephone number being absent from contacts information stored at the cellular telephone computing device, the cellular telephone computing device also being capable of displaying, via the display, one or more other visual notifications to the user, the one or more other visual notifications being to notify the user that the incoming call possibly is a scam call, the one or more other visual notifications being generated based, at least in part, upon the other information;
updating, at least in part, the reputation data, based at least in part upon user input received, at least in part, via a touch screen-based user interface of the cellular telephone computing device, the user input being capable of being in response, at least in part, to the incoming call;
wherein:
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of sensing biometric data and global positioning system-based location data; and
the cellular telephone computing device comprises at least one camera.
42. The one or more non-transitory computer-readable memories of claim 41 , wherein:
the telephone number is also capable of being associated with an incoming text message;
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of providing, based at least in part upon the other information, one or more further notifications to the user that the incoming text message is a scam text message;
the reputation data is based, at least in part, upon reverse telephone number lookup information, country calling code information, area code information, and whether the telephone number is associated with a commercial line or residential line;
the cellular telephone computing device also comprises a vibration-based user alert motor to provide at least one vibration alert to indicate, at least in part, the incoming call to the user.
43. The one or more non-transitory computer-readable memories of claim 41 , wherein:
the report information comprises social media site-related information;
the cellular telephone computing device is capable, when the cellular telephone computing device is in the operation, of sensing accelerometer information and compass-related information;
the reputation data includes reputation level to be associated with the telephone number; and
the reputation level is capable of being associated with probability that the incoming call is the scam call.
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/250,019 US10044855B2 (en) | 2014-12-23 | 2016-08-29 | Collaborative phone reputation system |
US15/910,362 US10715659B2 (en) | 2014-12-23 | 2018-03-02 | Collaborative phone reputation system |
US16/887,482 US11032417B2 (en) | 2014-12-23 | 2020-05-29 | Collaborative phone reputation system |
US17/313,824 US11838443B2 (en) | 2014-12-23 | 2021-05-06 | Collaborative phone reputation system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/581,446 US9432506B2 (en) | 2014-12-23 | 2014-12-23 | Collaborative phone reputation system |
US15/250,019 US10044855B2 (en) | 2014-12-23 | 2016-08-29 | Collaborative phone reputation system |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/581,446 Continuation US9432506B2 (en) | 2014-12-23 | 2014-12-23 | Collaborative phone reputation system |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/910,362 Continuation US10715659B2 (en) | 2014-12-23 | 2018-03-02 | Collaborative phone reputation system |
Publications (2)
Publication Number | Publication Date |
---|---|
US20170048387A1 true US20170048387A1 (en) | 2017-02-16 |
US10044855B2 US10044855B2 (en) | 2018-08-07 |
Family
ID=56130940
Family Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/581,446 Active US9432506B2 (en) | 2014-12-23 | 2014-12-23 | Collaborative phone reputation system |
US15/250,019 Active US10044855B2 (en) | 2014-12-23 | 2016-08-29 | Collaborative phone reputation system |
US15/910,362 Active 2035-02-27 US10715659B2 (en) | 2014-12-23 | 2018-03-02 | Collaborative phone reputation system |
US16/887,482 Active US11032417B2 (en) | 2014-12-23 | 2020-05-29 | Collaborative phone reputation system |
US17/313,824 Active 2035-08-17 US11838443B2 (en) | 2014-12-23 | 2021-05-06 | Collaborative phone reputation system |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/581,446 Active US9432506B2 (en) | 2014-12-23 | 2014-12-23 | Collaborative phone reputation system |
Family Applications After (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/910,362 Active 2035-02-27 US10715659B2 (en) | 2014-12-23 | 2018-03-02 | Collaborative phone reputation system |
US16/887,482 Active US11032417B2 (en) | 2014-12-23 | 2020-05-29 | Collaborative phone reputation system |
US17/313,824 Active 2035-08-17 US11838443B2 (en) | 2014-12-23 | 2021-05-06 | Collaborative phone reputation system |
Country Status (6)
Country | Link |
---|---|
US (5) | US9432506B2 (en) |
EP (3) | EP3238470B1 (en) |
JP (3) | JP2018505578A (en) |
KR (1) | KR102366307B1 (en) |
CN (2) | CN107113360A (en) |
WO (1) | WO2016105891A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018208646A1 (en) * | 2017-05-08 | 2018-11-15 | T-Mobile Usa, Inc. | Network-controlled robocall and scam call handling |
Families Citing this family (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9432506B2 (en) * | 2014-12-23 | 2016-08-30 | Intel Corporation | Collaborative phone reputation system |
DE112015006814T5 (en) * | 2015-08-20 | 2018-05-24 | Motorola Solutions, Inc. | METHOD AND DEVICE FOR CHANGING A MODE OF A DEVICE FROM A RIGHT HAND MODE TO A LEFT HAND MODE, AND VICE VERSA, OR TO A NORMAL MODE TO A DEFAULT MODE |
US9692885B2 (en) * | 2015-11-17 | 2017-06-27 | Microsoft Technology Licensing, Llc | Determining scam risk during a voice call |
US10476975B2 (en) | 2015-12-31 | 2019-11-12 | Palantir Technologies Inc. | Building a user profile data repository |
US10141009B2 (en) | 2016-06-28 | 2018-11-27 | Pindrop Security, Inc. | System and method for cluster-based audio event detection |
US10244109B2 (en) * | 2016-07-13 | 2019-03-26 | International Business Machines Corporation | Detection of a spear-phishing phone call |
CN106161713B (en) * | 2016-08-30 | 2019-10-29 | Tcl移动通信科技(宁波)有限公司 | A kind of method and system that strange number in mobile phone is automatically stored |
US10325601B2 (en) | 2016-09-19 | 2019-06-18 | Pindrop Security, Inc. | Speaker recognition in the call center |
US9654622B1 (en) * | 2016-10-05 | 2017-05-16 | Google Inc. | Automatically altering characteristics of audio alerts |
US10304445B2 (en) * | 2016-10-13 | 2019-05-28 | Viesoft, Inc. | Wearable device for speech training |
US10650055B2 (en) | 2016-10-13 | 2020-05-12 | Viesoft, Inc. | Data processing for continuous monitoring of sound data and advanced life arc presentation analysis |
GB2563947B (en) | 2017-06-30 | 2020-01-01 | Resilient Plc | Fraud Detection System |
US10805459B1 (en) * | 2018-08-07 | 2020-10-13 | First Orion Corp. | Call screening service for communication devices |
GB2580325B (en) | 2018-12-28 | 2023-09-06 | Resilient Plc | Fraud detection system |
US11019201B2 (en) | 2019-02-06 | 2021-05-25 | Pindrop Security, Inc. | Systems and methods of gateway detection in a telephone network |
WO2020198354A1 (en) * | 2019-03-25 | 2020-10-01 | Pindrop Security, Inc. | Detection of calls from voice assistants |
EP3633964A1 (en) * | 2019-03-28 | 2020-04-08 | ALE International | Method for assisting a callee with a reputation score of a caller |
US12015637B2 (en) | 2019-04-08 | 2024-06-18 | Pindrop Security, Inc. | Systems and methods for end-to-end architectures for voice spoofing detection |
CN110086943A (en) * | 2019-04-29 | 2019-08-02 | 北京羽乐创新科技有限公司 | Number monitoring method and device |
AU2019302938A1 (en) * | 2019-10-11 | 2021-04-29 | Alipay (Hangzhou) Information Technology Co., Ltd. | Decentralized automatic phone fraud risk management |
CN111046366B (en) * | 2019-12-17 | 2022-05-20 | 佳讯飞鸿(北京)智能科技研究院有限公司 | User identity identification method and device and electronic equipment |
WO2021247987A1 (en) * | 2020-06-04 | 2021-12-09 | Nuance Communications, Inc. | Fraud detection system and method |
US11283921B1 (en) * | 2020-08-10 | 2022-03-22 | Intrado Corporation | Mitigating disturbances at a call center |
US11838444B1 (en) | 2020-08-10 | 2023-12-05 | Intrado Life & Safety, Inc. | Queuing calls based on disturbance |
US11570297B2 (en) * | 2020-08-13 | 2023-01-31 | First Orion Corp. | Conditional communication forwarding based on origination and destination attributes |
US11330098B1 (en) | 2020-11-06 | 2022-05-10 | Sevis Systems, Llc | System and method for enabling trusted caller identity and spoofed call prevention |
US11882239B2 (en) * | 2021-05-19 | 2024-01-23 | Mcafee, Llc | Fraudulent call detection |
Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030156707A1 (en) * | 2002-02-21 | 2003-08-21 | International Business Machines Corporation | Rating parties according to party identities |
US20040264663A1 (en) * | 2002-01-10 | 2004-12-30 | Enzmann Mark J. | Call prevention device and method |
US20050185784A1 (en) * | 2004-02-20 | 2005-08-25 | Samuel Chiu | Method and electronic device for selective telephone call screening |
US20060182029A1 (en) * | 2005-02-15 | 2006-08-17 | At&T Corp. | Arrangement for managing voice over IP (VoIP) telephone calls, especially unsolicited or unwanted calls |
US20080077515A1 (en) * | 2006-09-18 | 2008-03-27 | Fair Isaac Corporation | Self-Calibrating Fraud Detection |
US20130268470A1 (en) * | 2012-04-06 | 2013-10-10 | Kaspersky Lab, Zao | System and method for filtering spam messages based on user reputation |
US8565396B1 (en) * | 2011-10-14 | 2013-10-22 | Symantec Corporation | Systems and methods to detect a scam on a communications device |
US8577002B2 (en) * | 2007-08-15 | 2013-11-05 | Primus Telecommunications Canada, Inc. | Call screening system and method |
US20140105373A1 (en) * | 2012-10-17 | 2014-04-17 | Kedlin Company, LLC | Methods and systems for inbound call control |
US8781093B1 (en) * | 2012-04-18 | 2014-07-15 | Google Inc. | Reputation based message analysis |
US9288319B2 (en) * | 2013-12-18 | 2016-03-15 | Aaron Foss | Call management system |
US20160094944A1 (en) * | 2014-09-30 | 2016-03-31 | Ebay Inc. | Super geo-fences and virtual fences to improve efficiency of geo-fences |
Family Cites Families (74)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5473671A (en) * | 1994-03-11 | 1995-12-05 | At&T Corp. | Selective screening of incoming calls for cellular telephone systems |
JP3508417B2 (en) * | 1996-08-22 | 2004-03-22 | ヤマハ株式会社 | Data communication method |
US20010036258A1 (en) * | 2000-06-01 | 2001-11-01 | Binay Sugla | Telecommunication service for prioritizing and enhancing privacy of incoming calls |
US6748422B2 (en) * | 2000-10-19 | 2004-06-08 | Ebay Inc. | System and method to control sending of unsolicited communications relating to a plurality of listings in a network-based commerce facility |
JP4632618B2 (en) * | 2002-05-09 | 2011-02-16 | 日本電気株式会社 | User data automatic change system |
JP2004260354A (en) * | 2003-02-24 | 2004-09-16 | Fujitsu Ltd | Method and program for controlling incoming call in telephone set, and telephone set |
JP2005072943A (en) * | 2003-08-25 | 2005-03-17 | Casio Comput Co Ltd | Communication terminal and communication information processing program |
US7454008B1 (en) * | 2004-03-25 | 2008-11-18 | Prairie Systems, Inc. | System for classifying lists of telephone numbers |
US7673003B2 (en) * | 2004-04-28 | 2010-03-02 | Microsoft Corporation | Social network email filtering |
CA2536725C (en) * | 2005-02-18 | 2014-04-22 | Telmetrics Inc. | Systems and methods for call measurement |
JP2006350870A (en) | 2005-06-17 | 2006-12-28 | Nippon Telegr & Teleph Corp <Ntt> | Method for generating reputation information, device for managing reputation information, receipt device, communication system, and program for managing reputation informaiton |
US20070106734A1 (en) * | 2005-11-10 | 2007-05-10 | Motorola, Inc. | Incentive driven subscriber assisted spam reduction |
CN101009737B (en) * | 2006-01-26 | 2010-09-15 | 国际商业机器公司 | Method and device for preventing rubbish voice call |
US20080015952A1 (en) | 2006-07-11 | 2008-01-17 | Jonathan William Medved | Drag and drop selection of products |
CN1937671B (en) * | 2006-09-25 | 2011-07-20 | 华为技术有限公司 | Garbage telephone-resistance method, system, terminal and server end |
US8270588B2 (en) | 2006-10-04 | 2012-09-18 | Ronald Schwartz | Method and system for incoming call management |
JP4636562B2 (en) * | 2006-10-16 | 2011-02-23 | 富士通株式会社 | Call control system, communication terminal, scale value data storage device, and program |
US8527592B2 (en) * | 2006-10-31 | 2013-09-03 | Watchguard Technologies, Inc. | Reputation-based method and system for determining a likelihood that a message is undesired |
US20080159521A1 (en) * | 2006-12-29 | 2008-07-03 | Dave Sneyders | System For Establishing Outbound Communications With Contacts From A Call Center |
US7895154B2 (en) * | 2007-03-28 | 2011-02-22 | Microsoft Corporation | Communication reputation |
ATE500671T1 (en) * | 2007-10-03 | 2011-03-15 | Research In Motion Ltd | METHOD AND DEVICE FOR COLLABORATIVE FILTERING OF ELECTRONIC MAIL |
US8176001B2 (en) | 2007-10-18 | 2012-05-08 | Redshift Internetworking, Inc. | System and method for detecting spam over internet telephony (SPIT) in IP telecommunication systems |
US20090136013A1 (en) * | 2007-11-19 | 2009-05-28 | Kuykendall Peter A | System for obtaining information regarding telephone calls |
US8141152B1 (en) * | 2007-12-18 | 2012-03-20 | Avaya Inc. | Method to detect spam over internet telephony (SPIT) |
US8713450B2 (en) * | 2008-01-08 | 2014-04-29 | International Business Machines Corporation | Detecting patterns of abuse in a virtual environment |
US8379816B1 (en) * | 2008-05-15 | 2013-02-19 | Trend Micro Incorporated | Methods and arrangement for handling phishing calls for telecommunication-enabled devices |
JP2009290248A (en) * | 2008-05-27 | 2009-12-10 | Sanyo Electric Co Ltd | Communication terminal device |
US8116727B1 (en) * | 2008-06-19 | 2012-02-14 | Sprint Spectrum L.P. | Method and system for determining and presenting a current likelihood of a mobile station successfully engaging in a communication session |
US9002333B1 (en) | 2008-08-11 | 2015-04-07 | Trend Micro Inc. | Mobile device reputation system |
US20100128863A1 (en) * | 2008-11-21 | 2010-05-27 | Robert Bosch Gmbh | Context aware voice communication proxy |
US8488479B2 (en) * | 2008-12-19 | 2013-07-16 | At&T Intellectual Property I, L.P. | Method and apparatus for providing protection against spam |
JP2010148003A (en) * | 2008-12-22 | 2010-07-01 | Nec Corp | System, method and program for preventing bank transfer scam using mail, server, and mobile terminal device |
JP2010232729A (en) * | 2009-03-25 | 2010-10-14 | Kyocera Corp | Communication terminal and communication system |
US20100268655A1 (en) * | 2009-04-15 | 2010-10-21 | Joel Cheuoua | Social Capital |
US8238532B1 (en) | 2009-05-19 | 2012-08-07 | TrustID, Inc. | Method of and system for discovering and reporting trustworthiness and credibility of calling party number information |
US8290132B2 (en) * | 2009-08-21 | 2012-10-16 | Avaya Inc. | Communications history log system |
US9277021B2 (en) * | 2009-08-21 | 2016-03-01 | Avaya Inc. | Sending a user associated telecommunication address |
US20110294478A1 (en) * | 2010-05-26 | 2011-12-01 | Google Inc. | Telephone Caller Classification |
US8416923B2 (en) | 2010-06-23 | 2013-04-09 | Twilio, Inc. | Method for providing clean endpoint addresses |
US9253199B2 (en) * | 2010-09-09 | 2016-02-02 | Red Hat, Inc. | Verifying authenticity of a sender of an electronic message sent to a recipient using message salt |
FR2969088B1 (en) | 2010-12-17 | 2013-04-12 | Bosch Gmbh Robert | BRAKE MASTER CYLINDER FOR AUTOMOTIVE VEHICLE BRAKES WITH ANTI-RETURN SEAL AND JOINT FOR SUCH A MASTER CYLINDER |
CN103688245A (en) * | 2010-12-30 | 2014-03-26 | 安比恩特兹公司 | Information processing using a population of data acquisition devices |
WO2012111489A1 (en) * | 2011-02-15 | 2012-08-23 | 富士通株式会社 | Operator selection device, operator selection program, and operator selection method |
US9137370B2 (en) * | 2011-05-09 | 2015-09-15 | Insidesales.com | Call center input/output agent utilization arbitration system |
CN202142288U (en) * | 2011-07-07 | 2012-02-08 | 龙旗科技(上海)有限公司 | Safety voice communication apparatus of portable terminal |
US11232476B1 (en) * | 2011-09-01 | 2022-01-25 | Dialogtech, Inc. | System, method, and computer program product for tracking calls |
JP6157881B2 (en) * | 2012-03-06 | 2017-07-05 | トビラシステムズ株式会社 | Terminal device, incoming call management system, and program |
US8634877B2 (en) * | 2012-04-09 | 2014-01-21 | International Business Machines Corporation | Automatic escalation/degradation of notifications of repetitive calls |
CN102724355A (en) * | 2012-05-04 | 2012-10-10 | 北京百纳威尔科技有限公司 | Garbage information processing method and mobile phone termina |
CN103458412B (en) * | 2012-06-04 | 2017-03-15 | 百度在线网络技术(北京)有限公司 | Prevent system, method and mobile terminal, the high in the clouds Analysis server of telephone fraud |
JP2014045454A (en) * | 2012-08-28 | 2014-03-13 | Sharp Corp | Telephone, telephone control method, program, and recording medium |
US20140096246A1 (en) * | 2012-10-01 | 2014-04-03 | Google Inc. | Protecting users from undesirable content |
US8913994B2 (en) * | 2012-11-02 | 2014-12-16 | Lookout, Inc. | System and method for call blocking and SMS blocking |
JP2014129067A (en) | 2012-12-28 | 2014-07-10 | Auto Network Gijutsu Kenkyusho:Kk | Control device |
US9014359B1 (en) * | 2013-01-11 | 2015-04-21 | Time Warner Cable Enterprises Llc | Generation of phone number lists and call filtering |
KR102069867B1 (en) * | 2013-03-14 | 2020-01-23 | 삼성전자주식회사 | Contact provision using context information |
CN103179122B (en) * | 2013-03-22 | 2015-11-18 | 马博 | A kind of anti-telecommunications telephone fraud method and system based on voice semantic content analysis |
US9264870B2 (en) * | 2013-04-08 | 2016-02-16 | Xiaomi Inc. | Mobile terminal, server and calling method based on cloud contact list |
CN104159229B (en) * | 2013-05-15 | 2019-01-11 | 腾讯科技(深圳)有限公司 | Incoming call processing method and device |
US9100475B2 (en) * | 2013-05-17 | 2015-08-04 | Vonage Network Llc | Routing communications based on history of previous communications |
CN103971700A (en) * | 2013-08-01 | 2014-08-06 | 哈尔滨理工大学 | Voice monitoring method and device |
US9386148B2 (en) * | 2013-09-23 | 2016-07-05 | Ooma, Inc. | Identifying and filtering incoming telephone calls to enhance privacy |
CN103685613B (en) * | 2013-12-05 | 2016-08-17 | 江苏大学 | A kind of anti-telephone fraud system and method based on speech recognition |
CN103731832A (en) * | 2013-12-26 | 2014-04-16 | 黄伟 | System and method for preventing phone and short message frauds |
EP3132596B1 (en) * | 2014-04-12 | 2021-03-17 | Pick up Mobile (2015) Ltd | Systems and methods for sharing selected data by phone call |
US9999019B2 (en) * | 2014-05-23 | 2018-06-12 | Samsung Electronics Co., Ltd. | Wearable device and method of setting reception of notification message therein |
CN104065836A (en) * | 2014-05-30 | 2014-09-24 | 小米科技有限责任公司 | Method and device for monitoring calls |
CH709795B1 (en) * | 2014-06-18 | 2021-02-26 | Katia Sa | A method and system for filtering unwanted incoming telephone calls. |
KR102150624B1 (en) * | 2014-07-01 | 2020-09-01 | 삼성전자 주식회사 | Method and apparatus for notifying smishing |
CN104052880A (en) * | 2014-07-02 | 2014-09-17 | 深圳市中兴移动通信有限公司 | Mobile terminal and harassment information processing method and device thereof |
US10070282B2 (en) * | 2014-07-23 | 2018-09-04 | Verizon Patent And Licensing Inc. | System and method for handling undesired communication at a mobile device |
US9432506B2 (en) * | 2014-12-23 | 2016-08-30 | Intel Corporation | Collaborative phone reputation system |
US9769310B2 (en) * | 2015-11-19 | 2017-09-19 | Global Tel*Link Corporation | Authentication and control of incoming communication |
US11330098B1 (en) * | 2020-11-06 | 2022-05-10 | Sevis Systems, Llc | System and method for enabling trusted caller identity and spoofed call prevention |
-
2014
- 2014-12-23 US US14/581,446 patent/US9432506B2/en active Active
-
2015
- 2015-12-02 JP JP2017528828A patent/JP2018505578A/en active Pending
- 2015-12-02 EP EP15874076.1A patent/EP3238470B1/en active Active
- 2015-12-02 WO PCT/US2015/063412 patent/WO2016105891A1/en active Application Filing
- 2015-12-02 EP EP22154943.9A patent/EP4027631A3/en active Pending
- 2015-12-02 EP EP17020462.2A patent/EP3291524B1/en active Active
- 2015-12-02 CN CN201580063496.XA patent/CN107113360A/en active Pending
- 2015-12-02 KR KR1020177013983A patent/KR102366307B1/en active IP Right Grant
- 2015-12-02 CN CN201811010744.6A patent/CN108696644A/en active Pending
-
2016
- 2016-08-29 US US15/250,019 patent/US10044855B2/en active Active
-
2017
- 2017-10-24 JP JP2017204974A patent/JP6701148B2/en active Active
-
2018
- 2018-03-02 US US15/910,362 patent/US10715659B2/en active Active
- 2018-09-05 JP JP2018165794A patent/JP2019004503A/en active Pending
-
2020
- 2020-05-29 US US16/887,482 patent/US11032417B2/en active Active
-
2021
- 2021-05-06 US US17/313,824 patent/US11838443B2/en active Active
Patent Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040264663A1 (en) * | 2002-01-10 | 2004-12-30 | Enzmann Mark J. | Call prevention device and method |
US20030156707A1 (en) * | 2002-02-21 | 2003-08-21 | International Business Machines Corporation | Rating parties according to party identities |
US20050185784A1 (en) * | 2004-02-20 | 2005-08-25 | Samuel Chiu | Method and electronic device for selective telephone call screening |
US20060182029A1 (en) * | 2005-02-15 | 2006-08-17 | At&T Corp. | Arrangement for managing voice over IP (VoIP) telephone calls, especially unsolicited or unwanted calls |
US20080077515A1 (en) * | 2006-09-18 | 2008-03-27 | Fair Isaac Corporation | Self-Calibrating Fraud Detection |
US8577002B2 (en) * | 2007-08-15 | 2013-11-05 | Primus Telecommunications Canada, Inc. | Call screening system and method |
US8565396B1 (en) * | 2011-10-14 | 2013-10-22 | Symantec Corporation | Systems and methods to detect a scam on a communications device |
US20130268470A1 (en) * | 2012-04-06 | 2013-10-10 | Kaspersky Lab, Zao | System and method for filtering spam messages based on user reputation |
US8781093B1 (en) * | 2012-04-18 | 2014-07-15 | Google Inc. | Reputation based message analysis |
US20140105373A1 (en) * | 2012-10-17 | 2014-04-17 | Kedlin Company, LLC | Methods and systems for inbound call control |
US9288319B2 (en) * | 2013-12-18 | 2016-03-15 | Aaron Foss | Call management system |
US20160094944A1 (en) * | 2014-09-30 | 2016-03-31 | Ebay Inc. | Super geo-fences and virtual fences to improve efficiency of geo-fences |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018208646A1 (en) * | 2017-05-08 | 2018-11-15 | T-Mobile Usa, Inc. | Network-controlled robocall and scam call handling |
Also Published As
Publication number | Publication date |
---|---|
EP3238470A1 (en) | 2017-11-01 |
JP2018505578A (en) | 2018-02-22 |
EP4027631A3 (en) | 2022-10-26 |
US11032417B2 (en) | 2021-06-08 |
EP3291524A1 (en) | 2018-03-07 |
JP2019004503A (en) | 2019-01-10 |
US10044855B2 (en) | 2018-08-07 |
CN107113360A (en) | 2017-08-29 |
JP2018038066A (en) | 2018-03-08 |
WO2016105891A1 (en) | 2016-06-30 |
US11838443B2 (en) | 2023-12-05 |
US20210360104A1 (en) | 2021-11-18 |
KR102366307B1 (en) | 2022-02-23 |
US20160182716A1 (en) | 2016-06-23 |
US20180295235A1 (en) | 2018-10-11 |
EP3291524B1 (en) | 2022-02-09 |
EP3238470B1 (en) | 2024-04-03 |
KR20170099854A (en) | 2017-09-01 |
US9432506B2 (en) | 2016-08-30 |
EP3238470A4 (en) | 2018-07-18 |
US10715659B2 (en) | 2020-07-14 |
JP6701148B2 (en) | 2020-05-27 |
EP4027631A2 (en) | 2022-07-13 |
CN108696644A (en) | 2018-10-23 |
US20200412870A1 (en) | 2020-12-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11838443B2 (en) | Collaborative phone reputation system | |
US10447838B2 (en) | Telephone fraud management system and method | |
US10116792B2 (en) | Adding additional information to caller ID information | |
US9531888B2 (en) | Intelligent ringer in smartphones | |
US20100087173A1 (en) | Inter-threading Indications of Different Types of Communication | |
US20140274002A1 (en) | Enhanced caller identification | |
EP3891971B1 (en) | Detection of spoofed calls using call header | |
US10659605B1 (en) | Automatically unsubscribing from automated calls based on call audio patterns | |
US7995719B2 (en) | Coordination of a voicemail response with calendar scheduling | |
JP6296159B2 (en) | Caller identification device, caller identification method, and recording medium for storing caller identification program | |
CN114731355A (en) | Incoming call control based on call settings | |
US20230040084A1 (en) | Automatic call categorization and screening | |
KR101593444B1 (en) | Method for providing estimated receipt result according to receiver list | |
US9881325B1 (en) | Real-time provision of ratings information and crowd-sourcing of ratings and reviews |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |