Verizon Patent and Licensing Inc.

Jeffrey Allen Haltom

Lulia Ann Barakat

Heath William Hendrickson

Brian Edmund Somes

Mark E Stallcup

Jeffrey J Reger

Thomas A Gallant

Tolga Asveren

John Hans Van Arkel

Duncan Archer

Michael Stovenour

Rachel Lee Scarbrough

Katrina Marie Kutchko

Karl Stang

Nayankumar Suryakant Patel

Regina A Chiurco

Joe B Thornton

Kent Lanier Hallford, Jr

Kevin V Bohn

Mark A Nicholson

Shawn Ferdinand

Vincent T Lally

Alejandro Lopez

Joseph G Oleska

A device receives call information associated with a call from a first user device to a second user device, where the first user device is associated with a first network, and the second user device is associated with a second network separate from the first network. The call information includes a caller identification and is received via an originating network device of the first network. The device determines whether the caller identification is verified, and adds authentication information to the call information when the caller identification is verified. The device receives the call information and the authentication information from a terminating network device of the first network, and removes the authentication information from the call information. The device adds a cryptographic signature to the call information, and causes the call information and the cryptographic signature to be provided to the second network for routing to the second user device.

Validating and securing caller identification to prevent identity spoofing

In some implementations, a device may receive a SIP invite associated with a call to a first user device from a second user device. The first user device may be associated with a first network and the second user device may be associated with a second network that is separate from the first network. The SIP invite may include an identity header that indicates a carrier identifier associated with the second network. The device may authenticate the call based on a caller identification associated with the second user device and the carrier identifier. The device may send, based on authenticating the call, the SIP invite to the first user device to indicate, in association with receiving the call and via a user interface, an authorized entity associated with the carrier identifier according to the SIP update.

Systems and methods for indicating and managing a validation of a caller identification to prevent identity spoofing

One or more computing devices, systems, and/or methods for ringless voicemail detection are provided. In an example, a first call attempt to a phone number may be detected. In response to detecting a second call attempt to the phone number occurring within a first threshold timespan of the first call attempt being detected, first processing of the second call attempt is withheld. In response to the first call attempt being cancelled within a second threshold timespan of the first call attempt being detected, second processing of the second call attempt is performed based upon a policy.

Ringless voicemail attempt detection

Disclosed are systems and methods for robocall steering over voice-hosted traffic networks. The disclosed framework provides novel systems and methods for increasing the accuracy and efficiency in tracking, identifying, blocking and preventing robocalls and robocallers. The disclosed systems and methods provide mechanisms for identifying and removing unwanted voice traffic from networks. The disclosed systems and methods analyze voice traffic over a predetermined period of time (e.g., 1 day or 30 days, for example), and leverage this information into a 'know your customer' (KYC) score. This score enables incoming calls to be routed, controlled and/or blocked as they are communicated over voice networks.

Computerized system and method for robocall steering

A device receives, from a server device, a request to determine whether a call is authorized to be forwarded, where the call is intended to be established between the server device and a first client device via a network, and the call is forwarded from the first client device to a second client device. The device receives, from the network, network data associated with the call and account data associated with a first user of the first client device. The device determines that the call is forwarded based on the network data, and processes the account data and information indicating that the call is forwarded, with a machine learning model, to determine a score indicating whether the call is authorized to be forwarded. The device provides the score to the server device to cause the server device to perform one or more actions.

Systems and methods for utilizing machine learning to detect and determine whether call forwarding is authorized

A device can receive a call from a calling party device to a called party device, and can determine caller information based on the call from the calling party device. The device can determine that the caller information satisfies a criterion, and can modify the caller information to create modified caller information, the caller information being modified based on the caller information satisfying the criterion. The device can compare the modified caller information to a data structure that includes information associated with multiple call handling decisions. The device can identify a call handling decision, of the multiple call handling decisions, based on comparing the modified caller information to the data structure that includes the plurality of call handling decisions, and can cause the call handling decision to be implemented.

Call handling based on augmented caller information

A device may receive a first query from a terminating device, The first query may be based on the terminating device having received, from a calling party device, a request to establish a connection with a called party device. The first query may be based on information associated with the calling party device. The device may send, to a caller information device, a second query based on the first query. The device may receive, from the caller information device, caller information based on the second query. The device may compare the caller information to a criterion. The device may modify the caller information, to create modified caller information, when the caller information satisfies the criterion. The device may send the modified caller information to the terminating device for forwarding to another device to support determining how to handle, for the called party device, the request to establish the connection.

Adding additional information to caller ID information

A device may receive, from a network device, call information associated with a call. The call may be from a calling party device. The call may appear to be intended for a destination device. The call information may be received, from the network device, based on the network device having routed the call. The device may determine, based on the call information, that the call appears to have been forwarded to a called party device that is different from the destination device. The device may determine, based on the call information, a forwarding characteristic for the call. The device may determine that the forwarding characteristic satisfies a criterion. The device may send an output message based on the forwarding characteristic satisfying the criterion to support responding to call forwarding activity that has the forwarding characteristic.

Analyzing call forwarding activity

A device may receive, from a network device, a resolution query associated with a call. The resolution query may include a device identifier of the network device. The network device may receive, from a user device, the call. The device may determine, based on the device identifier of the network device, whether an authentication condition is satisfied. The device may selectively provide, to the network device, an authentication token in association with the resolution query based on determining whether the authentication condition is satisfied. The authentication token may enable an endpoint device, associated with the call, to perform a particular action based on the call.

Network based call authentication

A device may receive a first query from a terminating device. The first query may be based on the terminating device having received, from a calling party device, a request to establish a connection with a called party device. The first query may be based on information associated with the calling party device. The device may send, to a caller information device, a second query based on the first query. The device may receive, from the caller information device, caller information based on the second query. The device may compare the caller information to a criterion. The device may modify the caller information, to create modified caller information, when the caller information satisfies the criterion. The device may send the modified caller information to the terminating device for forwarding to another device to support determining how to handle, for the called party device, the request to establish the connection.

Growing community of inventors

Fishers, IN, United States of America

Jeffrey Allen Haltom