IP Library Granted Patent US 6,850,928
Granted Patent B1
US 6,850,928 · App. 09/481,648 · Granted Feb 1, 2005

System and method for automatically retrieving proprietary and standard directory object formats

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 6,850,928
App. No.
09/481,648
Granted
Feb 1, 2005
Kind
B1
Abstract

A system for, and method of, automatically retrieving a directory object from a database and a directory server incorporating the system or the method. In one embodiment, the system includes: (1) a request reception module that receives a Lightweight Directory Access Protocol (LDAP) request for an attribute of the directory object that is expressed in a proprietary format and (2) a request fulfillment module, associated with the request reception module. If the directory object contains the attribute expressed in the proprietary format, the request fulfillment module retrieves the attribute expressed in the proprietary format from the database. If the directory object does not contain the attribute expressed in the proprietary format, the request fulfillment module retrieves the attribute expressed in a standard format from the database and recasts the attribute expressed in the standard format as the attribute expressed in the proprietary format.

Claims (62)

1. A system for automatically retrieving a directory object from a database, comprising:

a request reception module that receives a Lightweight Directory Access Protocol (LDAP) request for an attribute of said directory object that is expressed in a proprietary format; and

a request fulfillment module, associated with said request reception module, that, if said directory object contains said attribute expressed in said proprietary format, retrieves said attribute expressed in said proprietary format from said database and responds to said LDAP request with an LDAP response including said attribute expressed in said proprietary format and, if said directory object does not contain said attribute expressed in said proprietary format, retrieves said attribute expressed in a standard format from said database and responds to said LDAP request with an LDAP response including said attribute expressed in said standard format recast to appear to LDAP as if said attribute were expressed in said proprietary format even though said attribute in said response is actually expressed in said standard format.

2. The system as recited in claim 1 wherein said request fulfillment module responds to said LDAP request with an LDAP response including an indication of a format of said attribute.

3. The system as recited in claim 2 wherein said indication is of a standard type.

4. The system as recited in claim 1 wherein said attribute is a sampled stream of data.

5. The system as recited in claim 1 wherein said standard format is characterized by a 32 kilobit data rate.

6. A system for automatically retrieving a directory object from a database, comprising:

a request reception module that receives a Lightweight Directory Access Protocol (LDAP) request for an attribute of said directory object that is expressed in a proprietary format; and

a request fulfillment module, associated with said request reception module, that, if said directory object contains said attribute expressed in said proprietary format, retrieves said attribute expressed in said proprietary format from said database and, if said directory object does not contain said attribute expressed in said proprietary format, retrieves said attribute expressed in a standard format from said database and recasts said attribute expressed in said standard format as said attribute expressed in said proprietary format, wherein said proprietary format is selected from the group consisting of: a format characterized by a 16 kilobit data rate, a format characterized by a 24 kilobit data rate, a textual attribute, and a graphic image.

7. The system as recited in claim 1 wherein said directory object includes said attribute expressed in a plurality of proprietary formats.

8. A method of automatically retrieving a directory object from a database, comprising:

receiving a Lightweight Directory Access Protocol (LDAP) request for an attribute of said directory object that is expressed in a proprietary format;

retrieving said attribute expressed in said proprietary format from said database if said directory object contains said attribute expressed in said proprietary format and responding to said LDAP request with an LDAP response including said attribute expressed in said proprietary format; and

retrieving said attribute expressed in a standard format from said database if said directory object does not contain said attribute expressed in said proprietary format and responding to said LDAP request with an LDAP response including said attribute expressed in said standard format recast to appear to LDAP as if said attribute were expressed in said proprietary format even though said attribute in said response is actually expressed in said standard format.

9. The method as recited in claim 8 further comprises responding to said LDAP request with an LDAP response including an indication of a format of said attribute.

10. The method as recited in claim 9 wherein said indication is of a standard type.

11. The method as recited in claim 8 wherein said attribute is a sampled stream of data.

12. The method as recited in claim 8 wherein said standard format is characterized by a 32 kilobit data rate.

13. A method of automatically retrieving a directory object from a database, comprising:

receiving a Lightweight Directory Access Protocol (LDAP) request for an attribute of said directory object that is expressed in a proprietary format;

retrieving said attribute expressed in said proprietary format from said database if said directory object contains said attribute expressed in said proprietary format; and

retrieving said attribute expressed in a standard format from said database if said directory object does not contain said attribute expressed in said proprietary format and recast said attribute expressed in said standard format as said attribute expressed in said proprietary format, wherein said proprietary format is selected from the group consisting of: a format characterized by a 16 kilobit data rate, a format characterized by a 24 kilobit data rate, a textual attribute, and a graphic image.

14. The method as recited in claim 8 wherein said directory object includes said attribute expressed in a plurality of proprietary formats.

15. A directory server, comprising:

a database containing a plurality of directory objects having sampled streams of spoken voice data associated therewith;

a request reception module, associated with said database, that receives a Lightweight Directory Access Protocol (LDAP) request for an attribute of said directory object that is expressed in a proprietary format; and

a request fulfillment module, associated with said request reception module, that:

if said attribute contained in said database is expressed in said proprietary format, retrieves said attribute expressed in said proprietary format from said database and responds to said LDAP request with an LDAP response including said attribute expressed in said proprietary format, and

if said attribute is not expressed in said proprietary format, retrieves said attribute expressed in a standard format from said database and responds to said LDAP request with an LDAP response including said attribute expressed in said standard format recast to appear as if said attribute were expressed in said proprietary format even though said attribute in said response is actually expressed in said standard format.

16. The directory server as recited in claim 15 wherein said request fulfillment module responds to said LDAP request with an LDAP response including an indication of a format of said attribute.

