JP2011090352A - Retrieval data management device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To quickly register data in a data group as an object of retrieval of similar data without complicating a retrieval index. <P>SOLUTION: When a plurality of pieces of registration data are input, similar data about each registration data are quickly retrieved by graph retrieval processing of a graph retrieval part 40. Also, a similar data acquisition part 51 in a data registration part 50 inputs registration data to a graph retrieval part 40, and obtains a retrieval result (similar data) about each registration data. Then, a merge part 53 generates a link between the registration data and the similar data. Also, the merge part 53 generates a link between the pieces of registration data, and reads link information of the similar data from a graph index DB70, and merges it on a temporary memory 80. A link optimization part 55 reduces the number of links on the basis of the number of links and the length of the link. Then, database registration is performed by optimizing the number of links generated by additional registration. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to an apparatus for retrieving similar data from a database and registering new data in the database.

  A feature amount extracted from an image, sound, or the like is represented by multidimensional vector data, and similar data is searched using a distance between the vector data. When searching for multi-dimensional vector data, if the number of search target data is large, the distance between the search key data (search data) and the search target data must be calculated one by one. It will be long.

  Patent Document 1 describes the following technique. That is, for all feature quantities in the database, the similarity with other feature quantities is calculated in advance, and data with high similarity is stored in association with each other. Then, the nearest neighbor of the given search key is obtained, and similar data corresponding to the nearest neighbor data is returned as a search result.

JP 2001-52024 A

  By the way, when new data is to be registered in a data group (database) to be searched, an index considering the degree of similarity between the data is assigned in advance, thereby ensuring high speed search. For this reason, it is necessary to search similar data for the registered data from the database.

  However, in the technique of Patent Document 1, in order to speed up the search, it is necessary to store all data in order of similarity for each data, but it is necessary to pre-calculate the similarity to all data in the database. When the search target data is enormous, the time required for the search becomes longer depending on the number of data. In addition, every time data is registered, it is necessary to calculate the similarity between the data and review the index. Therefore, as the number of data increases, the construction of the index becomes complicated.

  The present invention has been made in view of the above-described problems, and an object of the present invention is to register data at high speed without complicating a search index in a data group to be searched for similar data. It is.

In order to achieve the above object, the search data management device according to the first invention provides:
A database in which a link for tracing from one data to the other data is set between the data and a plurality of the data is stored;
For the input search target data, select any of the data stored in the database as a search start point, and sequentially follow the link from the search start point to A graph search means for searching and outputting the data within a predetermined distance from the data to be searched as similar data among the data in
By inputting the data to be registered in the database as the search target to the graph search means, the similar data for the registration target data is obtained, and a link is established between the registration target data and the similar data. Similar data acquisition means to be generated;
Merge means for merging the links respectively generated by the similar data acquisition means for a plurality of registration target data;
Link optimization means for performing a reduction process on the link merged by the merging means and the link already set on the database in the data generated by the link;
Updating the link information of the database based on the result of the reduction process, and storing the data to be registered in the database;
It is characterized by having.

In the second invention, the link optimization means includes:
The reduction processing is performed based on the total number of links merged by the merging unit and links already set on the database in the data in which the links are generated.

In the third invention, the link optimization means includes:
The reduction processing is performed based on the length of the link merged by the merging means and the link already set on the database in the data in which the link is generated.

In the fourth invention, the link generation means includes:
A link is further generated between each of the plurality of registration target data.

According to a fifth aspect of the present invention, there is provided a search data management in which a computer for managing a database in which a plurality of data is stored by setting a link for tracing from one data to the other data as a data group to be searched. In the method
For the input search target data, select any of the data stored in the database as a search start point, and sequentially follow the link from the search start point to A graph search step of searching for and outputting similar data to data within a predetermined distance from the data to be searched among the data in
By inputting the data to be registered in the database as the search target to the graph search means, the similar data for the registration target data is obtained, and a link is established between the registration target data and the similar data. A similar data acquisition process to be generated;
A merge step of merging the links respectively generated by the similar data acquisition step for a plurality of registration target data;
A link optimization step for performing a reduction process on the link merged in the merging step and a link already set on the database in the data in which the link is generated;
A data update step of updating the link information of the database based on the result of the reduction process and storing the registration target data in the database;
It is characterized by including.

  According to a sixth aspect of the invention, there is provided a program for causing a computer to execute the processing of the search data management method according to the fifth aspect of the invention.

  According to the present invention, when registering a plurality of data in the database, registration is performed while reducing links using links generated between similar data. The data can be registered at high speed without complicating the search index. In addition, since data registration can sequentially prevent the link structure between data from becoming complicated, it is possible to prevent a decrease in search speed due to data registration.

