Patent Application
20100174751
1. Field of the Invention
The present invention relates to file management in a remote conference system.
2. Description of the Related Art
In recent years, electronic files such as presentation and documentation files have been used in conventional conferences held atone point or video conference systems interconnecting a plurality of remote locations. Normally, these electronic files are prestored in a predetermined storage device before a conference is started, or carried in a portable storage medium for use in a conference.
In a conventional conference participated by a plurality of members, it has been possible for the members to access an electronic file regardless of whether or not the author thereof attends the conference.
Japanese Patent Application Laid-Open No. 2000-043486 discusses a technique for changing the right to access an electronic file with touch-sensitive input or signature authentication on a software keyboard. This technique is used when accessing a file by using a digital white board in a conference system. However, this technique is not convenient to use since an authenticatable person needs to perform authentication on the white board each time a file is accessed.
Japanese Patent Application Laid-Open No. 2006-303683 (US2006-235851) discusses a technique for changing the right to access a shared electronic file after a user performs login processing from a controller in a video conference system. This technique is not convenient either since it is troublesome for each participant to perform login processing in a conference participated by a plurality of persons.
Further, in a known video conference system, a user changes the right to access an electronic file from the user's identification information and position information identified by a radio transmitter. In a video conference system, a participant at a remote location may access a file. In this case, authentication based on the position information does not work and therefore the participant cannot access the file.
The present invention is directed to permitting a file associated with a specific person to be accessed only when the specific person is authenticated in a file management system simultaneously accessed by a plurality of persons at one point; permitting a file associated with a specific person to be accessed in a multipoint remote conference system; and easily grasping a status of the file access right.
According to an aspect of the present invention, a method for managing a file includes: acquiring at least one personal ID for identifying a person associated with the right to access a file; setting a file operation method depending on whether or not a combination of the acquired personal ID satisfies a condition set for each type of operation for the file; and controlling a file operation based on the set file operation method.
Further features of the present invention will become apparent from the following description of exemplary embodiments with reference to the attached drawings.
The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate exemplary embodiments, features, and aspects of the invention and, together with the description, serve to explain the principles of the invention.
Various exemplary embodiments, features, and aspects of the invention will be described in detail below with reference to the drawings.
It should be noted that the relative arrangement of the components, the numerical expressions and numerical values set forth in these exemplary embodiments do not limit the scope of the present invention unless it is specifically stated otherwise.
A first exemplary embodiment will be described below based on a file management system in which a file icon is dynamically changed in association with a person at a file sharing terminal used by a plurality of persons to operate files.
A typical configuration of the file management system will be described below with reference to
The file management terminal 1 includes an input control unit 11, a shared file control unit 12, an output control unit 13, a personal authentication unit 14, an access right management unit 15, an icon creation unit 16, and an access right management table 17. The file management terminal 1 is connected with a personal ID database (DB) 21, an access right database (DB) 22, and a shared file database (DB).
Each database will be described below. The personal ID database 21 is used to store personal IDs and face information for identifying a person in association.
The access right database 22 is used to store personal IDs of authenticated persons and statuses of the access right (operation right) for each file associated with the personal IDs. The access right for a target file includes the access right to browse, the access right to change, and the access right to copy the file.
The shared file database 23 is used to store shared files.
Each unit in the file management terminal 1 will be described below. The input control unit 11 connects with the keyboard 6 and the mouse 7 connected thereto to acquire input information necessary to operate a file.
The shared file control unit 12 connects with the input control unit 11 to receive input information. The shared file control unit 12 also connects with the access right database 22 to acquire a status of the access right to a target file. The shared file control unit 12 also connects with the shared file database 23 to control file operations in association with the status of the access right to a target file.
The output control unit 13 connects with the shared file control unit 12 to display files and file operations via the projector 3. The output control unit 13 also connects with the icon creation unit 16 to display file icons via the projector 3.
The personal authentication unit 14 connects with the camera 2 to receive a picked-up image. The personal authentication unit 14 also connects with the personal ID database 21 to retrieve face information of a person from the picked-up image, inquires of the personal ID database 21 for the person, and acquires a relevant personal ID. Personal authentication is not limited to a picked-up image, but may use, for example, a record of entering/leaving a conference room or biometric authentication such as voiceprint, fingerprint, vein, and so on. Personal authentication may also use a personal authentication IC, or may be performed from other input terminals.
The access right management unit 15 connects with the access right database 22 to store in the access right database 22 a personal ID received from the personal authentication unit 14. The access right management unit 15 also connects with the shared file database 23 to create the access right management table 17 for determining the access right from file information. The access right management unit 15 determines the type of access right from the personal ID with reference to the access right management table 17 and stores it in the access right database 22.
The icon creation unit 16 connects with the access right management unit 15 to receive an access right change notification. Upon reception of the access right change notification, the icon creation unit 16 connects with the access right database 22 to acquire a status of the file access right and then create an icon associated therewith.
The file management terminal 1 can be an ordinary personal computer, and does not denote a particular terminal. The projector 3 is a display device such as a cathode-ray tube (CRT) and a liquid crystal display, and is not limited to a particular display device. The camera 2 is an input device for performing personal authentication, and is not limited to a camera. The keyboard 6 and the mouse 7 are devices for inputting user operations, and are not limited to particular input devices.
The personal ID database 21 can be provided within the file management terminal 1, and is not limited to the file management terminal having the configuration illustrated in
An exemplary display screen is illustrated in
The marking of the icon for a file not permitted to be browsed is not limited to the mark x, but the icon may be grayed out or outlined. In other words, any types of icons can be used as long as the status of the access right can be easily identified. When a file is permitted to be changed or copied, the file is supplied with a mark denoting the permission of change or a mark denoting the permission of copying, respectively. However, in addition to these marks, any types of icons can be used as long as the status, i.e., the permission of the change and the permission of the copying, can be easily identified. The access right information for each file is not limited to display in the pop-up window 35, but may be displayed, for example, in a status bar at the bottom of the screen.
Procedures for determining the access right will be described below with reference to
Suppose that a person A has a personal ID A, a person B has a personal ID B, and a person C has a personal ID C. In this case, the access right management table 17 illustrated in
The access right to browse a file “Document 1” is validated when a person having the personal ID B or a person having the personal ID C is authenticated. The access right to change the file “Document 1” is validated only when a person having the personal ID B and a person having the personal ID C are authenticated. The access right to copy the file “Document 1” is validated only when a person having the personal ID B and a person having the personal ID C are authenticated. When a file “Document 2” shows the personal ID conditions “ALL”, the access right to browse, the access right to change, and the access right to copy the file are given to any person.
Processing by the file management terminal 1 will be described below. The flow charts of
In step S12, the program creates the access right management table 17 from the extracted access right information. The access right management table 17 is created by the above operations. The program performs the above-mentioned processing for creating the access right management table 17 not only when file sharing starts but also when the number of files in a shared folder is increased or decreased.
In step S25, depending on the result of personal authentication, the program sets the access right for each file with reference to the access right management table 17 based on an acquired personal ID and then stores the access right in the access right database 22. In step S26, the program determines whether or not the access right is changed. When the access right is changed, the program proceeds to step S27 to refresh icon display. When the access right is not changed, the program returns to step S23 to determine whether or not timeout of the icon refresh timer occurs again. The program refreshes icon display according to the above-mentioned flow chart. Timing of refreshing the icon display is not limited to refreshing by the icon refresh timer. The icon display can also be refreshed when the status of personal authentication has changed as a result of personal authentication performed at fixed intervals.
Processing for accessing a file will be described below with reference to the flow chart of
When only the access right to browse a file is validated, for example, the file control setup performs control to permit the file to be browsed but does not permit it to be changed. When the access right to change a file is validated, the file control setup performs control to permit the file to be browsed and changed. In this way, the file control setup performs control to set a control mode to a file in association with the status of the access right for the file. As mentioned above, the first exemplary embodiment makes it possible to dynamically change the file access right and display its icon in association with the access right.
A second exemplary embodiment will be described below based on procedures for dynamically validating a file according to each participant in a multipoint remote conference system.
Each database will be described below. The participant ID database 61 is used to store participant IDs in association with face information for identifying a person. The access right database 62 is used to store participant IDs of authenticated persons and statuses of the access right for each file associated with the personal IDs. The access right for a target file includes the access right to browse, to change, and to copy the file. The shared file database 63 is used to store shared files.
Each unit of the conference terminal 41 will be described below. The conference terminal 41 connects with the participant ID database 61, the access right database 62, and the shared file database 63 via a communication unit 57 to send an inquiry to each database.
An input control unit 51 connects with the keyboard 6 and the mouse 7 to acquire necessary input information for operating a file.
A shared file control unit 52 connects with the input control unit 51 to receive the input information. The shared file control unit 52 also connects with the access right database 62 to acquire a status of the access right for a target file. When the target file is stored in the shared file database 63 at a local point, the shared file control unit 52 connects with the shared file database 63 to control file operations in association with the status of the access right for the target file. When the target file is stored in the shared file database 63 at a remote point, the shared file control unit 52 connects with the shared file database 63 to control file operations in association with the status of the access right for the target file.
An output control unit 53 connects with the shared file control unit 52 to display files and file operations via the projector 3. The output control unit 53 also connects with an icon creation unit 56 to display file icons via the projector 3.
A personal authentication unit 54 connects with the camera 2 to receive a picked-up image. The personal authentication unit 54 also connects with the participant ID database 61 to retrieve face information of a person from the picked-up image, inquires of the participant ID database 61 for the person, and acquires a relevant participant ID.
An access right management unit 55 connects with the shared file database 63 to create an access right management table 58 for determining the access right from file information. The access right management unit 55 also connects with the access right database 62 to store in the access right database 62 a participant ID received from the personal authentication unit 54. The access right management unit 55 acquires a participant ID at a remote point from the communication unit 57 and stores it in the access right database 62. The access right management unit 55 determines the type of access right from the participant ID with reference to the access right management table 17 and stores it in the access right database 62.
The icon creation unit 56 connects with the access right management unit 55 to receive an access right change notification. Upon reception of the access right change notification, the icon creation unit 56 connects with the access right database 62 to acquire a status of the file access right and then create an icon associated therewith.
An identical access right management table 58 is created at each point.
The participant ID database 61 is not limited to that configured in the conference server 71, but may be provided in one conference point or every conference point on the network 45. The access right database 62 is not limited to that configured in the conference server 71, but may be provided in one conference point or every conference point on the network 45. The shared file database 63 is not limited to that configured in the conference server 71, but may be provided in one conference point or every conference point on the network 45. A file display method according to the second exemplary embodiment is similar to that in the first exemplary embodiment.
Procedures for creating the access right management table 58 will be described below.
In step S11, when a conference starts, the program first extracts the access right information from a file stored in the shared file database 63 at local and remote points. The access right setup for a file according to the present exemplary embodiment is similar to that in the first exemplary embodiment. In step S12, the program creates the access right management table 58 from the extracted access right information. An identical access right management table 58 is created at each point.
Processing for changing icon display in a multipoint remote conference system will be described below. The flow chart of
In step S46, the program retrieves the participant ID from the participant ID database 61, sets the access right for each file with reference to the access right management table 58, and stores it in the access right database 62. In step S47, the program determines whether or not the access right is changed. When the access right is changed, the program proceeds to step S48 to refresh icon display. When the access right is not changed, the program returns to step S43 to determine whether or not timeout of the icon refresh timer occurs again. Timing of refreshing icon display is not limited to refreshing by the icon refresh timer. Icon display can also be refreshed when the status of personal authentication has changed as a result of personal authentication performed at fixed intervals.
Processing upon reception of a participant ID will be described below. The flow chart of
In step S51, the program receives a participant ID from other points. In step S52, the program updates the participant ID database 61 according to the received participant ID. In step S53, the program retrieves the participant ID from the participant ID database 61, sets the access right for each file with reference to the access right management table 58, and stores it in the access right database 62. In step S54, the program determines whether or not the access right is changed. When the access right is changed, the program proceeds to step S55 to refresh icon display. The program refreshes icon display according to the above-mentioned flow chart.
Processing for accessing a file according to the present exemplary embodiment is similar to that in the first exemplary embodiment. The second exemplary embodiment has specifically been described based on a remote conference system for two points. However, the present invention is not limited to two points, but can also be embodied at three or more points.
In the above-mentioned second exemplary embodiment, participants at both local and remote points can perform the same operation for a file when the relevant access right is validated. The following describes procedures for differentiating the file access right by using a different access right management table 58 at each point, in a multipoint remote video conference system. Further, at each point, icon display for a file is changed in association with the access right for the file.
Since a third exemplary embodiment differs from the second exemplary embodiment only in creation of the access right management table 58, procedures for creating the access right management table 58 will be described below. In the third exemplary embodiment, the access right management table 58 is created from the access right information for each file stored in the shared file database 63. When setting the access right information for each file, conditions for validating the access right are set distinguishing between local and remote points. This condition setup is performed when a file is created and stored or when a file is stored in a shared folder. The access right management table 58 is created based on conditions for validating the access right at the local point with respect to files at the local point, and on conditions for validating the access right at a remote point with respect to files at a remote point. At each point, operation control and icon creation for a file are performed based on respective access right management table 58 created at each point, thus enabling icon display in association with the access right for the file.
In a file management system simultaneously accessed by a plurality of persons, managing persons and files in an association makes it possible to control access to a file even when there is no author thereof, no right holder thereof, or no person in charge of its contents. This enables security protection of files and accordingly improves security functions. Further, the status of a file can be easily grasped in a visible way, for example, by dynamically changing icon display in association with the status of the access right for the file.
Aspects of the present invention can also be realized by a computer of a system or apparatus (or devices such as a CPU or MPU) that reads out and executes a program recorded on a memory device to perform the functions of the above-described embodiment (s), and by a method, the steps of which are performed by a computer of a system or apparatus by, for example, reading out and executing a program recorded on a memory device to perform the functions of the above-described embodiment (s). For this purpose, the program is provided to the computer for example via a network or from a recording medium of various types serving as the memory device (e.g., computer-readable medium).
While the present invention has been described with reference to exemplary embodiments, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. The scope of the following claims is to be accorded the broadest interpretation so as to encompass all modifications, equivalent structures, and functions.
This application claims priority from Japanese Patent Application No. 2009-001952 filed Jan. 7, 2009, which is hereby incorporated by reference herein in its entirety.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2009-001952 | Jan 2009 | JP | national |
