IP Library Granted Patent US 8,307,378
Granted Patent B2
US 8,307,378 · App. 13/205,336 · Granted Nov 6, 2012

Method, system and computer program product for a lightweight directory access protocol client application program interface

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,307,378
App. No.
13/205,336
Granted
Nov 6, 2012
Kind
B2
Abstract

A device, including a computer readable medium storing executable computer instructions for implementing an application program interface (API). The API including a function call for enabling communications between a calling application and a client on the device, the client communicating with a directory server. In another aspect, there is provided a computer-readable medium, including executable computer instructions for implementing an application program interface (API) on a device. The API, including a function call for enabling communications between a calling application and a client on the device, the client communicating with a directory server.

Claims (44)

1. A method comprising:

interfacing, via an application program interface (API) resident on a device, a lightweight directory access protocol (LDAP) client and one or more applications that are resident on the device; and

initiating termination, via the API, of a connection with a backend server and a local database associated with the LDAP client.

2. A method of claim 1 , further comprising:

invoking, on the device, the LDAP client configured to perform a plurality of function calls via the API, wherein the function calls perform tasks on behalf of the applications or the LDAP client.

3. A method of claim 1 , wherein the device includes or is included in a cellular phone.

4. A method of claim 1 , further comprising:

generating a single query to the directory server on behalf of one of the applications, the single query identifying data used by the one application; and

receiving the data in a single transmission in response to the single query.

5. A method of claim 1 , further comprising:

determining whether the one or more applications are configured to have data automatically retrieved by the LDAP client upon the LDAP client connecting to the backend server.

6. A method of claim 1 , further comprising:

storing, in the local client database, preference information for one of the applications.

7. A method of claim 1 , wherein the backend server includes a directory server.

8. An apparatus comprising:

at least one processor; and

at least one memory including computer program code for one or more programs,

the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following,

interface, via an application program interface (API) resident on a device, a lightweight directory access protocol (LDAP) client and one or more applications that are resident on the device, and

initiate termination, via the API, of a connection with a backend server and a local database associated with the LDAP client.

9. An apparatus of claim 8 , wherein the apparatus is further caused to:

invoke, on the device, the LDAP client configured to perform a plurality of function calls via the API, wherein the function calls perform tasks on behalf of the applications or the LDAP client.

10. An apparatus of claim 8 , wherein the apparatus is included in the device, the device including a cellular phone.

11. An apparatus of claim 8 , wherein the apparatus is further caused to:

generate a single query to the directory server on behalf of one of the applications, the single query identifying data used by the one application; and

receive the data in a single transmission in response to the single query.

12. An apparatus of claim 8 , wherein the apparatus is further caused to:

determine whether the one or more applications are configured to have data automatically retrieved by the LDAP client upon the LDAP client connecting to the backend server.

13. An apparatus of claim 8 , wherein the apparatus is further caused to:

store, in the local client database, preference information for one of the applications.

14. An apparatus of claim 8 , wherein the backend server includes a directory server.

15. A method comprising:

invoking a lightweight directory access protocol (LDAP) client that is resident on a device and configured to interface, via an application program interface (API), one or more applications,

wherein the API is configured to facilitate the LDAP client in performing a plurality of function calls on behalf of the one or more applications.

16. A method of claim 15 , further comprising:

initiating termination, via the API, of a connection with a backend server and a local database associated with the LDAP client.

17. A method of claim 15 , wherein the device includes or is included in a cellular phone, and the backend server includes a directory server.

18. A method of claim 15 , further comprising:

generating a single query to the directory server on behalf of one of the applications, the single query identifying data used by the one application; and

receiving the data in a single transmission in response to the single query.

19. A method of claim 15 , further comprising:

determining whether the one or more applications are configured to have data pulled by the LDAP client upon the LDAP client connecting to the backend server.

20. A method of claim 15 , further comprising:

storing, in the local client database, preference information for one of the applications.

Assignments (9)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 3, 2020
From: INTELLECTUAL VENTURES ASSETS 144 LLC
To: CDN INNOVATIONS, LLC
Reel/Frame 051406/0748 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 31, 2019
From: OL SECURITY LIMITED LIABILITY COMPANY
To: INTELLECTUAL VENTURES ASSETS 144 LLC
Reel/Frame 050885/0010 →
MERGER Recorded Oct 27, 2015
From: TEKLA PEHR LLC
To: OL SECURITY LIMITED LIABILITY COMPANY
Reel/Frame 036979/0106 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 28, 2012
From: VERIZON PATENT AND LICENSING INC.
To: TEKLA PEHR LLC
Reel/Frame 029368/0460 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 17, 2012
From: VERIZON BUSINESS GLOBAL LLC
To: VERIZON PATENT AND LICENSING INC.
Reel/Frame 028969/0914 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 5, 2012
From: ESPINO, MAYEL
To: WORLDCOM, INC.
Reel/Frame 027994/0489 →
MERGER Recorded Apr 5, 2012
From: WORLDCOM, INC.
To: MCI, INC.
Reel/Frame 027995/0215 →
MERGER Recorded Apr 5, 2012
From: MCI, INC.
To: MCI, LLC
Reel/Frame 027995/0248 →
CHANGE OF NAME Recorded Apr 5, 2012
From: MCI, LLC
To: VERIZON BUSINESS GLOBAL LLC
Reel/Frame 027995/0307 →