KR100424557B1 - a Memory Resident LDAP System and a Management Method thereof - Google Patents

Abstract

The present invention provides a memory resident LDAP system in which a main memory resident Database Engine is located in the back-end of an LDAP server to perform fast information processing in a real-time system having no data locality. It is about an operation method. The system of the present invention receives and analyzes an LDAP message, requests a query, converts a query request from the LDAP server to receive the result of the query, constructs a response message, and sends the response message, and processes the query. An interface for converting a result and applying it to the LDAP server, and a memory-resident database engine for searching a database according to a query request authorized through the interface and then applying the processing result to the interface; The memory resident database engine includes: a backup database including a DN table having information about an entry and an entry table having objects; a memory database storing a DN table and an entry table of the backup database at system initialization; A query processor that receives a query request from the interface, searches the memory database to process the query request, and authorizes the processing result to the interface; and a DN table and an entry table of the backup database when the system is initialized. It includes a loader that loads a memory database, and a metadata initializer that initializes metadata at system initialization. The method of the present invention comprises the steps of: performing an initialization of an LDAP service by performing a connection with an LDAP server after loading a DN table and an entry table and initializing metadata in a memory resident database engine; Performing a query request after analyzing the received LDAP message in the LDAP server; Converting the query request into a query to be used by a memory resident database engine at an interface and transmitting the query request to the memory resident database engine; Searching the memory database by checking the query in the memory resident database engine; Converting, by the interface, a result of processing the query by a memory resident database engine into a result statement for use in an LDAP server; Collecting the resultant message from the LDAP server and configuring the resultant message as an LDAP response message.

Description

Memory Resident LDAP System and a Management Method

The present invention relates to a memory-resident LDAP system and its operation method, and in particular, by placing the main memory-resident database engine in the back-end of the LDAP server for fast information processing in a real-time system having no locality of data. A memory resident LDAP system and a method of operating the same.

In general, LDAP proposed by the Internet Engineering Task Force (IETF) is used to store user profiles, address books, and information for network and service policies in applications based on a wide range of communication networks.

In addition, LDAP provides heterogeneous management more easily than that provided in relational or object-oriented databases, and because of its hierarchical structure, it allows for fast retrieval, which allows LDAP to store and retrieve information across a wide range of networks. This protocol is widely used in application fields, especially on the Internet, it is growing rapidly and is recommended to be applied in various application fields.

1 is a diagram showing the configuration of a disk-based LDAP system.

As shown in FIG. 1, the structure of the conventional LDAP system includes a disk-based database engine 13 at the rear of the LDAP server 11. Disk) In order to reduce the high cost of input / output, the corresponding cache server (Cash) technology is used.

The reason why the LDAP system is configured in the above-described manner is that a relatively slow search such as an Internet service or a locality of data is ensured, so that a system with a high hit ratio may benefit from the cache technology used by the corresponding LDAP server 11. It is because it can save enough and is suitable.

The basic operation of the conventional LDAP system having the configuration as described above is as follows. That is, the general processing operation after receiving the LDAP message will be described.

There are LDAP operations such as bind and search, which are data read operations, and add, delete, and modify, which are data write operations.

First, the LDAP server 11 checks whether an LDAP message is received. When receiving the LDAP message, the LDAP server 11 analyzes the received LDAP message to detect a message error and analyzes the message requirement.

Thereafter, the request data is searched and collected according to the analysis result of the received LDAP message, the collected data is configured as an LDAP message, and then the configured LDAP message is transmitted to the client.

2 is a flowchart illustrating a data retrieval process that is performed when a disk-based database engine 13 is used.

As shown in FIG. 2, first, in the read operation, the LDAP server 11 checks the cache and searches for the existence of the first cached data (step T1). In this case, the cache is performed in the first step T1. If there is no data, the database engine 13 asks the data on the hard disk (step T2).

At this time, the data in the hard disk is registered in the cache according to the cache policy of the LDAP server 11, for example, LRU (Least Recently Used) and the like, so that it can be used for a later search (step T3). ). Accordingly, the data registered in the third step T3 is returned as a result of the database (step T4).

On the other hand, if there is data cached in the first step (T1), the LDAP server 11 transmits the cached data without access to the hard disk (step T5).

Next, referring to the write operation, the LDAP server 11 checks the cache in the same manner as the read operation described above, and changes or deletes the cache when the first cached data exists, and the database engine 13 The data write operation is performed on the hard disk.

