JP2009211514A - Related information obtaining system, related information obtaining method, and related information obtaining program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a related information obtaining system which can add or define an application for obtaining user operation as a decision subject. <P>SOLUTION: The related information obtaining system includes: an application monitoring means which is set corresponding to each of applications, monitors user operation for the corresponding application and obtains operation information in accordance with a monitoring rule; a user operation monitoring and controlling means which stores the operation information obtained by the application monitoring means as information forming an operation history in an operation history recording section; and a user operation comparing means which obtains relationship between the operation information by comparing the operation information stored in the operation history recording section in accordance with a comparing rule. The monitoring rule corresponding to each of the applications is stored in a monitoring rule memory section. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a relational information acquisition system, a relational information acquisition method, and a relational information acquisition program, and in particular, by making a determination method for determining a relation between information based on a user's operation history, And a relation information acquisition system, a relation information acquisition method, and a relation information acquisition program that can add a user's operation target as a determination material and a criterion for determining a relation.

  Due to the increase in the storage capacity of computers and the spread of networks, the amount of information handled when working on computers has become large. For example, when creating a report, work is often done while referring to related past reports and reference materials. The task of calling it is becoming difficult.

  A technology aimed at addressing such problems by associating and managing information such as digitized documents so that when information is called, the information associated with the information can be called with less effort. Has been proposed.

  Patent Document 1 discloses a technique that aims to be able to collectively handle necessary related information for each “work” by managing the document to be operated in association with the concept of “work”. The technique described in Patent Document 1 is a technique for supporting efficient association between an operation history for a document and a business. Specifically, at the start of the document search, the user is allowed to specify an execution job, and thereafter, an operation history performed on the document is managed and displayed as a list of operation history for the job. Using the technology described in Patent Document 1, it is easy to find documents that have been manipulated in relation to the “business” such as “patent proposal”, “software ordering”, “development plan creation”, etc. become. However, since it is necessary for the user himself / herself to specify “business” as an operation for organizing information, there is a problem that a burden is imposed on the user or an operation omission occurs.

  There has been proposed a method for extracting a relationship between information from an operation history in daily work without forcing a user to organize information. The method of automatically extracting the relationship between information from normal business operations without requiring special operations from the user will reduce the burden on the user and reduce the user's operation omission. It is thought that such methods will increase.

  For example, Patent Document 2 proposes a method of automatically associating and managing documents based on a user's operation history. Specifically, when another user refers to another document between the start of editing and the end of editing when editing the document, the document to be edited and the referenced document are managed in association with each other. In this method, it can be said that the relationship is extracted based on temporal overlap of operations on the document.

  In Japanese Patent Laid-Open No. 2004-260688, a division of “business” is analyzed based on a user's operation history, and a document operated during the execution of the business is managed in association with the business, thereby retrieving a related document from the business. Document retrieval methods that can do this have been proposed. As business divisions, user operations such as document reference, document creation, and logout can be specified.

