WO2013153602A1

WO2013153602A1 - Access information output program and access information output method

Info

Publication number: WO2013153602A1
Application number: PCT/JP2012/059702
Authority: WO
Inventors: 那由他石井; 泰大山本; 恭平倉世古; 拓嗣島田
Original assignee: 株式会社Ｓｙｎｃｌｏｇｕｅ
Priority date: 2012-04-09
Filing date: 2012-04-09
Publication date: 2013-10-17

Abstract

The objective of the present invention is to enable the specification of a file accessed in an application. A computer records, in an application information recording unit, application information that is information in which an application identifier that is an identifier for an application and a process identifier that is an identifier for a process being executed by the application are associated, and in accordance with an access request containing information that can specify the process identifier of the process and a file that is the subject of access by the process, access information indicating that the process has accessed the file is output.

Description

Access information output program and access information output method

The present invention relates to an access information output program and an access information output method.

When an application is executed in an information processing apparatus such as a personal computer, various files such as a setting file and a user data file are required in addition to the application execution file. Therefore, in order to save such an application on a recording medium for disaster recovery or to make it available to other computers, it is necessary to specify not only the application executable file but also the file accessed in the application. There is. For example, Patent Document 1 discloses a system that specifies data that has been changed during execution of an application and automatically backs up the specified data.

Japanese Patent Laid-Open No. 2005-209065

However, in the system described in Patent Document 1, it is possible to specify the data changed during the execution of the application as a backup target, but it is not possible to specify the file accessed in the application.

Therefore, an object of the present invention is to make it possible to specify a file accessed in an application.

An access information output program according to an aspect of the present invention uses a computer to store application information, which is information that associates an application identifier that is an application identifier with a process identifier that is an identifier of a process that is executing the application. Access information indicating that the process has accessed the file in response to an access request including information that can identify the application monitoring unit stored in the information storage unit, the file to be accessed by the process, and the process identifier of the process It is made to function as an access information output unit that outputs.

In the access information output method according to one aspect of the present invention, the application information is information in which the computer associates an application identifier that is an application identifier with a process identifier that is an identifier of a process that is executing the application. Is stored in the application information storage unit, and access information indicating that the process has accessed the file in response to an access request including information capable of specifying the file to be accessed by the process and the process identifier of the process. Output.

In the present invention, the “unit” does not simply mean a physical means, but includes a case where the function of the “unit” is realized by software. Also, even if the functions of one “unit” or device are realized by two or more physical means or devices, the functions of two or more “units” or devices are realized by one physical means or device. May be.

According to the present invention, it is possible to specify a file accessed in an application.

It is a block diagram which shows an example of the function which the personal computer (PC) in the 1st Embodiment of this invention has. It is a figure which shows an example of the relationship of the function which PC has. It is a figure which shows an example of the monitoring object application information. It is a figure which shows an example of application information. It is a figure which shows an example of access information. It is a figure which shows an example of specific information. It is a flowchart which shows an example of the file specific process in 1st Embodiment. It is a figure which shows the structural example of the application synchronization system in 2nd Embodiment. It is a block diagram which shows an example of the function which a synchronous server has. It is a figure which shows an example of the data for a synchronization. It is a block diagram which shows an example of the function which PC has. It is a figure which shows an example of the screen displayed in the case of a synchronous setting. It is a figure which shows an example of a synchronous setting. It is a figure which shows an example of the screen which starts the application of a synchronous object. It is a flowchart which shows an example of the synchronous process in 2nd Embodiment.

== First Embodiment ==
First, a first embodiment of the present invention will be described. FIG. 1 is a block diagram illustrating an example of functions of the personal computer (PC) 10 according to the first embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a function relationship of the PC 10.

As shown in FIG. 1, the PC 10 includes a file storage unit 20, an application execution unit 22, a monitoring target application information storage unit 24, an application monitoring unit 26, an application information storage unit 28, a file system filter driver 30, and an access information storage unit 32. A file system driver 34, a file specifying unit 36, and a specific information storage unit 38. Each unit constituting the PC 10 can be realized, for example, by using a storage area such as a memory or a storage device, or by a processor executing a program stored in the storage area. In particular, the application monitoring unit 26, the file system filter driver 30, and the file specifying unit 36 are realized by a processor executing an access information output program. Hereinafter, each part which comprises PC10 is demonstrated, referring FIG.

The file storage unit 20 stores various files used in the PC 10. Various files include, for example, programs and data used in an operating system (OS) and applications. Each file can be identified by a file ID (file identifier) including a file path name and a file name.