17. The directory server as recited in claim 16 wherein said indication is of a standard type.

18. The directory server as recited in claim 15 wherein said standard format is characterized by a 32 kilobit data rate.

19. The directory server as recited in claim 15 wherein said directory objects include multiple sampled streams of spoken voice data expressed in a plurality of proprietary formats.

20. A directory server, comprising:

a database containing a plurality of directory objects having sampled streams of spoken voice data associated therewith;

a request reception module, associated with said database, that receives a Lightweight Directory Access Protocol (LDAP) request for an attribute of said directory object that is expressed in a proprietary format; and

a request fulfillment module, associated with said request reception module, that:

if said attribute contained in said database is expressed in said proprietary format, retrieves said attribute expressed in said proprietary format from said database,

if said attribute is not expressed in said proprietary format, retrieves said attribute expressed in a standard format from said database and recasts said attribute expressed in said standard format as said attribute expressed in said proprietary format, and wherein said proprietary format is selected from the group consisting of: a format characterized by a 16 kilobit data rate, a format characterized by a 24 kilobit data rate, a textual attribute, and a graphic image.

21. A directory server, comprising:

a database for containing a plurality of directory objects haring attributes associable therewith;

a provisioning module, associated with said database, that causes data associable with one of said directory objects and expressed in a standard format to be stored in said database and associated with said directory object both its a standard format attribute and as a proprietary format attribute;

and a request fulfillment module, associated with said database, that, in response to receipt of a Lightweight Directory Access Protocol (LDAP) request for an attribute expressed in said proprietary format, retrieves said attribute expressed in said proprietary format from said database, if said directory object contains said attribute expressed in said proprietary format, and responds to said LDAP request with an LDAP response including said attribute expressed in said proprietary format and, if said directory object does not contain said attribute expressed in said proprietary format, retrieves said attribute expressed in a standard format from said database and responds to said LDAF request with an LDAP response including said attribute expressed in said standard format recast to appear to LDAP as if said attribute were expressed in said proprietary format even though said attribute in said response is actually expressed in said standard format.

22. The directory server as recited in claim 21 wherein said request fulfillment module responds to said LDAP request with an LDAP response including an indication of a format of said attribute.

23. The directory server as recited in claim 22 wherein said indication is of a standard type.

24. The directory server as recited in claim 21 wherein said standard format is characterized by a 32 kilobit data rate.

25. The directory server as recited in claim 21 wherein said directory objects include multiple sampled streams of spoken voice data expressed in a plurality of proprietary formats.

26. A directory server, comprising:

a database for containing a plurality of directory objects having attributes associable therewith;

a provisioning module, associated with said database, that causes data associable with one of said directory objects and expressed in a standard format to be stored in said database and associated with said directory object both as a standard format attribute and as a proprietary format attribute; and

a request fulfillment module, associated with said database, that, in response to receipt of a Lightweight Directory Access Protocol (LDAP) request for an attribute expressed in said proprietary format, retrieves said attribute expressed in said proprietary format containing data expressed in said standard format, wherein said proprietary format is selected from the group consisting of: a format characterized by a 16 kilobit data rate, a format characterized by a 24 kilobit data rate, a textual attribute, and a graphic image.

27. A directory client, comprising:

a request generation module that generates a Lightweight Directory Access Protocol (LDAP) request for a proprietary format; attribute of a directory object contained in a directory server; and

an attribute parsing module, associated with said request generation module, that parses said proprietary format attribute received in response to said request to determine a format in which said attribute is actually expressed from said database and, if said directory object contains said attribute expressed in said proprietary format, determines that said attribute is expressed in said proprietary format and if said directory object does not contain said attribute expressed in said proprietary format, determines said attribute is expressed in a standard format from said database and determines a response to said LDAP request will include said attribute expressed in said standard format recast to appear to LDAP as if said attribute were expressed in said proprietary format even though said attribute in said response is actually expressed in said standard format.

28. The directory client as recited in claim 27 wherein said proprietary format attribute includes an indication of a format of said attribute.

29. The directory client as recited in claim 28 wherein said indication is of a standard type.

30. The directory client as recited in claim 27 wherein said format in which said attribute is actually expressed is characterized by a 32 kilobit data rate.

31. The directory client as recited in claim 27 wherein said directory objects include multiple sampled streams of spoken voice data expressed in a plurality of proprietary formats.

32. A directory client, comprising:

a request generation module that generates a Lightweight Directory Access Protocol (LDAP) request for a proprietary format attribute of a directory object contained in a directory server; and

an attribute parsing module, associated with said request generation module, that parses said proprietary format attribute received in response to said request to determine a format in which said attribute is actually expressed, wherein said format in which said attribute is actually expressed is selected from the group consisting of: a format characterized by a 16 kilobit data rate, a format characterized by a 24 kilobit data rate, a textual attribute, and a graphic image.

Assignments (10)
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001) Recorded May 18, 2023
From: GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT
To: ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.); AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; HYPERQUALITY, INC.; HYPERQUALITY II, LLC; CAAS TECHNOLOGIES, LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 063779/0622 →
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 →
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 →
RELEASE OF SECURITY INTEREST Recorded Jan 9, 2018
From: CITICORP USA, INC.
To: AVAYA, INC.; SIERRA HOLDINGS CORP.; AVAYA TECHNOLOGY, LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.
Reel/Frame 045032/0213 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 030083/0639 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVAYA INC.
Reel/Frame 045012/0666 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 025863/0535 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST, NA
To: AVAYA INC.
Reel/Frame 044892/0001 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 012816/0088 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK
To: AVAYA INC. (FORMERLY KNOWN AS AVAYA TECHNOLOGY CORP.)
Reel/Frame 044892/0158 →
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 →