JP4452211B2 - Data mismatch detection device and detection method - Google Patents

Description

  The present invention is intended to detect data inconsistency between a plurality of systems in a content distribution environment in which functions for providing a service are distributed and arranged in a network, or data in one system can be stored in another system. The present invention relates to a data inconsistency detection apparatus and a detection method for confirming whether or not there is a contradiction with respect to constraints on service provision.

  In recent years, in the digital content distribution environment, not only the function of simply providing content, but also the function of publishing content information and accepting content distribution requests, the function of providing information for using content, and the encryption A plurality of functions such as a function of delivering content decryption information are distributed on the network. And these functions cooperate to realize the provision of advanced content distribution services.

  In a content distribution environment in which a plurality of systems that share functions in this way cooperate to provide one service, data management is usually performed for each system in accordance with operating conditions. For such a system, data related to a plurality of systems is registered, and when each system functions based on the data, if there is inconsistency of the data, service provision may not be performed properly. . Such data inconsistency corresponds to, for example, a case where identification information for identifying a service such as a service ID in a function for accepting a content distribution request and a function for providing decryption information for encrypted content does not match. To do. However, depending on the service requirements, such as the relationship between the content distribution period and the content information disclosure period, the linkage method between systems is not necessarily the same. It is difficult to guarantee sex. In order to solve such problems, there is a means to check related data at the time of registration, but the registrant and registration time do not always match in operation, and if there are a wide variety of check items, the check Processing or confirmation work leads to an operational burden.

  For this reason, in the “data management apparatus” of Patent Document 1, the module has an interface function between various applications and the corresponding database, and can communicate with a data matching processor between modules or in the same network. A technique has been proposed in which consistency is ensured based on data of other systems and local or remote preset rules when data is requested.

An example of such a conventional data matching processing apparatus in a distributed environment is shown in FIG. The 4 conventional data consistency processing apparatus shown in 10 (data matching processor), integrally managing data registered in the n system 20 ₁ to 20 _n for realizing content distribution service to function sharing Process. Each system 20 _{1 to} 20 _n is provided with a common data processing module 21. Viewer terminal 30 ₁ to 30 _n may use the services of the distribution or the like of the content by accessing the system 20 ₁ to 20 _n via a network such as the Internet.

  The data consistency processing apparatus 10 also detects a data inconsistency based on a consistency confirmation rule storage unit 12 that stores a rule for consistency confirmation and a rule stored in the consistency confirmation rule storage unit 12. And a consistency confirmation unit 11.

In the conventional data integrity processing unit 10 receives the inconsistency check request data for each system 20 ₁ to 20 _n, each system 20 ₁ on the basis of rules set in advance check consistency rule storage unit 12 to 20 _n Data inconsistency between them is detected.

Here, the format of the data to be used between the system 20 ₁ to 20 _n, often are different, the data integrity processing unit 10, is possible to check consistency with the data format is not unified Can not. Therefore, in such a conventional service providing system, each of the data processing modules 21 for managing data in common is used as an interface between the application and the database in each of the systems 20 _{1 to} 20 _n to be checked for consistency. Must be implemented. For this reason, when a new system is added as a management target for consistency confirmation, the implementation of the data processing module 21 may be limited.

In addition, such a conventional data matching processing device can only detect data matching and mismatching, and cannot handle various data mismatching conditions depending on the form of service provision. There is also a problem. For example, the evaluation items cannot be flexibly set in accordance with the actual service operation, such as conditional branching that is inconsistent only under certain conditions, limit of the number of bytes in the character string, partial data matching, and the like.
Japanese Patent Laid-Open No. 10-124370

The above-described conventional data mismatch detection device has the following problems.
(1) Since the consistency check cannot be performed unless the data format between the systems is unified, a data processing module for managing data in common is required for each system.
(2) It is only possible to detect only data match or mismatch between systems, and it is not possible to flexibly set evaluation items for confirming data consistency according to service provision conditions.

  An object of the present invention is to provide each system even in the case where the data system is different in a target system for consistency check in a content distribution environment where various functions for providing services are distributed and arranged in a network. A data inconsistency detection device that can perform consistency confirmation without requiring the implementation of a data processing module, and can flexibly set evaluation items for confirming data consistency according to service provision conditions. And providing a detection method.

