IP Library Granted Patent US 8,600,028
Granted Patent B2
US 8,600,028 · App. 12/499,642 · Granted Dec 3, 2013

Contextual phone number validation

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,600,028
App. No.
12/499,642
Granted
Dec 3, 2013
Kind
B2
Abstract

A validation service offers the ability to validate a telephone conference. The validation service can verify that a telephone number and a pass code can be used to access the telephone conference at the time the telephone conference is scheduled. The validation service can also inform users about changes to the scheduled telephone conference, and provide alternative telephone numbers that can be used to access the telephone conference.

Claims (74)

1. An apparatus, comprising:

a machine ( 105 , 305 );

a database ( 315 ) of telephone conference identifiers ( 525 );

a receiver ( 320 ) on the machine ( 105 , 305 ) to receive from a second machine ( 205 , 505 ) a request ( 605 , 615 ) to validate a telephone conference identifier ( 525 ) identifying a telephone conference;

a validator ( 325 ) to validate said telephone conference identifier ( 525 ) against the database ( 315 ) of telephone conference identifiers ( 525 ) to produce a response ( 610 , 620 ); and

a transmitter ( 330 ) to transmit to said second machine ( 205 , 505 ) said response ( 610 , 620 ) from the validator ( 325 ).

2. An apparatus according to claim 1 , wherein:

the apparatus further comprises:

a second database ( 1305 ) of alternative telephone numbers ( 1205 , 1210 ) that the user can use to call into said telephone conference; and

a location identifier ( 1310 ) to identify a location ( 1215 ) of a user from said telephone conference identifier ( 525 ); and

the validator ( 325 ) is operative to select an alternative telephone number ( 1205 , 1210 ) from the second database ( 1305 ) based on said location ( 1215 ) of said user.

3. An apparatus according to claim 1 , wherein:

the database ( 315 ) of telephone conference identifiers ( 525 ) includes information ( 1405 , 1410 , 1415 , 1420 ) about at least one telephone conference;

the receiver ( 320 ) is operative to receive secondary information ( 1010 ) in said request ( 605 , 615 ); and

the validator ( 325 ) is operative to compare said secondary information ( 1010 ) in said request ( 605 , 615 ) with said information ( 1405 , 1410 , 1415 , 1420 ) in the database ( 315 ).

4. An apparatus according to claim 3 , wherein the validator ( 325 ) is operative to indicate whether said secondary information ( 1010 ) in said request ( 605 , 615 ) conflicts with said information ( 1405 , 1410 , 1415 , 1420 ) in the database ( 315 ) without providing any of said information ( 1405 , 1410 , 1415 , 1420 ) in the database ( 315 ).

5. An apparatus according to claim 1 , further comprising a second database ( 1315 ) of registered users.

6. An apparatus according to claim 5 , wherein:

said request ( 605 , 615 ) includes an e-mail address ( 710 ) for a user;

the validator ( 325 ) is operative to store said e-mail address ( 710 ) for said user in the second database ( 1315 ) of registered users; and

the apparatus further comprises a notifier ( 1320 ) to e-mail said user at said e-mail address ( 710 ) if a time of said telephone conference changes.

7. An apparatus according to claim 5 , wherein:

said request ( 605 , 615 ) includes a telephone number ( 720 ) for a user;

the validator ( 325 ) is operative to store said telephone number ( 720 ) for said user in the second database ( 1315 ) of registered users; and

the apparatus further comprises a dialer ( 1325 ) to call said user at said telephone number ( 720 ) at a time of said telephone conference.

8. An apparatus according to claim 1 , wherein:

the database ( 315 ) of telephone conference identifiers ( 525 ) is stored at a host ( 105 ) of said telephone conference;

the apparatus further comprises a second database ( 405 ) of hosts; and

the validator ( 325 ) is operative to use a telephone number ( 515 ) in said telephone conference identifier ( 525 ) and the second database ( 405 ) to identify the host ( 105 ) of said telephone conference to locate the database ( 315 ) of telephone conference identifiers ( 525 ).

9. An apparatus according to claim 1 , further comprising:

a telephone conference identifier device ( 230 ) on said second machine ( 205 , 505 ) to identify said telephone conference identifier ( 525 ) in a message ( 510 );

a second transmitter ( 235 ) on said second machine ( 205 , 505 ) to transmit to the machine ( 105 , 305 ) said request ( 605 , 615 ) to validate said telephone conference identifier ( 525 );

a second receiver ( 240 ) on said second machine ( 205 , 505 ) to receive from said validation service ( 310 ) said response ( 610 , 620 ); and

a processor ( 245 ) on said second machine ( 205 , 505 ) to process said response ( 610 , 620 ).

10. A method, comprising:

receiving ( 2005 ) at a machine a request ( 605 , 615 ) to validate a telephone conference identifier ( 525 ) identifying a telephone conference;

accessing ( 2010 ) information ( 1405 , 1410 , 1415 , 1420 ) about the telephone conference from a host ( 105 ) of the telephone conference responsive to the request ( 605 , 615 ) to validate a telephone conference identifier ( 525 );