However, in a system that needs to provide services in real time while having a low data hit rate, such as an exchange service, there is a drawback in that the system cannot provide the services required by the cache technology.

In other words, the conventional LDAP system based on disk has a high disk access cost, which is not suitable for real-time systems such as switching systems.

The present invention relates to retrieving and collecting data by implementing a memory resident LDAP system in order to solve the problems described above. The main memory resident database engine is located at the rear of the LDAP server so that the data does not have locality. It is an object of the present invention to provide a memory-resident LDAP system and its operation method capable of performing fast information processing in a real-time system.

In addition, the present invention is equipped with a memory-resident database engine on the back of the LDAP server implemented on the LDAP to make the data processing speed suitable for the real-time system, thereby improving the performance of the LDAP server and provide real-time services to standardize It is to provide a fast information service, which has a purpose.

In addition, the present invention places the interface between the memory-resident database engine and the LDAP server to convert the heterogeneous message structure between the memory-resident database engine and the LDAP server, perform a query conversion operation to query the LDAP server In addition to enabling the to be used in the memory-resident database engine, the purpose of the query processing is to make the query results available to the LDAP server.

In addition, an object of the present invention is to construct a DN (Distinguished Name) table structure in a database so as to perform an information structure conversion between a memory-resident database engine that is a relational database and an LDAP protocol.

1 is a view for explaining the structure of a conventional Lightweight Directory Access Protocol (LDAP) system.

2 is a flow diagram illustrating data access for a conventional LDAP scheme.

3 is a block diagram illustrating a structure of a memory resident LDAP system according to an embodiment of the present invention.

FIG. 4 is a diagram schematically illustrating a configuration of a memory resident database engine in FIG. 3. FIG.

FIG. 5 is a diagram showing a DN table structure of a database and a relationship between a DIT and an entry table in FIG. 4; FIG.

6 is a flowchart illustrating a method of operating a memory resident LDAP system according to an exemplary embodiment of the present invention.

FIG. 7 is a diagram illustrating an example of a query transformation structure in FIG. 6. FIG.

Explanation of symbols on the main parts of the drawings

20: LDAP Server 30: Interface

40: memory-resident database engine

41: Query Processor

42: Initial Processor

43: Loader

44: Meta-data Initial Part

45: Memory Database

46: backup database

Memory resident LDAP system according to an embodiment of the present invention for achieving the object as described above, to request the query after receiving and analyzing the LDAP message, receiving the result of the query to form a response message and transmits The LDAP server converts a query request of the LDAP server, converts a query processing result to the LDAP server, and searches a database according to a query request authorized through the interface. A memory resident database engine for applying to the interface; The memory resident database engine includes: a backup database including a DN table having information about an entry and an entry table having objects; a memory database storing a DN table and an entry table of the backup database at system initialization; A query processor that receives a query request from the interface, searches the memory database to process the query request, and authorizes the processing result to the interface; and a DN table and an entry table of the backup database when the system is initialized. And a metadata initializer that initializes metadata at system initialization.

On the other hand, the operating method of the memory-resident LDAP system according to an embodiment of the present invention for achieving the above object, after the loading of the DN table and the entry table and initialization of the metadata in the memory-resident database engine Performing an initialization of an LDAP service by performing a connection with an LDAP server; Performing a query request after analyzing the received LDAP message in the LDAP server; Converting the query request into a query to be used by a memory resident database engine at an interface and transmitting the query request to the memory resident database engine; Searching the memory database by checking the query in the memory resident database engine; Converting, by the interface, a result of processing the query by a memory resident database engine into a result statement for use in an LDAP server; Collecting the resultant message from the LDAP server and configuring the resultant message as an LDAP response message.

Preferably, the memory database retrieval process includes a data retrieval range of the base object, the single level, and the entire subtree.

Also, preferably, the memory resident database engine performs error processing by checking that there is an entry for the DN, inserts an object into the corresponding entry table by checking that there is no entry for the DN, and registers the DN in the DN table. It is characterized in that it further comprises the process of performing the add operation to configure a new entry. Alternatively, the memory resident database engine may further include performing a deliberate operation of confirming that there is an entry for the DN, deleting the object from the entry table, and deleting the entry for the DN in the DN table. It features. In addition, the memory-resident database engine, characterized in that further comprises the step of performing a modifier operation to check that there is an entry for the DN, search for the object using the entry and change the content of the object; do.

