JP2010282360A - Retrieval system and retrieval method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a retrieval system and a retrieval method, which reduce the computational complexity of a server while reducing traffic even in a poor network environment. <P>SOLUTION: The client-server retrieval system includes: an information management device including a database and managing a data change history by version; and an information terminal device connected to the information management device via a communication line, including a database constituted of the version and the data obtained in synchronization with the information management device. The information management device obtains a difference of the data between the information terminal devices by version in response to a retrieval request from the information terminal device, retrieves only difference data thereof, and transmits a retrieval result to the information terminal device. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a search system, and more particularly to a search system and a search method in a client-server database.

  Recently, in home appliances and the like, it is required that embedded device products have high functionality and the device itself becomes a server. On the other hand, a client device using a server often has performance similar to or higher than that of a server device, but it is still not sufficient in a network environment surrounding these devices. Although the client device has high performance, the server device is not so high, and the network environment is at a low level.

  When the network environment is fast and inexpensive, it is desirable to synchronize the data held in the database between the client device and the server. When synchronizing, for example, in a situation where wired use is possible, there is no communication problem, but when the client device is far away from the server, problems such as communication costs and traffic become a bottleneck.

  A database update method that reduces the amount of processing of a server has been proposed (see, for example, Patent Document 1). This realizes high-speed version upgrade by the server while ensuring the uniqueness of the client, and uses the difference between the logical copy and the physical copy (memcpy) whose contents are update processing.

  In addition, as a device for reducing the amount of synchronization for updating the database, SQL Anyway / Ultra Right that takes differential synchronization is well known (for example, see Non-Patent Document 1).

  These are contrivances for complete synchronization, and it is possible to specify which data is to be synchronized. For example, it is possible to specify a synchronization target table in units of tables. In addition, a conflict is resolved by describing a resolution rule in a database update conflict from a plurality of clients at the time of update.

JP 2009-20873 A

Release of the latest version of RDBMS package "SQL Anywhere 10" Japanese version 2007/05/10 20:05: <URL: http://codezine.jp/article/detail/1328?p=1/>

  Recently, however, devices that serve as clients often have database functions due to the high performance of mobile phones and portable players and the advent of UMPC. It is difficult to demand high performance from devices, and it is not possible to cope with cases where the network environment is not sufficient.

  Therefore, the present invention has been made in view of the above problems, and provides a search system and a search method that require a small amount of communication and a small amount of server processing even when the network environment is not sufficient.

  According to one aspect of the present invention, an information management device that includes a database and that manages version changes of data is connected to the information management device via a communication network, and is synchronized with the information management device. A client server type system search system comprising an information terminal device having a database composed of data and a version acquired in the information management device, wherein the information management device responds to a search request from the information terminal device. There is provided a search system characterized in that a difference in data with a terminal device is grasped by a difference in version, only a search for the difference data is executed, and a search result is transmitted to the information terminal device.

  According to another aspect of the present invention, the information management device includes a database and manages the data change history by version, and is connected to the information management device via a communication line network. A search method in a client server type system comprising an information terminal device having a database composed of data acquired in synchronization with a device and a version, wherein the information terminal device is synchronized with a database of the information management device Version information is transmitted to the information management device, and the information terminal device receives certain deletion data information from the information management device based on a version difference with the information management device, and the information terminal device And deleting the certain deletion data from the database based on the deletion data information, and the information management device The information terminal device receives a search result for the difference data from the information management device, and performs a search on the database after the fixed data deletion. A search method is provided that performs a search.

  According to the present invention, even when the network environment is not sufficient, the amount of communication between the client device and the server can be reduced, and the amount of processing for the server to care for the client device can be reduced. A search system can be constructed even if the server device is not a dedicated device.