The application execution unit 22 executes an application (application program) stored in the file storage unit 20. Specifically, the application execution unit 22 executes the application by generating a “process” that is an instance of the program. Each process is assigned a process ID (process identifier) for identifying the process. In the present embodiment, the application execution unit 22 can execute an application in a user mode. In this embodiment, a process of an application that is a file access monitoring target is called a monitoring target process 100, and a process of an application that is not a monitoring target is called a non-monitoring process 110.

The monitoring target application information storage unit 24 stores monitoring target application information, which is information related to an application that is a file access monitoring target. FIG. 3 shows an example of the monitoring target application information. In the example illustrated in FIG. 3, the monitoring target application information includes an application ID (application identifier). The application ID is information for identifying the application, and is, for example, an application name or an executable file name.

The application monitoring unit 26 monitors the execution state of the application on the PC 10. If the application specified by the monitoring target application information is being executed, the application monitoring unit 26 acquires the process ID of the application. For example, if the OS of the PC 10 is Windows (registered trademark), it is possible to monitor the execution state of the application and acquire the process ID by using an API (Application Program Interface) function such as ToolHelp32. When the process ID of the monitoring target application is acquired, the application monitoring unit 26 generates application information in which the application ID is associated with the process ID, and stores the application information in the application information storage unit 28. FIG. 4 shows an example of application information.

In addition, when the process ID of the monitoring target application is acquired, the application monitoring unit 26 notifies the file system filter driver 30 of the process ID. The application monitoring unit 26 may refer to the application information storage unit 28 instead of notifying the file system filter driver 30 of the process ID.

The file system filter driver 30 (access information output unit) specifies a file accessed from the monitoring target process 100 by filtering an access request for the file. In the present embodiment, the file system filter driver 30 is executed in the kernel mode. For example, if the OS of the PC 10 is Windows (registered trademark), an input / output request packet (IRP: I / O Request Packet) is issued when a process accesses a file. The IRP includes information that can specify the file to be accessed and the process ID of the process making the access request. Note that the file ID and process ID itself do not need to be included in the IRP, and it is sufficient that the file ID and process ID can be specified based on the information included in the IRP. In this embodiment, IRP is described as an example of an access request. However, the access request is not limited to the IRP, and can be in any format according to the OS.

In a configuration where the file system filter driver 30 does not exist, file access is executed by outputting the IRP to the file system driver 34. The file system filter driver 30 can intercept the IRP output to the file system driver 34 and specify a file accessed in the monitoring target process 100. Specifically, when the process ID of the process that issued the IRP is included in the process ID notified from the application monitoring unit 26, the file system filter driver 30 specifies the file ID of the file to be accessed by the IRP. . The file system filter driver 30 can store the process ID notified from the application monitoring unit 26. Then, the file system filter driver 30 generates access information in which the process ID and the file ID are associated with each other, and stores the access information in the access information storage unit 32. FIG. 5 shows an example of access information.

The file system filter driver 30 outputs the IRP to the file system driver 34 after generating the access information. If the process ID of the process that issued the IRP is not included in the process ID notified from the application monitoring unit 26, that is, if the process that issued the IPR is the non-monitoring process 110, the file system filter driver 30. Outputs the IRP to the file system driver 34 without generating access information.

The file system driver 34 receives the IRP via the file system filter driver 30 and executes access to the file specified by the IRP. In the present embodiment, the file system driver 34 is executed in the kernel mode.

The file specifying unit 36 specifies a file accessed in the monitoring target application based on the application information stored in the application information storage unit 28 and the access information stored in the access information storage unit 32. Specifically, the file specifying unit 36 determines the correspondence between the application ID and the file ID based on the correspondence between the application ID and the process ID in the application information and the correspondence between the process ID and the file ID in the access information. To do. Then, the file specifying unit 36 generates specific information in which the application ID and the file ID are associated with each other, and stores the specific information in the specific information storage unit 38. FIG. 6 shows an example of the specific information.

FIG. 7 is a flowchart showing an example of the file specifying process in the first embodiment. The application monitoring unit 26 monitors the execution state of the application by the application execution unit 22 (S700). For example, the application monitoring unit 26 can monitor the execution state of the application by repeatedly executing an API function for acquiring information related to the process being executed at short predetermined intervals.

When the application monitoring unit 26 detects that the application to be monitored is activated (S701: Y), it acquires the process ID of the application (S702). Then, the application monitoring unit 26 generates application information in which the application ID and the process ID are associated, and stores the application information in the application information storage unit 28 (S703). The application monitoring unit 26 notifies the file system filter driver 30 of the acquired process ID (S704).

