IP Library Granted Patent US 10,110,607
Granted Patent B2
US 10,110,607 · App. 14/946,974 · Granted Oct 23, 2018

Database access using a common web interface

Inventors: Mark McCray (Clayton, NC); Eric Scott Davis (Morrisville, NC)
Assignee: LexisNexis, A Division of Reed Elsevier, Inc.
H04L63/101G06F17/30557G06F21/6227G06Q50/18H04L63/083
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,110,607
App. No.
14/946,974
Granted
Oct 23, 2018
Kind
B2
Abstract

Methods and systems for accessing databases using a common web interface are provided. A method for transmitting data retrieved from an endpoint device to a client device using a common web interface includes providing the common web interface to the client device. The common web interface allows access to a plurality of endpoint devices, each endpoint device comprising a unique endpoint address. The method further includes receiving, by a computer, identification data from the client device, retrieving an endpoint address for one of the plurality of endpoint devices based on the identification data, connecting to the endpoint device corresponding to the endpoint address, retrieving data from the endpoint device, and transmitting the retrieved data to the client device.

Claims (50)

1. A computing system for transmitting data received from an endpoint device to a client device comprising:

a processor; and

a non-transitory memory component that stores a set of executable instructions that, when executed by the processor, cause the computing system to:

receive a registration request from the endpoint device, wherein the registration request comprises an endpoint address of the endpoint device and a plurality of user IDs authorized to access the endpoint device;

store the endpoint address and the plurality of user IDs authorized to access the endpoint device in an endpoint database;

receive a user ID from the client device;

retrieve the endpoint address for the endpoint device from the endpoint database based on the received user ID;

connect to the endpoint device corresponding to the endpoint address such that the computing system and the endpoint device may communicate data;

receive data from the endpoint device; and

transmit the received data to the client device.

2. The computing system of claim 1 , wherein the set of executable instructions when executed by the processor, cause the computing system to:

verify the registration request by sending a message requesting confirmation of the registration request to the endpoint device and receiving a registration request confirmation message from the endpoint device; and

in response to verifying the registration request, store the endpoint address and the plurality of user IDs authorized to access the endpoint address in the endpoint database.

3. The computing system of claim 1 , wherein the set of executable instructions when executed by the processor, cause the computing system to:

provide a common web interface to the client device, wherein the common web interface allows access to a plurality of endpoint devices, each endpoint device comprising a unique endpoint address and a plurality of databases.

4. The computing system of claim 1 , wherein the set of executable instructions when executed by the processor, cause the computing system to:

receive a password from the client device associated with the received user ID;

provide the received user ID and the received password to the endpoint device for authentication; and

receive an authentication indicator from the endpoint device.

5. The computing system of claim 1 , wherein the endpoint device comprises a firewall.

6. The computing system of claim 1 , wherein the endpoint device comprises a database.

7. The computing system of claim 1 , wherein the user ID comprises at least one of an email address, a telephone number, or a login name.

8. The computing system of claim 1 , wherein the endpoint device comprises a law firm server.

9. The computing system of claim 1 , wherein the data comprises law firm data.

10. The computing system of claim 9 , wherein the law firm data comprises at least one of time entry data, contact data, scheduling data, case data, matter data, or billing data.

11. The computing system of claim 1 , wherein the set of executable instructions, when executed by the processor, cause the computing system to store the endpoint address and the plurality of user IDs authorized to access the endpoint device in the endpoint database in response to receiving the registration message comprising the endpoint address of the endpoint device and the plurality of user IDs authorized to access the endpoint device.

12. A computer-implemented method for transmitting data received from an endpoint device to a client device comprising:

receiving, automatically by a computing system, a registration request from the endpoint device, wherein the registration request comprises an endpoint address of the endpoint device and a plurality of user IDs authorized to access the endpoint device;

storing the endpoint address and the plurality of user IDs authorized to access the endpoint device in an endpoint database;

receiving a user ID from the client device;

retrieving the endpoint address for the endpoint device from the endpoint database based on the received user ID;

connecting to the endpoint device corresponding to the endpoint address such that the computing system and the endpoint device may communicate data;

receiving data from the endpoint device; and

transmitting the received data to the client device.

13. The method of claim 12 , further comprising:

verifying the registration request by sending a message requesting confirmation of the registration request to the endpoint device and receiving a registration request confirmation message from the endpoint device; and

in response to verifying the registration request, storing the endpoint address and the plurality of user IDs authorized to access the endpoint address in the endpoint database.

14. The method of claim 12 , further comprising:

providing a common web interface to the client device, wherein the common web interface allows access to a plurality of endpoint devices, each endpoint device comprising a unique endpoint address and a plurality of databases.

15. The method of claim 12 , further comprising:

receiving a password from the client device associated with the received user ID;

providing the received user ID and the received password to the endpoint device for authentication; and

receiving an authentication indicator from the endpoint device.

16. The method of claim 12 , wherein the endpoint device comprises a firewall.

17. The method of claim 12 , wherein the endpoint device comprises a database.

18. The method of claim 12 , wherein the user ID comprises at least one of an email address, a telephone number, or a login name.

19. The method of claim 12 , wherein the endpoint device comprises a law firm server.

20. The method of claim 12 , wherein the data comprises law firm data.

21. The method of claim 20 , wherein the law firm data comprises at least one of time entry data, contact data, scheduling data, case data, matter data, or billing data.

22. The method of claim 12 , wherein the endpoint address and the plurality of user IDs authorized to access the endpoint device are stored in the endpoint database in response to receiving the registration message comprising the endpoint address of the endpoint device and the plurality of user IDs authorized to access the endpoint device.

Assignments (2)
CHANGE OF NAME Recorded Dec 3, 2019
From: LEXISNEXIS; REED ELSEVIER INC.
To: RELX INC.
Reel/Frame 051198/0325 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 5, 2016
From: MCCRAY, MARK; DAVIS, ERIC SCOTT
To: LEXISNEXIS, A DIVISION OF REED ELSEVIER INC.
Reel/Frame 037676/0145 →
Continuity (2)
Continuation 13228895 · Sep 9, 2011
Related Publication 20160080387A1 · Mar 17, 2016