It is a conceptual diagram which shows the structural example of the client server system which concerns on embodiment of this invention. It is a functional block diagram of the client server system which concerns on embodiment of this invention. It is a schematic diagram for demonstrating the update and version of a database in the client server type | mold search system which concern on 1st Embodiment. It is a flowchart which shows the flow of the request process with respect to the information management apparatus of an information terminal device. It is a flowchart which shows the flow of the update request process of the information terminal device which is a user of an information management apparatus. It is the figure which modeled the structure (contents) of the database. It is the figure which modeled the comparison of the data amount. It is the figure which modeled the comparison of the data amount. It is the figure which modeled the comparison of the data amount. It is the figure which modeled the comparison of the data amount. It is a figure which illustrates the change of the structure (contents) of a database when addition of a change history is made. It is a flowchart which shows the flow of the update process of the change log column at the time of change occurrence. It is a figure which illustrates the change of the structure (contents) of the database in a synchronous process. It is a figure which illustrates the change of the structure (contents) of the database in invalidation processing. It is a figure which illustrates the change of the structure (contents) of the database at the time of a search request | requirement. It is a figure which illustrates the change of the structure (contents) of the database in search execution. It is a flowchart which shows the flow of the difference grasp process in the information management apparatus side. It is a flowchart which shows the flow of the difference removal process in the information terminal device side. It is a flowchart which shows the flow of the difference search process in the information terminal device side. It is a flowchart which shows the flow of the difference search process in an information management device. It is a figure explaining the search process from the difference data using a change log | history. It is a schematic diagram for demonstrating the update and version of a database in the client server type search system which concern on 2nd Embodiment. It is a flowchart which shows the flow of the update process of the change log column at the time of change occurrence. It is a flowchart which shows the flow of the update process of the change log column at the time of change occurrence. It is a flowchart which shows the flow of the update process of the change log column at the time of change occurrence. It is a flowchart which shows the flow of the whole change history process after receiving an update request. It is a schematic diagram for demonstrating the update and version of a database in the client server type | mold search system which concern on 3rd Embodiment. It is a flowchart which shows the flow of the update process of the change log column at the time of change occurrence. It is a flowchart which shows the flow of the summarization process by the superordinate concept of a change history. It is a figure explaining the client server type | mold search system which concerns on 4th Embodiment. It is a flowchart which shows the flow of the difference search process in an information management device. It is a figure explaining the client server type | mold search system which concerns on 5th Embodiment. It is a flowchart which shows the flow of the difference search process in an information management device. It is a flowchart which shows the flow of the determination process of transmission data.

  Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In the drawings, the same portions are denoted by the same reference numerals, and redundant description is omitted.

  The present invention can search the latest data with much smaller communication volume compared to complete synchronization and all server inquiries, the server processing amount is small, even a low-spec device can become a server, and the server cost can be reduced. It is possible to obtain a search system.

  FIG. 1 is a conceptual diagram showing a configuration example of a client server system according to an embodiment of the present invention. As shown in FIG. 1, the client server system 100 includes an information management device 2 serving as a server and an information terminal device 1 serving as a client device in, for example, the Internet network or a wireless communication network 3. An information management apparatus (also referred to as a server in the following description) 2 is connected to a database 24 as shown in FIG. The database 24 is updated each time, and the current version and change history are managed. The information management device 2 does not have to be a dedicated device. Even so-called home appliances may be connected to a network, manage versions, and perform server functions. Further, the change history is grasped by each version and the ID of data targeted by the version. Details of these will be described later.

  The information terminal device (also referred to as a client in the following description) 1 is preferably a mobile phone or a mobile player as long as it has a database function. This is what is called an ultra mobile PC. As shown in FIG. 1, each information terminal device 1 is also connected to the database 14, but the database 14 is a version when synchronized with the database 24 of the information management device 2.

  FIG. 2 is a functional block diagram of the client server system 100 according to the embodiment of the present invention. The information management device 2 includes a connection unit 21 and a database 24, receives a request from the information terminal device 1, and transmits a result. The connection unit 21 communicates with the information terminal device 1 via the Internet network. The information terminal device 1 includes a user interface 10, a connection unit 11, and a database 14. The user interface 10 receives a user request and displays the result. The connection unit 11 communicates with the information management device 2 via the Internet network.

  Furthermore, the information management apparatus 2 includes an instruction control unit 22 and an SQL execution unit 23. The command control unit 22 issues a command to the SQL execution unit 23 and the connection unit 21 in response to a request from the information terminal device 1 and displays the result on the user interface 10. The commands include connection reception, difference notification, SQL reception, result transmission, synchronous transmission, and connection stop. The SQL execution unit 23 performs operations and definitions on the database 24 in accordance with requests from the instruction control unit 22 using SQL statements that are instructions for the database 24. The database 24 holds data 241, a change history 243, and a version 242 that have been added / changed / deleted by operation from the information terminal device 1. Furthermore, the information terminal device 1 has an instruction control unit 12 and an SQL execution unit 13. The command control unit 12 issues a command to the SQL execution unit 13 and the connection unit 11 in response to a request from the user interface 10 and displays the result on the user interface 10. The commands include connection start, difference removal, difference search, result acquisition, synchronous reception, and connection end. Details will be described later. The SQL execution unit 13 performs an operation on the database 14 in accordance with a request from the instruction control unit 12 using an SQL sentence that is an instruction for the database 14. The database 14 holds data 141 and a version 142 acquired in synchronization with the information management apparatus 2. The terms used in this embodiment are understood in the following meanings unless otherwise specified. “Synchronization” means a state in which data in the database is shared between the server and the client device, or processing for sharing. “Difference grasp” means that the difference between the data of the client and the server is grasped from each other version so that duplicate data is not searched in the search processing. “Differential search” refers to a search for differential data, that is, data that is not synchronized, and is executed by the server. Incidentally, it does not search for differences. The “change history” manages the difference of data in the database changed in the change history. The change history has a set of “version” and “data ID”. “Version” is a number that is uniquely issued on the server side, and one version is raised when the data in the database is changed. In this embodiment, “version” is a mechanism for simplifying “difference grasp” and “difference search”.

  Hereinafter, the description will be divided into several embodiments.

