JP4698295B2 - Operation history storage system and method, program - Google Patents

Description

  The present invention relates to an operation history storage system, method, and program that can store operation history.

  Remotely operable terminal devices and remote operation systems composed of these terminal devices have usage forms in which a user of a remote terminal device is requested to perform an operation substitution or is instructed. In these modes of use, there are many cases where the same operation as the operation that the remote user performs on behalf of or the operation that is taught is repeatedly performed as the user's own operation after the remote operation is completed.

  In conventional remote operation systems, the user cannot browse the operation history, it is difficult to understand the operation history even if it can be browsed, or the procedure until the browsing itself is complicated, Even if it is desired to newly perform the same operation as that performed at the time of the previous remote control, a function for easily referring to the previous operation history has not been provided so far.

On the other hand, although not remote control, there is a system that generates an operation manual from an operation history of a terminal (see Patent Document 1). In this system, an event input to the emulator of the operation unit of the operation target device is stored in association with an identifier of a user interface whose state changes when the event is executed and information indicating the state change. A manual is automatically generated based on user interface attribute information and event description data managed in the same terminal.
Japanese Unexamined Patent Publication No. 7-219897

  In many cases, operation events input to the terminal device are continuously input, and in order to generate an operation manual related to a predetermined process, it is necessary to extract only those related to the process from the operation event group. .

  However, conventionally, since the operation history used for generating the manual is an operation history for the emulator, it does not have a function of extracting only a specific one from a group of continuous operation events.

  For example, in the case of an information input operation to the address book, the address data input every time this operation is executed is different. In this way, when there is a place where a different operation event is input every time it is executed in a series of operation events despite the same operation, the place is replaced with a specific word / phrase, etc. A function to absorb the difference that arises is required.

  In addition, when the generated manual is stored in a server device via a network and the manual can be viewed by a third party, the operation event related to personal information is replaced with another word or phrase, It was necessary to prevent the leakage of personal information by performing a process such as deleting.

  The present invention has been made in view of such a problem, and an object of the present invention is to store the operation event executed as an operation history and the level information of the operation event in association with each other and execute the information input operation. Even if there is a place where a different operation event is input, the operation history that absorbs the difference that occurs every time it is executed is displayed.

  Another object of the present invention is to switch the display contents according to the attribute of the user who browses based on the level information accumulated in association with the operation event when a highly confidential operation event is included in the operation history. This is to prevent leakage of highly confidential information.

  Another object of the present invention is to store operation history in association with remote control identification information, group and manage highly related operation events executed in the same remote control session, and relate to a specific operation. It is to easily extract the operation history.

The present invention according to claim 1 is a remote control management unit that transmits and receives an operation event to and from a remote terminal device connected via a network, and a predetermined application unit that receives an operation event received from the remote control management unit. An application control unit that transmits to the application control unit, an operation history storage unit that stores a history of operation events input to the application control unit in association with remote control identification information for identifying a remote control session, and the application control unit Receiving the operation event from the application unit and performing an operation according to the operation event. The application unit transmits the operation event received from the application control unit to the application operation unit and the level information search unit. And an input management unit that receives the operation received from the input management unit. The application operation unit that performs a predetermined operation based on the event and outputs the operation state information indicating the current operation state, and when the operation state information is newly received from the application operation unit, the operation state information stored immediately before is An operation state information temporary storage unit that temporarily transmits the received operation state information to the level information search unit, a level information database that stores operation event level information associated with the operation event information, and the level information database; Using the operation event received from the input management unit and the operation state information received from the operation state information temporary storage unit, the level information of the operation event is searched from the level information database, and the level information acquired as a search result is A level information search unit for transmitting to the application control unit Wherein the level information of the operation event, an event level indicating whether the operation event whether a fixed or varying, include a security level indicating the degree of security of the operation event, the application control unit, Upon receiving the level information of the operation event transmitted from the level information search unit of the application unit to the application unit, the operation event and the level information are transmitted to the operation history storage unit, and the operation history storage unit The received operation event and level information and the remote control identification information of the remote control are stored in association with each other.

