Directory services system and methods with mapping in database tables
AssigneeComputer Associates Think, Inc.
InventorRichard Hans Harvey
Life of this patent
Estimating the term…
Loading patent…
AssigneeComputer Associates Think, Inc.
InventorRichard Hans Harvey
Estimating the term…
A method and apparatus for addressing problems associated with the implementation of directory services, such as X.500 and LDAP, in a SQL environment, particularly problems associated with interrogating database provided to implement directory services in the SQL environment. According to the disclosed method and apparatus, the system is based on the use of tables that may be arranged to have a plurality of columns, so that they support a variety of functions in order to implement directory services, such as X.500 and LDAP. In one aspect, the present invention provides a method of creating one or more SQL commands corresponding to a directory service. In another aspect, the present invention provides a many examples of tables and their function. Many examples of an implementation of directory services using SQL based technology are disclosed. This application is a divisional of U.S. Ser. No. 08/793,575, which is currently pending and which is incorporated herein by reference in its entirety.
A method of implementing directory services for a relational data base management system using a relational language comprising:
A method of implementing directory services for a relational data base management system using a relational language comprising:
34 A method of implementing directory services as claimed in claim 32 wherein said database comprises a directory tree, having a plurality of distinguished names (DN) each comprising one or more relative distinguished names (RDN), and said step of applying a process of name resolution comprises navigating said directory tree.
A method of implementing directory services as claimed in claim 34 wherein said process of navigating comprises a tree walk, which begins from the root of the directory tree and continues down the directory tree until all the RDNs in a DN have been resolved.
A method of implementing directory services as claimed in claim 34, further comprising:
A method of implementing directory services as claimed in claim 34, particularly a read service to extract information from an explicitly identified entry, further comprising:
A method of implementing directory services as claimed in claim 34, particularly a compare service for comparing a value with values of a particular attribute type in a particular object entry, further comprising:
A method of implementing directory services as claimed in claim 34, particularly a list service to obtain a list of immediate subordinates of an explicitly identified entry, further comprising:
A method of implementing directory services as claimed in claim 34, particularly a base object search service, further comprising:
A method of implementing directory services as claimed in claim 34, particularly a one level search service, further comprising:
A method of implementing directory services as claimed in claim 34, particularly a whole subtree search service, further comprising:
A method of implementing directory services as claimed in claim 34, particularly an add service to add a leaf entry, either an object entry or an alias entry, to the Directory Information Tree (DIT), further comprising:
A method of implementing directory services as claimed in claim 34, particularly a remove service to remove a leaf entry, either an object entry or an alias entry, to the Directory Information Tree (DIT), further comprising:
A method of implementing directory services as claimed in claim 34, particularly a modify entry service, further comprising:
A method of implementing directory services as claimed in claim 34, particularly a modify RDN service, further comprising:
A system for implementing directory services for a relational data base management system using a relational language comprising:
A system for implementing directory services for a relational data base management system using a relational language comprising:
A method of creating one or more SQL commands corresponding to a directory service, the method including the steps of:
A method of executing a service in a directory service system, the method including using a DIT Table for a navigate function.
A method of executing a service in a directory service system, the method including using a DIT Table for a one level search function.
A method of executing a service in a directory service system, the method including using a SEARCH Table for a find function.
A method of executing a service in a directory service system, the method including using a NAME Table for a returning DN function.
A method of executing a service in a directory service system, the method including using an ENTRY Table for a returning object function.
A method of executing a service in a directory service system, the method including using a TREE Table for a returning DN function.
A method of executing a service in a directory service system, the method including using a TREE Table for a subtree search function.
A method of executing a service in a directory service system, the method including using an ALIAS Table for an alias function.
A method of creating one or more SQL commands corresponding to a directory service, the method including the steps of:
A method of creating one or more SQL commands corresponding to a directory service, wherein the service control comprises a time limit.
A method of creating one or more SQL commands corresponding to a directory service, wherein the service control comprises a size limit.
A method of creating one or more SQL commands corresponding to a directory service, the method including the steps of:
A method of creating one or more SQL commands corresponding to a directory service, the method including the steps of:
A method of creating one or more SQL commands corresponding to a directory service, the method including the steps of:
A method of creating one or more SQL commands corresponding to a directory service, the method including the steps of:
A method of creating one or more SQL commands corresponding to a directory service, the method including the steps of:
A method of creating one or more SQL commands corresponding to a directory service, the method including the steps of:
A method of providing directory services in a directory service system, the method including the step of:
A method of providing directory services in a directory service system, the method including the step of:
A method of providing arbitrary complexity in directory services in a directory service system, the method including the step of:
A method of providing directory services in a directory service system, the method including the step of:
A method of providing directory services in a directory service system, the method including the step of:
A method of providing directory services in a directory service system, the method including the step of:
A method of providing directory services in a directory service system, the method including the step of:
A method of providing directory services in a directory service system, the method including the step of:
A method of implementing X.500 services in a RDBMS which supports a relational language, using service modeling, comprising:
An implementation of X.500 services in a RDBMS which supports a relational language, using service modeling, the implementation comprising:
149 The implementation of claim 148, wherein the alias column comprises an alias and an A-EID column providing information about the destination to which the alias points.
The invention as herein disclosed.
Dependencies are inferred from the claim text.
Drawings are temporarily unavailable. Open the PDF at USPTO
From the US filing history. Foreign family members aren’t listed.
Backward citations are indexed for grants only.
Network directories; Name-to-address mapping: lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g.…
Databases characterised by their database models, e.g. relational or object models: relational databases
Relational databases: entity relationship models
Databases characterised by their database models, e.g. relational or object models: object oriented databases
Term end not estimated
1. Field of the Invention
The present invention relates to the field of directory services. In particular, the present invention is directed to application of X.500, LDAP and similar services to a relational database, a database design and use of the database to perform X.500 services.
One aspect of the invention relates to implementing directory services, such as X.500 or LDAP services in an SQL environment. Furthermore, an aspect of invention relates to method(s) of interrogating logical design tables, as disclosed herein.
FIG. 1 is an illustration of a table that lists X.500 products currently available, none of which use a SQL data base as an underlying data store.
FIG. 2A is an illustration schematically of an overview of the present invention, particularly the principal design and the corresponding conceptual design, as applied to the provision of a table structure for an X.500 system.
FIG. 2B is an illustration schematically of an overview of the present invention, particularly the logical design and the corresponding physical design, as applied to the provision of a table structure for an X.500 system.
1. PRINCIPAL DESIGN
The X.500 prior art attempts at implementation have been unable to overcome the relatively basic structural and operational differences between the X.500 requirements and functionality and SQL. The X.500 standard has a particular structure by nature, whereas SQL is designed to operate on relational structured tables.
For a typical relational database application, the nature of data is well known, i.e. tables will consist of a number of columns and each column contains data relating to a particular data type (see Table B1). The different data types that can be stored is limited to the columns of the table. The data types are also limited to the types supported by the database (e.g. string, numeric, money, date). The database may also store data of a form not understood by the database per se, but understood by the application e.g. binary data. 1 TABLE B1 Employee Table Name Surname Title Phone Chris MASTERS Sales Manager 03 727-9456 Alana MORGAN Sales Support 03 727-9455 . . . . . . . . . . . .