(First embodiment)
FIG. 3 is a schematic diagram for explaining the update and version of the database in the client server type search system according to the first embodiment. When the database is updated in the information management device 2 that is a server, the information terminal device 1 that is a client device is incremented by one (the version is incremented by one) with respect to the current version. The content of the update is managed as a change history. The change history is made up of the version and the ID of the target data. Along with the update, a difference graspable range is set. This difference graspable range means a range in which a difference search is possible. This is to cope with the case where a client device that holds only an extremely old version of the database is cared for. When a search is performed on a database owned by the client device, there is a possibility that deleted or changed data still exists as a result of the database already being updated on the server side. It is completely meaningless to search for these deleted or changed data. Therefore, before performing a search on the database owned by the client device, the client device performs “invalidation processing” on the corresponding data. The “invalidation process” performs “difference grasp” at the server, and the client device receives the corresponding data ID from the server and performs the “invalidation process”. In “difference search”, an inquiry is made between the information management device and the information terminal device as to whether or not there is a difference in the data of each database. The information management device searches for the difference data from the “change history” and transmits the search result to the information terminal device.

  FIG. 4 is a flowchart showing a flow of a request process for the information management device of the information terminal device which is a user in the search system configured as described above. First, the information management device performs connection processing from the information terminal device (step S41). The information management device determines whether or not there is still processing (step S42). If there is no process, the connection / disconnection process which cancels | releases a connection with an information terminal device is performed (step S46). If there is a process (if YES), it is determined whether or not it is an update process (step S43). If YES, update processing is executed (step S44). If NO, search processing is executed (step S45). After executing the update process or the search process, the process returns to step S42.

  FIG. 5 is a flowchart showing the flow of the update request process of the information terminal device that is the user of the information management device. The information management apparatus receives a data update request from the information terminal apparatus and executes an update process (step S51). Along with the update, the information management apparatus updates the change history (step S52). The result for the data update request is returned (step S53), and the update completion is returned from the information management device to the information terminal device.

  FIG. 6 is a diagram schematically showing the structure (contents) of the database. The database shown in FIG. 6 is hierarchized as “Table”, “Page”, and “node”. For example, if you consider a database of “books” stored in a library, “Table” is a “city library”, “Page” is a “book shelf”, and “node” is an individual “book”. . Now, the database of the server is updated, the version is “3”, and “node4” is removed from the bookshelf of “Page B” by the update. The client version is “1” and does not match the server version.

  Under this situation, the flow of data search processing will be described. First, the client device makes an inquiry about the current version to the server. Upon receiving the version inquiry, the server checks the change history and searches for the changed node. Then, since the server is version 3 and “node4” has been changed, the client device is informed that “node4” is deleted data as a difference grasp. The client device that has received the grasp of the difference from “Page B” invalidates “node 4” from its own database. The client device searches all cases for the invalidated database. On the other hand, the server performs an all-case search for “node4”, which is difference data from the version 1 of the client device, that is, a differential search for determining whether or not the search condition is satisfied for “node4”. The client device that has received the result of the differential search can obtain the search result for the latest database.

  In order to search for the latest data, communication is always required between the server and the client device. According to the difference grasp and difference search, it is possible to realize a search for the latest data with a much smaller communication volume than complete synchronization or all server inquiries. Generally, this is because the complete synchronization data amount ≧ the difference search result data amount and the total search result data amount ≧ the difference search result data amount. FIG. 7 to FIG. 10 schematically show comparison of these data amounts. FIG. 7 exemplifies that the server and the client device are located at a short distance, and that the communication environment between them can perform high-speed communication. In this case, it is preferable to completely synchronize the update of both databases. It can be said that there is no problem even in the differential synchronization. FIG. 8 exemplifies the situation of all inquiries in which search is entrusted to the server without searching in the client device. In this case, the server performs a search on a database having a data capacity of 1 Gbyte and obtains a search result of 1 Mbyte. Therefore, the hit rate is h = 0.1%. Here, the search result is sent to the client device as it is, but since the communication capacity is not so large, it can be said that there is no problem even in low-speed communication. FIG. 9 illustrates the synchronization of difference data between the server and the client device. As a result of updating the database of the server, the situation where the difference data before and after the update is 1 Mbyte is illustrated. The difference ratio of the 1 Mbyte difference data with respect to the database before the update is 0.1%. Since the 1-Mbyte difference data is not so large as a communication capacity, it can be said that there is no problem even in low-speed communication. The client device executes a search on the 1 Gbyte database to which the received 1 Mbyte difference data is added, and obtains a 1 Mbyte search result. Next, FIG. 10 illustrates the difference search. 100 bytes are sent as a difference ID group from the server to the client device. The difference ID group means a group of IDs of data to be invalidated. Furthermore, the server extracts 1 Mbytes of difference data based on the change history, and executes a difference search for the client device. The obtained 1 Kbyte difference search result is sent to the client device. On the other hand, the client device updates its own database based on the difference ID group and executes a search. The client device obtains a 1 Mbyte search result together with the 1 Kbyte difference search result. For example, if one data length is 4000 bits and the data ID length is 4 bits, an information amount of 1/1000 is sufficient to specify a certain ID. Therefore, since the data capacity of the difference ID group and the difference search result is extremely small, there is no problem even in the low-speed communication, and this is particularly suitable when one data is large and the difference ratio is small.

  Next, how the structure (contents) of the database changes with the processing described above will be exemplified with reference to the drawings. FIG. 11 illustrates a change in the structure (contents) of the database when a change history is added. This is processing when the client device has a database and is synchronized. Now, a change has been made to the server database to add “node4” to “Page B”. With this change, the latest version is updated from “3” to “Ver = 4” in the change history column, and “node4” is updated as the change content. FIG. 12 is a flowchart showing the flow of update processing in the change history column when a change occurs. As shown in FIG. 12, the changed node = node4 is added to the change history column. And the version is incremented by one. FIG. 13 illustrates a change in the structure (contents) of the database in the synchronization process. The server version is “4”, while the client device version is “3”. Therefore, the updated “node4” data is sent to the client device together with the version information of the server from the change history. In the client device, the content of “node4” is updated.

  FIG. 14 illustrates a change in the structure (contents) of the database in the invalidation process. The version of the client device is “3”. The server confirms deletion of its current version “4” and its change content “node4” from the change history. The server version information and difference ID group information are sent to the client device. The client device deletes “node4”, which is a difference from version “3”, in order to reflect the contents of version “4” in the database it holds.

  FIG. 15 illustrates a change in the structure (contents) of the database at the time of a search request. The SELECT for the server database is a SELECT statement WHERE Ver> 3 AND Ver ≦ 4. The search (search) for the database with version “3” is assigned to the client device itself, and the search (search) reflecting version “4” is assigned to the server.

  FIG. 16 exemplifies a change in the structure (contents) of the database in the search execution. As shown in FIG. 16, when an instruction represented by SELECT statement WHERE Ver> 3 AND Ver ≦ 4 is issued to the database of the server, a search is performed for “node4” which is the modified content of version “4”. The search result S is sent to the client device. On the other hand, the client device executes a search for the database with version “3” by the SELECT statement, and obtains a search result C. Therefore, the search result C + search result S can be obtained as the search result for the latest data.

  Next, the flow of each process executed by the information management device and the information terminal device in the search system will be described in detail.

  FIG. 17 is a flowchart showing the flow of the difference grasping process on the information management apparatus side.