The file system filter driver 30 stores the process ID notified from the application monitoring unit 26 (S710). As described above, the file system filter driver 30 may refer to the application information storage unit 28 instead of storing the process ID notified from the application monitoring unit 26.

When the file system filter driver 30 receives the IRP (access request) (S711: Y), the file system filter driver 30 acquires the process ID of the application being executed based on the information included in the IRP (S712). When the acquired process ID is included in the process ID notified from the application monitoring unit 26, that is, when it is a process to be monitored (S713: Y), the file system filter driver 30 is based on information included in the IRP. The file ID of the file to be accessed is acquired (S714). Then, the file system filter driver 30 generates access information in which the process ID and the file ID are associated with each other, and stores them in the access information storage unit 32 (S715). Thereafter, the file system filter driver 30 outputs the IRP to the file system driver 34 (S716). If the process is not a process to be monitored (S713: N), the file system filter driver 30 outputs IRP to the file system driver 34 without generating access information (S716).

The file specifying unit 36 specifies a file accessed in each application based on the application information stored in the application information storage unit 28 and the access information stored in the access information storage unit 32 (S720). . Then, the file specifying unit 36 generates specific information in which the application ID and the file ID are associated with each other, and stores the specific information in the specific information storage unit 38 (S721).

Thus, according to the present embodiment, the relationship between the application and the process can be found from the application information, and the relationship between the process and the accessed file can be found from the access information. Therefore, a file accessed by each application can be specified based on the application information and access information. For example, in this embodiment, specific information indicating a file access result by each application is output based on the application information and the access information. By referring to this specific information, for example, when backing up a program file of each application together with a data file or a setting file required when executing the program to a recording medium or transferring it to another PC, Necessary files can be specified.

In the present embodiment, the application monitoring unit 26 acquires the process ID of the monitoring target application and generates application information. However, the application monitoring unit 26 acquires the process IDs of all the applications and acquires the application information. Information may be generated.

== Second Embodiment ==
Next, a second embodiment of the present invention will be described. In the second embodiment, application synchronization processing is executed among a plurality of PCs by using specific information. FIG. 8 is a diagram illustrating a configuration example of an application synchronization system according to the second embodiment. As shown in FIG. 8, the application synchronization system includes a synchronization server 200 and a plurality of PCs 210. The synchronization server 200 provides a service for enabling an application to be synchronized between a plurality of PCs 210, and is configured using one or a plurality of information processing apparatuses. The PC 210 is an information processing apparatus that allows a user to execute an application, and can communicate with the synchronization server 200 via a network such as the Internet.

Here, for example, it is assumed that the user “USER001” has two PCs, PC 210-1 and PC 210-2. By using the application synchronization system provided by the synchronization server 200, the user “USER001” does not need to install an application individually on each PC or manually synchronize data, and the PC 210-1 and the PC 210- It is possible to execute the application in a synchronized state in FIG. Here, the application synchronization means that the execution environment of the application is in the same state. Note that the execution environment includes a program file of an application, a data file required when executing the program, a setting file, and the like. By synchronizing applications among a plurality of PCs, the user can execute the applications in the same state regardless of which PC is used.

FIG. 9 is a block diagram illustrating an example of the functions of the synchronization server 200. As shown in FIG. 9, the synchronization server 200 includes a communication unit 300, a user account database (DB) 302, and a synchronization data storage unit 304. These units can be realized, for example, by using a storage area such as a memory or a storage device, or by executing a program stored in the storage area by a processor.

The communication unit 300 can transmit and receive data to and from other information processing apparatuses such as the PC 210 via the network. And the communication part 300 can perform various control for synchronizing an application between several PC210.

The user account DB 302 stores account information of users who use the application synchronization system. For example, the account information includes a user ID, a password, an email address, and the like.

The synchronization data storage unit 304 stores synchronization data that is data for synchronizing a user's application execution environment among a plurality of PCs. FIG. 10 shows an example of synchronization data. In the example illustrated in FIG. 10, the synchronization data includes data stored in the synchronization table and data stored in the data storage. The synchronization table stores a user ID, an application ID, an application file ID, a user file / file ID, and an update date / time, and the data storage stores application and user file data.

The user ID is for identifying each user, and the same information as that registered in the user account DB 302 is used. The application ID is for identifying an application selected as a synchronization target by each user. This application ID may be set, for example, when the user registers the synchronization target application in the synchronization server 200, or may be generated on the synchronization server 200 side.

