US6016499A
Expired / Lapsed
US
⏱️ 0.0 years remaining
System and method for accessing a directory services respository
Assignee: RPX Corp
•
Filing: 1997-07-21
•
Granted: 2000-01-18
•
Expires: 2017-07-21
Abstract
Abstract Methods and systems are provided for database-style access to a directory services repository stored on a computer network. A directory services application programming interface is controlled by a driver. The driver translates relational database language statements, such as ODBC-compliant SQL statements, into an executable API sequence that produces an API result. The driver also translates the API result into a relational database result. The repository may be a Novell Directory Services repository or an X.500 directory services repository. The invention maps an effective class of the repository to a table identified in the relational database language statement. Each object that is an instance of the effective class is mapped to a row in the table, and each attribute maps to a column of the table. As a result, the invention allows database tools such as report generators to work with the information stored in the repository.
Inventors
- 👤 Daniel T. Ferguson
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-30 22:36
CPC Classifications
G; G06; G06F; G06F16/00; G06F16/20; G06F16/25; G06F16/252; G06F16/258; Y; Y10; Y10S; Y10S707/00; Y10S707/99931; Y10S707/99941; Y10S707/99943; Y10S707/99944; Y10S707/99945; Y10S707/99948
Claims Analysis
Total Claims: 71
Claim 1
Independent Claim
152 words
A system providing access to a directory services repository which is stored on a computer system, the claimed system comprising: a directory services application programming interface, also known as the API, which includes at least one callable element that is capable of accessing a component of the directory services repository in response to being called; and a driver which is capable of translating a relational database language statement into an executable API sequence that includes a call to the callable element and produces an API result, the driver also being capable of translating the API result into a relational database result, wherein the directory services repository component includes an effective class and an object having a context the relational database language statement identifies a table and a subset restriction, and the driver and the API together map the effective class to the table and also map the context to the subset restriction.
Claim 2
Dependent Claim
25 words
The system of claim 1, wherein the directory services repository includes a Novell Directory Services repository and the API includes a Novell Directory Services API.
Claim 3
Dependent Claim
15 words
The system of claim 1, wherein the API includes a Lightweight Directory Access Protocol API.
Claim 4
Dependent Claim
16 words
The system of claim 1, wherein the API includes a Java Naming and Directory Interface API.
Claim 5
Dependent Claim
25 words
The system of claim 1, wherein the directory services repository includes an X.500 directory services repository and the API includes an X.500 directory services API.
Claim 6
Dependent Claim
72 words
The system of claim 1, further comprising a NetWare Core Protocol API, also known as the NCP API, wherein the driver is also capable of translating a relational database language statement into an executable NCP API sequence that includes a call to a callable element of the NCP API and produces an NCP API result, and the driver is also capable of translating the NCP API result into a relational database result.
Claim 7
Dependent Claim
19 words
The system of claim 1, wherein the relational database language statement is written in a Structured Query Language format.
Claim 8
Dependent Claim
23 words
The system of claim 1, wherein the relational database language statement conforms with at least one version of the Open Database Connectivity standard.
Claim 9
Dependent Claim
16 words
The system of claim 1, wherein the driver provides read-only access to the directory services repository.
Claim 10
Dependent Claim
18 words
The system of claim 1, wherein the driver provides read and write access to the directory services repository.
Claim 11
Dependent Claim
46 words
The system of claim 1, wherein the directory services repository component includes an object that is an instance of the effective class, the relational database language statement identifies a row in the table, and the driver and the API together map the object to the row.
Claim 12
Dependent Claim
54 words
The system of claim 1, wherein the driver and the API allow an application program to discover the number of rows of the table by visiting each object, if any, which is an instance of the effective class, until a "no more date" indication is returned because each object, if any, has been accessed.
Claim 13
Dependent Claim
38 words
The system of claim 1, wherein the directory services repository component includes an attribute, the relational database language statement identifies a column of a table, and the driver and the API together map the attribute to the column.
Claim 14
Dependent Claim
36 words
The system of claim 13, wherein the attribute has a plurality of simultaneous values, and the driver and the API together map each value to a separate row in the table, thereby presenting a one-to-many relation.
Claim 15
Dependent Claim
58 words
The system of claim 1, wherein the directory services repository component includes a distinguished name attribute, the relational database language statement requests identification of a column that is most efficient for repositioning to a row, and the driver and the API together respond to the statement by identifying the column that is mapped to the distinguished name attribute.
Claim 16
Dependent Claim
42 words
The system of claim 1, wherein the directory services repository component includes a non-mnemonic object name, the relational database language statement identifies a column of a table, and the driver and the API together map the non-mnemonic object name to the column.
Claim 17
Dependent Claim
42 words
The system of claim 1, wherein the directory services repository component includes a non-mnemonic tree name, the relational database language statement identifies a column of a table, and the driver and the API together map the non-mnemonic tree name to the column.
Claim 18
Independent Claim
164 words
A method for providing access to a directory services repository which is stored on a server computer in a computer network, the method comprising the steps of: interfacing with a directory services application programming interface, also known as the API, which includes at least one callable element that is capable of accessing a component of the directory services repository in response to being called; providing a driver which is capable of translating a relational database language statement into an executable API sequence that includes a call to the callable element and produces an API result; mapping an effective class in the directory services repository to a table identified in the relational database language statement; mapping an object that is an instance of the effective class to a row in the table; and mapping a context of the object to a subset restriction in the relational database language statement; and requesting access to the repository by passing the relational database language statement to the driver.
Claim 19
Independent Claim
164 words
A method for providing access to a directory services repository which is stored on a server computer in a computer network, the method comprising the steps of: interfacing with a directory services application programming interface, also known as the API, which includes at least one callable element that is capable of accessing a component of the directory services repository in response to being called; providing a driver which is capable of translating a relational database language statement into an executable API sequence that includes a call to the callable element and produces an API result; mapping an effective class in the directory services repository to a table identified in the relational database language statement; mapping an object that is an instance of the effective class to a row in the table; and mapping a context of the object to a subset restriction in the relational database language statement; and requesting access to the repository by passing the relational database language statement to the driver.
Claim 20
Dependent Claim
18 words
The method of claim 18, wherein the requesting step passes a Structured Query Language statement to the driver.
Claim 21
Dependent Claim
31 words
The method of claim 18, further including the step of mapping an attribute in the directory services repository to a column of a table identified in the relational database language statement.
Claim 22
Dependent Claim
190 words
A computer storage medium having a configuration that represents data and instructions which will cause at least a portion of a computer system to perform method steps for providing access to a directory services repository which is stored on a server computer in a computer network, the method steps comprising the steps of: interfacing with a directory services application programming interface, also known as the API, which includes at least one callable element that is capable of accessing a component of the directory services repository in response to being called; providing a driver which is capable of translating a relational database language statement into an executable API sequence that includes a call to the callable element and produces an API result; mapping an effective class in the directory services repository to a table identified in the relational database language statement; mapping an object that is an instance of the effective class to a row in the table; and mapping a context of the object to a subset restriction in the relational database language statement; and requesting access to the repository by passing the relational database language statement to the driver.
Claim 23
Dependent Claim
190 words
A computer storage medium having a configuration that represents data and instructions which will cause at least a portion of a computer system to perform method steps for providing access to a directory services repository which is stored on a server computer in a computer network, the method steps comprising the steps of: interfacing with a directory services application programming interface, also known as the API, which includes at least one callable element that is capable of accessing a component of the directory services repository in response to being called; providing a driver which is capable of translating a relational database language statement into an executable API sequence that includes a call to the callable element and produces an API result; mapping an effective class in the directory services repository to a table identified in the relational database language statement; mapping an object that is an instance of the effective class to a row in the table; and mapping a context of the object to a subset restriction in the relational database language statement; and requesting access to the repository by passing the relational database language statement to the driver.
Claim 24
Dependent Claim
19 words
The storage medium of claim 21, wherein the requesting step passes a Structured Query Language statement to the driver.
Claim 25
Dependent Claim
35 words
The storage medium of claim 21, wherein the method further includes the step of mapping an attribute in the directory services repository to a column of a table identified in the relational database language statement.
Claim 26
Independent Claim
162 words
A system providing access to a directory services repository which is stored on a computer system, the claimed system comprising: a directory services application programming interface, also known as the API, which includes at least one callable element that is capable of accessing a component of the directory services repository in response to being called, the API including a Java Naming and Directory Interface API; and a driver which is capable of translating a relational database language statement into an executable API sequence that includes a call to the callable element and produces an API result, the driver also being capable of translating the API result into a relational database results, wherein the directory services repository component includes an effective class and an object having a context the relational database language statement identifies a table and a subset restriction, and the driver and the API together map the effective class to the table and also map the context to the subset restriction.
Claim 27
Dependent Claim
25 words
The system of claim 24, wherein the directory services repository includes a Novell Directory Services repository and the API includes a Novell Directory Services API.
Claim 28
Dependent Claim
15 words
The system of claim 24, wherein the API includes a Lightweight Directory Access Protocol API.
Claim 29
Dependent Claim
25 words
The system of claim 24, wherein the directory services repository includes an X.500 directory services repository and the API includes an X.500 directory services API.
Claim 30
Dependent Claim
72 words
The system of claim 24, further comprising a NetWare Core Protocol API, also known as the NCP API, wherein the driver is also capable of translating a relational database language statement into an executable NCP API sequence that includes a call to a callable element of the NCP API and produces an NCP API result, and the driver is also capable of translating the NCP API result into a relational database result.
Claim 31
Dependent Claim
19 words
The system of claim 24, wherein the relational database language statement is written in a Structured Query Language format.
Claim 32
Dependent Claim
23 words
The system of claim 24, wherein the relational database language statement conforms with at least one version of the Open Database Connectivity standard.
Claim 33
Dependent Claim
16 words
The system of claim 24, wherein the driver provides read-only access to the directory services repository.
Claim 34
Dependent Claim
18 words
The system of claim 24, wherein the driver provides read and write access to the directory services repository.
Claim 35
Dependent Claim
46 words
The system of claim 24, wherein the directory services repository component includes an object that is an instance of the effective class, the relational database language statement identifies a row in the table, and the driver and the API together map the object to the row.
Claim 36
Dependent Claim
54 words
The system of claim 24, wherein the driver and the API allow an application program to discover the number of rows of the table by visiting each object, if any, which is an instance of the effective class, until a "no more data" indication is returned because each object, if any, has been accessed.
Claim 37
Dependent Claim
38 words
The system of claim 24, wherein the directory services repository component includes an attribute, the relational database language statement identifies a column of a table, and the driver and the API together map the attribute to the column.
Claim 38
Dependent Claim
36 words
The system of claim 35, wherein the attribute has a plurality of simultaneous values, and the driver and the API together map each value to a separate row in the table, thereby presenting a one-to-many relation.
Claim 39
Dependent Claim
58 words
The system of claim 24, wherein the directory services repository component includes a distinguished name attribute, the relational database language statement requests identification of a column that is most efficient for repositioning to a row, and the driver and the API together respond to the statement by identifying the column that is mapped to the distinguished name attribute.
Claim 40
Dependent Claim
42 words
The system of claim 24, wherein the directory services repository component includes a non-mnemonic object name, the relational database language statement identifies a column of a table, and the driver and the API together map the nonmnemonic object name to the column.
Claim 41
Dependent Claim
42 words
The system of claim 24, wherein the directory services repository component includes a non-mnemonic tree name, the relational database language statement identifies a column of a table, and the driver and the API together map the non-mnemonic tree name to the column.
Claim 42
Dependent Claim
25 words
The system of claim 28, wherein the directory services repository includes a Novell Directory Services repository and the API includes a Novell Directory Services API.
Claim 43
Dependent Claim
15 words
The system of claim 28, wherein the API includes a Lightweight Directory Access Protocol API.
Claim 44
Dependent Claim
25 words
The system of claim 28, wherein the directory services repository includes an X.500 directory services repository and the API includes an X.500 directory services API.
Claim 45
Dependent Claim
19 words
The system of claim 28, wherein the relational database language statement is written in a Structured Query Language format.
Claim 46
Dependent Claim
23 words
The system of claim 28, wherein the relational database language statement conforms with at least one version of the Open Database Connectivity standard.
Claim 47
Dependent Claim
16 words
The system of claim 28, wherein the driver provides read-only access to the directory services repository.
Claim 48
Dependent Claim
18 words
The system of claim 28, wherein the driver provides read and write access to the directory services repository.
Claim 49
Dependent Claim
36 words
The system of claim 28, wherein the directory services repository component includes an effective class, the relational database language statement identifies a table, and the drive and API together map the effective class to the table.
Claim 50
Dependent Claim
46 words
The system of claim 47, wherein the directory services repository component inlcudes an object that is an instance of the effective class, the relational database language statement identifies a row in the table, and the driver and the API together map the object to the row.
Claim 51
Dependent Claim
54 words
The system of claim 47, wherein the driver and the API allow an application program to discover the number of rows of the table by visiting each object, if any, which is an instance of the effective class, until a "no more data" indication is returned because each object, if any, has been accessed.
Claim 52
Dependent Claim
40 words
The system of claim 47, wherein the directory services repository component includes an object having a context, the relational database language statement identifies a subset restriction, and the driver and the API together map the context to the subset restriction.
Claim 53
Dependent Claim
38 words
The system of claim 28, wherein the directory services repository component includes an attribute, the relational database language statement identifies a column of a table, and the drive and the API together map the attribute to the column.
Claim 54
Dependent Claim
36 words
The system of claim 51, wherein the attribute has a plurality of simultaneous values, and the driver and the API together map each value to a separate row in the table, thereby presenting a one-to-many relation.
Claim 55
Dependent Claim
58 words
The system of claim 28, wherein the directory services repository component includes a distinguished name attribute, the relational database language statement requests identification of a column that is most efficient for repositioning to a row, and the driver and the API together respond to the statement by identifying the column that is mapped to the distinguished name attribute.
Claim 56
Dependent Claim
42 words
The system of claim 28, wherein the directory services repository component includes a non-mnemonic object name, the relational database language statement identifies a column of a table, and the driver and the API together map the non-mnemonic object name to the column.
Claim 57
Dependent Claim
42 words
The system of claim 28, wherein the directory services repository component includes a non-mnemonic tree name, the relational database language statement identifies a column of a table, and the driver and the API together map the non-mnemonic tree name to the column.
Claim 58
Independent Claim
165 words
A system providing access to a directory services repository which is stored on a computer system, the claimed system comprising: a directory services application programming interface, also known as the API, which includes at least one callable element that is capable of accessing a component of the directory services repository in response to being called; and a driver which is capable of translating a relational database language statement into an executable API sequence that includes a call to the callable element and produces an API result, the driver also being capable of translating the API result into a relational database result, wherein the directory services repository component includes an attribute which has a plurality of simultaneous values, the relational database language statement identifies a column of a table, the driver and the API together map the attribute to the column, and the driver and the API together map each value of the attribute to a separate row in the table, thereby presenting a one-to-many relation.
Claim 59
Dependent Claim
25 words
The system of claim 56, wherein the directory services repository includes a Novell Directory Services repository and the API includes a Novell Directory Services API.
Claim 60
Dependent Claim
15 words
The system of claim 56, wherein the API includes a Lightweight Directory Access Protocol API.
Claim 61
Dependent Claim
25 words
The system of claim 56, wherein the directory services repository includes an X.500 directory services repository and the API includes an X.500 directory services API.
Claim 62
Dependent Claim
19 words
The system of claim 56, wherein the relational database language statement is written in a Structured Query Language format.
Claim 63
Dependent Claim
23 words
The system of claim 56, wherein the relational database language statement conforms with at least one version of the Open Database Connectivity standard.
Claim 64
Dependent Claim
16 words
The system of claim 56, wherein the driver provides read-only access to the directory services repository.
Claim 65
Dependent Claim
18 words
The system of claim 56, wherein the driver provides read and write access to the directory services repository.
Claim 66
Dependent Claim
37 words
The system of claim 56, wherein the directory services repository component includes an effective class, the relational database language statement identifies a table, and the driver and the API together map the effective class to the table.
Claim 67
Dependent Claim
46 words
The system of claim 64, wherein the directory services repository component includes an object that is an instance of the effective class, the relational database language statement identifies a row in the table, and the driver and the API together map the object to the row.
Claim 68
Dependent Claim
54 words
The system of claim 64, wherein the driver and the API allow an application program to discover the number of rows of the table by visiting each object, if any, which is an instance of the effective class, until a "no more data" indication is returned because each object, if any, has been accessed.
Claim 69
Dependent Claim
58 words
The system of claim 56, wherein the directory services repository component includes a distinguished name attribute, the relational database language statement requests identification of a column that is most efficient for repositioning to a row, and the driver and the API together respond to the statement by identifying the column that is mapped to the distinguished name attribute.
Claim 70
Dependent Claim
42 words
The system of claim 56, wherein the directory services repository component includes a non-mnemonic object name, the relational database language statement identifies a column of a table, and the driver and the API together map the nonmnemonic object name to the column.
Claim 71
Dependent Claim
42 words
The system of claim 56, wherein the directory services repository component includes a non-mnemonic tree name, the relational database language statement identifies a column of a table, and the driver and the API together map the non-mnemonic tree name to the column.
References Cited (Backward Citations)
US4769772A
Cited
US4930071A
Cited
US5410675A
Cited
US5257366A
Cited
US5416917A
Cited
US5212787A
Cited
US5499358A
Cited
US5483586A
Cited
US5617568A
Cited
US5761499A
Cited
US5812653A
Cited
US5857190A
Cited
US5761494A
Cited
US5878415A
Cited
US5878411A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2003-01-17 | 2003-07-19 | 2004-01-18 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2007-01-17 | 2007-07-19 | 2008-01-18 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2011-01-17 | 2011-07-19 | 2012-01-18 | $7700.00 | Window Closed / Lapsed |