JP5430301B2 - Communication device management system and database access processing method - Google Patents

Description

  The present invention relates to a communication device management system that performs parallel processing on a configuration management database.

  Conventionally, with respect to a communication device management system (EMS), multiple configuration management database (CMDB) update / reference processing requests (hereinafter referred to as CMDB processing requests) that occur asynchronously are efficiently performed. In order to distribute the load dynamically, a database access processing application process group started for each queue is registered in each queue and distributed randomly to multiple queues for each transaction that is a series of multiple record accesses. Are taken out one by one in order, and CMDB access processing is performed.

  When CMDB processing requests are allocated to each queue in units of transactions, a plurality of transactions including processing requests for the same record are distributed to different queues, so contention for the same record occurs. Also, if the record update / reference order in each transaction is different, a deadlock occurs depending on the execution order. Therefore, it is necessary to periodically monitor the deadlock state, and when a deadlock occurs, it is necessary to reset the CMDB processing request by the transaction causing the deadlock and reissue the CMDB processing request. A process for monitoring the deadlock state is periodically started, and when the deadlock occurs, the processing load becomes high, resulting in problems such as deterioration in response performance.

  As a solution to such a problem, there is a method of unifying the CMDB processing queue. In order to avoid contention and deadlock between multiple CMDB processing requests that occur asynchronously with respect to EMS, CMDB processing requests are centrally aggregated in a single queue (queue) and registered in the order registered from the top. To process. However, in the single queue method, when a large amount of CMDB processing requests are generated and the load increases, it is difficult to realize the original purpose of load distribution by parallel processing.

  Therefore, a method of allocating to the queue for each CMDB processing request for the same record is conceivable. For example, a hash function is used for the record key on the database targeted by the CMDB processing request. Specifically, techniques for applying a hash function in processing of an update / reference request to a database are disclosed in the following Patent Documents 1 to 4.

JP-A-5-046454 JP-A-5-298366 JP 2000-187668 A JP 2000-250927 A

  However, according to the above-described conventional technique, a hash function is used for the purpose of post-registration processing such as distribution and averaging of record states after registration, smoothing of access frequency, and quickness of search. For this reason, when a large number of CMDB processing requests for record update processing occur, the update targets compete with each other, and there is a problem that the processing load cannot be reduced even if parallel processing is executed.

  The present invention has been made in view of the above, and an object of the present invention is to provide a communication device management system that can reduce processing load while avoiding record competition and deadlock.

  In order to solve the above-described problems and achieve the object, the present invention includes a configuration management database, and based on an access request that is a data update or data reference processing request from another device, In a communication device management system that performs access processing, when a hash function that obtains the same hash calculation value is applied to an access request that accesses the same record of the same table, access from another device The request is received, hash calculation is performed based on the table identifier and the record identifier that specify the access destination of the configuration management database described in the access request, and the distribution destination of the received access request is based on the hash calculation value It has a distribution processing means for determining and a plurality of queues and hashes Storage means for storing the same hash calculation value access request in the same queue for each arithmetic value, and database processing means for retrieving the stored access request for each queue and performing access processing to the configuration management database; It is characterized by providing.

  According to the present invention, it is possible to reduce the processing load while avoiding record competition and deadlock.

FIG. 1 is a diagram illustrating a configuration example of a communication device management system. FIG. 2 is a flowchart showing the configuration management DB update process. FIG. 3 is a diagram illustrating a configuration example of a communication device management system. FIG. 4 is a diagram illustrating a configuration example of a communication device management system. FIG. 5 is a flowchart showing the configuration management DB update process. FIG. 6 is a diagram illustrating a connection example of the communication device management system.

  Embodiments of a communication device management system according to the present invention will be described below in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