[Apparatus Configuration of First Embodiment]
A search device according to a first embodiment to which the present invention is applied will be described with reference to the accompanying drawings. The contents of the present invention are not limited to the present embodiment, and various modifications can be made to the specific configuration within the scope described in the claims.

  In the present embodiment, an example will be described in which multidimensional vector data representing the feature amount of an image is handled as vector data. However, the vector data may represent features of voice and other multimedia data information, or may be other types of multidimensional data.

  FIG. 1 is a block diagram showing a functional configuration of a search device 1 which is an example of the present invention. The search device 1 does not need to be configured by a single piece of hardware or software. If necessary, a function corresponding to the search device 1 can be provided by a combination of a plurality of hardware or software. The search device 1 of this embodiment can also be configured by a plurality of servers scattered on the network.

  The search device 1 performs data processing in response to various requests transmitted from the client terminal, and returns the processing result to the client terminal. Specifically, when receiving a search query that is a search request, the search device 1 performs a search according to the search query and returns a search result to the client terminal. When a request for registering new data in a database (hereinafter abbreviated as “DB”) that stores data to be searched is received, it is registered in the DB.

[Client terminal configuration]
Although illustration of the client terminal is omitted, the client terminal is configured by a personal computer including an input unit such as a keyboard, a mouse, and a touch pad, an output unit such as a display and a printer, and a CPU. The client terminal is connected to the search device 1 via a network. Further, the client terminal sends search data and registration data designated by the user to the search device 1.

  Here, the search data is data serving as a key for searching for similar data from data stored in the database of the search device 1. Registration data is data newly registered in the database of the search device 1. The vector data extracted from the search data and registration data is also referred to as “search data” and “registration data”.