First, the version of the information terminal device: Vc is acquired (step S1701). Next, the information management apparatus version: Vs is acquired (step S1702). Next, the two versions are compared (step S1703). If Vc = Vs, Vs and the result: R = “no change data” is notified to the information terminal device (step S1705). If Vc = Vs, the difference graspable range: Va is acquired from the change history (step S1704). Next, it is determined whether Va> Vc (step S1706). If Va> Vc, the information terminal device is notified of the result: R = “difference search not possible” (step S1711). If Va> Vc, the change ID is created from the database using the change history (step S1707). Next, it is determined whether or not the change is only deletion (step S1708). If the change is not only deletion, Vs and the difference ID: IDs are notified to the information terminal device (step S1709). If the change is only deletion, the result: R = “differential deletion only” Vs and the difference ID: IDs are notified to the information terminal device (step S1710).

  FIG. 18 is a flowchart showing the flow of difference removal processing on the information terminal device side. First, the result ID R of the information management device is acquired (step S1801). Next, it is determined whether or not R = “difference deletion only” (step S1802). If R = “difference deletion only”, the difference IDs are acquired (step S1803). Subsequently, data corresponding to IDs is deleted from the database (step S1804). Subsequently, the server flag is set to OFF (step S1805). This server flag indicates whether or not it is necessary to make a search request to the server, and is turned ON when a search request is made to the server. Subsequently, Vc = Vs is set (step S1806). Then, the difference comprehension completion flag is set to ON (step S1807). On the other hand, if R is not “difference only”, it is first determined whether R = “difference search not possible” (step S1808). If R = “difference search not possible”, it is subsequently determined whether R = “no change data” (step S1809). If R = “no change data”, the difference IDs are acquired (step S1810). Subsequently, the data corresponding to IDs is deleted from the database (step S1811). Subsequently, after setting the server flag = ON (step S1812), the process proceeds to step S1807. On the other hand, if R = “difference search not possible”, the server flag is set to ON (step S1813). Subsequently, after setting Vc = 0 (step S1814), the process proceeds to step S1807. If R = “no change data”, the server flag is set to OFF (step S1815). Subsequently, after setting Vc = Vs (step S1816), the process proceeds to step S1807.

  FIG. 19 is a flowchart showing the flow of the difference search process on the information terminal device side.