JP 11-250053 A (paragraphs 0051-0054) JP-A-8-63465 (FIG. 3) Japanese Patent Laid-Open No. 11-32923 (paragraph 0106-0115)

  The first problem is that when defining the relationship between information based on the analysis of the user's operation history, the application operations to be analyzed are limited, and the operation history of the application operations not being analyzed is This means that it is difficult to change it so that it is used for determining the relationship.

  The reason is that the rules and logic for judging and extracting the relationship are for specific application operations, so the operation history of a new application that is not included in the assumption is incorporated in the relationship judgment logic. Because there is no means. Further, this is because the architecture is not such that a module for acquiring an operation history of the application can be added according to the incorporated logic. For example, there is no means to incorporate the operation of the Web browser into the logic for determining the relationship even if an attempt is made to use not only the operation on the document but also the operation of browsing the Web site using the Web browser to extract the relationship. In addition, since there is no means for acquiring an operation history for the Web browser and passing it to the module for determining the relationship, it cannot be realized.

  The second problem is that the time range related to the operation for judging or extracting the relationship is limited.

  The reason is that the temporal analysis related to the operation for judging and extracting the relationship is based on the overlap of the operation time. In the techniques disclosed in Patent Documents 2 and 3, the relationship between information is extracted from the temporal overlap of operation histories, but in actuality, not only temporal overlap but also continuous operations, etc. There may be a relationship between the information. However, the techniques disclosed in Patent Documents 2 and 3 cannot extract these relationships.

  The third problem is that the granularity of the operation level (the degree of detail of the type of operation) to be analyzed in order to judge or extract the relationship is fixed.

  The reason for this is that there is no means to change the granularity of operations for judging and extracting relationships, and an architecture that can add a module for acquiring application operation history based on the changed granularity of operations. Because it is not.

  Therefore, the present invention provides a relational information acquisition system capable of adding or defining an application for acquiring a user operation to be determined in a system for acquiring a relationship between information based on a user operation history. The purpose is to provide.

  Another object of the present invention is not to fix a temporal range of operation objects to be analyzed in order to judge or extract a relationship in a system for acquiring a relationship between information based on a user's operation history. It is to provide an expandable relationship information acquisition system.

  Still another object of the present invention is to provide relation information that can arbitrarily define the granularity of an operation to be analyzed in order to judge or extract a relation in a system that obtains a relation between information based on a user's operation history. To provide an acquisition system.

  The related information acquisition system according to the present invention includes a monitoring rule storage unit that stores a monitoring rule for specifying operation information to be acquired, and a comparison that stores a comparison rule for comparing user operation history information. A rule storage unit and an application monitoring unit provided for each of the applications, monitoring a user operation to the corresponding application, and acquiring operation information according to the monitoring rule, and operation information acquired by the application monitoring unit, The user who acquires the relationship between the operation information by comparing the user operation monitoring control means stored in the operation history recording unit as information constituting the operation history with the operation information stored in the operation history recording unit according to the comparison rule. Operation comparison means, and monitoring corresponding to each application in the monitoring rule storage unit Wherein the Lumpur is stored.

  The relation information acquisition method according to the present invention stores a monitoring rule for prescribing operation information to be acquired corresponding to each application in a monitoring rule storage unit in advance, and a comparison for comparing user operation history information Rules are stored in the comparison rule storage unit in advance, application monitoring means is provided corresponding to each application, user operations on the application are monitored by the application monitoring means, operation information is acquired according to the monitoring rules, and the acquired operation The information is stored in the operation history recording unit as information constituting the operation history, and the operation information stored in the operation history recording unit is compared according to the comparison rule, thereby acquiring the relationship between the operation information. To do.

  The related information acquisition program according to the present invention provides a computer with a process for providing a monitoring rule to an application monitoring unit provided corresponding to each application, and an operation of a user operation on an application acquired by the application monitoring unit according to the monitoring rule. A process of storing information in the operation history recording unit as information constituting the operation history, and a process of acquiring the relationship between the operation information by comparing the operation information stored in the operation history recording unit according to a comparison rule Is executed.

  A first effect is that an application for acquiring a user operation to be determined can be added or defined in a system that acquires the relationship between information based on the user operation history. This is because a monitoring rule that defines a rule for monitoring an application can be added later, and application monitoring means for monitoring an application according to the rule is prepared for each application.

  The second effect is that the temporal range of the operation target to be analyzed in order to judge or extract the relationship can be expanded instead of being fixed. The reason is that a range for comparing operation histories can be specified in a comparison rule for comparing user operation histories, and the user operation comparison means compares operation histories based on the operation history comparison ranges. .

  The third effect is that the granularity of the operation to be analyzed for judging or extracting the relationship can be defined. This is because the monitoring target information can be defined in the monitoring rule for each application in the monitoring rule.

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