[Configuration of search device]
According to FIG. 1, the search device 1 includes a registration data input unit 10, a search data input unit 20, a search result output unit 30, a graph search unit 40, a data registration unit 50, an image DB 60, a graph index. A DB 70 and a temporary memory 80 are provided.

  The registration data input unit 10 is a functional unit that receives registration data transmitted from a client terminal. When registration data is received together with a data registration request, the registration data input unit 10 inputs the registration data to the data registration unit 50.

  The search data input unit 20 is a functional unit for receiving the search data transmitted from the client terminal. When the search data is received together with the search request, the search data input unit 20 inputs the search data to the graph search unit 40.

  The search result output unit 30 is a functional unit for transmitting the search result by the graph search unit 40 to the client terminal according to the input of the search data input unit 20. The search result output unit 30 generates display data for displaying the search result and transmits it to the client terminal.

  The image DB 60 is a database that stores and stores image data to be searched, and stores an image ID, image data, and vector data in association with each other as shown in FIG. The graph search unit 40 extracts and stores multidimensional vector data as a plurality of feature amounts from the image data stored in the image DB 60. The number of dimensions of the vector data is not particularly limited, but is preferably set to a high number of dimensions (for example, 10 dimensions or more) in order to improve search accuracy.

  The graph index DB 70 is a database that stores an index having a graph structure, and stores vector data representing feature amounts of data to be searched. The data registration unit 50 generates a graph structure index based on the vector data extracted from the image data.

  Further, the graph index DB 70 stores information on links set to trace from one vector data to the other vector data. Specifically, as shown in FIG. 1, the graph index DB 70 displays an image ID that is a link source corresponding to the image DB 60 and one or more other link destination image IDs linked to the vector data. Store in association with each other. By establishing a link between the vector data, a graph structure is formed between the vector data a to f in the vector space as shown in FIG.

  The graph structure formed by the link information in the graph index DB 70, that is, the link information is appropriately referred to as “graph index”. A link is information that can trace one data to another data. The link may be unidirectional, but as shown in FIG. 1, the data indicating one link destination and the data indicating the link destination in the opposite direction are stored as a pair and can be traced bidirectionally. Thus, the data search speed can be improved.

  In FIG. 4A, vector data is represented by points (a to f), and shows a state in which vector data is distributed in a multidimensional feature amount space. A link is set between each vector data, and the link is represented by a solid line. In the following description, vector data will be referred to as “points” as appropriate.

  The graph search unit 40 searches for data similar to the search data by circulating the links set in the graph index DB 70. As shown in FIG. 1, the graph search unit 40 includes a vector data generation unit 41, a search start point determination unit 43, a graph circulation unit 45, and a similar data specification unit 47.

  The vector data generation unit 41 extracts feature quantities that become multidimensional vector data from the data input from the search data input unit 20 or the data registration unit 50.

  The search start point determination unit 43 determines the existing vector data on the graph index close to the vector data extracted from the search data as the search start point. The graph search unit 40 determines any one of the plurality of vector data as a search start point, and starts the link circulation starting from the search start point.

  The graph circulator 45 performs a process of sequentially following the links set in the graph index DB 70 from the search start point until a predetermined search end condition is satisfied.

  The similar data specifying unit 47 specifies, as similar data, vector data within a predetermined distance with respect to the search data among vector data on the link route followed by the graph circulating unit 45. The identified similar data or related information is sent to the client terminal as a search result.

  The data registration unit 50 performs processing for registering the registration data input from the registration data input unit 10 in the image DB 60 and the graph index DB 70. The data registration unit 50 assigns a new image ID to the image data input as registration data, and stores it in the image DB 60. In addition, the image data is stored in the image DB 60 in association with the vector data extracted from the image data.

  According to FIG. 1, the data registration unit 50 includes a similar data acquisition unit 51, a merge unit 53, a link optimization unit 55, and a DB update unit 57.

  The similar data obtaining unit 51 obtains data similar to the registered data by outputting a request for retrieving similar data for the registered data input from the registered data input unit 10 to the graph retrieving unit 40. The similar data is temporarily stored in the memory in association with the registration data as appropriate.

  Moreover, the similar data acquisition part 51 produces | generates a link between the similar data searched with respect to registration data. This link is temporarily generated before the main registration of data in the graph index DB 70, and a data table having the same data structure as the graph index DB 70 is generated and stored in the temporary memory 80.

  The merging unit 53 merges link information generated between similar data searched for each registered data in the temporary memory 80 by inputting a plurality of registered data. Also, the merge unit 53, for similar data stored as a link destination in the temporary memory 80, for which a link has already been set on the graph index DB 70, obtains information on the link destination for the similar data from the graph index DB 70. Read out and store in temporary memory 80. In addition, a link is generated between a plurality of registration data and stored in the temporary memory 80. Thereby, the temporary memory 80 stores the link generated between the registered data and the similar data and the link already set for the similar data.

  The link optimization unit 55 is a functional unit that optimizes the link so that the graph structure of the graph index is not complicated. By adding link destinations to similar data, the number of links from similar data increases, and this may increase the number of links that the graph search unit 40 circulates, leading to a decrease in search speed. There is. Therefore, when adding a link destination from similar data, the number of links is reviewed so as to keep the number of links appropriate.

  Based on the processing result of the link optimization unit 55, the DB update unit 57 stores data of the registered data in the image DB 60 and the graph index DB 70, and updates the link information of the graph index DB 70. Specifically, when registering the image ID and vector data for the registered data in the graph index DB 70, the image ID of the similar data is stored in association with the link destination. Further, by adding the image ID of the registration data to the link destination with respect to the image ID of the similar data, a mutual link is formed between the registration data and the similar data.

  The search device 1 generates a graph index DB 70 that is a search index having a graph structure, and searches for data similar to the search data by following links on the graph structure. In addition, when registration data is input, the registration data is newly added to the search index that circulates at the time of the search, and the registration data can also be searched by making the registration data a circulation route. A graph index is formed in a self-generating manner.

[Operation of search device]
Next, the operation of the graph self-generation process performed when the search device 1 according to the present embodiment registers data will be described in detail with reference to FIGS. This graph self-generation process is executed based on a program stored in advance in the memory of the search device 1. 2, 3 and 6 are flowcharts showing an example of the operation of the search device 1, and FIGS. 4, 5, 7 and 8 are views showing the state of the data search and link optimization processing on the graph index. is there.

[Graph self-generation processing]
First, the search device 1 performs an initial setting process (step S1). In this initial setting, the number of links set in newly registered data when data registration is performed, and a threshold value (link reduction threshold value) when performing link reduction are set in advance.

  Next, when registration data is input from the registration data input unit 10 to the data registration unit 50 (step S2), the vector data generation unit 41 generates vector data by extracting feature amounts from the registration data ( Step S3). At this time, when a plurality of registration data are input, vector data is generated for a predetermined number (for example, three) of registration data among the plurality of data.

  And the similar data acquisition part 51 outputs registration data to the graph search part 40, and performs a graph search process (step S4). At this time, when a plurality of registered data are input, the graph search process may be performed by a parallel process using a plurality of CPUs. FIG. 2 shows an example in which the graph search processes A to C are processed in parallel by three processes when three pieces of registration data are input. However, the number of processes for parallel processing can be changed as appropriate. .