First, it is determined whether or not the difference grasp completion flag = ON (step S1901). If the difference grasping completion flag is not ON, connection processing (passing Vc to the information management apparatus) is performed (step S1902). Subsequently, the difference ID is transmitted and received (step S1903), and the difference ID is removed (step S1904). On the other hand, if the difference grasping completion flag = ON, it is determined whether Vc ≠ 0 (step S1905). If Vc ≠ 0, a search is executed from the database of the information terminal device (step S1906). Next, it is determined whether or not the server flag is ON (step S1907). On the other hand, if Vc ≠ 0, the process immediately proceeds to step S1907 to determine whether or not the server flag is ON. If the server flag is ON, a search is performed from the information management apparatus (step S1908). Then, the search result is displayed (step S1909). FIG. 20 is a flowchart showing the flow of the difference search process in the information management apparatus. First, in response to a search request to the information management apparatus, an SQL sentence is created on the information terminal apparatus side using Vc and Vs (step S2001), and the SQL sentence is transmitted to the information management apparatus side (step S2002). On the information management apparatus side, when an SQL sentence is received (step S2003), a search is executed from the difference data using the change history (step S2004). The information management device transmits the search result (step S2005), and the information terminal device acquires the search result (step S2006). FIG. 21 is a diagram for explaining search processing from difference data using the change history in step S2004 described above. When the information management apparatus receives an SQL statement of SELECT WHERE 2 <Ver AND Ver ≦ 4 (step S2101), the information management device executes the SELECT statement (step S2102). In the example illustrated in FIG. 21, from the change history, node 3 is changed in version 3 and node 4 is changed in version 4. Therefore, it can be seen that the difference search to be executed by the information management apparatus is only the node 2 and the node 4 as search targets. Therefore, the time required for the search is extremely short. As described above, according to the present embodiment, since the difference processing is performed, the number of search targets is small, and the data size of the difference search result is much smaller than the difference data size, so that the processing amount of the server can be significantly reduced. Can care for client equipment. Furthermore, the latest data can be grasped efficiently by version management.

  On the client side, invalidation processing is performed as pre-processing for search, so efficient search is possible. Further, since the processing amount of the server is small, it is possible to use a low-performance device as a database server, so that an inexpensive search system can be constructed.

