IP Library Granted Patent US 10,164,977
Granted Patent B2
US 10,164,977 · App. 15/354,816 · Granted Dec 25, 2018

Mobile caller authentication for contact centers

Inventors: Joel Ezell (Broomfield, CO); David Chavez (Broomfield, CO); Michael Krack (Los Altos, CA)
Assignee: Avaya Inc.
H04L63/0876H04L63/083H04L63/0861H04M2203/40H04M2203/6045H04M2203/6054H04M2203/6072
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 10,164,977
App. No.
15/354,816
Granted
Dec 25, 2018
Kind
B2
Abstract

A call request is received, from a mobile device, to establish a communication with a contact center. For example, the call request may be to establish a voice call with the contact center. In response to the call request, the mobile device sends authentication factors to a cloud authentication service that the user/mobile device has previously registered with. For example, the authentication factors may include usage factors of the mobile device, such as a call history of the user on the mobile device. If the authentication factors are validated, a token is generated. The token is sent to the contact center along with the call request. The token is validated at the contact center. At this point, the contact center knows that the user/mobile device are authentic. A call is then established between the user and the contact center.

Claims (31)

1. A system comprising:

a microprocessor; and

a computer readable medium, coupled with the microprocessor and comprising microprocessor readable and executable instructions that program the microprocessor to:

receive, from a mobile application in a mobile device of a user, a call request for establishing a call with a contact center, wherein the call request comprises an identity token that is generated in response to an authentication process that captures authentication factors of the mobile device of the user to confirm an identity of the mobile device of the user;

determine if the identity token is valid;

in response to determining that the identity token is valid, send the call request with the identity token to the contact center for validation of the identity of the mobile device of the user and send a notification of the incoming call with a plurality of call identification factors, wherein the plurality of call identification factors comprise a confidence level of the identity of the mobile device of the user and a confidence level of an identity of the user, wherein sending the call request with the identity token and sending the notification of the call with the plurality of call identification factors are used to determine if the call is established or not established between the mobile device and the contact center; and

establishing the call based on the confidence level of the identity of the mobile device of the user and the confidence level of the identity of the user meeting a threshold.

2. The system of claim 1 , wherein custom logic in the contact center determines if the confidence level of the identity of the mobile device of the user or the confidence level of the user is below the threshold and in response to the confidence level being below the threshold, uses an additional authentication procedure.

3. The system of claim 1 , wherein the authentication factors of the mobile device are sent by the mobile application as part of a registration process with a cloud authentication service for an individual enterprise of the contact center.

4. The system of claim 3 , and wherein the authentication factors of the mobile device are sent by the mobile application in a first message that comprises at least a first one of the authentication factors and a second message that comprises at least a second one of the authentication factors and wherein the at least first one of the authentication factors comprises a usage characteristic of the mobile device.

5. The system of claim 1 , wherein the authentication factors of the mobile device comprise a plurality of times when a plurality of telephone calls were made by the mobile device and a plurality of times were a plurality of telephone calls were received by the mobile device.

6. The system of claim 5 , wherein the authentication factors of the mobile device are combined with biometric/password authentication to confirm the identity of one or more of the mobile device or the user.

7. The system of claim 1 , wherein at least one of the authentication factors of the mobile device is invalidated based on a smart watch of the user not being in proximity to the mobile device of the user.

8. The system of claim 1 , wherein at least one of the authentication factors of the mobile device is validated based on a smart watch of the user being in proximity to the mobile device of the user.

9. A method comprising:

receiving, by a microprocessor, from a mobile application in a mobile device of a user, a call request for establishing a call with a contact center, wherein the call request comprises an identity token that is generated in response to an authentication process that captures authentication factors of device of the mobile device of the user to confirm an identity of the mobile device of the user;

determining, by the microprocessor, if the identity token is valid; and

in response to determining that the identity token is valid, sending, by the microprocessor, the call request with the identity token to the contact center for validation of the identity of the mobile device of the user;