[Graph search processing]
[Search start point determination processing]
When the graph search unit 40 starts the graph search process, the search start point determination unit 43 first determines vector data close to the registered data as a search start point (step S41). FIG. 3 is a flowchart illustrating an example of a process for determining a search start point.

  The search start point determination unit 43 first selects an arbitrary point (for example, point a in FIG. 4B) from the graph index (step S430), and is linked to the selected point (selected point). Points (for example, points c and d in FIG. 4C) are acquired based on the graph index DB 70 (step S432).

  Next, the distance in the feature amount space with the registered data for the linked point is calculated (step S434). The search start point determination unit 43 extracts the point having the shortest distance from the registered data in the calculated distance (step S436), and the distance D2 between the point and the registered data is the distance D1 between the registered data and the selected point. Or less (steps S438 and 440). In FIG. 4D, when the distance D1 between the selected point a and the registered data g is compared with the distance D2 between the selected point a and the link destination c, it is determined that the distance D2 is smaller.

  When the search start point determination unit 43 determines that the distance D2 is smaller than the distance D1 (step S440; Yes), the search start point determination unit 43 selects the point extracted in step S436 (step S442), and the process proceeds to step S432. .

  That is, by performing the loop processing of steps S432 to S442, the link is traced so as to select a point close to the registered data on the graph index from the point arbitrarily selected first.

  When determining that the distance D2 is greater than the distance D1 in step S440 (step S440; No), the search start point determination unit 43 determines the selected point as the search start point (step S444).

  In FIG. 4E, the point closest to the registration data g is sequentially selected from the point a selected first, and the point c → the point b → the point d is circulated so that the point d closest to the registration data becomes the point d. It is determined as a search start point.

  In the search start point determination process described above, even when the search start point is determined on the assumption that the distance D2 is greater than the distance D1, the search start point may be outside the search range centered on the registered data. is there. In this case, the search cannot be started because the search start point is outside the search range. Therefore, if the search start point determined in step S444 is outside the search range, an arbitrary point is newly selected from the graph index, and the search start point determination process is performed a predetermined number of times to start the search within the search range. Determine the point.

  Further, if a point to be arbitrarily selected in step S430 is selected at random, there is a possibility that an adjacent point will be selected again when the search start point determination process is repeated. In this case, even if the link is traced from the adjacent point, the possibility that the link of the same path is traced is high, and the search start point within the search range cannot be determined.

  Therefore, when the search start point determination process is repeatedly performed, it is preferable to newly select a point that is a predetermined distance away from a previously selected point. A plurality of points dispersed in the vector space may be specified in advance, and an arbitrary point may be selected from them. Thereby, the search start point within the search range can be determined efficiently.

[Turning the graph]
When the search start point is determined as described above, the graph circulator 45 sequentially follows the links starting from the search start point (step S43). At this time, there is a case where the link is branched from one vector data (that is, there are a plurality of paths). In this case, the vector data on the traced path, or information for specifying it is used. Then, it is stored in the memory of the search device 1 by an appropriate method.

[Search for similar data]
The graph circulating unit 45 determines whether or not a predetermined search end condition is satisfied while following the link on the route (step S45). Various search termination conditions can be considered. For example, there may be any of the following search end conditions.

(Search end condition 1)
The result of following the link starting from the search start point is a range obtained by multiplying a predetermined search range (for example, the search range in FIG. 5A) centered on the registered data by α (α> 1) (that is, the search limit range). ). Here, for α, an appropriate value such as 1.5 can be adopted. As α increases, search leaks can be reduced. On the other hand, the search time can be shortened as α is reduced.

  When the number of data searched by following links increases, the search can be terminated early by decreasing the value of α. Thereby, even when the number of data is excessive, a search result can be acquired early. Note that it is preferable to set the value of α so as not to be 1 or less in order to improve the search accuracy. However, if it is desired to end the search at an early stage, it is possible to set α <1.

