IP Library Granted Patent US 8,817,961
Granted Patent B1
US 8,817,961 · App. 13/771,711 · Granted Aug 26, 2014

Method and apparatus for providing trusted caller ID services

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,817,961
App. No.
13/771,711
Granted
Aug 26, 2014
Kind
B1
Abstract

Methods and apparatus for providing trusted caller identification services between a first entity and a second entity are provided herein. In some embodiments, a method for validating an identity of a first entity to the second entity may include registering the first entity with a trust authority, wherein registering the first entity includes authenticating the identity of the first entity, and associating the unique code with a caller ID name (CNAM) of the first entity, receiving an identifier in association with a call request, determining that the identifier is correlated with the unique code, and providing to the second entity the CNAM together with an indication of validity.

Claims (33)

1. A method of providing trusted caller identification services between a first entity and a second entity comprising:

(a) registering the first entity with a trust authority, wherein registering the first entity includes authenticating the identity of the first entity, and associating a unique code with a caller ID name (CNAM) of the first entity;

(b) receiving an identifier included with a call request;

(c) determining that the identifier is correlated with the unique code; and

(d) providing to the second entity the CNAM together with an indication of validity.

2. The method of claim 1 , wherein the unique code is different than a phone number, a CNAM, a network connection identifier, or device specific information associated with the first entity.

3. The method of claim 1 , wherein the unique code can be derived from the identifier.

4. The method of claim 1 , wherein the identifier is the same as the unique code.

5. The method of claim 4 , wherein the unique code is included in a certificate supplied to the first entity by the trust authority, and wherein the certificate is stored on a device associated with the first entity.

6. The method of claim 1 , wherein the unique code is a user name and password.

7. The method of claim 1 , wherein providing an indication of validity includes at least one of (1) augmenting the CNAM with a reserve character, (2) playing to the second entity a reserved audio tone, (3) sending a message to the second entity using another communication means, (4) playing to the second entity an interactive voice response message, or (5) causing a device associated with the second entity to play a special ring tone.

8. The method of claim 1 , wherein the first entity's contact number is used to lookup the first entity's CNAM to further verify the validity of the first entity.

9. The method of claim 1 , further comprising:

(e) receiving a second call request from a device associated with a third entity to establish a call with the second entity, wherein the third entity is not registered with the trust authority; and

(f) providing to the second entity the CNAM together without an indication of validity.

10. The method of claim 1 , wherein the trust authority is maintained by a telephony provider that establishes the call between the first entity and the second entity.

11. The method of claim 1 , wherein the trust authority is maintained by an entity that is not a telephony provider that establishes the call between the first entity and the second entity.

12. A method of providing trusted caller identification services between a first entity and a second entity comprising:

(a) registering the second entity in a database maintained by the first entity, wherein registering includes associating a personal code in a secure database with one or more contact numbers associated with the second entity;

(b) receiving a call from the second entity;

(c) retrieving, from the database, the second entity's personal code; and

(d) after the call is established, providing a verification message including the second entity's personal code to verify that the second entity called the first entity.

13. The method of claim 12 , wherein the second entity's personal code is retrieved from the database using the second entity's contact number.

14. The method of claim 12 , wherein the calling party's personal code is retrieved from the database using an account number and password supplied by the calling party.

15. A method of providing trusted caller identification services between a first entity and a second entity comprising:

(a) registering the second entity in a database maintained by the first entity, wherein registering includes associating a personal code in a secure database with one or more contact numbers associated with the second entity;

(b) retrieving, from the database, the second entity's personal code; and

(c) calling the second entity; and

(d) after the call is established, providing a verification message including the second entity's personal code to verify the identity of the first entity.

16. The method of claim 15 , wherein the second entity's personal code is retrieved from the database using the second entity's contact number.

17. The method of claim 15 , wherein the second entity establishes or updates the personal code over a secure SSL connection.

18. The method of claim 15 , wherein the second entity establishes or updates the personal code over the Web.

19. The method of claim 15 , wherein the database maintained by the first entity stores personal codes for a plurality of customers.

Assignments (9)
RELEASE OF SECURITY INTEREST Recorded Jul 28, 2022
From: JPMORGAN CHASE BANK, N.A.
To: VONAGE AMERICA INC.; VONAGE HOLDINGS CORP.; VONAGE BUSINESS INC.; NEXMO INC.; TOKBOX, INC.
Reel/Frame 061002/0340 →
SECURITY INTEREST Recorded Nov 12, 2018
From: VONAGE BUSINESS INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 047502/0432 →
CORRECTIVE ASSIGNMENT TO CORRECT THE LIST BY DELETING 13831728 13831785 14291602 13680382 14827548 14752086 13680067 14169385 14473289 14194220 14194438 14317743 PREVIOUSLY RECORDED ON REEL 038328 FRAME 501. ASSIGNOR(S) HEREBY CONFIRMS THE SALE, ASSIGNMENT, TRANSFER AND CONVEYANCE OF REMAINING PROPERTIES. Recorded Oct 28, 2016
From: VONAGE NETWORK LLC
To: VONAGE BUSINESS INC.
Reel/Frame 040540/0702 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 1, 2016
From: VONAGE NETWORK LLC
To: VONAGE BUSINESS INC.
Reel/Frame 038328/0501 →
CORRECTIVE ASSIGNMENT TO CORRECT THE PATENT APPLICATION NUMBER 13966486 PREVIOUSLY RECORDED ON REEL 033545 FRAME 0424. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST. Recorded Jan 21, 2016
From: VONAGE HOLDINGS CORP.; VONAGE NETWORK LLC; VONAGE BUSINESS SOLUTIONS INC.; VONAGE AMERICA INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 037570/0203 →
SECURITY INTEREST Recorded Jul 29, 2015
From: VONAGE HOLDINGS CORP.; VONAGE AMERICA INC.; VONAGE BUSINESS SOLUTIONS, INC.; VONAGE NETWORK LLC
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 036205/0485 →
SECURITY INTEREST Recorded Aug 14, 2014
From: VONAGE HOLDINGS CORP.; VONAGE NETWORK LLC; VONAGE BUSINESS SOLUTIONS INC.; VONAGE AMERICA INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 033545/0424 →
SECURITY AGREEMENT Recorded May 20, 2013
From: VONAGE NETWORK LLC
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 030450/0586 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 22, 2013
From: STERMAN, BARUCH
To: VONAGE NETWORK LLC
Reel/Frame 029856/0622 →