Real-time systems do not use a database that uses a hard disk, but many memory-resident databases are used due to a decrease in hardware prices, design convenience, and speed. In the present invention, an LDAP directory information tree (DIT) and database elements are used. Implement an LDAP system that resides in main memory. Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

As shown in FIG. 3, a memory resident LDAP system according to an embodiment of the present invention includes an LDAP server 20, an interface 30, and a memory resident database engine 40. The resident database engine 40 is mounted on the rear of the LDAP server 20.

After receiving and analyzing the LDAP message, the LDAP server 20 applies the query request to the interface 30, receives the query result from the interface 30, forms an LDAP response message, and transmits the result to the client.

The interface 30 converts a query request from the LDAP server 20 into a query that can be used by the memory resident database engine 40, and the query statement from the memory resident database engine 40. After receiving the processing result, the query result conversion operation is transmitted so that the query result can be used in the LDAP server 20.

The memory resident database engine 40 is a relational database. As shown in FIG. 4, the query processor 41, the initialization processor 42, the loader 43, the metadata initializer 44, And a memory database 45 and a backup database 46. The query processor 41 receives a query from the interface 30, searches the memory database 45 to process the query, and applies the processing result to the interface 30. The initialization processor 42 controls the operations of the loader 43 and the metadata initializer 44. The loader 43 loads the DN table and the entry tables of the backup database 46 in the memory database 45 at system initialization. The metadata initializer 44 initializes metadata at system initialization. The database 45, 46 comprises a DN table having information on an entry and an entry table having objects. The DN table is formed by representing DIT information in a table form.

FIG. 5 is a diagram illustrating the structure of the DN table and a relationship between a DIT and an entry table representing an object. As shown in FIG. 5, in the structure of the DN table, entries of the same layer are linked by a colliegue to search for a lower entry, and a child indicates a lower entry. Or, it indicates that the entry is an end, parent refers to the parent entry, entry table (entryTable) and entry index (entryIndex) is a pointer to the object as the table and index where the actual object is represented.

A method of operating a memory resident LDAP system according to an exemplary embodiment of the present invention will be described with reference to the flowchart of FIG. 6.

First, at the initial start-up of the system, an initialization operation is performed (step S1), and the memory-resident database engine 40 located at the rear side has a DN table in a file in an internal backup database 46 at an internal loader 43. And entry tables are loaded into the internal memory database 45, and the internal metadata initializer 44 initializes the metadata. Next, the connection with the LDAP server 20 is performed to complete an initialization operation for the LDAP service with connection completion (ConnectReq).

Therefore, after completing the initialization operation of the first step (S1), the LDAP server 20 maintains the message reception waiting state to confirm whether the LDAP message is received (step S2), and then the corresponding LDAP message Upon receipt, the received LDAP message is analyzed to detect the message error and to analyze the message requirements including the data retrieval range (step S3).

When the analysis of the received LDAP message is completed, the LDAP server 20 performs a query request to the memory resident database engine 40 to check and collect necessary data as a result of the analysis (step S4). In this case, the query request is made through the interface 30.

That is, the interface 30 converts and authorizes a query request from the LDAP server 20 into a query statement that can be used by the memory resident database engine 40 while performing a query conversion operation (step S5). ). Here, the query is transformed into the structure shown as an example as shown in FIG. 7, but it should be understood that the query can be applied differently according to the shape of the memory-resident database engine 40 in the present invention. do.

Accordingly, the memory resident database engine 40 checks the query from the interface 30 in the internal query processor 41, searches the database 45 resident in memory, and processes the query. (Step S6), and then the processing result is applied to the interface 30.

Then, the interface 30 receives a query processing result from the memory resident database engine 40 and performs a query result conversion operation to convert the result into a result statement that can be used by the LDAP server 20 and transmits the result. (Step S7).

Accordingly, the LDAP server 20 receives the query result from the interface 30, thereby completing the operation of searching for and collecting necessary data as a result of analyzing the received LDAP message (step S8). After the configured data is composed of the LDAP response message (step S9), the configured LDAP response message is transmitted to the client, and the operation of the second step (S2) is repeated by maintaining the first message reception state. To perform (step S10).