(Search end condition 2)
The result of following the link starting from the search start point is that the link has been traced a predetermined number of times outside the search range centered on the registered data.

  Here, the predetermined number of times is, for example, five, but an appropriate value can be adopted. For example, in FIG. 5A, when the point a is traced from the point b, the search range is exceeded, but when the link is followed once more after the search range is exceeded, the point c is reached. Thus, the omission of search can be reduced by setting the number of rounds outside the search range.

  When the search end condition is satisfied for one route, the link in the other route is traced. When the search end condition is satisfied for any route, the process proceeds to the next step.

  The similar data specifying unit 47 circulates the graph until the search end condition is satisfied (step S45 → S43). If the search end condition is satisfied (step S45; Yes), the circulated point (vector data) is registered. The distance to the data is calculated, and similar data ranked based on the distance is output (step S47).

  For example, when the search start point is point d in FIG. 5 (a), the links of points b, e, and f which are link destinations are traced and then linked to point e as shown in FIG. 5 (b). Trace to point c. Then, as shown in FIG. 5C, when the point c is traced to the point a, the search range is exceeded. When the search end condition is that the search range is exceeded, the link circulation is ended.

  Then, ranking of similar data is obtained based on the distance between each of the points b to f and the registered data g traced from the search start point d. In FIG. 5C, rankings are obtained in the order of points d, b, c, e, and f.

[Link generation processing]
When the similar data retrieval by the graph retrieval unit 40 is completed, the similar data acquisition unit 51 of the data registration unit 50 generates a link between the registered data and the similar data (the flowchart in FIG. 6A) (step S1). S5).

  The similar data acquisition unit 51 first acquires similar data that is a search result obtained for each registered data (step S51), and generates a link between the similar data and the registered data (step S52). When there are a plurality of registered data, a link is generated between similar data corresponding to the input of each registered data.

  The similar data acquisition unit 51 further generates a link between the respective registration data (step S53). And the link information about the similar data of the search result is read from the index DB 70 (step S54). The similar data acquisition unit 51 stores the link generated / read out in steps S52 to S54 in the temporary memory 80, and merges them (step S55).

  For example, when registering registered data X to Z in a data group having a graph structure as shown in FIG. 7A, a graph search process is performed for each registered data. As for the registered data X, as shown in FIG. 7B, points a to c are obtained as search results, and a link in which the image ID is associated with the link destination is generated. For registered data Y, points a, b, and d are obtained as shown in FIG. For the registration data Z, points b, d, and f are obtained as search results as shown in FIG.

  Link information about similar data of these search results is read from the graph index DB 70. 7A to 7E, a broken line indicates a newly generated link for registered data, and a solid line indicates a link that is already set and stored on the graph index DB 70. For example, for the point a obtained as the search result of the registration data X, the link information in which the points b, c, and d are the link destinations is read. Moreover, a link is produced | generated between each of registration data XZ.

  FIG. 7E shows an example of data in the temporary memory 80. As shown in the figure, the temporary memory 80 stores and merges links between registered data and similar data, links between registered data, and links already set in similar data.

[Link optimization processing]
Next, the link optimization unit 55 performs a link optimization process shown in FIG. 6B (step S6). In the present embodiment, the link optimization process is performed by using similar data (search results) in which links are generated as a link reduction target. That is, link reduction target data is acquired (step S61), and the number of links on the temporary memory 80 and the length of the link are acquired based on the vector data of the graph index DB 70 and the image DB 60 (step S61). Step S62). If the number of links is equal to or greater than the link reduction threshold, link reduction is performed based on the link length (step S63).

  At this time, among the data linked to the similar data for which the link is generated, the data is reduced in order of increasing distance. For example, when the link reduction threshold is “5”, in FIG. 8A, among the points a to d and f where the links are generated, the number of links set to the points c and d is 6 or more, The link reduction threshold is exceeded. Therefore, the link set between the point c and the point b farthest among the links is reduced. For point d, the link set between point a and point c is reduced.

[Database registration]
The DB update unit 57 updates the link information of the graph index DB 70 based on the result of the link reduction processing by the link optimization unit 55, and additionally stores the link destination for the registered data in the graph index DB 70. Also, the registration data and the vector data input from the registration data input unit 10 are stored in the image DB 60 (step S7). If there is unprocessed data in the data input from the registered data input unit 10 (step S8; Yes), the process proceeds to step S3 to perform graph search processing, link generation, and link optimization. I do. If there is no new data (step S8; No), the graph self-generation process is terminated.

  Further, although detailed description is omitted, in the case of only the search processing for searching similar data to the search data and returning the search result to the client terminal, the search data input from the search data input unit 20 is processed. The graph search processing by the graph search unit 40 described above is performed. And the search result output part 30 produces | generates the search result which ranked similar data obtained by the similar data specific | specification part 47 based on distance as display data, and returns it to a client terminal.

  As described above, according to the first embodiment, similar data for registered data is searched using a search algorithm that searches for similar data by searching for links between graph index data. By newly generating a link in the meantime, data is registered in the graph index searched by the search device 1 following the link, and the link is formed as data to be circulated after registration. Thus, the search device 1 registers data on the graph index that circulates during the search, and self-generates the graph index.

  In addition, when a plurality of registration data are input, similar data for each registration data is searched at a high speed, and the number of links generated by additional registration of each registration data is optimized, and then database registration is performed. By doing so, the search apparatus 1 performs self-repair by optimizing the link structure of the graph index when registering data.

  Therefore, similar data can be searched without calculating the distance to all data in the database by a search algorithm using a graph index, so that data can be registered at high speed in a database storing multidimensional vector data. Can do. In addition, since the number of links in the graph index is kept optimal, it is possible to prevent the search speed from being lowered due to a complicated link structure due to an increase in data.