sending, by the microprocessor, a notification of the incoming call with a plurality of call identification factors, wherein the plurality of call identification factors comprise a confidence level of the identity of the mobile device of the user and a confidence level of an identity of the user, wherein sending the call request with the identity token and sending the notification of the call with the plurality of call identification factors are used to determine if the call is established to not established between the mobile device and the contact center; and

establishing, by the microprocessor, the call based on the confidence level of the identity of the mobile device of the user and the confidence level of the identity of the user meeting a threshold.

10. The method of claim 9 , wherein custom logic in the contact center determines if the confidence level of the identity of the mobile device of the user or the confidence level of the user is below the threshold and in response to the confidence level being below the threshold, uses an additional authentication procedure.

11. The method of claim 9 , wherein the authentication factors of the mobile device are sent by the mobile application as part of a registration process with a cloud authentication service for an individual enterprise of the contact center.

12. The method of claim 11 , wherein the authentication factors of the mobile device are sent by the mobile application in a first message that comprises at least a first one of the authentication factors and a second message that comprises at least a second one of the authentication factors and wherein the at least first one of the authentication factors comprises a usage characteristic of the mobile device.

13. The method of claim 9 , wherein the authentication factors of the mobile device comprise when a memory or a Subscriber Identity Module (SIM) card was installed or removed.

14. The method of claim 9 , wherein at least one of the authentication factors of the mobile device is invalidated based on a smart watch of the user not being in proximity to the mobile device of the user.

15. The system of claim 1 , wherein the authentication factors of the mobile device of the user comprise at least one of a hardware upgrade history and a power up/power down history.

16. The system of claim 1 , wherein the authentication factors of the mobile device of the user comprises a list of email addresses used for sending and receiving emails.

17. The system of claim 1 , wherein the authentication factors of the mobile device of the user comprises a number of applications installed at a specific time.

18. The system of claim 1 , wherein the authentication factors of the mobile device of the user comprises an operating system version installation history.

19. The system of claim 1 , wherein the authentication factors of the mobile device of the user comprises a location history of the mobile device of the user.

20. The system of claim 1 , wherein the authentication factors of the mobile device of the user comprises an angle that the mobile device of the user is typically held by the user.

Assignments (14)
(SECURITY INTEREST) GRANTOR'S NAME CHANGE Recorded Sep 21, 2023
From: AVAYA INC.
To: AVAYA LLC
Reel/Frame 065019/0231 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 53955/0436) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063705/0023 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 61087/0386) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063690/0359 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001) Recorded May 18, 2023
From: GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT
To: AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.); HYPERQUALITY, INC.; HYPERQUALITY II, LLC; CAAS TECHNOLOGIES, LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 063779/0622 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 4, 2023
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 063542/0662 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 3, 2023
From: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; KNOAHSOFT INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB [COLLATERAL AGENT]
Reel/Frame 063742/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026 Recorded Apr 26, 2023
From: CITIBANK, N.A., AS COLLATERAL AGENT
To: AVAYA HOLDINGS CORP.; AVAYA INC.; AVAYA MANAGEMENT L.P.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063457/0001 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Aug 5, 2022
From: AVAYA INC.; INTELLISIST, INC.; AVAYA MANAGEMENT L.P.; AVAYA CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 061087/0386 →
SECURITY INTEREST Recorded Sep 25, 2020
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 053955/0436 →
SECURITY INTEREST Recorded Jan 23, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 045124/0026 →
SECURITY INTEREST Recorded Jan 10, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 045034/0001 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001 Recorded Dec 15, 2017
From: CITIBANK, N.A.
To: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION); VPNET TECHNOLOGIES, INC.
Reel/Frame 044893/0531 →
SECURITY INTEREST Recorded Jan 27, 2017
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS CORPORATION; VPNET TECHNOLOGIES, INC.
To: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 041576/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 17, 2016
From: EZELL, JOEL; CHAVEZ, DAVID; KRACK, MICHAEL
To: AVAYA INC.
Reel/Frame 040363/0738 →
Continuity (1)
Related Publication 20180139206A1 · May 17, 2018
Cited By (1)
US 12,273,463