And performing a third step (S3) of analyzing the received LDAP message, searching and collecting the necessary data (S4 to S8), and constructing and transmitting the LDAP response message (S9 and S10). In the second step (S2), the LDAP server 20 detects whether an error has occurred in each step, checks and processes the error when the error is detected, and maintains a message reception waiting state which is the first state. Perform the operation again.

In the step of searching and collecting data by requesting the query (S4 to S8), the LDAP server 20 obtains an entry which is an information unit for an object using a DN as a key value, and the entry is the database 45. , 46), which is represented as a DN table, and the scope of the data retrieval is specified in three forms: baseObject, singleLevel, and wholeSubtree.

Here, the baseObject specifier searches only the objects whose DNs match exactly, and retrieves the entries from the DN table, and retrieves the entry table information and the entry index information from the attribute values of the imported entries. To find the object.

In addition, the single-level designator extends up to one level lower entry in the DN, and searches for the lower entry using the children information of the corresponding entry in the DN table. Use colleague) information to search for entries of the same level.

In addition, the wholeSubtree specifier looks for entries the same as the corresponding SignalLevel specifier, and searches for subentries until there are no children and no colleagues.

Meanwhile, add, delete and modify operations, which are data write operations of the LDAP server 20, are performed in the same manner as a base object of the search operation.

First, the add operation performs error processing when there is an entry for the DN. If there is no entry for the DN, the add operation inserts an object into the corresponding entry table and registers the DN in the DN table to configure a new entry.

Second, the delete operation deletes an object from the entry table and deletes an entry for the DN in the DN table when there is an entry for the DN.

Third, if there is an entry for the DN, the modifier uses that entry to search for the object and change its contents.

On the other hand, in a system such as SCP (Service Control Point) having a subscriber profile or the like, the SDF (Service Data Function) is a functional entity that includes customer data and network data used by the Service Control Function (SCF), It is one of the functional entities that interacts with the SCF to control and is important for the control operation of the service managed by the SMF. When the SCF is applied to the LDAP system according to an embodiment of the present invention, the standardized fast Information services can be provided.

As described above, the present invention converts a heterogeneous message structure by placing an interface between the memory resident database engine and the LDAP server, and mounts the memory resident database engine on the back of the LDAP server to have no locality of data. It is possible to improve the performance of the LDAP server and to provide a standardized fast information service by providing a real time service.

Claims (6)

An LDAP server that receives and analyzes an LDAP message and requests a query, receives the results of the query, constructs a response message, and sends it; An interface for converting a query request of the LDAP server, converting a query processing result, and applying the result to the LDAP server; A memory resident database engine for retrieving a database according to a query request authorized through the interface and then applying the processing result to the interface; The memory resident database engine includes a backup database including a DN table having information about an entry and an entry table having objects; A memory database for storing a DN table and an entry table of the backup database at system initialization; A query processor that receives a query request from the interface, searches the memory database to process the query request, and then authorizes the processing result to the interface; A loader which loads the DN table and the entry table of the backup database into the memory database during system initialization; A memory resident LCD system comprising a metadata initializer for initializing the metadata at system initialization. delete Performing an initialization of the LDAP service by performing a connection with the LDAP server after loading the DN table and the entry table and initializing the metadata in the memory resident database engine; Performing a query request after analyzing the received LDAP message in the LDAP server; Converting the query request into a query to be used by a memory resident database engine at an interface and transmitting the query request to the memory resident database engine; Searching the memory database by checking the query in the memory resident database engine; Converting, by the interface, a result of processing the query by a memory resident database engine into a result statement for use in an LDAP server; Collecting the resultant message from the LDAP server and constructing an LDAP response message and transmitting the resultant message to a client. The method of claim 3, In the memory resident database engine, it checks that there is an entry for the DN, performs error processing, confirms that there is no entry for the DN, inserts an object into the corresponding entry table, and registers a DN in the DN table to form a new entry. Operating method of a memory resident RFID system characterized in that it further comprises the process of performing the add operation. The method of claim 3, The memory resident database engine further includes a process of performing a delete operation for confirming that there is an entry for the DN, deleting the object from the corresponding entry table, and deleting the entry for the corresponding DN in the DN table. Operation method of memory resident LDP system. The method of claim 3, In the memory resident database engine, the memory resident type further comprises a process of performing a modifi operation of searching for an object using the entry and changing the contents of the object by checking that there is an entry for the DN. How to operate LDP system.