[Second Embodiment]
Next, a second embodiment of the search device 1 will be described. Note that the description of the same functional configuration and the same processing steps as those in the first embodiment will be omitted. The search device 1 in the second embodiment is realized by replacing the link optimization process in FIG. 2 with the link optimization process according to the flowchart shown in FIG. Hereinafter, the link optimization process will be described with reference to the diagram showing the state of the link optimization process of FIG. In the illustration of the link structure in FIG. 9, the illustration of the links between the data in FIG.

  As described above, a search algorithm using a graph index searches for similar data by circulating links between vector data. However, if a link break occurs, it cannot be performed due to isolation of vector data. End up. The search device 1 according to the second embodiment repairs the link when the link is reduced.

  First, the link optimizing unit 55 specifies a point (link holding point) that holds the link among all the points linked to the point for which the reduction target link is set (step S61). The link holding point may be specified by, for example, a predetermined number of points that are close to the point to be reduced or a point within a predetermined distance. Further, the points to be reduced may be included in the link holding points.

  In FIG. 10A, five points b, c, d, e, and f that are close to the point a to be reduced are specified as link holding points. Then, points other than the link holding point among points linked to the reduction target points are selected one by one from the repair target points as link repair targets (step S62). In FIG. 10A, the point g is selected as the repair target point.

  Next, the link optimization unit 55 calculates the distance between the repair target point and each link holding point (step S63), and the link holding point having the shortest distance among the calculated distances and the repair target point are calculated. A new link is set between them (step S64).

  For example, as shown in FIG. 10B, the distance between the restoration target point g and each of the link holding points b to f is calculated, and the link holding point having the shortest distance as shown in FIG. 10C. A new link is set between e and the repair target point g. When a link has already been set between the repair target point and the link holding point, the link need not be set.

  The link optimization unit 55 releases the link set between the repair target point for which the link has been set and the reduction target point (step S65). In FIG. 10D, the link between the points a and g is released.

  Next, when the points linked to the reduction target points other than the link holding points, that is, the repair process in steps S62 to S65 is performed on all the points among the repair target points (step S66; No). When the link optimization process is finished and there is a point that has not been repaired (step S66; Yes), the process proceeds to step S62.

  Even if the link to the reduction target point is released for points other than the points b to f specified as the link holding point in FIG. 10A, a link is set for each link holding point as shown in FIG. Therefore, it is possible to prevent the link from being broken.

  As described above, according to the second embodiment, even if the link between the link reduction target point and the repair target point is released, a link from the repair target point to the link holding point is secured. It is possible to prevent cutting. Therefore, it is possible to prevent a decrease in search performance even when the graph index link is deleted.

