# US 9,264,536 B1 · Systems and methods to identify ANI and caller ID manipulation for determining trustworthiness of incoming calling party and billing number information > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 9,264,536 B1 - Document ID: US9264536B1 - Status: Granted - Kind: B1 - Application number: 13/355,135 - Filed: 2012-01-20 - Granted: 2016-02-16 - Earliest claimed: 2012-01-20 - Assignees: TrustID, Inc. - Applicants: Shreyas Dattatraya Saitawdekar; Patrick Michael Cox; Daniel Vincent Stone; Dean Franklin Black; Richard J. Greene - Inventors: Shreyas Dattatraya Saitawdekar; Patrick Michael Cox; Daniel Vincent Stone; Dean Franklin Black; Richard J. Greene - Web page: https://patentgrep.com/patent/US9264536B1 ## CPC - H04M 3/42059: {Making use of the calling party identifier} - H04M 3/38: Graded-service arrangements, i.e. some subscribers prevented from establishing certain connections (queuing arrangements H04Q3/64) - 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)} - H04M 3/4365: {based on information specified by the calling party, e.g. priority or subject} - H04M 15/06: Recording class or number of calling {, i.e. A-party} or called party {, i.e. B-party} - H04M 15/41: {Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]} - H04M 15/56: {for VoIP communications} - H04M 2203/6045: Identity confirmation - H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08) ## Abstract Systems and methods for determining the trustworthiness of calling party information, such as caller ID and ANI information, contained in a call request are provided. The method includes receiving a call request at a service provider network element, such as a telecommunication carrier switch. A decision is made as to whether the call request should be verified by reviewing a database of called telephone numbers for monitoring. When the call request is to be verified, a determination is made whether a discrepancy exists between the calling party information contained within the call request and authenticated stored calling party information. For example, the caller ID information in a call request is compared to service provider caller ID information for the calling party to determine if they match. When a discrepancy exists, a discrepancy report is transmitted to the called party. ## Claims ### Claim 1 A computer-implemented method, comprising: receiving from a calling party by a discrepancy detector a call request having a called telephone number, wherein the call request includes calling party information, wherein the discrepancy detector determines discrepancies in calling party information and is ancillary to an originating service provider network element that provides a telephone line for the calling party placing the call request; accessing a monitored called party number database, wherein accessing the monitored called party number database includes determining whether the call request to the called telephone number is to be verified, wherein the monitored called party number database includes telephone numbers, wherein the telephone numbers include only telephone numbers and related information for called party numbers for which call request validity is to be assessed; when the call request is to be verified, determining by the discrepancy detector whether a discrepancy exists between the calling party information contained within the call request and stored calling party information; and when a discrepancy exists between the calling party information contained within the call request and stored calling party information, causing call processing of a call requested in the call request to be suspended. ### Claim 2 (depends on 1) The method of claim 1, further comprising when a discrepancy exists between the calling party information contained within the call request and stored calling party information, generating by the discrepancy detector a discrepancy report. ### Claim 3 (depends on 2) The method of claim 2, further comprising capturing call parameters from the call request. ### Claim 4 (depends on 3) The method of claim 3, wherein the call parameters include one or more of an identity of the service provider receiving the call request, Automatic Number Identification (ANI) information from the call request, caller identification (ID) information from the call request, the called party number, a type of discrepancy event, a date of the call request, and a time of the call request. ### Claim 5 (depends on 2) The method of claim 2, further comprising: transmitting by the discrepancy detector the discrepancy report to the called party or an agent for the called party. ### Claim 6 (depends on 5) The method of claim 5, wherein transmitting the discrepancy report occurs after call completion to the called party, wherein the discrepancy report is transmitted either individually or in a batch transmission with other discrepancy reports. ### Claim 7 (depends on 5) The method of claim 5, wherein transmitting the discrepancy report comprises transmitting the discrepancy report via the Internet or a virtual private network. ### Claim 8 (depends on 1) The method of claim 1, wherein a discrepancy exists when calling party information received in a call request does not match stored calling party information assigned by a service provider receiving the call request. ### Claim 9 (depends on 1) The method of claim 1, wherein calling party information includes ANI information or caller ID information. ### Claim 10 (depends on 1) The method of claim 1, wherein the calling party information is included in a Session Initiation Protocol (SIP), Integrated Services Digital Network (ISDN), Plain Old Telephone Service (POTS), Time Division Multiplexing (TDM) or Voice over Internet Protocol (VOIP) call set up message. ### Claim 11 (depends on 1) The method of claim 1, wherein detecting a discrepancy within the call request is not detectable by the calling party. ### Claim 12 A system, comprising: a service provider interface configured to receive call request information from a service provider network element that receives a call request having calling party information to a called telephone number; a discrepancy detector coupled to the service provider interface, configured to determine whether a discrepancy exists between the calling party information contained within the call request from a calling party and stored calling party information and generate discrepancy reports, wherein the discrepancy detector determines discrepancies in calling party information and is ancillary to an originating service provider network element that provides a telephone line for the calling party placing the call request; a monitored called party number database coupled to the discrepancy detector, configured to include telephone numbers, wherein the telephone numbers include only telephone numbers and related information for called party numbers for which call request validity is to be assessed; a service provider assigned calling party information database coupled to the discrepancy detector, configured to contain service provider assigned calling party information; and a network interface coupled to the discrepancy detector, configured to transmit discrepancy reports, wherein the discrepancy detector is configured to cause call processing of a call requested in the call request to be suspended when a discrepancy between calling party information in the call request and calling party information stored in the service provider assigned calling party information database is detected. ### Claim 13 (depends on 12) The system of claim 12, wherein the discrepancy detector is configured to determine whether the call request to the called telephone number is to be verified and determine whether a discrepancy exists between calling party information contained within the call request and stored calling party information when the call request is to be verified. ### Claim 14 (depends on 13) The system of claim 13, wherein the discrepancy detector is configured to generate a discrepancy report when a discrepancy exists between calling party information contained within the call request and stored calling party information. ### Claim 15 (depends on 14) The system of claim 14, wherein a discrepancy exists when the calling party information in the received call request does not match calling party information stored within the service provider assigned calling party information database for the calling party. ### Claim 16 (depends on 14) The system of claim 14, wherein the discrepancy detector is configured to capture call parameters from the call request, when a discrepancy exists. ### Claim 17 (depends on 16) The system of claim 16, wherein the call parameters include one or more of an identity of the service provider receiving the call request, Automatic Number Identification (ANI) information from the call request, caller identification (ID) information from the call request, the called party number, a type of discrepancy event, a date of the call request, and a time of the call request. ### Claim 18 (depends on 14) The system of claim 14, wherein the network interface is configured to transmit the discrepancy report to the called party or an agent for the called party. ### Claim 19 (depends on 18) The system of claim 18, wherein the network interface is configured to transmit the discrepancy report after call completion to the called party, wherein the discrepancy report is transmitted either individually or in a batch transmission with other discrepancy reports. ### Claim 20 (depends on 18) The system of claim 18, wherein the network interface is configured to transmit the discrepancy report via the Internet or a virtual private network. ### Claim 21 (depends on 12) The system of claim 12, wherein calling party information includes ANI information or caller ID information. ### Claim 22 (depends on 12) The system of claim 12, wherein the calling party information is included in a Session Initiation Protocol (SIP), Integrated Services Digital Network (ISDN), Plain Old Telephone Service (POTS), Time Division Multiplexing (TDM) or Voice over Internet Protocol (VOIP) call set up message. ### Claim 23 (depends on 12) The system of claim 12, wherein operation of the system is not detectable by the calling party. ### Claim 24 (depends on 1) The method of claim 1, wherein the telephone numbers and related information for called party numbers for which call request validity is to be assessed includes toll free numbers and non-toll free numbers associated with a financial institution's credit card verification services. ### Claim 25 (depends on 12) The system of claim 12, wherein the telephone numbers and related information for called party numbers for which call request validity is to be assessed includes toll free numbers and non-toll free numbers associated with a financial institution's credit card verification services. ### Claim 26 (depends on 1) The method of claim 1, further comprising when a discrepancy exists between the calling party information contained within the call request and stored calling party information, transmitting the discrepancy report while call processing is suspended. ### Claim 27 (depends on 12) The system of claim 12, wherein the discrepancy detector is further configured when a discrepancy between calling party information in the call request and calling party information stored in the service provider assigned calling party information database is detected transmitting the discrepancy report while call processing is suspended.