To achieve the above object, the data inconsistency detecting apparatus of the present invention is a content distribution environment in which functions for service provision are arranged distributed in the network, Oh Ru data in the system of the other system A data inconsistency detection device for confirming whether or not there is a contradiction with respect to constraints on service provision,
An evaluation item definition file in which evaluation items are set to confirm whether data in one system is consistent with the restrictions on service provision of other systems ,
A conversion definition file in which rules for converting data read from each system into common data are set;
A data conversion unit that acquires designated evaluation target data from a system that holds the evaluation target data, and converts the acquired evaluation target data into a common data format based on rules set in the conversion definition file;
In response to the consistency check request, the evaluation item set in the evaluation item definition file is read out, the data conversion unit is instructed to read out the evaluation target data designated by the evaluation item from each system, and the data conversion By comparing and verifying the data after being converted into a common data format by the section based on the evaluation condition specified by the evaluation item, the data in one system becomes a constraint condition on service provision of another system. And a consistency confirmation unit that confirms whether there is any contradiction .

  According to the present invention, after the registration data acquired from each system in the data conversion unit is converted into a common data format based on the rules set in the conversion definition file, the consistency check process in the consistency check unit is performed. Done. Therefore, in a content distribution environment where various functions for providing services are distributed over the network, services can be provided without being aware of the data management method of each system while supporting various service operating conditions. In addition, it is possible to detect inconsistent data inconsistencies with specified data in other systems and inconsistencies with service provision constraints.

In addition, the evaluation item definition file is configured by a plurality of evaluation item definition files in which different evaluation items are set according to the service operation conditions, and the evaluations specified from the plurality of evaluation item definition files. An evaluation item management unit for selecting an item definition file is further provided.
In response to the consistency check request, the consistency check unit instructs the evaluation item management unit to select the evaluation item definition file designated by the consistency check request, and selects the selected evaluation item definition file. The consistency evaluation process may be performed by reading the set evaluation item.

  According to the present invention, a plurality of evaluation item definition files corresponding to operating conditions of various services are provided, and an evaluation item for performing consistency check processing is set from the plurality of evaluation item definition files. Since the selection is made, it becomes possible to cope with various service operating conditions.

Furthermore, the consistency check unit is pre-implemented with a standard evaluation condition that uses a comparison operator for comparing a plurality of values,
A function for performing evaluation based on an evaluation condition that cannot be evaluated under the standard evaluation condition using the comparison operator is provided, and further provided with an evaluation condition expansion module that obtains evaluation target data and returns the evaluation result as a true / false value. You may do it.

  According to the present invention, when there is an evaluation item that cannot be evaluated under the standard evaluation condition, an evaluation condition extension module is created and implemented, so that an evaluation item that cannot be evaluated under the standard evaluation condition can be obtained. Consistency confirmation can be performed, and the evaluation conditions can be expanded.

  As described above, according to the present invention, in a content distribution environment in which various functions for providing a service are distributed and arranged in a network, the data of each system can be handled while corresponding to the operating conditions of various services. Without being aware of the management method, it is possible to detect a wide range of data inconsistencies that are inconsistent with other systems of specified data or with restrictions on service provision in service provision. Thus, it is possible to obtain an effect that appropriate data registration can be efficiently ensured in the entire content distribution environment.

  Next, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a diagram showing a system configuration of a data mismatch detection device according to an embodiment of the present invention. In FIG. 1, systems 301 ₁ to 301 _n that realize a function-distributed content distribution service are distributed in a network. The systems 301 _{1 to} 301 _n include, for example, an apparatus that manages and provides information related to content distribution distributed on a network as metadata, an apparatus that publishes content information using metadata and receives a viewing request from a viewer, A device that manages the decryption information of the encrypted content and provides the decryption information of the content in response to a request from the viewer, a device that distributes the content based on a designated distribution form, or a device that controls the distribution; These devices cooperate to provide a content distribution service.