Embodiment 1. FIG.
FIG. 1 is a block diagram showing a first embodiment of a relationship information acquisition system according to the present invention. The relationship information acquisition system shown in FIG. 1 is a system in which a client unit 100 and a server unit 200 are communicably connected via a communication network 300. The client unit 100 is realized by, for example, a personal computer, and the server unit 200 is realized by, for example, a server device. The communication network 300 is, for example, a LAN or the Internet.

  The client unit 100 includes an application 101 operated by the user and an application monitoring unit 102 that monitors the user's operation on the application.

  The application 101 is a program or service operated by the user. The application monitoring unit 102 is software that monitors user operations on the application 101. In addition, application monitoring means is provided for each different application. FIG. 1 shows an example in which an application monitoring unit 102 ′ corresponding to an application 101 ′ as a second application is mounted on the client unit 100 in addition to the application monitoring unit 102 corresponding to the first application 101. Has been. Note that the applications 101 and 101 ′ may be implemented as application programs in the client unit 100, but may use services provided outside the client unit 100 via a communication network.

  The server unit 200 includes a user operation monitoring control unit 110, a monitoring rule storage unit 120, an operation history storage unit 121, a user operation comparison unit 130, a comparison rule storage unit 122, and a relationship information storage unit 123. The process of the user operation monitoring control unit 110 and the process of the user operation comparison unit 130 are realized, for example, when the CPU in the server unit 200 executes a program. The relationship information storage unit 123 is connected to an external relationship information utilization system 190 that uses the relationship information stored in the relationship information storage unit 123. That is, the relationship information utilization system 190 can refer to the relationship information stored in the relationship information storage unit 123.

  The monitoring rule storage unit 120 stores monitoring rules for monitoring user operations on the application in advance. The user operation monitoring control unit 110 acquires the monitoring rule from the monitoring rule storage unit 120 and transmits it to the application monitoring unit 102. That is, the monitoring rule is read from the monitoring rule storage unit 120 and transmitted to the client unit 100 via the communication network 300. In the client unit 100, the application monitoring unit 102 monitors user operations based on the monitoring rules, and notifies the user operation monitoring control unit 110 of the monitoring results. The user operation monitoring control unit 110 records the monitoring result in the operation history storage unit 121.

  The comparison rule storage unit 122 stores comparison rules for comparing operation histories of user operations in advance. The user operation comparison unit 130 acquires a comparison rule from the comparison rule storage unit 122, analyzes an operation history stored in the operation history storage unit 121 based on the comparison rule, and acquires relation information. Then, the user operation comparison unit 130 records the acquired relation information in the relation information storage unit 123.

  Next, the operation of this embodiment will be described with reference to the flowcharts of FIGS. 2, 3, 7, and 8 and the explanatory diagrams of FIGS. 4 to 6.

  FIG. 2 is a flowchart showing the overall processing flow of the relationship information acquisition system of this embodiment. First, the server unit 200 performs an initialization process (step S200), and then proceeds to a user operation monitoring process (step S300). When the process of step S300 is completed, the initialization process ends.

  FIG. 3 is a flowchart showing the initialization process in step S200. In the initialization process, first, the user operation monitoring control unit 110 acquires a monitoring rule from the monitoring rule storage unit 120 (step S210). Next, the user operation monitoring control unit 110 notifies the contents of the acquired monitoring rule to the application monitoring units 102 and 102 ′ provided for each application type (step S 220).

  Next, the user operation comparison unit 130 acquires a comparison rule from the comparison rule storage unit 122 (step S230). When the process of step S230 is completed, the initialization process ends.

  FIG. 4 is an explanatory diagram illustrating an example of the monitoring rules stored in the monitoring rule storage unit 120 in advance. As shown in FIG. 4, the monitoring rule includes four items: an application type, monitoring target information of the application, a monitoring event, and a representative entity recorded in a log as a result of monitoring.

  The information (data) set as the application type is information indicating the type of application or service, such as file management, browser (Web browser), mail client, search service.

  The monitoring target information indicates information to be monitored for the operation of the application. In the example illustrated in FIG. 4, the application monitoring unit corresponding to the application that performs file management sets “file ID” and “file name” as monitoring targets. The application monitoring unit corresponding to the browser application sets “URL” as a monitoring target. The application monitoring means corresponding to the mail client application monitors “Subject”, “To”, “Cc.”, And “Attached file”. Application monitoring means corresponding to the application of the search service sets “search keyword” as a monitoring target. The application monitoring unit corresponding to the transfer guidance application sets “station name” as the monitoring target.

  Information (data) set as a monitoring event is information indicating an event that is a timing for monitoring the application. In the example illustrated in FIG. 4, the application monitoring unit corresponding to the application that performs file management performs monitoring at the timing of “reference”, “edit”, and “end” of the file. In other words, when “reference”, “edit”, and “end” operations of the file by the user are detected, necessary information to be recorded in the operation history is collected. Necessary information is information defined as “monitoring target information”. When the application monitoring unit corresponding to the browser application detects operations of “reference”, “page transition”, and “end”, it collects necessary information to be left in the operation history. When the application monitoring unit corresponding to the mail client application detects the operations of “reference” and “send”, it collects necessary information to be left in the operation history. When the application monitoring unit corresponding to the application of the search service detects an operation of “search execution”, it collects necessary information to be left in the operation history. When the application monitoring unit corresponding to the transfer guidance application detects the “search execution” operation, the application monitoring unit collects necessary information to be left in the operation history.

  The representative entity is information recorded in the operation history of the monitoring result of the application. In the example illustrated in FIG. 4, the application monitoring unit corresponding to the application that performs file management records “file ID” in the operation history. The application monitoring unit corresponding to the browser application records “URL” in the operation history. The application monitoring means corresponding to the mail client application records the “mail ID” in the operation history. The application monitoring means corresponding to the application of the search service records the “search keyword” in the operation history. The application monitoring means corresponding to the “transfer guidance” application records the “search keyword” in the operation history.

  FIG. 5 is an explanatory diagram showing an example of comparison rules stored in the comparison rule storage unit 122 in advance. As shown in FIG. 5, as the comparison rule, the identity determination rule shown in FIG. 5 (A) and the operation history comparison range designation shown in FIGS. 5 (B-1), (B-2), and (B-3). There are two types of rules.

  The identity determination rule includes two items, an application type and an identity determination condition. The identity determination rule is a rule for finding the same operation (operation satisfying the identity determination condition) from the user operation history. That is, when finding the same operation for an operation (operation specified by the history information) corresponding to certain history information (corresponding to one line in FIG. 6) in the user operation history (see FIG. 6), Among the history information that includes the same “application type” as the “type”, the operation specified by the history information that includes the same “monitoring target information” as the content of the “monitoring target information” in the history information is regarded as the same operation. .

  The operation history comparison range designation rule is information for designating a comparison range when the same operation is found from the user operation history and the operation history before and after both operations is compared to check whether there is a common operation. . With the operation history comparison range specification rule, a time range, a range of the number of operations, and the like can be specified. For example, in the example shown in FIG. 5B-1, when the operation A and the operation B are the same operation, the operation history for 5 minutes before and after the operation A and the operation history for 5 minutes before and after the operation B are compared. To check for common operations.

  FIG. 6 is an explanatory diagram illustrating an example of an operation history notified from the application monitoring unit 102 to the user operation monitoring control unit 110 and recorded in the operation history storage unit 121 by the user operation monitoring control unit 110. A collection of information recorded in the operation history storage unit 121 is referred to as an operation history, and each data in the operation history (corresponding to each row in FIG. 6) is referred to as operation information or history information. As shown in FIG. 6, the operation history includes, for each piece of operation information, “operation history ID”, “date and time” when the operation occurred, “application type”, “monitoring target information”, “monitoring event”, and A set of “representative entities” is recorded.

  Next, the user operation monitoring process (step S300 in FIG. 2) will be described with reference to the flowchart of FIG. Hereinafter, a case where the application monitoring unit 102 shown in FIG. 1 monitors the operation of the application 101 by the user is taken as an example.

  In the user operation monitoring process, first, the application monitoring unit 102 enters a standby state for waiting for a user operation (step S301). If the operation performed during the standby state is an end instruction to the related information acquisition system (step S302), the application monitoring unit 102 ends the user monitoring process.

  If it is not an end instruction, the application monitoring unit 102 compares the operation that occurred during the process execution of the application 101 with the monitoring rule notified from the user operation monitoring control unit 110 in the process of step S220 shown in FIG. It is determined whether the generated operation matches the monitoring event of the application type described in the monitoring rule (step S303). In other words, it is determined whether or not the operation is compatible with the application type monitoring event.

  In order to determine whether or not the operation conforms to the application type monitoring event, the application monitoring unit 102 acquires the type of operation every time the user operates the application 101. As a method for acquiring the operation type, the operation type may be transmitted from the application 101, or the application monitoring unit 102 may be designated, for example, through a mouse attached to the client unit 100. Or information input via a keyboard may be obtained, and the type of operation may be determined based on the obtained information. Further, any other method may be used as long as the type of operation can be recognized.

  When the user operation includes the “monitoring event” in the monitoring rule shown in FIG. 4, the application monitoring unit 102 notifies the user operation monitoring control unit 110 of operation information (hereinafter referred to as an acquisition operation). . Specifically, when it is detected that the “monitoring event” has occurred, the monitoring target information corresponding to the “monitoring event” (information defined as “monitoring target information” in the monitoring rule shown in FIG. 4) is displayed. Acquired from the user operation. Also, a “representative entity” is determined. For example, when the application 101 is a file management application and “reference” as a “monitoring event” occurs, the “file ID” and “file name” input by the user are acquired, and the “file ID” is set to “representative entity”. " Then, the acquired “monitoring target information” and “monitoring target information” are transmitted to the user operation monitoring control unit 110 in the server unit 200 via the communication network 300 together with the “monitoring event”.

  When the content of the user operation does not match the monitoring event, the process returns to the user operation standby state (step S301).

  The user operation monitoring control unit 110 records the contents of the acquisition operation notified from the application monitoring unit 102 in the operation history storage unit 121 (step S310). In step S310, the contents of the acquisition operation are added to the operation history as shown in FIG. The “operation history ID” shown in FIG. 6 is numbered by the user operation monitoring control unit 110. Also, the user operation monitoring control unit 110 sets, for example, the time obtained from the time measuring unit in the server unit 200 as “date and time”.

  After recording the data of a new operation (acquisition operation) in the operation history storage unit 121, the user operation monitoring control unit 110 notifies the user operation comparison unit 130 of the operation history ID of the acquisition operation, and stores the operation history. Instructed to compare with the past operation history recorded in the section (step S311).

  The user operation comparison unit 130 performs an operation that satisfies the identity determination condition specified for the application type of the acquisition operation based on the identity determination rule of the comparison rule acquired in the process of step S230 illustrated in FIG. A process of searching from the operation history storage unit 121 is performed (step S320).

  The case where the acquisition operation is an operation with the operation history ID “00105” shown in FIG. 6 is taken as an example. In this case, since “application type” is “file management”, according to the comparison rule shown in FIG. 5, the identity determination conditions are “ID match” and “file name partial match”. Therefore, the user operation comparison unit 130 has operation information whose ID matches “F001” (ID recorded in the operation information of the operation history ID “00105”) for all information stored in the operation history storage unit 121. Then, the operation information whose file name partially matches “A company proposal material 1” is searched. When all the information stored in the operation history storage unit 121 shown in FIG. 6 is searched, operation information with the operation history ID “00002” is found as operation information satisfying the identity determination condition with the operation history ID “00105”. It will be. Note that the search range for the same operation is, for example, the operation history is traced back from the current time until the most recent cases are found, or all operation histories satisfying the conditions are extracted from all operation histories for the past week. You may do it. Also, here, the identity determination condition is satisfied when both “ID match” and “file name partial match” in the identity determination condition are satisfied, but a plurality of conditions are defined as the identity determination condition. If any of the conditions is satisfied, the identity determination condition may be satisfied. In the example shown in FIG. 6, the file name in the operation information with the operation history ID “00105” and the file name in the operation information with the operation history ID “00002” are exactly the same. Instead, the identity determination condition may be satisfied if they partially match.

  If there is no operation that satisfies the identity determination condition, that is, there is no operation (same operation) specified by the operation information that satisfies the identity determination condition, the process returns to the standby state of the user operation (step S301). (Step S330). The operation specified by the operation information is an operation that triggered the operation information recording.

  Next, the user operation comparison unit 130 performs a common operation search process for searching the operation history before and after each of the acquisition operation and the same operation found in the process of step S330 (step S340).

  FIG. 8 is a flowchart showing the common operation search process. First, the user operation comparison unit 130 initializes an area in which the user operation comparison unit 130 temporarily stores common operations (step S510). Next, the user operation comparison unit 130 stores the peripheral operation information (operation history) from the operation history storage unit 121 within the range specified by the operation history comparison range specification rule of the comparison rule acquired in the process of step S230 shown in FIG. In step S520, a process of acquiring operation information within the range specified by the operation history comparison range specification rule is performed.

  Hereinafter, an example in which the acquisition operation is the operation with the operation history ID “00105”, the same operation is the operation with the operation history ID “00002”, and the search is performed on the operation history shown in FIG. For example, when the operation history comparison range is set to “within 30 minutes before and after” as shown in FIG. 5B-1, operation information within 30 minutes before and after the operation history ID “00105” is stored in the operation history storage unit 121. Therefore, four pieces of operation information with operation history IDs “00101”, “00102”, “00103”, and “00104” are acquired as peripheral operation information.

  Next, the user operation comparison unit 130 acquires one piece of operation information from the operation information of the same operation acquired in the process of step S320 (see FIG. 7) (step S530). If the acquisition operation is an operation with the operation history ID “00105”, only the operation information with one operation history ID “00002” has been found as the same operation in the process of step S320. Is acquired.

  And the peripheral operation acquisition process regarding the same operation is performed (step S540). In step S540, the user operation comparison unit 130 acquires peripheral operation information for the same operation from the operation history storage unit 121 within the range specified in the operation history comparison range specification rule for the same operation.

  In this case, since operation information for 30 minutes before and after the operation history ID “00002” which is the same operation is acquired, the operation history IDs are “00001”, “00003”, “00004”, “00005”, “00006”. The five pieces of operation information are acquired.

  Next, the user operation comparison unit 130 selects each operation information in the group of peripheral operation information related to the acquisition operation acquired in the process of step S520 and each operation information in the group of peripheral operation information related to the same operation acquired in the process of step S540. And whether or not there is an operation that matches the identity determination rule acquired in the process of step S230 (see FIG. 3) (step S550).

  In this case, an operation history (peripheral operation information) having operation history IDs “00101”, “00102”, “00103”, and “00104”, and operation history IDs “00001”, “00003”, and “00004”. , “00005”, and “00006” are compared with the peripheral operation information. Therefore, the operation information of the operation history IDs “00003” and “00101” that are operation information satisfying the identity determination rule (URL match) of the same application type (browser) is common as the operation that matches the identity determination rule. Found as operation information of the operation.

  If there is a common operation that matches the identity determination rule (step S560), the user operation comparison unit 130 additionally records common operation information in the common operation temporary storage area (S570). If there is operation information of the same operation that has not yet been processed in steps S540 and S550 (step S580), the process returns to step S530. Then, the next same operation is acquired (step S530). In addition, when a plurality of pieces of operation information for the same operation are acquired in the process of step S320 (see FIG. 7), a process of returning to step S530 occurs. In the common operation temporary storage area, four types of information, that is, the application type and representative entity of the acquisition operation notified from the application monitoring unit 102, and the application type and representative entity of the common operation are recorded as common operation information as a set. Is done. In this case (when the acquisition operation is an operation with an operation history ID “00105” and the same operation is an operation with an operation history ID “00002”), as shown in FIG. 9, (file management, F001, browser, http: //www.url2/) information will be recorded as a set.

  If it is confirmed in step S580 that there is no operation information for the same operation, the user operation comparison unit 130 completes the common operation search process.

  With the above processing, finally, the investigation for the presence of a common operation is completed for the acquisition operation notified from the application monitoring unit 102 and all the same operations.

  When the common operation information exists as an output of the common operation search process after completing the common operation search process in step S340 in FIG. 7 (step S350), that is, when the common operation information is stored in the common operation temporary storage area. The common operation information stored in the common operation temporary storage area is stored in the related information storage unit 123 (step S360). Thereafter, the process returns to the standby state of the user operation in S301. If there is no common operation information in the output of the common operation search process in step S350, the process directly returns to the standby state of the user operation in S301.

  In the above description, the case where the application 101 is a file management application is mainly exemplified. However, when the application 101 is a browser, the application monitoring unit 102 corresponding to the browser executes the following processing.

  The application monitoring unit 102 notifies the user operation monitoring control unit 110 of an acquisition operation when, for example, “page transition” is included in the operation that occurs during the processing of the application 101. When the application monitoring unit 102 detects that “page transition” has occurred, the monitoring target information corresponding to the “monitoring event” (information specified as “monitoring target information” in the monitoring rule shown in FIG. 4) Is acquired from the user's operation content. Also, a “representative entity” is determined. In this example, the URL of the transition destination corresponding to “page transition” as the “monitoring event” is acquired, and “URL” is set as “representative entity”.

  The user operation monitoring control unit 110 records the contents of the acquisition operation notified from the application monitoring unit 102 in the operation history storage unit 121 (step S310 in FIG. 7). It is assumed that the content of the acquisition operation is added to the operation history as shown in FIG. 10 in the process of step S310. That is, it is assumed that the content of the acquisition operation related to the browser operation is recorded as information shown in the row of the operation history ID “00106”.

  The user operation monitoring control unit 110 notifies the user operation comparison unit 130 of the operation history ID “00106” and instructs to compare with the past operation history recorded in the operation history storage unit ( Step S311 in FIG.

  The user operation comparison unit 130 sets the identity determination condition specified for the application type of the operation history ID “00106” based on the identity determination rule of the comparison rule acquired in the process of step S230 shown in FIG. A process for searching the operation history storage unit 121 for a satisfying operation is performed (step S320 in FIG. 7).

  In this example, since the “application type” is “browser”, according to the comparison rule shown in FIG. 5, the identity determination condition is “URL match” and “domain match”. Therefore, the user operation comparison unit 130 records the URL of “http: //www.url1/” (operation history ID “00106”) for all information stored in the operation history storage unit 121. Search for operation information that matches (URL). When all the information stored in the operation history storage unit 121 illustrated in FIG. 10 is searched, operation information with the operation history ID “00001” is found as operation information that satisfies the identity determination condition with the operation history ID “00106”. It will be. In this case, the identity determination condition is satisfied when either one of “URL match” and “domain match” matches, but “URL match” and “domain match” The identity determination condition may be satisfied when both coincide.

  Next, the user operation comparison unit 130 performs a common operation search process for searching the operation history before and after each of the acquisition operation and the same operation found in the process of step S330 (step S340 in FIG. 7).

  In the common operation search process, when the operation history comparison range is set to “within 30 minutes before and after” as shown in FIG. 5B-1, for example, the peripheral operation acquisition process related to the acquisition operation (step S520 in FIG. 8). ), Since operation information within 30 minutes before and after the operation history ID “00106” is obtained from the operation history storage unit 121, the operation history IDs “00102”, “00103”, “00104”, “00105” Four pieces of operation information are acquired as peripheral operation information for the acquisition operation.

  Further, in the peripheral operation acquisition process related to the same operation (step S540 in FIG. 8), operation information for 30 minutes before and after the operation history ID “00001” that is the same operation is acquired, so that the operation history IDs are “00002” and “00003”. ”,“ 00004 ”,“ 00005 ”, and“ 00006 ”are obtained.

  Next, the user operation comparison means 130 compares each operation information in the group of peripheral operation information related to the acquisition operation with each operation information in the group of peripheral operation information related to the same operation, and the process of step S230 (see FIG. 3). Whether or not there is an operation that matches the identity determination rule acquired in step S550 is checked (step S550 in FIG. 8).

  In this example, an operation history (peripheral operation information) with operation history IDs “00102”, “00103”, “00104”, “00105”, and operation history IDs “00002”, “00003”, “00004”, The peripheral operation information “00005” and “00006” is compared. Therefore, the operation information of the operation history IDs “00004” and “00102”, which are operation information satisfying the identity determination rule (ID match) of the same application type (file management) as the operation that matches the identity determination rule, Found as operation information for common operations.

  Therefore, as shown in FIG. 11, the user operation comparison unit 130 records the common operation information of (browser, http: //www.url1/, file management, F002) in the common operation temporary storage area. Then, the common operation information recorded in the common operation temporary storage area is stored in the related information storage unit 123 (step S360 in FIG. 7).

  Next, the effect of this embodiment will be described. In the present embodiment, application monitoring means 102 and 102 'are provided corresponding to the applications 101 and 101', respectively. That is, an application monitoring unit is provided for each application type. Further, in the monitoring rule stored in the monitoring rule storage unit 120, a rule can be added for each application type, and furthermore, monitoring target information and monitoring events can be defined for each application type in the monitoring rule. . That is, an application monitoring unit 102 that monitors an application according to a monitoring rule for each application type can be added. Therefore, in a system that acquires the relationship between information based on the user operation history, it is possible to easily add and define an application that acquires a user operation to be determined. Furthermore, it is possible to define the granularity of operations to be analyzed to determine the relationship. That is, the granularity of the desired operation can be defined by making the content of the “monitoring event” in the monitoring rule a rule at a level corresponding to the desired granularity. Furthermore, the granularity of operation can be defined for each application type.

  In the present system, when a new application is added to the client unit 100, application monitoring means corresponding to the application is installed in the client unit 100. In the server unit 200, a monitoring rule corresponding to the added application is added to the monitoring rule storage unit 120. In addition, a comparison rule corresponding to the added application is added to the comparison rule storage unit 122.

  Further, in the present embodiment, the time of the operation target to be analyzed in order to judge or extract the relationship based on the operation history comparison range designation rule in the comparison rule stored in the comparison rule storage unit 122. Since the distance between operations represented by a range and the number of operations can be defined and the relationship is judged within the operation target based on the rule, in the system that acquires the relationship between information based on the user's operation history, The time range of the operation target to be analyzed in order to judge or extract the relationship can be expanded instead of being fixed.

  The present invention can be applied to databases and knowledge management systems that manage and store relationships between information. In addition, a program that realizes a function that presents related information when opening a document stored in a document management system for editing, and a function that recommends a destination or a subject when opened for editing a mail. It can be applied to uses such as programs.

It is a block diagram which shows the structure of the 1st Embodiment of this invention. It is a flowchart which shows operation | movement of 1st Embodiment. It is a flowchart which shows the operation | movement of the initialization process in 1st Embodiment. It is explanatory drawing which shows an example of the monitoring rule stored in the monitoring rule memory | storage part. It is explanatory drawing which shows an example (identity determination rule and operation history comparison range designation | designated rule) among the comparison rules stored in a comparison rule memory | storage part. It is explanatory drawing which shows an example of the operation history information stored in the operation history storage unit. It is a flowchart which shows operation | movement of the user operation monitoring process in 1st Embodiment. It is a flowchart which shows the common operation search process in 1st Embodiment. It is explanatory drawing which shows an example of the relevant information stored in a relevant information storage part. It is explanatory drawing which shows the other example of the operation history information stored in the operation history memory | storage part. It is explanatory drawing which shows the other example of the relevant information stored in a relevant information storage part.

Explanation of symbols

DESCRIPTION OF SYMBOLS 101,101 'Application 102,102' Application monitoring means 110 User operation monitoring control means 120 Monitoring rule memory | storage part 121 Operation history memory | storage part 122 Comparison rule memory | storage part 123 Relation information memory | storage part 130 User operation comparison means 190 Relation information utilization system

Claims (15)

A relationship information acquisition system that acquires a relationship between information based on a user's operation history,
A monitoring rule storage unit that stores monitoring rules for defining operation information to be acquired;
A comparison rule storage unit storing a comparison rule for comparing user operation history information;
Application monitoring means provided corresponding to each of the applications, monitoring a user operation to the corresponding application, and acquiring operation information according to the monitoring rule;
User operation monitoring control means for storing the operation information acquired by the application monitoring means in the operation history recording unit as information constituting the operation history;
User operation comparison means for acquiring the relationship between operation information by comparing operation information stored in the operation history recording unit according to the comparison rule,
The relationship information acquisition system, wherein the monitoring rule storage unit stores the monitoring rule corresponding to each application. The relation information acquisition according to claim 1, wherein the comparison rule storage unit stores a comparison rule including a determination condition corresponding to each of the applications and a determination condition for determining that the plurality of pieces of operation information are related. system. The relation information acquisition system according to claim 2, wherein data indicating a comparison target range of history information stored in the operation history recording unit is stored in the comparison rule storage unit. User operation comparison means
For the operation information acquired by the application monitoring means, the operation information that satisfies the determination condition in the comparison rule for the range determined by the data indicating the comparison target range among the history information stored in the operation history recording unit. Discriminate,
The operation information acquired by the application monitoring unit and the operation information determined to satisfy the determination condition are used to determine a plurality of operation information having a relationship based on the comparison rule from the history information. 3. The related information acquisition system according to 3. User operation comparison means
For the operation information acquired by the application monitoring means, the operation information in the range determined by the data indicating the comparison target range in the history information stored in the operation history recording unit is specified as the first peripheral operation information,
For the operation information determined to satisfy the determination condition in the comparison rule, the operation information in the range determined by the data indicating the comparison target range in the history information stored in the operation history recording unit is set as the second peripheral operation. Identified as information,
Determining whether each operation information in the first peripheral operation information and each operation information in the second peripheral operation information satisfy the determination condition;
The relation information according to claim 4, wherein the operation information in the first peripheral operation information determined to satisfy the determination condition and the operation information in the second peripheral operation information are determined as a plurality of related operation information. Acquisition system. The monitoring rule including monitoring event data indicating a trigger for acquiring operation information and monitoring target data indicating information to be acquired is stored in the monitoring rule storage unit. The related information acquisition system according to item 1. A relationship information acquisition system that acquires a relationship between information based on a user's operation history,
The client device includes a client device and a server device that are communicably connected via a communication network. The client device is provided corresponding to each application, monitors a user operation on the corresponding application, and operates according to a monitoring rule. Including application monitoring means for acquiring and transmitting information,
The server device
A monitoring rule storage unit that stores monitoring rules for defining operation information to be acquired;
A comparison rule storage unit storing a comparison rule for comparing user operation history information;
User operation that transmits the monitoring rule stored in the monitoring rule storage unit to the client device, receives the operation information transmitted by the application monitoring unit, and stores it in the operation history recording unit as information constituting the operation history Monitoring control means;
A server device having user operation comparison means for obtaining a relationship between operation information by comparing operation information stored in the operation history recording unit according to the comparison rule,
The relationship information acquisition system, wherein the monitoring rule storage unit stores the monitoring rule corresponding to each application. A relationship information acquisition method for acquiring a relationship between information based on a user's operation history,
Corresponding to each of the applications, the monitoring rules for defining the operation information to be acquired are stored in advance in the monitoring rule storage unit,
A comparison rule for comparing user operation history information is stored in the comparison rule storage unit in advance,
Provide application monitoring means corresponding to each application,
The user operation on the application is monitored by the application monitoring unit, and operation information is acquired according to the monitoring rule.
The acquired operation information is stored in the operation history recording unit as information constituting the operation history,
The relationship information acquisition method characterized by acquiring the relationship between operation information by comparing the operation information stored in the said operation history recording part according to the said comparison rule. The relation information acquisition method according to claim 8, wherein the comparison rule storage unit stores a comparison rule including a determination condition corresponding to each of the applications and a determination condition for determining that the plurality of pieces of operation information are related. The relation information acquisition method according to claim 9, wherein data indicating a comparison target range of history information stored in the operation history recording unit is stored in the comparison rule storage unit. For the operation information acquired by the application monitoring means, the operation information that satisfies the determination condition in the comparison rule for the range determined by the data indicating the comparison target range among the history information stored in the operation history recording unit. Discriminate,
The operation information acquired by the application monitoring unit and the operation information determined to satisfy the determination condition are used to determine a plurality of operation information having a relationship based on the comparison rule from the history information. 10. The related information acquisition method according to 10. For the operation information acquired by the application monitoring means, the operation information in the range determined by the data indicating the comparison target range in the history information stored in the operation history recording unit is specified as the first peripheral operation information,
For the operation information determined to satisfy the determination condition in the comparison rule, the operation information in the range determined by the data indicating the comparison target range in the history information stored in the operation history recording unit is set as the second peripheral operation. Identified as information,
Determining whether each operation information in the first peripheral operation information and each operation information in the second peripheral operation information satisfy the determination condition;
The relation information according to claim 11, wherein the operation information in the first peripheral operation information determined to satisfy the determination condition and the operation information in the second peripheral operation information are determined as a plurality of related operation information. Acquisition method. A device that acquires the relationship between information based on user operation history, and compares the history information of user operations with a monitoring rule storage unit that stores monitoring rules for defining operation information to be acquired. A relation information acquisition program installed in a device including a comparison rule storage unit storing a comparison rule for
On the computer,
A process of providing the monitoring rule to application monitoring means provided corresponding to each of the applications;
A process of storing operation information of a user operation on an application acquired according to the monitoring rule by the application monitoring unit in an operation history recording unit as information constituting an operation history;
The relationship information acquisition program for performing the process which acquires the relationship between operation information by comparing the operation information stored in the said operation history recording part according to the said comparison rule. A comparison rule that is a determination condition corresponding to each application and includes a determination condition for determining that there is a relationship with a plurality of pieces of operation information, and data indicating a comparison target range of history information stored in the operation history recording unit Is a program installed in the device stored in the comparison rule storage unit,
On the computer,
For the operation information acquired by the application monitoring means, the operation information that satisfies the determination condition in the comparison rule for the range determined by the data indicating the comparison target range among the history information stored in the operation history recording unit. Processing to determine,
A process of determining a plurality of operation information having a relationship based on the comparison rule from the history information based on the operation information acquired by the application monitoring unit and the operation information determined to satisfy the determination condition; 14. The related information acquisition program according to claim 13, for executing On the computer,
Processing for identifying operation information in a range defined by data indicating a comparison target range in the history information stored in the operation history recording unit as the first peripheral operation information for the operation information acquired by the application monitoring unit When,
For the operation information determined to satisfy the determination condition in the comparison rule, the operation information in the range determined by the data indicating the comparison target range in the history information stored in the operation history recording unit is set as the second peripheral operation. Processing to identify as information,
A process for determining whether each operation information in the first peripheral operation information and each operation information in the second peripheral operation information satisfies the determination condition;
A process for determining operation information in the first peripheral operation information and operation information in the second peripheral operation information determined to satisfy the determination condition as a plurality of related operation information. The related information acquisition program according to claim 14.

Images