Application is a file including an executable file and DLL (Dynamic Link Library). The application also includes information for designating a folder for storing the application in the PC 210. The application file ID indicates the storage location of the application in the data storage. The user file is a file including user data that is accessed when the application is executed. User data is data for each user that is referred to when the application is executed. For example, each user's e-mail data in an e-mail application for sending and receiving e-mails, each user's bookmark data in a web browser It is. The user file also includes information for designating a folder for storing the user file in the PC 210. The user file / file ID indicates the storage location of the user file in the data storage. The date and time when the application or user file was updated is set as the update date and time.

FIG. 11 is a block diagram illustrating an example of functions that the PC 210 has. The PC 210 includes a file storage unit 20, an application execution unit 22, an application monitoring unit 26, an application information storage unit 28, a file system filter driver 30, an access information storage unit 32, a file system driver 34, a file specification unit 36, and a specific information storage. Part 38 is included. Since the functions of these units are the same as those in the first embodiment, description thereof is omitted. Further, the PC 210 includes a synchronization setting unit 400, a synchronization setting storage unit 402, an application activation unit 404, and a synchronization communication unit 406. Each unit constituting the PC 210 can be realized, for example, by using a storage area such as a memory or a storage device, or by executing a program stored in the storage area by a processor.

The synchronization setting unit 400 performs settings for synchronizing applications among a plurality of PCs 210. FIG. 12 shows an example of a screen displayed at the time of synchronization setting. This screen is displayed when the application synchronization system program is started. By using this screen, the user can register an application to be synchronized or start an application in a synchronized state. For example, when the user moves a shortcut 510 of an application APL001 on the desktop of the PC 210 to the display area 512 of the screen 500 by drag and drop, the synchronization setting unit 400 sets the application specified by the shortcut to be synchronized You can register as an application.

It should be noted that any method for causing the synchronization setting unit 400 to recognize the application to be synchronized can be used, not limited to drag and drop. For example, as shown in FIG. 12, the application to be registered may be specified by pressing an application addition button 514 to display a file reference interface. Then, the synchronization setting unit 400 stores information related to the synchronization target application in the synchronization setting storage unit 402. Note that the synchronization setting unit 400 may store the information related to the synchronization target application in the synchronization data storage unit 304 of the synchronization server 200 instead of storing the information in the synchronization setting storage unit 402.

FIG. 13 shows an example of the synchronization setting stored in the synchronization setting storage unit 402. As shown in FIG. 13, the synchronization setting includes information indicating the user ID, password, application ID, application file ID, user file / file ID, and update date / time. The user ID and password are for using the application synchronization system. For example, the user ID and password are registered by the synchronization setting unit 400 at the start of use of the system. The application ID, application file ID, user file / file ID, and update date / time are equivalent to the information stored in the synchronization data storage unit 304 of the synchronization server 200.

The application activation unit 404 activates the synchronization target application in response to a user operation. For example, when the display area 520 assigned to the application APL001 is selected on the screen 500 shown in FIG. 14, the application activation unit 404 refers to the synchronization setting stored in the synchronization setting storage unit 402 and sets the application APL001. to start. The application activated by the application activation unit 404 is executed by the application execution unit 22 in the same manner as other applications.

The synchronous communication unit 406 performs data communication for synchronizing applications among a plurality of PCs 210. Specifically, the synchronization communication unit 406 can synchronize the synchronization target application and user file with the synchronization server 200 with reference to the synchronization setting storage unit 402. Specifically, for example, the synchronization communication unit 406 includes the content of the synchronization setting stored in the synchronization setting storage unit 402 and the content of the synchronization data stored in the synchronization data storage unit 304 of the synchronization server 200. It is possible to match the contents of the application and the user file to the latest state for each user ID and application ID. Furthermore, the synchronization communication unit 406 can synchronize the file accessed by the synchronization target application with the synchronization server 200 as a user file based on the specific information stored in the specific information storage unit 38. . That is, the synchronization communication unit 406 cannot include the synchronization setting, but can include a file accessed by the synchronization target application as the synchronization target. Note that the timing at which the synchronization communication unit 406 communicates with the synchronization server 200 is, for example, a predetermined value set by a timer when the application activation unit 404 activates the screen 500 or when the synchronization target application ends. Any timing such as an interval may be used.

FIG. 15 is a flowchart illustrating an example of the synchronization processing in the second embodiment. When the program for the application synchronization system is activated, the synchronization communication unit 406 accesses the synchronization server 200 and executes synchronization processing (S1500). Specifically, the synchronization communication unit 406 compares the content of the synchronization setting stored in the synchronization setting storage unit 402 with the content of the synchronization data stored in the synchronization data storage unit 304 of the synchronization server 200. If it is determined that the file stored in the synchronization server 200 is newer than the file stored in the PC 210, the file stored in the synchronization server 210 is stored in the file storage unit 20 of the PC 210. Update the file.