The viewer terminals 400 _{1 to} 400 _n are connected to the systems 301 ₁ to 301 _n via the networks, respectively, and sequentially communicate with the systems 301 _{1 to} 301 _n to use the content distribution service. The network here may be any network such as a telephone network, a LAN, and the Internet.

The data inconsistency detection apparatus 200 of this embodiment communicates with each of the systems 301 _{1 to} 301 _n and is connected via a network so that data can be acquired. Further, the data inconsistency detection apparatus 200 is connected to the operator terminal 100 directly or through various networks such as a LAN and the Internet, so that the data inconsistency detection apparatus 200 can be operated from the operator terminal 100.

The inconsistency detection apparatus 200 includes a consistency confirmation unit 201, an evaluation item management unit 202, evaluation item definition files 203 _{1 to} 203 _n , evaluation condition expansion modules 204 _{1 to} 204 _n , a data conversion unit 205, And the conversion definition file 206.

In the evaluation item definition files 203 _{1 to} 203 _n , evaluation items for detecting the presence or absence of data inconsistency between the systems 301 _{1 to} 301 _n are set. When there are different service operation conditions, different evaluation items are set in the evaluation item definition files 203 _{1 to} 203 _n according to the service operation conditions. The evaluation item definition files 203 _{1 to} 203 _n are configured such that the service operator can freely change them according to the operation conditions.

The evaluation item management unit 202 manages evaluation items by the evaluation item definition files 203 _{1 to} 203 _n for setting evaluation items for detecting inconsistencies. In addition, the evaluation item management unit 202 selects a specified evaluation item definition file from among the plurality of evaluation item definition files 203 _{1 to} 203 _n .

The conversion definition file 206 is set with rules for converting data read from the systems 301 _{1 to} 301 _n into common data.

The data conversion unit 205 acquires the evaluation target data designated by the evaluation item from the system that holds the evaluation target data among the system systems 301 _{1 to} 301 _n , and stores the acquired evaluation target data in the conversion definition file 206. The data is converted into a common data format in the data inconsistency detection apparatus 200 based on the set rule.

The consistency confirmation unit 201 receives the consistency confirmation request from the operator terminal 100 and executes consistency confirmation processing. Specifically, the consistency confirmation unit 201 receives the consistency confirmation request, reads the evaluation items set in the evaluation item definition files 203 _{1 to} 203 _n, and sets the evaluation target data specified by the evaluation item for each item. The data conversion unit 205 is instructed to read from the systems 301 _{1 to} 301 _n , and the data after being converted into a common data format by the data conversion unit 205 is compared and verified based on the evaluation condition specified by the evaluation item. Inconsistency of data between systems is detected. When a plurality of evaluation item definition files 203 _{1 to} 203 _n that differ depending on the service operating conditions are provided, the consistency confirmation unit 201 receives the consistency confirmation request and specifies the consistency confirmation request. The evaluation item management unit 202 is instructed to select the selected evaluation item definition file, the evaluation item set in the selected evaluation item definition file is read, and the consistency check process is performed.