[Third Embodiment]
Next, a third embodiment of the search device 1 will be described. Note that the description of the same functional configuration and the same processing steps as those in the first embodiment will be omitted. FIG. 11 is a block diagram showing a functional configuration of the search device 1 in the third embodiment.

  The search device 1 according to the third embodiment includes a main index 72 and a provisional index 74 as the graph index DB 70. The main index 72 and the provisional index 74 are the same as the data configuration shown in FIG. 1, and store the image ID and the link destination in association with each other as link information.

  The temporary index 74 is a database that temporarily stores link information before main registration in the main index 72, and the number of data is set to a sufficiently small number with respect to the main index 72.

  When the number of registered data in the index DB 70 becomes enormous, the graph structure of the index DB 70 becomes complicated and the number of links that circulate increases, and the processing time for searching for similar data gradually increases. Therefore, in the search device 1 having a two-stage process of searching for similar data and registering data, a waiting time for data search may occur when a plurality of data is input.

  Therefore, the search device 1 according to the third embodiment provides an index with the number of data limited as compared with the main index 72, which is a provisional index 74, and when a plurality of registered data is input, And register. Then, a plurality of registration data registered in the provisional index 74 in an appropriate time zone is registered in the main index 72 using the method described above.

  In the third embodiment, the data registration unit 50 further includes an index switching unit 52 and an additional registration determination unit 54. The index switching unit 52 performs control for selecting either the main index 72 or the provisional index 74 and switching the database target for which the DB update unit 57 updates / registers link information. Specifically, when the registration data is newly input from the registration data input unit 10, registration to the provisional index 74 is performed. Further, in the case of a plurality of registration data input from the provisional index 74, registration to the main index 72 is performed.

  The additional registration determination unit 54 determines whether or not data registered in the provisional index 74 is registered in the main index 72. As a criterion for determination, for example, the number of data registered in the provisional index 74 may reach a specified number (for example, 100). Further, it may be based on reaching a predetermined time (for example, midnight).

  When the registration data is input, the search device 1 according to the third embodiment first performs the graph self-generation process described above and stores link information in the provisional index 74. At this time, since the number of data is smaller than that of the main index, high-speed data registration can be performed.

  Further, when the registration data is input, for example, if the number of data in the provisional index 74 exceeds a predetermined number specified in advance, the vector data stored in the provisional index 74 is input as registration data, and the main index 72 Change to.

  That is, similar data for individual vector data (registered data) in the provisional index 74 is searched from the main index 72, and vector data to be linked to the similar data is specified. Then, a link is generated between the similar data searched for the plurality of vector data of the provisional index 74, and the link merge / reduction processing is performed as described above, and the vector data is stored in the main index 72 as the link destination. And the data in the provisional index 74 is deleted.

  Further, when data is stored in the temporary index 74, the graph search unit 40 searches both the main index 72 and the temporary index 74 and merges the respective search results. Although two indexes are searched at the time of searching, the size of the provisional index is small, so the decrease in search speed is small.

  In this way, by pre-registering with the temporary index 74 before registering with the main index 72, data registration can be immediately reflected in the graph index DB 70, and data search can be performed. Further, by performing registration from the temporary index 74 to the main index 72 as a batch process, it is possible to periodically create a graph index DB 70 that is linked to all data. Note that data registration can be performed at high speed by performing graph search processing on each registered data at the time of graph registration in parallel.

Next, a modification of the above-described embodiment will be described.
[Modification 1]
When the same vector data as the vector data of the registered data is already stored in the graph index DB 70, it is stored only in the image DB 60 without being stored in the graph index DB 70. Can be associated with In this case, in addition to the image ID, the graph index DB 70 is newly provided with a data item for storing the image ID of image data having the same vector data as a related ID.

  When a related ID is associated with data searched as similar data during data search, the image data indicated by the related ID can also be output as a search result. For this reason, it is possible to prevent the search speed from being lowered due to the complicated structure of the graph index due to the registration of the same vector data.

[Modification 2]
Although the search range of the graph search process is determined by a specified distance centered on the registered data, it may be determined by the number of searches that circulate from the search start point. That is, the search start point is determined by the method described above, and the link is traced from the search start point. At this time, data of a predetermined number of searches (for example, 10) is collected by link circulation. Then, each data is sorted in the order of the distance between each collected data and the registered data to obtain a list of data obtained by circulation. Vector data corresponding to the number of searches is held in this list, and the distance corresponding to the farthest vector data with respect to the registered data is updated as the search range.

  That is, as long as the search end condition is not satisfied, the link is followed, and if data closer to the registered data than the data in the list is found, the data is added to the list in the order of the distance. Then, the search range is updated according to the farthest data updated in the list by this data addition. Thus, the search range can be narrowed by updating the list with data that is close to the registered data according to the collection of data for the number of searches. For this reason, the search range can be dynamically determined according to the designation of the number of searches. Moreover, since the search range can be narrowed each time near data is searched, the search speed can be improved while maintaining the search accuracy.

[Modification 3]
The range of link circulation for determining the search start point may be determined using the method of the second modification described above. That is, the process of selecting an arbitrary point from the graph index and specifying the nearest point is regarded as a graph search process with one search, and the data closer to the registered data to be searched by link circulation is obtained. By collecting, holding and updating one, the distance between the data and the registered data is dynamically determined as the radius of the search range.

  When the link is visited, data is selected so as not to exceed the dynamically determined search range. Therefore, the search range can be narrowed while following the link to specify the search start point, and the time until the search start point is specified can be shortened.

  In addition, the link is circulated within a range that does not exceed the range (search limit range) obtained by multiplying the search range by α (α> 1), so that the range that circulates even when data close to the registered data may not be linked. As a result, the optimum search start point can be identified.