verifying ( 2015 ) whether the telephone conference identifier ( 525 ) is consistent with the information ( 1405 , 1410 , 1415 , 1420 ) about the telephone conference; and

transmitting ( 2020 ) whether the telephone conference identifier ( 525 ) is valid.

11. A method according to claim 10 , wherein:

receiving ( 2005 ) a request ( 605 , 615 ) to validate a telephone conference identifier ( 525 ) includes receiving ( 2105 ) a location ( 1215 ) of a user and a telephone number ( 515 ); and

verifying ( 2015 ) whether the telephone conference identifier ( 525 ) is consistent with the information ( 1405 , 1410 , 1415 , 1420 ) about the telephone conference includes determining ( 2120 ) whether the telephone number ( 515 ) is the best way for the user to access the telephone conference from the location ( 1215 ).

12. A method according to claim 11 , wherein verifying ( 2015 ) whether the telephone conference identifier ( 525 ) is consistent with the information ( 1405 , 1410 , 1415 , 1420 ) about the telephone conference further includes transmitting ( 2125 ) an alternative telephone number ( 1205 , 1210 ) to access the telephone conference from the location ( 1215 ).

13. A method according to claim 12 , wherein determining ( 2120 ) whether the telephone number ( 515 ) is the best way for the user to access the telephone conference from the location ( 1215 ) includes accessing ( 2110 ) the alternative telephone number ( 1205 , 1210 ) from a database ( 1305 ) of alternative telephone numbers ( 1205 , 1210 ) from the host ( 105 ) of the telephone conference.

14. A method according to claim 10 , wherein:

receiving ( 2005 ) a request ( 605 , 615 ) to validate a telephone conference identifier ( 525 ) includes receiving ( 2135 ) secondary information ( 1010 ) about the telephone conference; and

verifying ( 2015 ) whether the telephone conference identifier ( 525 ) is consistent with the information ( 1405 , 1410 , 1415 , 1420 ) about the telephone conference includes determining ( 2140 ) whether the secondary information ( 1010 ) is consistent with the information ( 1405 , 1410 , 1415 , 1420 ) about the telephone conference.

15. A method according to claim 14 , further comprising if the secondary information ( 1010 ) is not consistent with the information ( 1405 , 1410 , 1415 , 1420 ) about the telephone conference, transmitting ( 2145 , 2150 ) that the secondary information ( 1010 ) is not consistent with the information ( 1405 , 1410 , 1415 , 1420 ) about the telephone conference without transmitting the information ( 1405 , 1410 , 1415 , 1420 ) about the telephone conference.

16. A method according to claim 10 , wherein:

receiving ( 2155 ) a request ( 605 , 615 ) to validate a telephone conference identifier ( 525 ) identifying a telephone conference includes receiving ( 2205 ) an e-mail address ( 710 ) for a user; and

the method further comprises:

storing ( 2210 ) the e-mail address ( 710 ) for the user; and

transmitting ( 2215 ) a message ( 510 ) to the e-mail address ( 710 ) for the user if a time for the telephone conference changes.

17. A method according to claim 10 , wherein:

receiving ( 2005 ) a request ( 605 , 615 ) to validate a telephone conference identifier ( 525 ) identifying a telephone conference includes receiving ( 2220 ) a telephone number ( 720 ) for a user; and

the method further comprises:

storing ( 2225 ) the telephone number ( 720 ) for the user; and

calling ( 2230 ) the user at the telephone number ( 720 ) at a time for the telephone conference.

18. A method according to claim 10 , further comprising:

transmitting ( 1535 ) from a machine ( 205 , 505 ) to a validation service ( 310 ) the request ( 605 , 615 ) to validate the telephone conference identifier ( 525 );

receiving ( 1540 ) at the machine ( 205 , 505 ) from the validation service ( 310 ) the response ( 610 , 620 ); and

processing ( 1545 ) the response ( 610 , 620 ) at the machine ( 205 , 505 ).

19. An article, comprising a non-transitory storage medium, said non-transitory storage medium having stored thereon instructions that, when executed by a machine, result in:

receiving ( 2005 ) a request ( 605 , 615 ) to validate a telephone conference identifier ( 525 ) identifying a telephone conference;

accessing ( 2010 ) information ( 1405 , 1410 , 1415 , 1420 ) about the telephone conference from a host ( 105 ) of the telephone conference responsive to the request ( 605 , 615 ) to validate a telephone conference identifier ( 525 );

verifying ( 2015 ) whether the telephone conference identifier ( 525 ) is consistent with the information ( 1405 , 1410 , 1415 , 1420 ) about the telephone conference; and

transmitting ( 2020 ) whether the telephone conference identifier ( 525 ) is valid.

20. An article according to claim 19 , wherein:

receiving ( 2005 ) a request ( 605 , 615 ) to validate a telephone conference identifier ( 525 ) includes receiving ( 2105 ) a location ( 1215 ) of a user and a telephone number ( 515 ); and