Here, the data conversion unit 205 searches for registration data in accordance with the interface method of each target system. As a data acquisition function modularized for each target system 301 _{1 to} 301 _n by be implemented, it may be configured in consideration of extensibility to accommodate additional systems 301 ₁ to 301 _n. Also, the evaluation condition expansion module systems 204 _{1 to} 204 _n are configured to extend the evaluation condition when there are evaluation items that cannot be evaluated only with the conditions implemented as basic evaluation conditions in the consistency check unit 201. It is to be added.

  Next, the operation of the data mismatch detection device 200 of this embodiment will be described with reference to the flowchart of FIG.

  As an inconsistency detection operation, first, the operator terminal 100 is connected to the inconsistency detection apparatus 200. After the connection, the operator inputs key information for specifying a consistency confirmation target such as a content ID, and issues a consistency confirmation request to the inconsistent connection device 200. The data inconsistency detection apparatus 200 starts the operation of detecting data inconsistency by receiving the consistency confirmation request from the operator terminal 100.

  When receiving the consistency check request from the operation terminal 100 (step 501), the data mismatch detection apparatus 200 analyzes the received consistency check request (step 502) and calls the evaluation item management unit 202 (step 503). The contents described in the evaluation item definition file 203 managed by the evaluation item management unit 202 are acquired (step 504).

  The consistency checking unit 201 determines whether or not the data group of the target system designated as the consistency evaluation item has been acquired (step 505). If the data group has not been acquired, the data conversion unit 205 is determined. The data acquisition function of the target system is called (step 506).

Then, the data conversion unit 205 obtains a series of data searched by the key for specifying the confirmation target designated at the time of the consistency confirmation request from the operator terminal 100 for each system designated by the consistency confirmation item for each system 301. Acquired collectively in accordance with the interface methods _{1 to} 301 _n (step 507). Here, the data conversion unit 205 determines whether or not a conversion definition file has been specified (step 508). If a conversion definition file has been specified, the conversion function is called (step 509). The conversion definition file 206 is read, and data conversion is performed based on the rules set in the read conversion definition file 206 (step 510).

  The data conversion unit 205 stores and holds the data acquired in this way in the memory area in a data format common to the inconsistency detection apparatus 200 (step 511).

  The consistency checking unit 201 acquires the target data specified in the evaluation item definition file 203 from the acquired data from the target system held in the memory (step 512). The consistency confirmation unit 201 acquires target data in the same manner when evaluating a plurality of data. The consistency checking unit 201 determines whether or not the current consistency check is to check only the basic standard consistency relationship that is implemented (step 513). If it is determined in step 513 that only the standard consistency relationship is to be confirmed, the consistency confirmation unit 201 evaluates the acquired data under the evaluation conditions specified in the evaluation item definition file 203 (step 514). The evaluation result is stored as a true / false value as a pair with evaluation item information such as a data value to be evaluated and an evaluation condition (step 515).

In the determination of step 513, if an evaluation condition is specified by the evaluation condition expansion modules 204 _{1 to} 204 _n added when a condition that cannot be evaluated as a basic evaluation condition is extended, The evaluation condition expansion module is called (step 516), and evaluation is performed using the evaluation condition expansion module (step 517). When a plurality of evaluation items are defined in the evaluation item definition files 203 _{1 to} 203 _n , the processing so far is repeated, and the stored result information is filtered at the point where evaluation of all the items is completed. By generating an evaluation result screen based on the output rule for this and returning it to the operation terminal 100 (step 518), the operator can detect inconsistencies in the registered data from the evaluation result. The operator corrects the corresponding data in the inconsistency confirmed here, thereby ensuring proper data registration in the entire content distribution environment. Here, in addition to making a consistency check request when the operator needs to check, the mismatch detection apparatus 200 periodically issues a consistency check request and detects an inconsistency when an inconsistency is detected. The location may be transmitted to the operator terminal 100.

The systems 301 ₁ to 301 _n that realize the content distribution service are not necessarily managed by the same method, and the data is registered and managed by a unique method that is suitable for each operation. When performing inconsistency detection of data registered in each of these system systems 301 _{1 to} 301 _n , inconsistencies with data with other systems specified in advance, and restrictions on service provision, The contents for confirming the inconsistency are described in the evaluation item definition files 203 _{1 to} 203 _n as consistency confirmation items. The evaluation item definition files 203 _{1 to} 203 _n are managed by the evaluation item management unit 202 in the data inconsistency detection apparatus 200.