Embodiment 1 FIG.
FIG. 1 is a diagram illustrating a configuration example of a communication device management system (EMS: Element Management System). The communication device management system 1 processes a plurality of CMDB (Configuration Management Database) processing requests that occur at the same time in parallel while preventing contention. The CMDB process request is a message for requesting an update / reference process for the configuration management database (CMDB) included in the communication device management system 1. Here, it is assumed that the transaction unit is a simple system in which update / reference is performed in units of one record. It is assumed that the upper management application apparatus 2, the EMS user terminal 3, and the managed communication apparatus 4 are apparatuses that transmit the CMDB processing request.

  The communication device management system 1 includes a distribution processing unit 10, database (DB) processing request queues 11 to 13, database (DB) processing units 14 to 16, and a configuration management database (DB) 17. The distribution processing unit 10 calculates a hash function in response to a CMDB processing request from the upper management application apparatus 2 or the like, and performs a distribution process based on the calculation result. The DB process request queues 11 to 13 register the distributed CMDB process requests. The DB processing units 14 to 16 take out the CMDB processing request registered in each DB processing request queue, execute the application in parallel, and access the configuration management DB 17. The configuration management DB 17 is a database that manages information about the system.

  The configuration management DB 17 includes tables 18 and 19. Tables 18 and 19 are relational database tables registered on the database. Records 181, 182, and 183 indicate records registered in the table 18, and records 191, 192, and 193 indicate records registered in the table 19.

  Next, the operation of the communication device management system 1 will be described. FIG. 2 is a flowchart showing an update process of the configuration management DB 17 in the communication device management system. First, a plurality of CMDB processing requests are generated asynchronously in the upper management application device 2, the EMS user terminal 3, and the managed communication device 4. Here, each device transmits a CMDB processing request in the order of the upper management application device 2, the EMS user terminal 3, and the managed communication device 4. The CMDB processing request from the upper management application device 2 and the EMS user terminal 3 is a record update request for the record 181 in the table 18, and the CMDB processing request from the managed communication device 4 is a record update request for the record 192 in the table 19. To do.

  In the communication device management system 1, the distribution processing unit 10 receives a CMDB processing request transmitted from each device (step S1). The distribution processing unit 10 executes a calculation process using a hash function based on the table identifier and record identifier of the DB process target given to the CMDB process request (step S2), and accepts the CMDB process received based on the calculation result. The request is registered in each DB processing request queue (step S3). The table identifier is a table number assigned to each table by a serial number, and the record identifier is defined as a record key number. The value of the hash function calculation result is set so as to uniquely correspond to the access request queue number based on the input value.

Here, since there are three DB processing request queues, a remainder obtained by dividing the sum of the table number and the record key by 3 is set as a hash calculation result value. Specifically, it is defined as the following formula (1).
Hash function F (x, y, z) = MOD (x + y, z) (1)
(X = table number, y = record key number, z = DB processing request queue number)
In this embodiment, z = 3. That is, the distribution processing unit 10 stores the DB processing request queue 11 when the hash value is 2, the DB processing request queue 12 when the hash value is 1, and the DB processing request queue 13 when the hash value is 0. Allocate to process request queue.

  In order to simplify the calculation, the table number of the table 18 is 1, the record key numbers of the records 181 to 183 are 1 to 3, the table number of the table 19 is 2, and the record key numbers of the records 191 to 193 are 1 to 3. To do. When the above formula (1) is applied, the hash value for the CMDB processing request from the upper management application device 2 and the EMS user terminal 3 is a remainder obtained by dividing the numerical value of (table number 1 + record key number 1) = 2 by 3. Calculation result 2 is obtained. The distribution processing unit 10 registers in the DB processing request queue 11 because both cases have the hash value 2. Similarly, the hash value for the CMDB processing request from the managed communication device 4 obtains the calculation result 1 as a remainder obtained by dividing (table number 2 + record key number 2) = 4 by 3. The distribution processing unit 10 registers the hash value 1 in the DB processing request queue 12.

  The DB processing units 14 to 16 sequentially retrieve CMDB processing requests registered in each DB processing request queue (step S4), and execute CMDB update / reference processing on the configuration management DB 17 (step S5). Here, the DB processing unit 14 takes out two CMDB processing requests from the DB processing request queue 11 and executes them in order from the upper management application device 2 and the EMS user terminal 3, and records 181 in the table 18 are set to “10”. , “20” are sequentially rewritten. Further, the DB processing unit 15 retrieves and executes the CMDB processing request from the DB processing request queue 12 and rewrites the record 192 of the table 19 to “30”.

  As described above, since the records to be updated by each DB processing unit do not compete with other DB processing units, each DB processing unit can perform parallel processing of record update on the configuration management DB 17.

  As described above, according to the present embodiment, when single record processing is performed in units of a single transaction, the calculation by the hash function is performed on the CMDB processing request received by the distribution processing unit, and the same After allocating CMDB processing requests for the same record in the table to the same DB processing request queue, the DB processing unit corresponding to each DB processing request queue performs update processing of the configuration management DB. As a result, the same record is not updated / referenced simultaneously by a plurality of DB processing units, and no conflict occurs. In addition, there is no time-series inversion in response to an update / reference request for the same record, and parallel processing can be performed efficiently while maintaining time-series characteristics.

  In addition, for three parallel processes, three DB processing request queues, three DB processing units are prepared, and the hash function is divided by 3, so that three numerical values from 0 to 2 can be calculated. However, it is possible to flexibly change the degree of parallelism by setting the degree of parallel processing to the divisor value of equation (1) according to the load. For example, when the degree of parallelism is to be increased to 4, by changing the divisor used in the hash calculation formula of Formula (1) to 4, the calculation result of the hash calculation formula can be obtained as a range of queue numbers to be distributed in parallel. It can be applied to a range of 0-3. The linkage between the table identifier and the record identifier is the sum of the table number and the record number. However, any linkage may be used as long as each link calculation value can be uniquely identified. For example, the table name and the record key value may be numerical values, and the mutual linkage does not need to be summation, and in any of the linkage calculations using two numbers such as multiplication, division, and exponent calculation, Similar effects can be obtained.