According to a second aspect of the present invention, in the remote control management unit, an operation event is transmitted / received to / from a remote terminal device connected via a network, and in the application control unit, the remote control management unit A step of transmitting an operation event received from a predetermined application unit, and a history of the operation event input to the application control unit in the operation history storage unit as remote control identification information for identifying a remote control session Storing in association with each other, and in the application unit, receiving an operation event from the application control unit and performing an operation according to the operation event, the application unit in the input management unit, Operation events received from the application control unit To the application operation unit and the level information search unit, and the application operation unit performs a predetermined operation based on the operation event received from the input management unit, and outputs operation state information indicating the current operation state And when the operation state information is newly received from the application operation unit in the operation state information temporary storage unit, the operation state information stored immediately before is transmitted to the level information search unit, and the newly received operation state information is received. Temporarily storing information, a step of accumulating the level information of the operation event associated with the operation event and the operation state information in the level information database, and an operation event received from the input management unit and the operation in the level information search unit Uses the operation status information received from the status information temporary storage unit. Te, said level information to search the level information of the operation event from the database has, and sending the acquired level information to the application control unit as a search result, the level information of the operation event, An event level indicating whether the operation event is fixed or fluctuates, and a security level indicating the degree of security of the operation event are included. In the application control unit, the level information search unit of the application unit Receiving the level information of the operation event transmitted from the application unit to the application unit, the step of transmitting the operation event and the level information to the operation history storage unit, and the received operation event and level in the operation history storage unit Information and the remote control concerned Storing the remote control identification information in association with each other.