In the evaluation item definition files 203 _{1 to} 203 _n , the system to be confirmed, the target data, the data type of the target data, and the evaluation conditions are designated as the consistency confirmation items, and the conversion definition is required for data that needs to be converted. A file path of the file 206 is designated.

Next, a specific method of inconsistency detection processing in the consistency confirmation unit 201 will be described. For example, in the consistency check unit 201, an evaluation using a comparison operator for comparing a plurality of values is mounted in advance as a standard evaluation condition. Then, the evaluation condition expansion modules 204 _{1 to} 204 _n are provided with a function for performing evaluation based on an evaluation condition that cannot be evaluated under the standard evaluation condition using this comparison operator, and obtained and evaluated evaluation target data. Returns the result as a Boolean value. This function is a function created in advance by the operator in accordance with the service operation conditions, and the data mismatch detection apparatus 200 of the present embodiment can return the evaluation result by this function as a common truth value. Inconsistency detection using not only the standard evaluation condition but also the evaluation condition based on a preset function is possible.

  In this case, the consistency check unit 201 includes, as data evaluation conditions for inconsistency detection, equivalent (=), non-equivalent (≠), greater (>), more (≧), less (<), A general comparison operator for comparing a plurality of values such as the following (≦) can be designated as a standard comparison condition. Also, when specifying the data type, considering that the data to be compared handles various data types such as numeric values, character strings, and dates, the function that detects the data type of the data specified in the device is not implemented. , Specify the data type so that it can be evaluated under the same conditions. Here, the data acquired from the system to be checked is converted to a data format that is commonly handled in the device, but by converting the data format into a hierarchical structure such as an XML (eXtensible Markup Language) object, Corresponding to various data structures, it is possible to specify the data path of data of any system in a common format. As a result, inconsistency detection can be set without the operator being aware of the data management method of each system. Here, a plurality of data to be confirmed may be specified as data of one or a plurality of systems, or one data of a certain system and a fixed value extracted as an operational condition by an operator may be specified. .

  FIG. 3 is a description example of the evaluation item definition file 203. In this description example, the evaluation item definition file is described in the XML format, and the “ValidationItem” element indicates a consistency check item. In the “relation” attribute of this element, “below” is designated by the expression “lessorequal” as the evaluation condition, and “date type” is designated by the expression “date” as the data type in the “type” attribute. In the “DataPath” element, the path of the data to be evaluated is specified. In the “SystemId” attribute of this element, the target system is specified. As a result, the target data is handled as a date type, and it is set to evaluate that the value of the system data specified by “01” as “SystemId” is equal to or less than the value of the data specified by “02”. .

  In addition, the data conversion at this time is not only unified in the data format common to the apparatus, but also given a data path name that is easy for the operator to specify, for example, the representation method of date data of another system to be compared is different. In some cases, the same representation method can be used for comparison, data can be converted appropriately according to the evaluation conditions for inconsistency detection, such as obtaining only part of the data or combining multiple data. It is possible to extend the target range.

  For example, when there are a plurality of purchase patterns for the target content, in order to confirm whether the price information for the purchase ID given for each purchase pattern is the same in the data of the system A and the system B In the data acquired using the content ID as a key, there are a plurality of price information, and it is not possible to identify which price information is to be evaluated. For this reason, evaluation must be performed after associating the purchase ID with the price information, but in each data of each system, the two data of the purchase ID and the price are combined to form a data name “idprice”. By handling and confirming the match of the “idprice” value of each system, it is possible to confirm the match of the price corresponding to the ID.

  Even in such data conversion, when data is handled as XML format in a data format that is common to devices, a data structure conversion method such as XSLT (XML Stylesheet Language Transformation) may be used. The definition file 206 can be described in the XSLT stylesheet format.