(Second Embodiment)
FIG. 22 is a schematic diagram for explaining the update and version of the database in the client server type search system according to the second embodiment. In other words, the second embodiment aims to reduce the memory required for managing the change history. Therefore, (1) If the change history column is full, delete the old one. (2) If the same data ID exists in the change history column, summarize it to the latest one. If the version is out of range, the main point is not to search for differences. FIG. 23 is a flowchart showing the flow of update processing in the change history column when a change occurs, and in the case of a change only for deletion. First, the changed node = node4 is added to the change history column (step S2301). Next, it is determined whether there is any change other than deletion (step S2302). If YES, the DELETE ONLY flag is turned on (step S2303). Here, a change that only deletes node 4 is made as version “3”, and the DELETE ONLY flag is set to ON. Next, the version is incremented by 1 (step S2304). FIG. 24 is a flowchart showing the flow of updating the change history column when a change occurs and saving data. First, the changed node = node4 is added to the change history column (step S2401). Next, it is determined whether or not the same data ID exists in the change history (step S2402). If YES, the old change history is deleted (step S2403). Here, since the change for node 4 has been made in version “2” in the past, the history of version “2” is deleted and the change history for node 4 is compiled into version “4”. . Next, the version is incremented by 1 (step S2404). FIG. 25 is a flowchart showing the flow of updating the change history column when a change occurs, and deleting old difference information. First, the changed node = node4 is added to the change history column (step S2501). Next, it is determined whether or not the change history is full (step S2502). If YES, the old difference information is deleted (step S2503). Here, the change history of version “1” for node 12 is deleted. When the change history of version “1” is erased, the oldest version of the change history: Vo is substituted for the difference graspable range: Va (step S2504). Here, the oldest version is “2”, and the difference comprehensible range is also version “2”. Next, the version is incremented by 1 (step S2505).

  FIG. 26 is a flowchart showing the flow of the entire change history process after receiving an update request from the user.

  First, after receiving an update request, update processing is executed (step S2601). Next, the changed node is added to the change history (step S2602). Next, the server version is incremented by 1 and Vs = Vs + 1 is set (step S2603). Subsequently, it is determined whether there is any change other than deletion (step S2604). If only deletion, the DELETE ONLY flag is turned ON (step S2605). After setting the flag, it is determined whether there is the same ID in the change history (step S2606). If there are changes other than deletion, the process moves to step S2606. If there is the same ID in the change history, the old change history is deleted (step S2607). After deletion, it is determined whether the change history is full (step S2608). If there is no same ID in the change history, the process proceeds to step S2608. If the change history is full, the old difference information is deleted (step S2609), and the oldest version of the change history is substituted into the possible difference range (step S2610). Next, the change history is summarized by a superordinate concept (step S2611), and the result is returned (step S2612). If the change history is not full, the process moves to step S2611 and subsequent steps. According to the second embodiment, in addition to the effects of the first embodiment, the change history can be managed more efficiently.

(Third embodiment)
FIG. 27 is a schematic diagram for explaining the update and version of the database in the client-server search system according to the third embodiment. The third embodiment aims to more efficiently perform the process associated with version upgrade. For this reason, the change history is managed in a higher concept, for example, in units of Tables or Pages in FIG.

  FIG. 28 is a flowchart showing the flow of update processing in the change history column when a change occurs. First, the changed node = node4 is added to the change history column (step S2801). Next, it is determined whether or not those belonging to the same Page are equal to or greater than a certain value (step S2802). If it is equal to or greater than a certain value, the ID of the same Page is deleted (Step S2803), and the Page ID is added (Step S2804). Here, the change history for node 12 and node 13 is superordinated as version “4” for page A as the change target. Next, the version is incremented by 1 (step S2805).

  FIG. 29 is a flowchart showing the flow of the summarization process based on the superordinate concept of the change history.