According to a third aspect of the present invention, there is provided an operation history accumulating program for causing a computer to execute the operation history accumulating method according to the second aspect.

  According to the present invention, the operation event executed as the operation history and the level information of the operation event are stored in association with each other, and even if there is a place where a different operation event is input every time the information input operation is executed, It is possible to display an operation history that absorbs the difference that occurs every time.

  Another effect of the present invention is that, when a highly confidential operation event is included in the operation history, the display content is switched depending on the attribute of the user who browses based on the level information accumulated in association with the operation event. It is possible to prevent leakage of highly confidential information.

  Another effect of the present invention is that operation history is stored in association with remote control identification information, highly related operation events executed in the same remote control session are grouped and managed, and related to a specific operation. The operation history can be easily extracted.

  Hereinafter, the present embodiment will be described with reference to the drawings.

  FIG. 1 is a flowchart showing an outline of the operation of the terminal device of the operation history storage system according to the first embodiment.

  A remote control start process is performed with a remote terminal device connected via the network (S101). Next, the application is controlled by an operation event received from a remote terminal device (S102). Next, the received operation event is accumulated (S103). Unless the remote control session is terminated by the termination process (S104), the processes of S102 and S103 are repeatedly executed.

  FIG. 2 is a block diagram of the terminal device according to the first embodiment.

  The terminal device 100 according to the embodiment of the operation history storage system receives a remote control management unit 110 that transmits / receives an operation event to / from a remote terminal device connected via a network, and receives from the remote control management unit 110. An application control unit 120 that transmits an operation event to a predetermined application unit, and an operation event history input to the application control unit 120 is stored in association with remote control identification information for identifying a remote control session. The operation history storage unit 130 and the application unit 140 that receives an operation event from the application control unit 120 and performs an operation according to the operation event.

  The application unit 140 receives an operation event received from the application control unit 120, an input management unit 141 that transmits the operation event to the application operation unit 142 and the level information search unit 145, and a predetermined operation based on the operation event received from the input management unit 141. When the operation state information is newly received from the application operation unit 142 and the application operation unit 142 that outputs the operation state information to the level information search unit 145, the operation state information stored immediately before is received. An operation state information temporary storage unit 143 that temporarily stores newly received operation state information transmitted to the level information search unit 145, and a level information database 144 that stores operation event level information related to the operation state information. And the input management unit 141 Using the received operation event and the operation state information received from the operation state information temporary storage unit 143, the level information of the operation event is searched from the level information database 144, and the level information acquired as a search result is used as the application control. And a level information search unit 145 that transmits to the unit 120.

  The application unit 140 operates, for example, a general application such as a Web browser or a video player mounted on the terminal device 100. The application operation unit 142 performs a general application operation. When the terminal device 100 requires functions of both the Web browser and the video player, application units having the respective functions are mounted. As described above, a plurality of application units 140 may be provided in the terminal device 100.

  First, a detailed operation of the terminal device 100 in the remote control start process (S101) will be described. FIG. 3 is a flowchart showing the detailed operation of the terminal device 100 in the remote control start process (S101).

  First, the remote control management unit 110 generates remote control identification information of a remote control session to be started or receives it from a remote terminal device connected via a network (S201). FIG. 4 is an example of remote control identification information. In this case, the terminal device 100 indicates that the terminal device A is requested to remotely control the video player and the browser among the application units installed in the terminal device 100.

  Here, the remote control identification number is a unique number determined for each remote control session. In addition, information that identifies a terminal device to be connected is described in a portion described as “terminal device A”, for example, an IP address or a host name of the terminal device. Indicates which communication device is the operation side communication device in the remote control, an application that delegates the operation to the operation side communication device, a method for obtaining output data of the application, and an input event for operating the application A type is specified.

  Components (1) and (2) indicate combinations of operation target applications, application output data acquisition methods, and event types. In the case of FIG. 4, the up / down direction key event is assigned to the operation of the video player, and the left / right direction key event is assigned to the operation of the browser.

  This remote control identification information is generated by a remote terminal device when remote control is started with a remote terminal device connected via a network, or by the remote control management unit 110 of the terminal device 100. Generated. When the remote control identification information is generated by the remote terminal device, the terminal device 100 receives it.

  Next, the remote control identification information is transmitted from the remote control management unit 110 to the application control unit 120 and set in the application control unit 120 (S202).

  Next, the application control unit 120 sets an operation event distribution rule specified in the remote control identification information (S203). In the case of the remote control identification information shown in FIG. 4, the up / down direction key event is set to be assigned to the video player operation, and the left / right direction key event is set to be assigned to the browser operation.

  Next, the application control unit 120 traverses the application unit specified in the remote control identification information (S204). In the case of the remote control identification information shown in FIG. 4, a video player and a browser are activated.

  Next, the application control unit transmits the remote control identification information to the operation history accumulation unit, and accumulates the remote control identification information (S205).

  Next, a setting for receiving an operation event from a remote terminal device is performed (S206). For example, if a specific TCP or UDP port is set to be used for the transfer of operation events, or if the firewall function of the terminal device is enabled, the firewall for the communication port only during the remote control Processing such as stopping the function is performed in S206.

  Next, the detailed operation of the application unit control process (S102) by the operation event received from the remote terminal device of the terminal device 100 will be described. FIG. 5 is a flowchart showing a detailed operation of the terminal device 100 in the application control process (S102).

  When the remote control management unit 110 receives an operation event from a remote terminal device (301), the remote control management unit 110 transmits the operation event to the application control unit 120 (302).

  The application control unit 120 that has received the operation event transmits the operation event to the input management unit 141 of the application unit 140 (S303). Here, the application control unit 120 transmits the operation event to an appropriate application unit in accordance with the operation event distribution rule set in the remote control start process (S101).

  When the distribution rule based on the remote control identification information shown in FIG. 4 is set, when the up / down direction key event is received, it is transmitted to the video player, and when the left / right direction key event is received, Send to browser.

  The input management unit 141 of the application unit 140 that has received the operation event transmits the operation event to the level information search unit 145, temporarily stores it (S304), and transmits it to the application operation unit (305).

  Next, the application operation unit 142 performs a predetermined operation based on the received operation event, and transmits operation state information indicating the current operation state to the operation state information temporary storage unit 143 (S306). When the application unit 140 is a browser, the application operation unit 142 acquires and displays a predetermined Web page according to the operation event. The operation state information transmitted to the level information search unit 145 indicates the state of the application operation unit 142 after executing the operation event. In the case of a browser, the displayed page, the state of the cursor, and the like are described. Is done.

  Next, a detailed operation of the terminal device 100 in the accumulation process (S103) of the operation event received from the remote terminal device will be described. FIG. 6 is a flowchart showing a detailed operation of the terminal device 100 in the operation event accumulation process (S103).

  When the operation state information temporary storage unit 143 receives the operation state information from the application unit 142 (S401), the operation state information stored immediately before is transmitted to the level information search unit 145 (S402), and the operation state received in S401. Information is newly temporarily stored (S403). As shown in S401 to S403, the operation state information temporary storage unit 143 functions to delay the operation state information transmitted from the application unit 142 to the level information search unit 145 by one cycle.

  The operation state information output from the application control unit 142 indicates the operation state transitioned by the operation event input to the application control unit in the same cycle, that is, the operation state when the operation event is input is immediately before It becomes equal to the operation state transitioned by the input operation event. Therefore, due to the effect of the operation state information temporary storage unit 143, the level state search unit can associate the operation event with the operation state information when the operation event is input.

  The level information search unit 145 that has received the operation state information in S402 transmits the operation state information and the operation event temporarily stored in S304 to the level information database 144, and acquires the corresponding level information (S404).

  FIG. 7 shows an example of level information stored in the level information database 144. Level information corresponding to combinations of operation events and operation state information is managed in a table as shown in FIG. In FIG. 7, an event level and a security level are described as examples of level information. The event level indicates whether different operation events are input when the same operation is performed.

  The security level indicates the degree of confidentiality of the input event to a third party user. For example, in FIG. 7, when the event level is “fluctuation”, this indicates that the operation event may fluctuate when the same operation is executed, and when the event level is “fixed” , Show no change when performing the same operation.

  The security levels “high”, “medium”, and “low” indicate high confidentiality of the operation event. The level state information search unit searches the level information corresponding to the operation event and the operation state information stored temporarily from the data table as shown in FIG. 7 accumulated in the level information database. In the case of FIG. 7, the corresponding event level and security level are acquired.

  In the example of FIG. 7, a plurality of types of level information are managed by the same data table. However, this may be managed by an independent data table for each level information, or managed by another database. It may be. In such a case, the level information search unit needs to perform the process shown in S404 for each of a plurality of data tables or databases.

  Next, the level information search unit 145 transmits the operation event and the level information to the application control unit 120 (S405).

  Next, the application control unit 120 transmits the received operation event and level information to the operation history storage unit 130 (S406). The operation history accumulation unit 130 accumulates the operation event and the level information in association with the remote control identification information accumulated in S205 of FIG. 3 (S407). FIG. 8 is an example of operation history information stored in the operation history storage unit. As shown in FIG. 8, the history of operation events is accumulated in association with the level information, and is accumulated together with the remote control identification number described in the remote control identification information of the remote control session. As described above, by storing the operation event and the level information in association with the remote control identification information, the operation event group can be managed for each remote control session.

  Next, a second embodiment will be described.

  FIG. 9 is a flowchart illustrating an outline of the operation of the terminal device according to the second embodiment. S501 to S504 are the same as S101 to S104 of the terminal device according to the first embodiment. After the remote control is completed, when a display of the operation history of a specific remote control session is requested due to a request from the user, etc., the operation history information of the remote control session is analyzed and edited (S505). The result is displayed (S506).

  FIG. 10 is a block diagram of a terminal device according to the second embodiment.

  The terminal device according to the present embodiment includes the operation event group described in the operation history information stored in the operation history storage unit 130 in addition to the components included in the terminal device according to the first embodiment. Is provided with an operation history analysis / editing unit 150 for editing based on the above. The operation history information analysis / editing process (S505) is executed by the operation history analysis / editing unit 150.

  FIG. 11 is a flowchart showing the detailed operation of the operation history information analysis / editing process (S505).

  First, the operation history analysis / editing unit 150 acquires specific operation history information from the operation history information stored in the operation history storage unit 130 (S601). This process is assumed to be executed automatically on the operation history information of the remote control session after the remote control session ends, or when an operation history information display request is received by the user. In the latter case, as a method for designating specific operation history information from a plurality of operation history information, a list of operation history information is displayed to the user, and desired operation history information is selected from the list. A method is conceivable.

  Next, the operation history analysis / editing unit 150 generates operation event edit data corresponding to the operation history information, and writes the remote control identification number described in the operation history information in the operation event edit data (S602). .

  Next, the operation event is analyzed and edited. In this process, the operation events described in the operation history information are read one by one in the execution order, and the read operation event is analyzed and edited.

  First, the value n indicating the execution order of the operation events to be read is designated as an initial value 1 (S603).

  Next, the operation history analysis / editing unit 150 reads the operation event whose execution order is the nth and the related level information from the acquired operation history information (S604).

  Next, the operation history analysis / editing unit 150 determines a corresponding operation event editing rule from the combination of the operation event read in S604 and its level information (S605). FIG. 12 is an example of an operation event editing rule used for editing an operation event of the operation history analysis / editing unit 150. The operation history analysis / editing unit 150 has an operation event editing rule as shown in FIG. 12, and when an operation event and its level information are input, the corresponding editing rule is selected from the operation event editing rules. Search for.

  In this example, an operation event editing rule for changing the display of the operation event is defined by the attribute of the user who uses the terminal device. For example, a left key event with an event level of “fixed” and a security level of “high” means that “left button pressed” is displayed only to the user of the party who executed the operation history. When the event level is “change”, the name of the device group to which the operation device belongs is specified instead of specifying the operation device name for inputting the operation event as the display name.

  For example, in the case of the left direction key, the “left / right direction key” that is the device group to which the left direction key belongs is specified. In the case of a text event, for example, “a”, a “character button” that is a device group to which a button for inputting “a” belongs is designated. As described above, when an operation event is displayed, the device group name to which the operation device belongs is used instead of the operation device name for inputting the operation event. It is possible to absorb differences in operation events. In addition, by using the device group name, it is possible to conceal specific input contents, and it is possible to prevent leakage of confidential information to a third party.

  Also, in FIG. 12, when the editing method is designated as “pressing any of the left / right buttons or pressing the left button”, the name of the operation device for inputting the operation event or the operation device is This means that you can select which device group name to display. This is displayed when you want to refer to past actual operation examples even if you replace the operation event using the device group name to absorb the difference in the operation event that occurs at each execution depending on the event level. Used when switching methods.

  When the operation event editing rule corresponding to the operation event and the level information is acquired, data according to the rule is written into the operation event editing data (S606).

  This process is repeatedly executed on the operation event described in the operation history information according to the execution order (S607, S608).

  FIG. 13 is an example of operation event edit data generated by the processing shown in FIG. In this manner, the history of each operation event is changed to an expression according to the operation event editing rule and stored by the operation history analysis / editing process shown in FIG.

  The operation history edited by the processing of S505 is displayed by the operation history display processing (S506). FIG. 14 is a flowchart illustrating an example of detailed operation of the operation history display process (S506). FIG. 15 is an example of display data displayed by this processing. This example is generated based on the operation event editing data in FIG. 13 and is displayed as an operation manual for the user.

  The operation history analysis / editing unit 150 first generates a data file for display data recording, and from the operation event edit data generated in S505 and the remote control identification information for the remote control identification number described in the operation event edit data. The title of the page to be displayed is written (S701).

  In this process, the remote control identification information in the manual is automatically extracted from, for example, the title of the Web page specified on the initial display screen of the browser. For example, if the initial screen of the browser in the remote control session is “XX service / information input screen”, this is extracted and used as the title of the display screen as shown in FIG.

  Next, display data is generated. In this process, the operation events described in the operation event editing data are read one by one in the execution order and executed.

  First, the value n indicating the execution order of the operation events to be read is designated as an initial value 1 (S702).

  Next, when the same operation event continues, the value of m for counting the consecutive number is designated as an initial value 1 (S703).

  Next, the nth operation event is compared with the (n + 1) th operation event (S704). If the results are equal, one is added to the values of n and m (S705). When a plurality of the same operation events continue by S704 to S705, it is possible to display “the operation event m times” instead of arranging a plurality of the same operation events.

  If the nth and n + 1th operation events are not equal in S704, the type of the nth operation event is analyzed (S706).

  If the nth operation event indicates the execution of the operation device itself in S706, the fact that the operation event is to be executed m times is written in the display data (S707). This makes it possible to display “pressing the right direction key” shown in FIG. 15 together with the number of executions.

  If the nth operation event indicates execution of the device group of the operation device in S706, the fact that the operation event is to be executed is written in the display data (S708). Here, in S707, the number of consecutive operation events is also written, whereas in S708, this writing is not performed. This is because, in the case of S708, every time an operation is executed, it is predicted that the number of times the operation event is input is different. In FIG. 15, a portion where “input a character with a character button” is displayed is a portion generated by the processing of S708.

  In S706, when a plurality of nth operation events are designated, the display data indicates that one of the operation events is displayed and a switching button for displaying another operation event is displayed. (S709). By this processing, the button “Display previous history” in FIG. 15 can be displayed. This display switching button can provide a selection tool for displaying to the user which operation event changes each time an operation is executed.

  This process is repeatedly executed on the operation event described in the operation event edit data in accordance with the execution order (S710, 711).

  FIG. 16 is an example of display data for a user who is not an operation history execution party but is registered in the terminal device, which is generated based on the same operation history information as the display data of FIG. The display data in FIG. 16 is different from that in FIG. 15 in that the display content switching button is not displayed. This is because the operation event editing rule shown in FIG. 12 prohibits the display of the previous character input history for users other than the operation history execution party.

  Furthermore, since a user who is not registered in the terminal device includes an operation event that cannot be displayed in the operation event in the operation history information, the user cannot even browse the display data. As described above, the display content can be changed by the user attribute according to the level information of the operation event.

  Next, a third embodiment will be described.

  FIG. 17 is a sequence diagram illustrating an outline of the operation of the operation history storage system according to the third embodiment. S801 to S805 are the same as operations S501 to S505 of the terminal device according to the second embodiment. Following these processes, the terminal device 100 of the operation history storage system according to the present embodiment transmits the operation event editing data generated in S805 and the remote control identification information to the server device 200 (S806). The server device 200 accumulates the received operation event edit data and remote control identification information (S807).

  FIG. 18 is a block diagram of an operation history storage system according to the third embodiment.

  The operation history storage system according to the present embodiment includes the terminal device 100 and the server device 200 according to the first embodiment. Among these, the terminal device 100 includes an operation history analysis / editing unit that transmits the generated operation event editing data together with the remote control identification information to the server device 200 in addition to the processing unit included in the terminal device 100 of the first embodiment. 150 '. The server device 200 also includes an operation history storage unit 210 that stores the operation event editing data and remote control identification information received from the terminal device 100, and a third party's data from the operation event editing data stored in the operation history storage unit. An operation history display unit 220 that generates and displays operation history display data for the terminal device is provided.

  The system according to the present embodiment makes it possible to refer to operation examples of other users by publishing an operation history generated by the terminal device 100 to a third party via the server device 200, thereby improving usability. It is said. When transmitting the operation history to the server apparatus 200, by performing the processing of S801 to S805 in advance, it is possible to transmit a highly confidential operation history such as input of personal information and a password to the server apparatus 200. It becomes possible to prevent.

  Also, instead of simply canceling the transmission of the operation history, the operation history with high confidentiality is edited, replaced with another data, transmitted, and stored in the server device 200. It can be made public. When the operation history display unit 220 of the server device 200 receives a predetermined operation history display request from a third-party terminal device, the operation history display unit 220 reads the corresponding operation event editing data and remote control identification information, and displays the operation history of FIG. Processing similar to the display processing (S506) is performed, and the operation history is displayed to a third party.

  Next, a fourth embodiment will be described.

  The operation history storage system of the fourth embodiment is the same system as that of the third embodiment, but the operation events transmitted and received in the system do not depend on the device and are used universally in any device. It is a message format that can be used. Thereby, the operation history generated by the terminal device 100 can be used even for a device of a model different from the terminal device 100.

  Next, a fifth embodiment will be described.

  FIG. 19 is a sequence diagram illustrating an outline of the operation of the operation history accumulation system according to the fifth embodiment. Steps S901 to S905 are the same as the operations S801 to S805 of the operation history storage system according to the third embodiment. Following these processes, the terminal device 100 transmits terminal attribute information indicating the attributes of the terminal in addition to the operation event editing data and the remote control identification information (S906). The server device 200 generalizes the operation events described in the received operation event edit data and remote control identification information (S907) and accumulates them (S908).

  FIG. 20 is a block diagram of an operation history storage system according to the fifth embodiment.

  Among them, the terminal device 100 transmits the generated operation event editing data, remote control identification information, and terminal attribute information to the server device 200 in addition to the processing unit included in the terminal device 100 of the first embodiment. An operation history analysis / editing unit 150 ″ is provided. The server device 200 includes a processing unit similar to that of the server device 200 of the third embodiment, and operation event editing data received from the terminal device 100 and remote control. An operation history generalization unit 230 that generalizes the operation event described in the identification information is provided.

  Next, the operation event generalization process of S907 will be described.

  FIG. 21 is a flowchart showing a detailed operation of the operation history generalization process (S907).

  First, the operation history generalization unit 230 of the server device 200 receives operation event edit data, remote control identification information, and terminal attribute information from the terminal device 100 (S1001).

  Next, the operation history generalization unit 230 reads an operation event generalization rule that matches the terminal attribute information from the operation event generalization rules stored for each terminal attribute information (S1002).

  Next, the operation events are generalized in order from the first.

  First, the value of n indicating the execution order of operation events to be generalized is designated as an initial value 1 (S1003).

  Next, the nth operation event is rewritten according to the operation event generalization rule (S1004).

  This process is repeatedly executed for the operation event described in the operation event edit data in accordance with the execution order (S1005, S1006).

  When the rewriting process of the operation event described in the operation event edit data is completed, the operation event edit data and the remote control identification information are stored in the operation history storage unit 210 (S1007).

  With this operation history generalization process, the operation history stored in the operation history storage unit 210 becomes data independent of attributes such as the model of the terminal device.

  When a third party terminal device requests the server device 200 to display a specific operation history, first, the third party terminal device transmits its own terminal attribute information to the server device 200 together with the request. . In addition to the operation similar to the case of the third embodiment, the operation history display unit 220 of the server device 200 performs the generated display data according to the operation event reverse generalization rule stored for each terminal attribute information. The display is converted to a display unique to the third-party terminal device and then transmitted to the third-party terminal device.

  By absorbing the difference between the operation events in the server device 200 by the processing described above, the operation history of the terminal device having different attributes can be used.