The evaluation item definition files 203 _{1 to} 203 _n are managed by the evaluation item management unit 202. When the consistency check item changes depending on the requirements of the service applied in the same system, a plurality of evaluation item definition files 203 _{1 to} 203 n are used. _A file ID and a file name are assigned to _n and managed by the evaluation item management unit 202. When an inconsistency detection is triggered or an operator selects a file to be applied in advance, the evaluation item management unit 202 calls the evaluation item definition file to be applied from the specified file ID, and detects inconsistency. By doing so, it is possible to detect inconsistencies according to the operating conditions. In addition, the evaluation item definition file is divided and managed according to the importance of data consistency, and alerts are only issued when inconsistencies are detected in the evaluation item definition file to detect the most important inconsistencies. May be notified to the operator. In this way, when the data data inconsistency detection device automatically and periodically detects inconsistencies, only when the most important data inconsistency is detected by the output rule, the data of the alert is detected. It is possible to notify the occurrence of inconsistency and, in the case of other minor inconsistencies, the operator can correct the data as necessary after confirming the occurrence status of the data inconsistency in the log etc. is there.

In the data inconsistency detection apparatus 200 of the present embodiment, the operator basically designates the target system data and the standard comparison condition in the evaluation item definition files 203 _{1 to} 203 _n . There are cases where evaluation is performed for contents that cannot be evaluated under standard comparison conditions even if conversion of acquired data is performed, such as evaluation based on branching, presence of prohibited characters, evaluation of whether the specified character string is included, etc. is there. In order to cope with such a case, the evaluation condition expansion modules 204 _{1 to} 204 _n can be applied to evaluate a condition that cannot be evaluated under the standard comparison condition.

Therefore, a unified adapter interface is defined in the apparatus for using the evaluation condition expansion modules 204 _{1 to} 204 _n , and the consistency confirmation unit 201 can call the evaluation condition expansion modules 204 _{1 to} 204 _n from the adapter interface. . This adapter interface is a comparison target such as an acquisition destination and a data type of data to be given to a module when a corresponding evaluation condition extension module 204 _{1 to} 204 _n is called by an identifier such as an evaluation condition name or a module ID. Is used as an argument, and is used as a return value when obtaining the evaluation results in the evaluation condition expansion modules 204 _{1 to} 204 _n such as true / false values. The evaluation condition expansion module 204 is created as a program that acquires and processes target data that is an argument in accordance with this adapter interface, and returns the evaluation result as a true / false value.

In addition, the consistency checking unit 201 manages available evaluation condition expansion modules 204 _{1 to} 204 _n . When the evaluation item definition file 203 specifies that the evaluation by the evaluation condition expansion modules 204 _{1 to} 204 _n is to be performed, the evaluation condition name or module ID corresponding to the evaluation condition expansion module is specified as the evaluation condition.

As a result, the evaluation condition expansion module 204 is created according to the needs of the operator and managed by the consistency check unit 201, so that the evaluation conditions specified in the evaluation item definition files 203 _{1 to} 203 _n can be extended. it can.

In the data inconsistency detection apparatus 200 of this embodiment, the data conversion unit 205 converts the registration data acquired from each of the systems 301 _{1 to} 301 _n into a common data format based on the rules set in the conversion definition file 206. After that, consistency check processing is performed. Therefore, according to the data inconsistency detection apparatus 200 of the present embodiment, in a content distribution environment in which various functions for providing services are distributed and arranged in a network, while corresponding to the operating conditions of various services, Regardless of the data management method of each system, there is a wide range of data inconsistencies that are inconsistent with other systems of specified data or inconsistent with restrictions on service provision. This makes it possible to detect data efficiently and ensure appropriate data registration in the entire content distribution environment.

It is a block diagram which shows the system configuration example of the data inconsistency detection apparatus of one Embodiment of this invention. It is the figure which showed the operation | movement flow of the mismatch detection apparatus of one Embodiment of this invention. It is a description example of an evaluation item definition file. It is an example of the data management apparatus in the conventional distributed environment.

Explanation of symbols