First, the IDs of the same page are counted (step S2901). It is determined whether or not the pages can be collected (step S2902). If the pages are grouped together, the ID of the same page is deleted from the change history (step S2903). Next, IDs of the same table are counted (step S2904). If the pages cannot be collected, the process immediately proceeds to step S2904. Next, it is determined whether or not the data is grouped in the table (step S2905). If the tables are grouped together, the IDs of the same table are deleted from the change history (step S2906), and the summarization based on the superordinate concept is terminated. Even when it cannot be summarized by Table, the summary of the superordinate concept is terminated.

  As a device for simplifying the version upgrade in the information terminal device, the data ID is received regarding the difference grasp, the DELETE ONLY flag is checked, and if the flag is set, the difference data is received. It is possible to update the version or update the difference data when it is received. According to the third embodiment, it is possible to more efficiently perform processing associated with version upgrade.

(Fourth embodiment)
FIG. 30 is a diagram for explaining a search system according to the fourth embodiment. In the fourth embodiment, in order to further reduce the communication amount of the search result in the information management device, regarding the difference search, when it is determined that synchronization is determined from the search result and difference data, and it is better to synchronize, Synchronous data is transmitted, and such synchronization determination may be performed step by step. Here, as shown in FIG. 30, the data size of the difference data Ds and the difference search result Rs are compared. FIG. 31 is a flowchart showing the flow of difference search processing in the information management apparatus. First, in response to a search request to the information management apparatus, the information terminal apparatus creates an SQL sentence using Vc and Vs (step S3101), and transmits the SQL sentence to the information management apparatus (step S3102). On the information management apparatus side, when an SQL sentence is received (step S3103), a search is executed from the difference data using the change history (step S3104). Next, the difference data size: Sd is acquired (step S3105). Subsequently, the search result data size: Sr is acquired (step S3106). Then, for difference data size: Sd and integral difference search data size: ΣSr, it is determined whether Sd> ΣSr (step S3106). If Sd> ΣSr is not satisfied, the information management device transmits difference data instead of the search result (step S3108), and if Sd> ΣSr, the search result is transmitted (step S3109). The information terminal device acquires data (step S3110) and determines whether the data is difference data (step S3111). If it is difference data, the difference data is updated in the database (step S3112). Vc = Vs is set (step S3113), and the server flag is set to OFF (step S3114).

  There is a possibility that the search result data becomes larger than the difference data by repeated search. In such a case, (accumulated difference search result data size) ≤ (difference data size), and sending the accumulated difference search result data size results in a smaller amount of data. Is special. On the other hand, if (accumulated difference search result data size)> (difference data size), the difference data is sent and the subsequent communication amount is set to be zero. According to this embodiment, the communication amount due to repetition is reduced. be able to. In the above description, the determination based on the magnitude relationship between the integrated search result data and the difference data has been described. However, the determination is not limited thereto. For example, comparison may be made with 80% of the difference data, or a search request may be predicted.

(Fifth embodiment)
In the fifth embodiment, the communication amount of the search result in the information management apparatus is further reduced. FIG. 32 is a diagram for explaining a search system according to the fifth embodiment. Here, as shown in FIG. 32, the difference data Ds and the total size of the difference search result Rs are compared with the data for each version.

  FIG. 33 is a flowchart showing the flow of difference search processing in the information management apparatus.