verifying ( 2015 ) whether the telephone conference identifier ( 525 ) is consistent with the information ( 1405 , 1410 , 1415 , 1420 ) about the telephone conference includes determining ( 2120 ) whether the telephone number ( 515 ) is the best way for the user to access the telephone conference from the location ( 1215 ).

21. An article according to claim 19 , wherein:

receiving ( 2005 ) a request ( 605 , 615 ) to validate a telephone conference identifier ( 525 ) includes receiving ( 2135 ) secondary information ( 1010 ) about the telephone conference; and

verifying ( 2015 ) whether the telephone conference identifier ( 525 ) is consistent with the information ( 1405 , 1410 , 1415 , 1420 ) about the telephone conference includes determining ( 2140 ) whether the secondary information ( 1010 ) is consistent with the information ( 1405 , 1410 , 1415 , 1420 ) about the telephone conference.

22. An article according to claim 19 , wherein accessing ( 2010 ) information ( 1405 , 1410 , 1415 ) about the telephone conference from a host ( 105 ) of the telephone conference includes identifying ( 2315 ) the host ( 105 ) of the telephone conference using a telephone number ( 515 ) in the telephone conference identifier ( 525 ).

Assignments (13)
RELEASE OF SECURITY INTEREST REEL/FRAME 035656/0251 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: BORLAND SOFTWARE CORPORATION; ATTACHMATE CORPORATION; NETIQ CORPORATION; MICRO FOCUS (US), INC.; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.)
Reel/Frame 062623/0009 →
RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC); BORLAND SOFTWARE CORPORATION; MICRO FOCUS (US), INC.; SERENA SOFTWARE, INC; ATTACHMATE CORPORATION; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.); NETIQ CORPORATION
Reel/Frame 062746/0399 →
CORRECTIVE ASSIGNMENT TO CORRECT THE TO CORRECT TYPO IN APPLICATION NUMBER 10708121 WHICH SHOULD BE 10708021 PREVIOUSLY RECORDED ON REEL 042388 FRAME 0386. ASSIGNOR(S) HEREBY CONFIRMS THE NOTICE OF SUCCESSION OF AGENCY. Recorded Jul 26, 2018
From: BANK OF AMERICA, N.A., AS PRIOR AGENT
To: JPMORGAN CHASE BANK, N.A., AS SUCCESSOR AGENT
Reel/Frame 048793/0832 →
SECURITY INTEREST Recorded Oct 11, 2017
From: ATTACHMATE CORPORATION; BORLAND SOFTWARE CORPORATION; NETIQ CORPORATION; MICRO FOCUS (US), INC.; MICRO FOCUS SOFTWARE, INC.; ENTIT SOFTWARE LLC; ARCSIGHT, LLC; SERENA SOFTWARE, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 044183/0718 →
NOTICE OF SUCCESSION OF AGENCY Recorded May 2, 2017
From: BANK OF AMERICA, N.A., AS PRIOR AGENT
To: JPMORGAN CHASE BANK, N.A., AS SUCCESSOR AGENT
Reel/Frame 042388/0386 →
CHANGE OF NAME Recorded Sep 13, 2016
From: NOVELL, INC.
To: MICRO FOCUS SOFTWARE INC.
Reel/Frame 040020/0703 →
SECURITY INTEREST Recorded May 13, 2015
From: MICRO FOCUS (US), INC.; BORLAND SOFTWARE CORPORATION; ATTACHMATE CORPORATION; NETIQ CORPORATION; NOVELL, INC.
To: BANK OF AMERICA, N.A.
Reel/Frame 035656/0251 →
RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 028252/0216 Recorded Nov 24, 2014
From: CREDIT SUISSE AG
To: NOVELL, INC.
Reel/Frame 034470/0680 →
RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 028252/0316 Recorded Nov 24, 2014
From: CREDIT SUISSE AG
To: NOVELL, INC.
Reel/Frame 034469/0057 →
GRANT OF PATENT SECURITY INTEREST FIRST LIEN Recorded May 23, 2012
From: NOVELL, INC.
To: CREDIT SUISSE AG, AS COLLATERAL AGENT
Reel/Frame 028252/0216 →
GRANT OF PATENT SECURITY INTEREST SECOND LIEN Recorded May 23, 2012
From: NOVELL, INC.
To: CREDIT SUISSE AG, AS COLLATERAL AGENT
Reel/Frame 028252/0316 →
RELEASE OF SECURITY INTEREST IN PATENTS FIRST LIEN (RELEASES RF 026270/0001 AND 027289/0727) Recorded May 22, 2012
From: CREDIT SUISSE AG, AS COLLATERAL AGENT
To: NOVELL, INC.
Reel/Frame 028252/0077 →
RELEASE OF SECURITY IN PATENTS SECOND LIEN (RELEASES RF 026275/0018 AND 027290/0983) Recorded May 22, 2012
From: CREDIT SUISSE AG, AS COLLATERAL AGENT
To: NOVELL, INC.
Reel/Frame 028252/0154 →