Table arrangement for a directory service system and for related method facilitating queries for the directory

Abstract

A directory services system, such as one providing a X.500 or LDAP directory service, having a design and a method of operation which facilitates queries in and out of the directory, table organisation/layout and clustering. In the arrangement of the directory service, tables are organized corresponding to their function, thereby permitting an arrangement based on service modeling and functional organisation that permits clustering. A preferred layout design incorporates principal, conceptual, logical and/or physical designs.

1 . A directory service arrangement comprising a data base using a plurality of tables, each of said tables comprising a plurality of rows and columns, and each of said tables modeled according to a service modeling approach.  
   
   
       2 . (canceled)  
   
   
       3 . (canceled)  
   
   
       4 . (canceled)  
   
   
       5 . (canceled)  
   
   
       6 . A method of providing tables in a directory service apparatus, comprising: establishing a plurality of tables in a directory service apparatus, each of said tables comprising a plurality of rows and columns; and 
 defining each of the tables according to a service modeling approach.    
   
   
       7 . (canceled)  
   
   
       8 . (canceled)  
   
   
       9 . (canceled)  
   
   
       10 . (canceled)  
   
   
       11 . (canceled)  
   
   
       12 . (canceled)  
   
   
       13 . (canceled)  
   
   
       14 . (canceled)  
   
   
       15 . (canceled)  
   
   
       16 . (canceled)  
   
   
       17 . (canceled)  
   
   
       18 . (canceled)  
   
   
       19 . (canceled)  
   
   
       20 . (canceled)  
   
   
       21 . (canceled)  
   
   
       22 . (canceled)  
   
   
       23 . (canceled)  
   
   
       24 . (canceled)  
   
   
       25 . (canceled)  
   
   
       26 . (canceled)  
   
   
       27 . (canceled)  
   
   
       28 . (canceled)  
   
   
       29 . (canceled)  
   
   
       30 . (canceled)  
   
   
       31 . (canceled)  
   
   
       32 . (canceled)  
   
   
       33 . (canceled)  
   
   
       34 . (canceled)  
   
   
       35 . (canceled)  
   
   
       36 . (canceled)  
   
   
       37 . (canceled)  
   
   
       38 . (canceled)  
   
   
       39 . (canceled)  
   
   
       40 . (canceled)  
   
   
       41 . (canceled)  
   
   
       42 . (canceled)  
   
   
       43 . (canceled)  
   
   
       44 . (canceled)  
   
   
       45 . (canceled)  
   
   
       46 . (canceled)  
   
   
       47 . (canceled)  
   
   
       48 . (canceled)  
   
   
       49 . (canceled)  
   
   
       50 . (canceled)  
   
   
       51 . (canceled)  
   
   
       52 . (canceled)  
   
   
       53 . (canceled)  
   
   
       54 . (canceled)  
   
   
       55 . (canceled)  
   
   
       56 . (canceled)  
   
   
       57 . (canceled)  
   
   
       58 . (canceled)  
   
   
       59 . (canceled)  
   
   
       60 . (canceled)  
   
   
       61 . (canceled)  
   
   
       62 . A method of arranging tables of a plurality of tables of a directory service arrangement, for providing directory services, comprising primary services and secondary services, the method comprising the steps of: 
 decomposing the tables around primary service relationships, and    deriving secondary services by using table joins.    
   
   
       63 . (canceled)  
   
   
       64 . A method of decomposing a principal database design, according to a service modeling approach, having a PROPERTY table comprising at least a column for object name and parent name, in a directory service system, the method comprising: 
 applying functional decomposition to the PROPERTY table, and deriving a conceptual design having a HIERARCHY table, an OBJECT table, and an ATTRIBUTE table from the PROPERTY table.    
   
   
       65 . A method of decomposing a conceptual design in a directory service system offering a plurality of services and being operative with a database having a plurality of tables, including a HIERARCHY table and an OBJECT table, each comprising a plurality of columns, the method comprising: 
 a. applying service decomposition to said HIERARCHY table, thereby deriving at least two table(s) comprising a DIT (Directory Information Tree) table having information required for navigation, a NAME table having information required for returning names, including raw relative distinguished name (RDN), a TREE table having information about an entry's path, and an ALIAS table having entries that are aliases;    b. applying service decomposition to said OBJECT table, thereby deriving at least two tables, a SEARCH table for resolving filters in a Search service, said SEARCH table including one row for each attribute value of each entry, and an ENTRY table for returning values in Read and Search services, said ENTRY table having one row for each attribute value of each entry, and    c. deriving a logical design having tables defined in steps a and b above and an ATTR (ATTRIBUTE) table.    
   
   
       66 . A method of decomposing a logical design of a directory service system into a physical design according to a service modeling approach, comprising: 
 applying physical decomposition to the logical design, thereby deriving the physical design.    
   
   
       67 . A directory service system for one or more objects, wherein said system comprises: 
 a plurality of tables according to a principal design, a conceptual design and a logical design,    wherein said principal design comprises at least one table which is a PROPERTY table.    
   
   
       68 . (canceled)  
   
   
       69 . (canceled)  
   
   
       70 . (canceled)  
   
   
       71 . (canceled)  
   
   
       72 . (canceled)  
   
   
       73 . (canceled)  
   
   
       74 . A directory service system, having a plurality of tables arranged in a conceptual design, wherein each table comprises a plurality of columns, said system comprising: 
 a HIERARCHY table, adapted to contain information about objects, comprising their parents, their names, their relative positions in a hierarchy, and if they are aliases, for defining the structural relationship between objects;    an OBJECT table, adapted to contain information for finding a particular value and for retrieving values, for defining the attribute values within each object; and    an ATTRIBUTE table, adapted to contain information about the attributes of object(s).    
   
   
       75 . (canceled)  
   
   
       76 . (canceled)  
   
   
       77 . (canceled)  
   
   
       78 . (canceled)  
   
   
       79 . (canceled)  
   
   
       80 . An implementation of directory services in a RDBMS which supports a relational language, using service modeling, the implementation comprising: 
 an ATTRIBUTE table, where extensibility is provided by allowing the definition of a new attribute type by adding a row to the table;    an OBJECT table, which defines the attributes within each object; and    a HIERARCHY table which defines the relationship between the objects.    
   
   
       81 . (canceled)  
   
   
       82 . (canceled)  
   
   
       83 . (canceled)  
   
   
       84 . (canceled)  
   
   
       85 . (canceled)  
   
   
       86 . (canceled)  
   
   
       87 . (canceled)  
   
   
       88 . (canceled)  
   
   
       89 . (canceled)  
   
   
       90 . (canceled)  
   
   
       91 . (canceled)  
   
   
       92 . (canceled)  
   
   
       93 . (canceled)  
   
   
       94 . (canceled)  
   
   
       95 . (canceled)  
   
   
       96 . (canceled)  
   
   
       97 . A data arrangement for implementing directory services in a RDBMS which supports a relational language, having a fixed set of queries/services defined by a service modeling approach, the data arrangement comprising: 
 an extensible ATTRIBUTE table, comprising information about attributes;    an OBJECT table, comprising data which defines the attributes within each object; and/or    a HIERARCHY table, comprising data which defines the relationship between the objects.    
   
   
       98 . (canceled)  
   
   
       99 . (canceled)  
   
   
       100 . (canceled)  
   
   
       101 . (canceled)  
   
   
       102 . (canceled)  
   
   
       103 . (canceled)  
   
   
       104 . (canceled)  
   
   
       105 . (canceled)  
   
   
       106 . (canceled)  
   
   
       107 . (canceled)  
   
   
       108 . (canceled)  
   
   
       109 . (canceled)  
   
   
       110 . (canceled)  
   
   
       111 . (canceled)  
   
   
       112 . (canceled)  
   
   
       113 . (canceled)