First, in response to a search request to the information management apparatus, an SQL sentence is created on the information terminal apparatus side using Vc and Vs (step S3301), and the SQL sentence is transmitted to the information management apparatus side (step S3302). On the information management device side, when an SQL sentence is received (step S3303), N = N + 1 is counted up (step S3304), and then a search is executed from the difference data using the change history to create data (step S3305). ). The information management device transmits transmission data: S to the information terminal device (step S3306). The information terminal device acquires data (step S3307) and determines whether there is difference data in the data (step S3308). If there is difference data, the difference data is updated in the database (step S3309). Vc = Vd is set (step S3310), and it is determined whether Vc = Vs (step S3311). If Vc = Vs, the server flag is set to OFF (step S3312). On the other hand, if there is no difference data in the data, the process proceeds to step S3312. If Vc = Vs is not satisfied, the process ends.

  Next, transmission data determination by comparing the search result and the synchronization data will be described. FIG. 34 is a flowchart illustrating a flow of transmission data determination processing. First, i = Vc + 1 is set (step S3401). Next, it is determined whether Vs = i (step S3402). If Vs = i is not satisfied, i = i + 1 is set (step S3403), and when the difference data amount of version i is Dd, Sd = Sd + Dd is set (step S3404). Next, it is determined whether or not the difference data of i hits the search (step S3405). If there is a hit, the difference search result data amount i of i: Rd is obtained (step S3406), and then added to the integrated search result data amount Sr, so that Sr = Sr + Rd (step S3407). Subsequently, it is determined whether or not Sd> Sr (step S3408). If the difference data of i does not hit the search in step S3405, the process proceeds to step S3408. If Sd> Sr, it is ensured to which version the difference is sent, and Vd = i is set (step S3409). Thereafter, the process returns to step S3402. If Sd> Sr, the process immediately returns to step S3402.

  On the other hand, if Vs = i, the version difference data up to Vd is copied to the transmission data: S (step S3410). Subsequently, the search result after Vd is additionally copied to the transmission data: S (step S3411).

  According to the fifth embodiment, a partial version upgrade is performed, so that the amount of difference search processing can be reduced and the amount of difference data can be reduced. Further, the subsequent communication amount can be reduced. In the above description, the determination based on the size relationship between the difference data and the total size of the difference search results has been described. However, the present invention is not limited to this. For example, comparison may be made with 80% of the difference data, or a search request may be predicted.

  Note that the present invention is not limited to the above-described embodiments as they are, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage. Moreover, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the above embodiments. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, constituent elements over different embodiments may be appropriately combined.

  DESCRIPTION OF SYMBOLS 1 ... Information terminal device, 10 ... User interface, 11 ... Connection part, 12 ... Command control part, 13 ... SQL execution part, 14 ... Database, 2 ... Information management apparatus, 21 ... Connection part, 22 ... Command control part, 23 ... SQL execution unit, 24 ... database, 100 ... client server system.

Claims (13)

An information management device that has a database and manages the data change history by version, and is connected to the information management device via a communication network, and consists of data and version acquired in synchronization with the information management device A client-server system search system comprising an information terminal device equipped with a database,
In response to the search request from the information terminal device, the information management device grasps the difference in data from the information terminal device by the difference in version, executes only the search for the difference data, and sends the information to the information terminal device. A search system characterized by transmitting a search result.   The search system according to claim 1, wherein the change history manages a difference in data by a combination of a version and a data ID.   The search system according to claim 1 or 2, wherein the version is uniquely issued on the information management device side and is upgraded every time data is changed.   The information terminal device receives a data ID of differential data that has already been changed from the database on the information management device side by update or deletion, and executes a search after deleting the data from its own database. The search system according to any one of claims 1 to 3.   The search system according to any one of claims 1 to 4, wherein when the same data ID exists in the change history, the latest changes are collected.   6. The search system according to claim 1, wherein when the change history exceeds a certain value, the oldest difference data is deleted.   The search system according to any one of claims 1 to 6, wherein the information management device does not search for the difference data if the difference data is out of a graspable range.   8. The database according to any one of claims 1 to 7, wherein the database is hierarchized, and if the change of data belonging to the same hierarchy is a predetermined value or more, the change history is regrouped in a higher concept. The described search system.   2. The version management in the information terminal device is performed when a data ID is received from the information management device and a change only in deletion can be confirmed or when difference data is received. 9. The search system according to any one of items 1 to 8.   In the information management device, the difference data is compared with the data size of the result of the difference search. If the difference data is small, the difference data is transmitted to the information terminal device, and the information management device and the information terminal device database are transmitted. The search system according to any one of claims 1 to 9, wherein synchronization is performed so as to hold the same data.   11. The search system according to claim 10, wherein the comparison between the difference data and the data size of the difference search result is executed in total for the data for each version.   12. The information terminal device according to claim 1, wherein the information terminal device selectively uses database synchronization and a search request for the difference data to the information management device according to an environment of a communication network with the information management device. The search system according to any one of the above. An information management device that has a database and manages the data change history by version, and is connected to the information management device via a communication network, and consists of data and version acquired in synchronization with the information management device A search method in a client server type system comprising an information terminal device equipped with a database,
The information terminal device transmits version information when synchronized with the database of the information management device to the information management device,
The information terminal device receives certain deletion data information from the information management device based on a version difference with the information management device,
The information terminal device, based on the deleted data information, deletes the certain deleted data from the database,
The information management device executes a search for difference data grasped based on a version difference,
The information terminal device receives a search result for the difference data from the information management device, and executes a search for the database after the fixed data deletion.