Method and System for Incoming Call Management

• US 20080084975A1
• Filed: 01/05/2007
• Published: 04/10/2008
• Est. Priority Date: 10/04/2006
• Status: Active Grant

• Current Assignee: Ronald Schwartz
• Original Assignee: Ronald Schwartz
• Inventors: Schwartz, Ronald
• Granted Patent: US 8,270,588 B2
• Time in Patent Office: Days
• US Class Current: 379/88.22
• CPC Class Codes: H04M 1/57 Arrangements for indicating or recording the number of the calling subscriber at the called subscriber's set at the operator set in a manual exchange H04M5/20
• CPC Class Codes: H04M 1/663 Preventing unauthorised calls to a telephone set
• CPC Class Codes: H04M 2201/18 Comparators
• CPC Class Codes: H04M 2250/60 logging of communication history, e.g. outgoing or incoming calls, missed calls, messages or URLs logging of telephone numbers H04M1/56, H04M1/57
• CPC Class Codes: H04M 3/436 Arrangements for screening incoming calls , i.e. evaluating the characteristics of a call before deciding whether to answer it based on the calling party profile H04M3/42059; based on location H04M3/42348; based on presence H04M3/42365; diversion H04M3/54

Abstract

A method and system for automatic incoming call management uses function test results to build call signatures that are stored for later use in incoming call analysis. The function test results are used to compute a suspect score and confidence level associated with each incoming call, and are also used for making incoming call management decisions. A call treatment is selected based on the function test results and/or the computed suspect score and confidence level.

Claims

1. A method of managing an incoming call to a service subscriber, comprising:

performing at least one real-time function test on a call offer message associated with the incoming call to build a signature for the incoming call; and

using information associated with the signature to make an incoming call management decision to determine a treatment for the incoming call.

2. The method as claimed in claim 1 wherein performing at least one real-time function test comprises performing function tests to confirm a validity of a caller identity and a call source associated with the call offer message.

3. The method as claimed in claim 1 further comprising storing the signature in a call state database prior to using the information to make the incoming call management decision.

4. The method as claimed in claim 1 further comprising using the information to compute a suspect score and a confidence level respecting the incoming call to determine the treatment for the incoming call.

5. The method as claimed in claim 4 further comprising using the suspect score and the confidence level to determine whether the caller identity is valid.

6. The method as claimed in claim 5 wherein if the caller identity is valid, the method further comprises checking a subscriber black list to determine whether the caller identity is associated with an unwanted caller, and directing the incoming call to special treatment if the caller identity is in the subscriber black list.

7. The method as claimed in claim 6 wherein if the caller identity is valid and not in the subscriber black list, the method further comprises checking a subscriber white list to determine whether the caller identity is associated with an wanted caller, and offering the incoming call to the subscriber if the caller identity is in the subscriber white list.

8. The method as claimed in claim 7 wherein checking the subscriber white list comprises checking a permanent white list maintained by the subscriber, and checking a dynamic white list automatically maintained by a call director responsible for making the incoming call management decision.

9. The method as claimed in claim 4 wherein if the caller identity is not valid, the method comprises using the signature to search a signatures database for matching signatures to determine the treatment for the incoming call.

10. The method as claimed in claim 8 wherein if the caller identity is valid but of the caller identity is not found in the subscriber black list, the subscriber white list, or the dynamic white list the method further comprises performing function test to determine whether the call is suspect to determine the treatment for the call.

11. The method as claimed in claim 10 wherein if it is determined that the call is suspect, the suspect score is analyzed to determine whether the call requires special treatment.

12. The method as claimed in claim 11 wherein if special treatment is required for the call, the special treatment is selected from a plurality of options using information retrieved from a subscriber preferences database.

13. The method as claimed in claim 11 wherein if it is determined that special treatment is not required, the incoming call is offered to the subscriber.

14. A call director for making incoming call management decisions respecting incoming calls for subscribers to an incoming call management service, the call director comprising:

at least one interface for receiving call control messages associated with the incoming calls;

at least one interface for querying a signatures database;

program instructions for performing function tests associated with various call states of the incoming calls;

program instructions for building a signature associated with each of the incoming calls using results of the function tests; and

program instructions for making incoming call management in decisions using information associated with the function test results.

15. A system for providing an incoming call management service, comprising:

a call director for receiving call control messages respecting incoming calls to subscribers of the incoming call management service, performing function tests associated with various call states of the incoming calls, building a call signature associated with each incoming call using the function test results, and making incoming call management decisions based on the function test results;

a subscriber'"'"'s preferences database for storing subscriber preference information also used by the call director in making the call management decisions; and

a signatures database for storing selected signatures built by the call director.

16. The system as claimed in claim 16 further comprising a call state database for storing the call signatures and other information about incoming calls required by the call director, while the incoming calls are being tracked by the call director.

17. The system as claimed in claim 16 further comprising a scratch pad database for storing original copies of call control messages received in a format that is not native to a service provider'"'"'s network that supports the call director.

18. The system as claimed in claim 16 further comprising a call history database for storing call records associated with calls tracked by the call director.

19. The system as claimed in claim 16 further comprising a record analyzer for analyzing call detail records associated with calls not monitored by the call director to improve call screening procedures by analyzing a greater volume of call data.

20. The system as claimed in claim 16 further comprising a global signatures database for storing call signatures that are shared with other service providers of incoming call management services.