For example, as illustrated in FIG. 14, when an application to be executed is selected, the application activation unit 404 activates the selected application (S1501). As a result, a process is generated by the application execution unit 22 and the application is executed.

The application monitoring unit 26 acquires the process ID of the application by monitoring the execution state of the application started by the application starting unit 404 (S1502). Note that the application monitoring unit 26 can set the application specified by the synchronization setting as a monitoring target application. That is, in this embodiment, it can be said that the synchronization setting includes monitoring target application information.

Subsequently, the application monitoring unit 26 generates application information in which the application ID and the process ID are associated with each other and stores the application information in the application information storage unit 28 (S1503). The application monitoring unit 26 notifies the file system filter driver 30 of the acquired process ID (S1504).

The application execution unit 22 executes the application until the processing is completed (S1505, S1506).

The file system filter driver 30 stores the process ID notified from the application monitoring unit 26 (S1510). When the file system filter driver 30 receives the IRP (access request) (S1511: Y), the file system filter driver 30 acquires the process ID of the application being executed based on the information included in the IRP (S1512). When the acquired process ID is included in the process ID notified from the application monitoring unit 26, that is, when it is a process to be monitored (S1513: Y), the file system filter driver 30 is based on information included in the IRP. The file ID of the file to be accessed is acquired (S1514). Then, the file system filter driver 30 generates access information in which the process ID and the file ID are associated with each other, and stores them in the access information storage unit 32 (S1515). Thereafter, the file system filter driver 30 outputs the IRP to the file system driver 34 (S1516). If the process is not a process to be monitored (S1513: N), the file system filter driver 30 outputs IRP to the file system driver 34 without generating access information (S1516).

When the execution of the application is completed (S1506: Y), the file specifying unit 36 determines whether to execute the application based on the application information stored in the application information storage unit 28 and the access information stored in the access information storage unit 32. The file accessed in step S1520 is specified (S1520). Then, the file specifying unit 36 generates specific information in which the application ID and the file ID are associated with each other, and stores the specific information in the specific information storage unit 38 (S1521).

Thereafter, the synchronization communication unit 406 executes a synchronization process with the synchronization server 200 based on the synchronization setting stored in the synchronization setting storage unit 402 and the specific information stored in the specific information storage unit 38. (S1522). Thereby, in addition to the file predetermined by the synchronization setting, the file accessed in the application can be synchronized. That is, even if it is difficult to specify all the files to be accessed in the application in advance, it is possible to synchronize the files necessary for executing the application.

In addition, this embodiment is for making an understanding of this invention easy, and is not for limiting and interpreting this invention. The present invention can be changed / improved without departing from the spirit thereof, and the present invention includes equivalents thereof.

10 PC
DESCRIPTION OF SYMBOLS 20 File storage part 22 Application execution part 24 Monitoring object application information storage part 26 Application monitoring part 28 Application information storage part 30 File system filter driver 32 Access information storage part 34 File system driver 36 File specification part 38 Specific information storage part 200 Synchronization server 210 PC
300 Communication unit 302 User account DB
304 synchronization data storage unit 400 synchronization setting unit 402 synchronization setting storage unit 404 application activation unit 406 synchronization communication unit

Claims

Computer
An application monitoring unit that stores application information, which is information in which an application identifier that is an application identifier is associated with a process identifier that is an identifier of a process that is executing the application, in an application information storage unit;
An access information output unit that outputs access information indicating that the process has accessed the file in response to an access request including information that can identify the file to be accessed by the process and the process identifier of the process;
Program to function as.
The program according to claim 1,
The access information output unit outputs the access request to an access processing unit that executes access processing for a file.
program.
The program according to claim 1 or 2,
Said computer further
A specific information output unit that outputs specific information in which an application identifier of an application is associated with a file identifier of a file accessed by the process of the application based on the application information and the access information;
Program to function as.
A program according to any one of claims 1 to 3,
The application monitoring unit generates the application information for the predetermined application by monitoring an execution state of the predetermined application.
program.
The program according to claim 4,
The application monitoring unit notifies the access information output unit of a process identifier obtained by the monitoring;
The access information output unit outputs the access information in response to the access request from the process indicated by the notified process identifier;
program.
Computer
Storing application information, which is information in which an application identifier, which is an application identifier, is associated with a process identifier, which is an identifier of a process that is executing the application, in the application information storage unit;
Outputting access information indicating that the process has accessed the file in response to an access request including information capable of specifying the file to be accessed by the process and the process identifier of the process;
Access information output method.