The flowchart which shows the outline | summary of operation | movement of the terminal device of 1st Embodiment is shown. The block diagram of the terminal device of 1st Embodiment is shown. The flowchart for demonstrating the detailed operation | movement in the remote control start process (S101) of the terminal device 100 is shown. An example of remote control identification information is shown. The flowchart for demonstrating the detailed operation | movement in the application control process (S102) of the terminal device 100 is shown. The flowchart for demonstrating the detailed operation | movement in the accumulation | storage process (S103) of the operation event of the terminal device 100 is shown. An example of level information stored in the level information database 144 is shown. An example of operation history information stored in the operation history storage unit is shown. The flowchart for demonstrating the outline | summary of operation | movement of the terminal device of 2nd Embodiment is shown. The block diagram of the terminal device of 2nd Embodiment is shown. 7 is a flowchart for explaining detailed operations of operation history information analysis / edit processing (S505). An example of an operation event editing rule used for editing an operation event of the operation history analysis / editing unit 150 is shown. 12 shows an example of operation event edit data generated by the processing shown in FIG. 5 is a flowchart for explaining an example of detailed operation of an operation history display process (S506). An example of display data displayed by this processing is shown. An example of display data for a user who is not a party who executes the operation history and is registered based on the operation history information similar to the display data of FIG. 15 but registered in the terminal device is shown. The sequence diagram which shows the outline | summary of operation | movement of the operation history storage system of 3rd Embodiment is shown. The block diagram of the operation history storage system of 3rd Embodiment is shown. The sequence diagram which shows the outline | summary of operation | movement of the operation history storage system of 5th Embodiment is shown. The block diagram of the operation history storage system of 5th Embodiment is shown. The flowchart which shows the detailed operation | movement of operation log generalization processing (S907) is shown.

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 Terminal device 110 Remote control management part 120 Application control part 130 Operation history storage part 140 Application part 141 Input management part 142 Application operation part 143 Operation state temporary storage part 144 Level information database 145 Level information search part 150,150 ', 150 " Operation history analysis / storage unit 200 Server device 210 Operation history storage unit 220 Operation history display unit 230 Operation history generalization unit

