WO2001011494A2 - Method and device for accessing a storage device with a directory structure - Google Patents
Method and device for accessing a storage device with a directory structure Download PDFInfo
- Publication number
- WO2001011494A2 WO2001011494A2 PCT/DE2000/002541 DE0002541W WO0111494A2 WO 2001011494 A2 WO2001011494 A2 WO 2001011494A2 DE 0002541 W DE0002541 W DE 0002541W WO 0111494 A2 WO0111494 A2 WO 0111494A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- directory
- dir
- access
- findextension
- application
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/258—Data format conversion from or to a database
Definitions
- the invention relates to a method and an arrangement for memory access of a database application to a memory device with a directory structure via a so-called ODBC (Open DataBase Connectivity) and a so-called LDAP (Light Weight Directory Access Protocol) driver.
- ODBC Open DataBase Connectivity
- LDAP Light Weight Directory Access Protocol
- a memory access to a database starting from a database application running on a data processing device under the operating system 'Microsoft Windows' usually takes place by means of a so-called ODBC driver (Open DataBase Connectivity).
- This ODBC software interface controls the bidirectional data exchange between the database application and the database.
- the ODBC software interface realizes database access to a so-called relational database.
- Relational databases have a table structure, so that the database is subdivided into fields that can be addressed using columns and rows.
- An example of a relational database with such a table structure is the well-known 'Microsoft Access' database.
- LDAP driver Light Weight Directory Access Protocol
- the directory usually has a directory hierarchy consisting of individual objects and sub-objects, so that a tree structure, the so-called directory tree arises.
- the present invention has for its object to provide measures by which the effort for such memory access to a directory can be reduced.
- An essential advantage of the method and / or the arrangement according to the invention is that by expanding a schema depicting the object structure of the directory for the database application by at least one freely configurable quasi-object representing an additional function, the amount of data that can be read from the directory is easily changed the results of the additional function can be expanded.
- Another advantage of the invention is that the additional functions that can be implemented in any programming language are based on modules of the ODBC and LDAP driver that are present as standard, so that the implementation process wall for these additional functions, in contrast to the additional modules for the LDAP driver, is low.
- 1 a structure diagram for the schematic representation of the functional units essential for a read access of a database application to a database
- 2 shows a structure diagram for the schematic representation of a table structure required for read access by the database application
- 3 a structural diagram for the schematic representation of the functional units of an access unit according to the invention which are essential for read access to a directory
- 4 a flow chart to illustrate the essential procedural steps that take place during read access to the directory.
- FIG. 1 shows a structure diagram with the essential functional units necessary for read access of a database application DB-A to differently structured databases.
- DB-A database application
- the database application DB-A For read access to a database, the database application DB-A is connected to an ODBC manager ODBC-M (Open DataBase Connectivity) that controls the read access, whereby the database application DB-A uses the so-called SQL queries (SQL queries ( Structured Query Language) to the ODBC Manager ODBC-M transmitted.
- SQL queries SQL queries ( Structured Query Language)
- SQL is a specially developed for queries from relational databases database Abfragespra ⁇ che.
- the ODBC manager ODBC-M converts the received SQL queries m appropriate ODBC messages and forwards them depending on the type of the addressed database - relatio ⁇ dimensional database or directory - to different, the read access outfeed end of drive units on.
- the ODBC manager forwards the appropriate ODBC queries designed to access a table structure to an ODBC driver ODBC-T1, ODBC-T2, .. ., ODBC-T3, which carries out the read access without further conversions and transfers the results obtained to the database application DB-A.
- a relational database DB1, DB2, ..., DBn the ODBC manager forwards the appropriate ODBC queries designed to access a table structure to an ODBC driver ODBC-T1, ODBC-T2, .. ., ODBC-T3, which carries out the read access without further conversions and transfers the results obtained to the database application DB-A.
- Database DB1, DB2, ..., DBn is the well-known database 'Microsoft Access'. If, on the other hand, the read access to a directory DIR takes place, the ODBC manager forwards the corresponding ODBC queries to a so-called LDAP directory specially designed for read access to the directory DIR.
- the LDAP driver LDAP-T converts the ODBC queries designed for access to a table structure into LDAP queries specially designed for access to a directory DIR and carries out read access to the directory DIR. The determined data is then inserted into a table structure by the LDAP driver LDAP-T m and transferred to the database application DB-A.
- LDAP-T is connected to a specific expansion unit KSE.
- the ODBC manager, the LDAP driver and the expansion unit KSE are collectively referred to as the access unit ZE for the directory DIR.
- the other is of a read access to em 'Corporate Di ⁇ rectory' from an electronic phonebook Ap ⁇ plication considered as a database application DB-A.
- Em In ⁇ play for such a phone book application is the electronic telephone directory DS-Win V2.0 under the Radiosys ⁇ tem 'Microsoft Windows'.
- FIG. 2 shows a structure picture of a table structure required for read access by the telephone book application by means of an SQL query.
- the figure shows a table 'partici ⁇ mer' with a participant associated attributes Last name, first name, organization Org, telephone number TELNU and brutalized in ⁇ Phone InvTelNum.
- the inverted phone number ⁇ InvTelNum m is usually without the leading zeros stored and used an identification of a calling party for an incoming to the telephone book application reputation.
- the number received as part of a call setup on the telephone book application has a plurality of leading zeros. For example, if the calling subscriber is located in another region in Germany, the received number m usually has a leading zero.
- the received number usually has two leading zeros.
- the received phone number is mirrored by the phone book application and the subscriber is clearly identified by comparing the last digits of the inverted received phone number with the inverted telephone number InvTelNum stored in the database.
- FIG. 3 shows a structure diagram of the functional units of the access unit ZE which are essential for read access to the directory DIR.
- a section of the directory tree VB of the directory DIR is shown.
- the nodes of the directory tree VB are often referred to as objects, each of which is assigned a specific object class OC.
- the object hierarchy of the directory tree VB are a first step m a schematic configuration SK istbil ⁇ det.
- the schema configuration SK which is predetermined by the directory tree is expanded according to the invention by at least one quasi-object.
- a quasi-object Ext: FindExtension is shown, the function of which is explained in more detail with reference to FIG. 4.
- FK fields F are defined in the LDAP driver LDAP-T of a field configuration.
- the field definition takes place, for example, by specifying a field name, the length of the field to be defined, the type of the field to be defined, the object class OC of the associated object in the directory tree VB and the attribute assigned to this object.
- each field F is defined for the last name and first name of a subscriber. Both fields F each have a length of 50 characters and a field type 'Strmg'.
- field F is defined for the inverted telephone number of a subscriber, which has a length of 20 characters and a field. type 'integer'. Since the attributes of the directory DIR are not assigned an attribute for an inverted telephone number of a subscriber, it is not possible in this case to directly assign an object and an attribute of the directory DIR to this field F.
- any fields F m of a table configuration TB defined in the field configuration can be combined to form the table structure T necessary for read access by the telephone book application by means of an SQL query.
- a table 'subscriber' is shown as an example analogous to the table structure T described with reference to FIG.
- the table structure T for transfer to the telephone book application is defined by specifying the attribute assigned to the respective field name, the field type and the object class OC.
- FIG. 4 now shows a flowchart to illustrate the essential procedural steps involved in reading access to the directory DIR starting from the database application DB-A.
- the ODBC manager ODBC-M checks whether the addressed database in the directory is DIR. If this is not the case, the ODBC manager ODBC-M transmits an ODBC query corresponding to the SQL query received to an ODBC driver ODBC-Tl, ODBC-T2, ..., ODBC-Tn, which stores the data reads from the corresponding relational database DB1, DB2, ..., DBn and transfers it to the database application DB-A.
- the LDAP driver LDAP-T calls the additional function FindExtension stored in the extension unit KSE with the parameter
- InvTelNum 059132279894.
- the amount of data that can be read from the directory DIR can be easily added to the results of the additional function , e.g. the inverted telephone number InvTelNum can be expanded.
- a further advantage of the invention is that the additional functions which can be implemented in any programming language are based on modules of the ODBC and LDAP driver LDAB-T which are present as standard, so that the implementation effort for these additional functions, in contrast to the development of new additional modules for the LDAP Driver LDAP-T, is relatively low.
Abstract
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP00963866A EP1266306A2 (en) | 1999-08-04 | 2000-08-01 | Method and device for accessing a storage device with a directory structure |
JP2001516075A JP2003522352A (en) | 1999-08-04 | 2000-08-01 | Method and apparatus for memory access to a memory device having a directory structure |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE19936604A DE19936604C1 (en) | 1999-08-04 | 1999-08-04 | Memory access to memory device with directory structure |
DE19936604.7 | 1999-08-04 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2001011494A2 true WO2001011494A2 (en) | 2001-02-15 |
WO2001011494A3 WO2001011494A3 (en) | 2002-10-03 |
Family
ID=7917093
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/DE2000/002541 WO2001011494A2 (en) | 1999-08-04 | 2000-08-01 | Method and device for accessing a storage device with a directory structure |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP1266306A2 (en) |
JP (1) | JP2003522352A (en) |
DE (1) | DE19936604C1 (en) |
WO (1) | WO2001011494A2 (en) |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE19541315A1 (en) * | 1995-11-06 | 1996-10-02 | Siemens Ag | Telecommunication device with relational database |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6553368B2 (en) * | 1998-03-03 | 2003-04-22 | Sun Microsystems, Inc. | Network directory access mechanism |
-
1999
- 1999-08-04 DE DE19936604A patent/DE19936604C1/en not_active Expired - Fee Related
-
2000
- 2000-08-01 EP EP00963866A patent/EP1266306A2/en not_active Withdrawn
- 2000-08-01 WO PCT/DE2000/002541 patent/WO2001011494A2/en active Application Filing
- 2000-08-01 JP JP2001516075A patent/JP2003522352A/en not_active Withdrawn
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE19541315A1 (en) * | 1995-11-06 | 1996-10-02 | Siemens Ag | Telecommunication device with relational database |
Non-Patent Citations (2)
Title |
---|
"SUPPORTING LDAP MULTI-VALUE ATTRIBUTES WITH RELATIONAL TABLES" RESEARCH DISCLOSURE, KENNETH MASON PUBLICATIONS, HAMPSHIRE, GB, Bd. 121, Januar 1999 (1999-01), XP000828849 ISSN: 0374-4353 * |
OLSON, M., HOLLY, L., STRUTT, C.: "Integrating Multiple Directory Services" DIGITAL TECHNICAL JOURNAL, [Online] 31. Mai 1996 (1996-05-31), Seiten 1-14, XP002191163 Gefunden im Internet: <URL:http://research.compaq.com/wrl/DECarchives/DTJ/DTJL04/DTJL04.HTM> [gefunden am 2002-02-22] * |
Also Published As
Publication number | Publication date |
---|---|
WO2001011494A3 (en) | 2002-10-03 |
EP1266306A2 (en) | 2002-12-18 |
DE19936604C1 (en) | 2001-01-25 |
JP2003522352A (en) | 2003-07-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE69530595T2 (en) | SYSTEM AND METHOD FOR THE X.500 DATABASE STANDARD | |
DE69333960T2 (en) | Name resolution in a multi-system network | |
DE69916928T2 (en) | Access method and server for network directory | |
DE19747583B4 (en) | Communication system and method | |
DE602004005035T2 (en) | IMPROVING DATA BANKING CAPABILITY IN A DOMAIN NAME SYSTEM | |
DE60035432T2 (en) | SYSTEM FOR MANAGING THE RDBM FRAGMENTATION | |
DE69833026T2 (en) | METHOD AND SYSTEM FOR AUTOMATICALLY VERIFYING THE DELIVERY OF REMOTE CONTROL SERVICES | |
DE10162495A1 (en) | Extensible database | |
DE19928666A1 (en) | Mobile telephone has expanded telephone directory with directories stored in SIM card memory and in non-volatile memory, each with associated database(s) in non-volatile memory. | |
DE10018993B4 (en) | A database management device and a database record retrieval device, and methods for managing a database and retrieving a database record | |
CN106503040B (en) | It is applicable in the KV database and its creation method of SQL query method | |
DE19836064A1 (en) | Procedure for displaying data about target participants | |
EP1276056B1 (en) | Method for managing a Database | |
DE102010013753B4 (en) | Dial plan analysis and cleanup | |
WO2001011494A2 (en) | Method and device for accessing a storage device with a directory structure | |
WO1999011023A2 (en) | Method for determining the technical address of a communication partner and a telecommunication device | |
DE10059103B4 (en) | Unit for managing data stored in a data processing device | |
EP1052579A1 (en) | Method to manage bookmarks in an Internet Browser | |
EP1994734A1 (en) | Method for identifying spit or spam for voip | |
WO2009097887A2 (en) | Method for the automatic generation of address book entries | |
EP1248430B1 (en) | Method and device for generating filter masks for checking relevance of features | |
DE1487637B2 (en) | PROCEDURE AND ARRANGEMENT FOR SEARCHING FOR DIRECTIONS IN COUPLING PANELS CONSTRUCTED WITH SWITCHING MATRICES | |
EP1000497A1 (en) | Method for accessing a classified telephone directory, in a mobile telephone, through an interface for external control (remote-control interface), using one or several letters as search keys, and device for implementing said method | |
DE10151749B4 (en) | Web-based search engine for finding communication links | |
DE10017608B4 (en) | Method for performing operations in a database system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): JP US |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2000963866 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10049098 Country of ref document: US |
|
AK | Designated states |
Kind code of ref document: A3 Designated state(s): JP US |
|
AL | Designated countries for regional patents |
Kind code of ref document: A3 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE |
|
WWP | Wipo information: published in national office |
Ref document number: 2000963866 Country of ref document: EP |