10 Data alignment processor (data alignment processor)
11 consistency check unit 12 Consistency check rule storing unit 20 ₁ to 20 _n system 21 the data processing module 30 ₁ to 30 _n viewer terminal 100 operator terminal 200 data inconsistency detecting device 201 integrity checking unit 202 evaluation item managing section 203 _{1 to} 203 _n evaluation item definition file 204 _{1 to} 204 _n evaluation condition expansion schedule 205 data conversion unit 206 conversion definition file 301 _{1 to} 301 _n system 401 _{1 to} 401 _n viewer terminal 501 to 518 steps

Claims (6)

In content distribution environment in which functions for service provision are arranged distributed in the network, because the data in the system Ru Oh to see if there is a conflict for the constraint conditions on the servicing of other systems The data inconsistency detection device of
An evaluation item definition file in which evaluation items are set to confirm whether data in one system is consistent with the restrictions on service provision of other systems ,
A conversion definition file in which rules for converting data read from each system into common data are set;
A data conversion unit that acquires designated evaluation target data from a system that holds the evaluation target data, and converts the acquired evaluation target data into a common data format based on rules set in the conversion definition file;
In response to the consistency check request, the evaluation item set in the evaluation item definition file is read out, the data conversion unit is instructed to read out the evaluation target data designated by the evaluation item from each system, and the data conversion By comparing and verifying the data after being converted into a common data format by the section based on the evaluation condition specified by the evaluation item, the data in one system becomes a constraint condition on service provision of another system. A data inconsistency detection apparatus comprising: a consistency confirmation unit that confirms whether there is a contradiction with respect to the data. The evaluation item definition file is composed of a plurality of evaluation item definition files in which different evaluation items are set according to the service operating conditions,
An evaluation item management unit that selects a specified evaluation item definition file from the plurality of evaluation item definition files;
In response to the consistency check request, the consistency check unit instructs the evaluation item management unit to select the evaluation item definition file designated by the consistency check request, and selects the selected evaluation item definition file. The data inconsistency detection apparatus according to claim 1, wherein the consistency evaluation process is performed by reading the set evaluation item. The consistency checking unit is pre-implemented with a standard evaluation condition using a comparison operator for comparing a plurality of values,
A function for performing evaluation based on an evaluation condition that cannot be evaluated under the standard evaluation condition using the comparison operator, and further including an evaluation condition expansion module that obtains evaluation target data and returns the evaluation result as a true value The data mismatch detection device according to claim 1 or 2. In content distribution environment in which functions for service provision are arranged distributed in the network, because the data in the system Ru Oh to see if there is a conflict for the constraint conditions on the servicing of other systems Data inconsistency detection method of
An evaluation item definition in which an evaluation item is set in order for the evaluation item management unit to check whether the data in one system is consistent with the constraints on the service provision of another system in response to a consistency check request A step of reading evaluation items set in the file;
The data conversion unit acquires the evaluation target data specified by the evaluation item from the system that holds the evaluation target data, and converts the acquired evaluation target data from the data read from each system into common data Converting to a common data format based on the rules for
By comparing and verifying the evaluation target data after the consistency check unit has been converted into a common data format based on the evaluation condition specified by the evaluation item, the data in one system can be serviced by another system. And a step of confirming whether or not there is a contradiction to the provisional constraint condition . The evaluation item definition file is composed of a plurality of evaluation item definition files in which different evaluation items are set according to operation conditions,
In the step of reading the evaluation item set in the evaluation item definition file, the evaluation item management unit receives the consistency check request from the plurality of evaluation item definition files and is designated by the consistency check request 5. The data inconsistency detection method according to claim 4, wherein an evaluation item definition file is selected and an evaluation item set in the selected evaluation item definition file is read. In the step of comparing and verifying the evaluation object data after being converted into a common data format based on the evaluation condition specified by the evaluation item,
When an evaluation condition that cannot be evaluated by a standard evaluation condition using a comparison operator for comparing a plurality of values is specified by the consistency checking unit, a function that is set in advance according to the specified evaluation condition evaluating the data obtained using, the evaluating step of obtaining a boolean value results, according to claim 4 or 5 data inconsistency detection method according to further comprising.

Images