Claims (3)

A remote control manager that transmits and receives operation events to and from a remote terminal connected via a network;
An application control unit that transmits an operation event received from the remote control management unit to a predetermined application unit;
An operation history storage unit that stores a history of operation events input to the application control unit in association with remote control identification information for identifying a remote control session;
The application unit that receives an operation event from the application control unit and performs an operation according to the operation event;
With
The application part is
An input management unit that transmits the operation event received from the application control unit to the application operation unit and the level information search unit;
The application operation unit that performs a predetermined operation based on the operation event received from the input management unit and outputs operation state information indicating a current operation state;
When newly receiving operation state information from the application operation unit, the operation state information stored immediately before is transmitted to the level information search unit, and the operation state information temporary storage unit that temporarily stores the newly received operation state information;
A level information database for storing level information of operation events associated with operation events and operation state information;
Using the operation event received from the input management unit and the operation state information received from the operation state information temporary storage unit, the level information of the operation event is searched from the level information database, and the level information acquired as a search result is A level information search unit for transmitting to the application control unit;
With
The level information of the operation event includes an event level indicating whether the operation event is fixed or fluctuates, and a security level indicating a degree of security of the operation event ,
When receiving the level information of the operation event transmitted from the level information search unit of the application unit to the application unit, the application control unit transmits the operation event and the level information to the operation history storage unit,
The operation history storage unit stores the received operation event, level information, and remote control identification information of the remote control in association with each other. In the remote control manager, sending and receiving operation events to and from a remote terminal device connected via a network;
In the application control unit, transmitting an operation event received from the remote control management unit to a predetermined application unit;
In the operation history storage unit, the operation event history input to the application control unit is stored in association with remote control identification information for identifying a remote control session;
In the application unit, receiving an operation event from the application control unit, and performing an operation according to the operation event;
Have
The application part is
In the input management unit, transmitting the operation event received from the application control unit to the application operation unit and the level information search unit;
In the application operation unit, performing a predetermined operation based on the operation event received from the input management unit, and outputting operation state information indicating a current operation state;
In the operation state information temporary storage unit, when new operation state information is received from the application operation unit, the operation state information stored immediately before is transmitted to the level information search unit, and the newly received operation state information is temporarily stored. Steps,
Storing level information of operation events associated with operation events and operation state information in a level information database;
In the level information search unit, the level information of the operation event is searched from the level information database using the operation event received from the input management unit and the operation state information received from the operation state information temporary storage unit. Transmitting the level information acquired as to the application control unit;
Have
The level information of the operation event includes an event level indicating whether the operation event is fixed or fluctuates, and a security level indicating a degree of security of the operation event ,
In the application control unit, when receiving the level information of the operation event transmitted from the level information search unit of the application unit to the application unit, the step of transmitting the operation event and the level information to the operation history storage unit When,
In the operation history storage unit, the received operation event and level information, and the step of storing the remote control identification information of the remote control in association with each other,
An operation history accumulating method characterized by comprising:   An operation history storage program for causing a computer to execute the operation history storage method according to claim 2.

Images