Embodiment 2. FIG.
In this embodiment, a system for avoiding deadlock when a transaction is a group of update / reference processes for a plurality of records will be described. A different part from Embodiment 1 is demonstrated.

  In the present embodiment, the CMDB processing request from the EMS user terminal 3 or the like is a transaction unit, and the transaction is a group of update / reference processing of a plurality of records, and permits the intervention of other target record update / reference. A series of processing is not performed. The transaction can be decomposed into CMDB processing requests for a plurality of different record processing units in the distribution processing unit of the communication device management system. Each transaction is assigned a transaction number (denoted as TR-1, TR-2,...), And the decomposed CMDB processing request includes the transaction number to which the transaction belongs. It can be read by the DB processing unit.

  First, a process in which deadlock occurs in the prior art will be described. FIG. 3 is a diagram illustrating a configuration example of a communication device management system. The communication device management system 1a includes a distribution processing unit 10a, DB processing request queues 11a and 12a, DB processing units 14a and 15a, and a configuration management DB 17. The distribution processing unit 10a performs distribution processing for each transaction from the EMS user terminal 3 or the like. The DB processing request queues 11a and 12a register distributed transactions. The DB processing request queue 11a registers the transaction TR-1 from the EMS user terminal 3. In addition, the DB processing request queue 12a registers the transaction TR-2 from the managed communication device 4. The DB processing units 14a and 15a take out the transaction registered in each DB processing request queue, execute the application based on the CMDB processing request included in the transaction in parallel, and access the configuration management DB 17.

  Here, the transaction TR-1 is based on two CMDB processing requests: (1) a request to lock and update the record 181 of the table 18, and (3) a request to lock and update the record 191 of the table 19. Composed. The transaction TR-2 is composed of two CMDB processing requests: (2) a request to lock and update the record 191 in the table 19 and (4) a request to lock and update the record 181 in the table 18. Is done. That is, the two transactions TR-1 and TR-2 are transactions in which the same two records are updated, but the update order is reversed in both. As the processing order, since the DB processing units 14a and 15a process requests in the respective DB processing request queues in parallel, the requests are registered in the respective DB processing request queues and processed asynchronously. Here, it is assumed that (1), (2), (3), and (4) are executed in this order.

  Next, the operation of the communication device management system 1a will be described. First, the EMS user terminal 3 and the managed communication device 4 transmit individual CMDB processing requests for the transactions TR-1 and TR-2, respectively. Transaction TR-1 can be broken down into two CMDB processing requests: (1) update of record 181 of table 18 and (3) update of record 191 of table 19. Transaction TR-2 can also be broken down into two CMDB processing requests: (2) update of record 191 in table 19 and (4) update of record 181 in table 18.

  Conventionally, since the transaction processing unit 10a has registered in the DB processing request queue for each transaction, the distribution processing unit 10a collectively combines the CMDB processing requests (1) and (3) belonging to the same transaction TR-1 into the DB processing request queue 11a. Sort and register. Similarly, the distribution processing unit 10a distributes and registers the CMDB processing requests (2) and (4) belonging to the same transaction TR-2 in the DB processing request queue 12a.

  The DB processing units 14a and 15a take out CMDB processing requests registered in the CMDB processing request queues 11a and 12a, respectively, and update the configuration management DB 17 asynchronously and independently. As described above, (1), (2), (3), and (4) are taken out and executed in this order.

  As a result, first, the DB processing unit 14a locks the record 181 of the table 18 by the update process based on the top (1) CMDB process request, and updates this record. When a record is locked, it becomes impossible to refer to or update the target record from another DB processing unit. Other DB processing units that update / reference the locked record are put in a wait state until the previously locked DB processing unit releases the lock. When the entire transaction process including the process for locking is completed and the record is unlocked, the wait state generated by the lock is released and the record can be updated / referenced.

  Here, by executing (1), the record 181 of the table 18 is locked. Next, the DB processing unit 15a is in a state where the record 191 of the table 19 is locked by the update processing based on the CMDB processing request of (2). Further, the DB processing unit 14a attempts to update the record 191 of the table 19 by the update process based on the CMDB process request (3). However, since the record lock is already applied during the update process (2), the process (3) of the transaction TR-1 is in a waiting state. Further, the DB processing unit 14b attempts to update the record 181 of the table 18 by the update process based on the CMDB process request (4). In this case as well, since the record lock is applied during the update process (1), the process (4) of the transaction TR-2 is in a waiting state.

  As described above, since the locks are applied to each other, the transactions TR-1 and TR-2 are both in a waiting state. If the transaction is not unlocked from the other DB processing unit, the transaction cannot proceed. However, since the lock cannot be released in a stopped state, a so-called deadlock state in which a permanent waiting state continues. A common way to eliminate deadlocks is to periodically start a process that monitors the deadlock state to monitor for deadlocks and cancel both or one of the transactions when a deadlock occurs. It is. The same operation is executed again for the canceled transaction.

  When a deadlock occurs, a delay or permanent stop of DB processing occurs. In addition, when a deadlock is detected, a method is generally employed in which one or both of the transaction processes are once deleted by a deadlock monitoring process and the transaction is started again from the beginning. When such processing is performed, the response performance is greatly deteriorated due to an increase in system load, deadlock detection, and re-execution of processing at the time of deadlock.

  Next, processing for avoiding deadlock will be described. FIG. 4 is a diagram illustrating a configuration example of a communication device management system. The communication device management system 1b includes a distribution processing unit 10b, DB processing request queues 11b and 12b, DB processing units 14b and 15b, a configuration management DB 17, and a current transaction list 100. For the transaction from the EMS user terminal 3 or the like, the distribution processing unit 10b calculates a hash function for a CMDB processing request for each record processing unit included in the transaction, and performs a distribution process. The DB processing request queues 11b and 12b register the distributed CMDB processing requests. The DB processing request queue 11b registers a CMDB processing request for updating the record 181 of the table 18. The DB processing request queue 12b registers a CMDB processing request for updating the record 191 of the table 19. The DB processing units 14b and 15b take out the CMDB processing request registered in each DB processing request queue, execute the application in parallel, and access the configuration management DB 17. Also, the CMDB processing requests registered in each DB processing request queue are rearranged. The current transaction list 100 is a current transaction priority table that manages transaction numbers that determine the order in each DB processing request queue.

  Here, the distribution processing unit 10b performs a hash function calculation based on the table number and the record key number for the CMDB processing request in the record processing unit included in the transaction, not in the transaction unit, and generates the hash function value. Based on this, it is divided into record processing units, distributed to each DB processing request queue, and registered. Specifically, the update request for the record 181 in the (1) table 18 of the transaction TR-1 and the update request for the record 181 in the (4) table 18 of the transaction TR-2 are registered in the DB processing request queue 11b. . In the DB processing request queue 12b, the update request for the record 191 in the (3) table 19 of the transaction TR-1 and the update request for the record 191 in the (2) table 19 of the transaction TR-2 are registered.

  Next, the operation of the communication device management system 1b will be described. FIG. 5 is a flowchart showing an update process of the configuration management DB 17 in the communication device management system. First, the EMS user terminal 3 and the managed communication device 4 transmit individual CMDB processing requests for the transactions TR-1 and TR-2, respectively. The contents of the record update included in each are the same as those when a deadlock occurs in FIG.

  Here, each device that transmits a CMDB processing request determines a unique transaction ID (TR-ID) for each transaction, and assigns this TR-ID to all CMDB processing requests of the same transaction. Furthermore, a transaction start mark (StartTR) is assigned to the first CMDB processing request of a transaction, and a transaction end mark (EndTR) is assigned to the last CMDB processing request.

  In the communication device management system 1b, the distribution processing unit 10b accepts a transaction transmitted from each device (step S11), and decomposes the received transactions TR-1 and TR-2 into CMDB processing requests in record processing units ( Step S12). The distribution processing unit 10b executes a calculation process using a hash function based on the table identifier and record identifier of the DB processing target given to the CMDB processing request for the CMDB processing request in the disassembled record processing unit (step S13). Based on the calculation result, the CMDB processing request is registered in each DB processing request queue (step S14).

  The calculation method using the hash function is the same as in the first embodiment. That is, CMDB processing requests for the same record in the same table are distributed and registered in the same DB processing request queue. Specifically, the distribution processing unit 10b registers (1) of the transaction TR-1 and (4) of the transaction TR-2, which are processing requests for the record 181 of the table 18, in the DB processing request queue 11b. Further, the distribution processing unit 10b registers (3) of the transaction TR-1 and (2) of the transaction TR-2, which are processing requests for the record 191 of the table 19, in the DB processing request queue 12b.

  At this time, the distribution processing unit 10b registers the current transaction list 100 as a currently executing transaction in the order of receiving the transactions TR-1 and TR-2. Since the transaction priority is in the registration order of the current transaction list 100, the transaction TR-1 has a higher priority than the transaction TR-2.

  Next, when executing the CMDB processing request, each DB processing unit rearranges the CMDB processing requests in each DB processing request queue based on the registration order (priority order) of the current transaction list 100 (step S15). As a rearrangement method, for example, a CMDB processing request assigned with the same TR-ID as the TR-ID having the highest priority is extracted, and all the TR-IDs assigned with the TR-ID in each BD processing request queue are extracted. The CMDB processing requests are collected and rearranged in each DB processing request queue according to the priority order of TR-IDs. At this time, the CMDB processing requests to which the same TR-IDs as the TR-IDs of the second and subsequent priorities are assigned may be rearranged. Note that the rearrangement method is not limited to this.

  Further, as the timing of rearrangement, for example, when a CMDB processing request with an EndTR mark is processed in any DB processing unit, processing for deleting the TR-ID from the current transaction list 100 is performed. It is good. Note that the rearrangement timing is not limited to this.

  Specifically, the DB processing unit 14b sorts the CMDB processing requests belonging to the transaction TR-1 with priority. As a result, in the DB processing request queue 11b, (1) of the transaction TR-1 is registered at the head, and then re-registered so that (4) of the transaction TR-2 is located. Similarly, the DB processing unit 15b registers (3) of the transaction TR-1 at the top in the DB processing request queue 12b, and then re-registers it so that (2) of the transaction TR-2 is located.

  The DB processing units 14b and 15b take out the CMDB processing request registered in each DB processing request queue (Step S16), and execute the CMDB update / reference processing for the configuration management DB 17 (Step S17). The process for the configuration management DB 17 is the same as described above.

  When any of the DB processing units retrieves a CMDB processing request to which an EndTR mark is added, it is confirmed whether or not a CMDB processing request with the same TR-ID remains in another DB processing request queue. If it remains, the CMDB processing request with the EndTR mark is not processed. If not, after processing the extracted CMDB processing request, the TR-ID is deleted from the current transaction list 100.

  In this way, each DB processing unit rearranges the CMDB processing requests registered in each DB processing request queue in the registration order of the current transaction list 100. As a result, the CMDB processing requests for each record in the priority order of transactions. Is executed, so no deadlock occurs. Each DB processing unit rearranges the CMDB processing requests registered in each DB processing request queue, but may be performed when the distribution processing unit 10b registers in each DB processing request queue.

  In the present embodiment, the priority order of transactions is the order received by the distribution processing unit 10b, but the present invention is not limited to this. For example, each DB processing unit may record the transaction start time in the current transaction list 100 so that the earlier the transaction start timing, the higher the priority. The same effect can be expected even when the transaction priority is determined by other rules, such as when the user explicitly sets the priority when a CMDB process is requested.

  For example, in the case of increasing the priority of a transaction with an early start timing, any DB processing unit that has fetched a CMDB processing request to which StartTR has been assigned obtains the TR-ID of the transaction to which the StartTR has been assigned as the current transaction list. Record 100. Thereafter, each DB process extracts the CMDB request to which the TR-ID is assigned from each DB process request queue, and performs rearrangement based on the priority order in each DB process request queue. The CMDB processing request for which the waiting flag is set is reset. The wait flag is not subject to processing by the DB processing unit that has taken out a CMDB processing request that is not in the current transaction list 100, in response to the CMDB processing request. When determining the transaction priority in the order of reception, the TR-ID assigned to the CMDB processing request registered in each DB processing request queue is always registered in the current transaction list 100. Therefore, it is possible to rearrange based on the current transaction list 100, and there is no need for a waiting flag.

  As described above, according to the present embodiment, when a transaction is a group of update / reference processing of a plurality of records, the distribution processing unit decomposes the received transaction into CMDB processing requests in units of record processing. Then, the calculation by the hash function is executed, and the DB processing unit rearranges the CMDB processing requests registered in the DB processing request queue based on the transaction priority. Thereby, in addition to the effects of the first embodiment, deadlock can be prevented and the load of the entire system can be reduced.

  In the description so far, it is assumed that the upper management application apparatus and the like all transmit the CMDB processing request to the communication apparatus management system through a common interface. However, it may be difficult to collectively change all the CMDB processing request side interfaces. As described above, even when there is a CMDB processing request source that is not common, parallel processing can be performed by using a gateway or the like that converts the message format to the common format.

  FIG. 6 is a diagram illustrating a connection example with a communication device management system in which a conversion gateway is arranged. For example, the CMDB processing request in a unique message format that cannot communicate with the communication device management system 1 is transmitted from the management target communication device 4. In such a case, the conversion gateway 5 that converts a message in a unique format into a message in a common format is used.

  The conversion gateway 5 converts the CMDB processing request in the unique message format input from the managed communication device 4 into a CMDB processing request in a common message format that can be received by the communication device management system 1 and outputs the CMDB processing request. The communication device management system 1 can accept the CMDB processing request by receiving the CMDB processing request in the converted common message format.

  As described above, even when the CMDB processing request message is not common, the conversion gateway 5 converts the different message format into the common request message format and transmits it to the communication device management system, so that CMDB processing requests of different message formats can be obtained. The processing load in the communication device management system can be distributed by processing in common.

  In addition, although the case where the structure which converts a message format is arrange | positioned between a communication apparatus management system and the apparatus which transmits a CMDB process request was demonstrated, it is not limited to this and may be provided in a communication apparatus management system. Good.

  In addition to the CMDB processing request message format, even when the communication protocol or code system is different from the standard, such as when it differs from the common communication interface specification, the conversion gateway can be used to intervene with the communication device management system. It is possible to share an interface, and it can be expected to obtain an equivalent effect of load distribution of database update / reference processing.

  In addition, although a single database is assumed, even when a database system that spans multiple databases is targeted, the hash function target is extended to the database identifier, and the database identifier, the table identifier, and the record identifier are linked. The calculation can be applied and the same effect can be obtained.

  In this parallel processing method, a plurality of DB processing request queues are provided according to the degree of parallelism. However, the DB processing request queue may be a logically separated queue, and is physically implemented in a single queue. However, the same effect can be expected without problems. That is, even when the distribution processing unit receives a CMDB processing request and registers the CMDB processing request in a single queue, even if it is physically implemented as a single DB processing request queue, It is added to the CMDB processing request and registered. Thereafter, when a plurality of DB processing units retrieves a CMDB processing request from a single queue, only the CMDB processing request belonging to the hash function value assigned to each DB processing unit is retrieved with reference to the added hash function value, A similar effect can be expected by executing in parallel.

  As described above, the communication device management system according to the present invention is useful for data processing on a configuration management database, and is particularly suitable for a system that performs parallel processing on a configuration management database.

