IP Library Granted Patent US 10,841,778
Granted Patent B2
US 10,841,778 · App. 16/710,882 · Granted Nov 17, 2020

Locating user devices in enterprises

Inventors: Parameshwaran Krishnan (Basking Ridge, NJ); Navjot Singh (Somerset, NJ)
Assignee: AVAYA INC.
H04W4/90H04B5/0031H04W4/029H04W4/80
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,841,778
App. No.
16/710,882
Granted
Nov 17, 2020
Kind
B2
Abstract

A device, system, and method locates user devices in enterprises. The method performed by an enterprise server of an enterprise includes receiving contact data from an emergency services device, the contact data comprising location related data of a user device and identification data of the user device. The method includes determining if a general location data of the user device is associated with an area data of the enterprise as a function of the location related data. The method includes determining a precise location data of the user device within the area data of the enterprise based on the contact data.

Claims (46)

1. A method, comprising:

establishing a communication channel between an enterprise server of an enterprise and an emergency services device;

in the enterprise server:

receiving contact data from the emergency services device over the communication channel, wherein the contact data comprises location data indicating a first location of a user device and identification data identifying the user device;

in response to the enterprise server determining that the first location includes an area of the enterprise, determining a second location of the user device based on the identification data, wherein the second location comprises a location within the area of the enterprise, and wherein the second location is more precise than the first location; and

transferring the second location to the emergency services device over the communication channel.

2. The method of claim 1 , wherein determining the second location comprises:

determining where the user device is located on a wireless network at the area of the enterprise.

3. The method of claim 1 , further comprising:

determining, in the enterprise server, enterprise location data of the user device based on data received from near field communications (NFC) components distributed in the area of the enterprise,

wherein the determining the second location of the user device is further based on the enterprise location data.

4. The method of claim 1 , further comprising:

transmitting, in the enterprise server, a notification to a security device of the enterprise, the notification being indicative of the contact data having been received from the emergency services device.

5. The method of claim 1 , wherein the identification data comprises a media access control (MAC) address of the user device, a phone number associated with the user device, or a combination thereof.

6. The method of claim 1 , wherein the location data comprises identities of networks that the user device has discovered and signal strengths corresponding to the discovered networks.

7. The method of claim 6 , wherein determining the second location comprises:

determining that the signal strengths of the discovered networks fall within predetermined ranges of signal strengths; and

identifying a floor of a plurality of building floors, which comprise the area of the enterprise, that corresponds to the predetermined ranges of the signal strengths, wherein the second location comprises the floor.

8. An enterprise server of an enterprise, comprising:

a transceiver configured to communicate with an emergency services device over a communication channel established with the emergency services device;

a memory arrangement; and

a processor coupled to the transceiver and the memory arrangement,

wherein the processor is configured to instruct the transceiver to contact data from the emergency services device over the communication channel, wherein the contact data comprises location data indicating a first location of a user device and identification data identifying the user device,

wherein, in response to a determination by the processor that the first location includes an area of the enterprise, the processor is configured to determine a second location of the user device based on the identification data, wherein the second location comprises a location within the area of the enterprise, and wherein the second location is more precise than the first location; and

wherein the processor is configured to instruct the transceiver to transmit the second location to the emergency services device over the communication channel.

9. The enterprise server of claim 8 , wherein the processor configured to determine the second location comprises the processor configured to determine where the user device is located on a wireless network at the area of the enterprise.

10. The enterprise server of claim 8 , wherein the processor is further configured to instruct the transceiver to receive data from near field communications (NFC) components distributed in the area of the enterprise, wherein the processor is further configured to determine enterprise location data of the user device based on the data from the NFC components, and wherein the determining the second location of the user device is further based on the enterprise location data.

11. The enterprise server of claim 8 , wherein the processor is further configured to instruct the transceiver to transmit a notification to a security device of the enterprise, the notification being indicative of the contact data having been received from the emergency services device.

12. The enterprise server of claim 8 , wherein the identification data comprises a media access control (MAC) address of the user device, a phone number associated with the user device, or a combination thereof.

13. The enterprise server of claim 8 , wherein the location data comprises identities of networks that the user device has discovered and signal strengths corresponding to the discovered networks.

14. The enterprise server of claim 13 , wherein to determine the second location, the processor is configured to:

determine that the signal strengths of the discovered networks fall within predetermined ranges of signal strengths; and

identify a floor of a plurality of building floors, which comprise the area of the enterprise, that corresponds to the predetermined ranges of the signal strengths, wherein the second location comprises the floor.

15. A method, comprising:

establishing a communication channel between an enterprise server of an enterprise and an emergency services device;

in the emergency services device:

receiving contact data, wherein the contact data comprises location related data of a user device and identification data identifying the user device;

determining general location data indicating a first location of the user device based on the contact data;

determining an identity of an enterprise included in the first location based on the general location data;

transmitting the contact data and a request for a second location to the emergency services device over the communication channel, wherein the second location comprises a location within an area of the enterprise, and wherein the second location is more precise than the first location; and

receiving the second location from the enterprise server over the communication channel.

16. The method of claim 15 , further comprising:

prior to receiving the contact data:

performing, by the emergency services device, a registration process for the enterprise device to register with the emergency services device, wherein the registration process includes the emergency services device receiving information about the enterprise and a contact mechanism for the emergency services device to contact the enterprise device.

17. The method of claim 15 , wherein the identification data comprises a media access control (MAC) address of the user device, a phone number associated with the user device, or a combination thereof.

18. The method of claim 15 , wherein the location data comprises identities of networks that the user device has discovered and signal strengths corresponding to the discovered networks.

Assignments (8)
(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 →
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 →
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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 11, 2019
From: KRISHNAN, PARAMESHWARAN; SINGH, NAVJOT
To: AVAYA INC.
Reel/Frame 051252/0572 →
Continuity (2)
Continuation 15096981 · Apr 12, 2016
Related Publication 20200120471A1 · Apr 16, 2020
Cited By (1)
US 12,341,707