[Modification 4]
Since the data circulated when determining the search start point may be the final search result, the distance calculated in step S434 in FIG. The distance calculation process can be omitted by referring to the history.

  The operations of the above-described embodiments can be implemented by incorporating appropriate computer software into the computer. For example, each component described above may exist as a functional block, and may not exist as independent hardware. As a mounting method, hardware or computer software may be used. Furthermore, one functional element in the present invention may be realized by a set of a plurality of functional elements, and a plurality of functional elements in the present invention may be realized by one functional element.

  Moreover, the functional element may be arrange | positioned in the position physically separated. In this case, the functional elements may be connected by a network. It is also possible to realize functions or configure functional elements by grid computing.

The block diagram which shows an example of a function structure of the search device in 1st Embodiment. The flowchart for demonstrating the processing content of the graph self-generation process in 1st Embodiment. The flowchart for demonstrating the processing flow of the search start point determination in 1st Embodiment. The schematic diagram which shows the specific example of the process of the determination of the search start point in 1st Embodiment. The schematic diagram which shows the specific example of the process of searching for similar data in 1st Embodiment. The schematic diagram which shows the specific example of the processing content of the temporary link production | generation process and link optimization process in 1st Embodiment. The schematic diagram which shows the specific example of the link production | generation process in 1st Embodiment. The schematic diagram which shows the specific example of the link optimization process in 1st Embodiment. The schematic diagram which shows the specific example of the processing content of the link optimization process in 2nd Embodiment. The schematic diagram which shows the specific example of the link optimization process in 2nd Embodiment. The block diagram which shows the function structure of the search device in 3rd Embodiment.

DESCRIPTION OF SYMBOLS 1 Search apparatus 10 Registration data input part 20 Search data input part 30 Search result output part 40 Graph search part 41 Vector data generation part 43 Search start point determination part 45 Graph circulation part 47 Similar data specification part 50 Data registration part 51 Similar data acquisition Unit 53 merge unit 55 link optimization unit 57 DB update unit 60 image DB
70 Graph Index DB
72 Main index 74 Provisional index

Claims (6)

A database in which a link for tracing from one data to the other data is set between the data and a plurality of the data is stored;
For the input search target data, select any of the data stored in the database as a search start point, and sequentially follow the link from the search start point to A graph search means for searching and outputting the data within a predetermined distance from the data to be searched as similar data among the data in
By inputting the data to be registered in the database as the search target to the graph search means, the similar data for the registration target data is obtained, and a link is established between the registration target data and the similar data. Similar data acquisition means to be generated;
Merge means for merging the links respectively generated by the similar data acquisition means for a plurality of registration target data;
Link optimization means for performing a reduction process on the link merged by the merging means and the link already set on the database in the data generated by the link;
Updating the link information of the database based on the result of the reduction process, and storing the data to be registered in the database;
A search data management device comprising: The link optimization means includes:
The search according to claim 1, wherein the reduction processing is performed based on a total number of links merged by the merging means and links already set in the database in the data in which the links are generated. Data management device. The link optimization means includes:
3. The reduction processing is performed based on a length of a link merged by the merging unit and a link already set on the database in the data in which the link is generated. The described search data management device. The link generation means includes
The search data management apparatus according to any one of claims 1 to 3, wherein a link is further generated between each of the plurality of registration target data. In a search data management method in which a link for tracing from one data to the other data is set between the data, and a computer manages a database in which a plurality of the data is stored as a data group to be searched,
For the input search target data, select any of the data stored in the database as a search start point, and sequentially follow the link from the search start point to A graph search step of searching for and outputting similar data to data within a predetermined distance from the data to be searched among the data in
By inputting the data to be registered in the database as the search target to the graph search means, the similar data for the registration target data is obtained, and a link is established between the registration target data and the similar data. A similar data acquisition process to be generated;
A merge step of merging the links respectively generated by the similar data acquisition step for a plurality of registration target data;
A link optimization step for performing a reduction process on the link merged in the merging step and a link already set on the database in the data in which the link is generated;
A data update step of updating the link information of the database based on the result of the reduction process and storing the registration target data in the database;
A search data management method comprising:   The program for making a computer perform the process of the search data management method of Claim 5.

Images