DESCRIPTION OF SYMBOLS 1 Communication apparatus management system 2 Upper management application apparatus 3 EMS user terminal 4 Management object communication apparatus 5 Conversion gateway 10, 10a, 10b Distribution processing part 11, 11a, 11b, 12, 12a, 12b, 13 DB process request queue 14 , 14a, 14b, 15, 15a, 15b, 16 DB processing unit 17 Configuration management DB
18, 19 Table 100 Current transaction list

Claims (9)

A communication device management system comprising a configuration management database and performing access processing to the configuration management database based on an access request that is a data update or data reference processing request from another device,
When applying a hash function that obtains the same hash calculation value when hash calculation is performed for access requests that access the same record in the same table, the access request from another device is received and described in the access request. A distribution processing means for performing a hash calculation based on a table identifier and a record identifier specifying an access destination of the configuration management database, and determining a distribution destination of the received access request based on the hash calculation value;
A storage unit that includes a plurality of queues and stores access requests for the same hash calculation value in the same queue for each hash calculation value;
Database processing means for retrieving the stored access request for each queue and performing access processing to the configuration management database;
A communication device management system comprising: The distribution processing unit calculates a hash calculation value of a type within the range of the number of queues provided in the storage unit.
The communication device management system according to claim 1. When the access request from each device is transmitted in a transaction including a plurality of access requests,
The distribution processing means decomposes the received transaction into individual access request units, calculates a calculated value of a hash function for the decomposed access request,
The database processing means rearranges the access requests stored in the respective queues provided in the storage means based on the priority of the transaction in which the access request is included, and the configuration management database from the access request having a high priority. Process access to
The communication device management system according to claim 1 or 2, The distribution processing means determines the priority order based on the order of receiving transactions.
The communication device management system according to claim 3. The database processing means determines a priority order based on a transaction processing start order;
The communication device management system according to claim 3. further,
When the other apparatus transmits an access request in a communication format that cannot be received by the distribution processing unit, the conversion unit converts the access request into an access request in a communication format that can be received by the distribution processing unit;
The communication device management system according to any one of claims 1 to 5, further comprising: A database access processing method employed by a communication device management system that includes a configuration management database and performs access processing to the configuration management database based on an access request that is a data update or data reference processing request from another device. And
A receiving step of receiving an access request from another device;
Specify the access destination of the configuration management database described in the access request when applying a hash function to obtain the same hash calculation value when performing hash calculation for access requests that access the same record in the same table A hash calculation step for performing a hash calculation based on the table identifier and the record identifier to be performed;
A distribution step of determining a distribution destination of the received access request based on the hash calculation value;
A storage step of storing access requests with the same hash calculation value in the same queue;
A database processing step of retrieving an access request stored in the queue and performing an access process to the configuration management database;
A database access processing method comprising: When the access request from each device is transmitted in a transaction including a plurality of access requests,
In the receiving step, the received transaction is broken down into individual access request units;
In the hash calculation step, a hash calculation value is calculated for each decomposed access request,
further,
A prioritizing step of prioritizing the transactions based on predetermined rules;
A reordering step for reordering access requests stored in the queue based on priority;
The database access processing method according to claim 7, further comprising: further,
A conversion step of converting the access request into an access request in a communication format receivable in the reception step when the other apparatus transmits an access request in a communication format that cannot be received in the reception step;
The database access processing method according to claim 7 or 8, characterized by comprising:

Images