JPH08202659A - Common information processing system - Google Patents

Abstract

PURPOSE: To protect common information against alteration individually by managing the information showing whether a terminal is permitted to access the common information and permitting only a terminal which is permitted to access the common information according to the managed information. CONSTITUTION: To offer the common information 7 to a conference server 5 from a terminal 1 as owner, a document number, owner information (terminal 1 in this case), and connection information (terminals 2 and 4 in this case) are added to a document when the common information 7 is the document. The conference server 5 receives a request to access the common information 7, judges whether or not the terminal is the owner of the common information on the basis of the owner information, and allows access when so. When the terminal is not the owner, on the other hand, it is judged from the connection information whether or not a connection with the owner is set, and access is allowed when the connection is set, but rejected when not.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a shared information processing system that protects alterations to shared information when performing collaborative work using a computer via a network, for example.

[0002]

2. Description of the Related Art Conventionally, when performing work in a shared window or collaborative work via a network, information is written by logging in to a device in which shared information is stored. In addition, modification and protection of shared information has been performed by designating a disk or directory for storing shared information and granting write and read rights to the disk and directory only to group members. In such a conventional method, there is a problem in that the protection against the alteration can be performed only on a disk or directory basis, and the protection against the alteration of individual shared information cannot be performed. Therefore, it is conceivable to prepare a disk and a directory for each piece of shared information to protect against alteration, but in this case, there arises a problem of inefficiency.

[0003]

As described above, according to the conventional method, the shared information is protected against modification by the unit of disk or directory, and there is a problem that the modification cannot be protected individually for each shared information.

Therefore, an object of the present invention is to provide a shared information processing system capable of eliminating such problems and performing alteration protection for individual shared information.

[0005]

In order to solve the above problems, the present invention is configured so that a plurality of terminals are connected via a network and each terminal can access and rewrite shared information between these terminals. In the shared information processing system,
A means for managing information as to whether or not to permit access to the shared information when the shared information is accessed from the terminal, and the shared information only for the terminal to which access is permitted based on this management information And means for permitting access to.

According to another aspect of the invention, in a shared information processing system in which a plurality of terminals are connected via a network and each terminal can access and rewrite shared information between these terminals, A means to determine whether the terminal is the owner of the shared information when the shared information is accessed, and whether the terminal has a connection with the owner when the terminal is not the owner of the shared information. And a means for determining whether the ID code or password entered from the terminal is correct when the terminal has a connection with the owner, and the terminal is correct from the owner of the shared information or the terminal. And means for permitting access to the shared information only when an ID code or a password is input.

In the above invention, whether to permit access to the shared information may be managed separately for writing and reading, or the rewritten shared information may be the shared information before rewriting. It may be managed separately.

[0008]

According to the present invention, when the terminal accesses the shared information, the information as to whether or not the terminal is permitted to access is managed, and the access is permitted based on this management information. Since it is configured such that only the terminals that have access to the shared information are permitted, it is possible to prevent disorderly alteration of individual shared information.

[0009]

Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 is a diagram showing the configuration of a system according to an embodiment of the present invention. In the figure, 1-4 are terminals, 5
Is a conference server, and 6 is a network. The conference server 5 includes an information storage unit 8 that stores shared information 7, an access management unit 9, and a filing processing unit 10.

In the system as described above, the operation when the collaborative work is performed will be described. The range in which the connection is set is shown in FIG. In the figure, 11 is the range in which the connection is set. Here, the terminal 1,
It is assumed that a connection is set up between the second and fourth servers and the conference server 5 via the network 6 to carry out a joint work such as a conference. That is, no connection is set for the terminal 3.

On each of the terminals 1 to 4, there is a shared window for displaying shared information commonly used by the terminals holding the conference, and the conference is advanced by reading and writing information on this shared window.

FIG. 3 shows the display of each of the terminals 1 to 4. 12 is the display of the terminal 1, 13 is the display of the terminal 2, 14 is the display of the terminal 3, 15 is the display of the terminal 4, and 16 to 19 are the shared windows of the respective terminals 1 to 4. Here, terminal 1,
Since two and four work together, the shared windows 16, 17, and 19 in FIG. 3 have the same material (shared information), for example, "a".
bcdefghij ”is displayed. The shared window 18 on the display of the terminal 3 cannot be the same as the shared windows of the terminals 1, 2, and 4. The shared window 18 on the display of the terminal 3 is, for example,“ Aiue Okakike This is displayed.

In this embodiment, for example, when the shared information (material) for holding a conference is provided from the terminal 1, the terminal 1
Is the owner of the shared information 7, and only the owner of the shared information 7 or the terminal setting the connection to the owner (here, terminals 1, 2, 4) can access (write, read, etc.) the shared information. You can That is,
Terminal 3 with no connection set up for terminal 1
Cannot access the shared information 7.

The shared information is provided from the terminal 1 as the owner to the conference server 5, as shown in FIG. 4, when the shared information is, for example, a document, a document 41, a document number 42,
The owner information 43 (here, terminal 1) and the connection terminal information 44 (here, terminals 2 and 4) are attached.

At this time, if each of the terminals 1, 2 and 4 requests access to the shared information 7 to the conference server 5 and writes and reads to the shared information 7, the conference server 5 is assumed.
The access request control flow in is as shown in FIG. That is, the conference server 5 receives an access request to the shared information 7 (step 501), determines whether the terminal is the owner of the shared information based on the owner information 43 of FIG. 4 (step 502), and if it is the owner. Access is permitted (step 503), and if it is not the owner, it is judged whether or not the connection with the owner is set based on the connection terminal information 44 of FIG. 4 (step 50).
4) If it is set, access is permitted (step 503), and if it is not set, access is denied (step 505).

For example, when the terminal 1 (owner of shared information) requests access to the shared information 7, the conference server 5 determines that the owner is the owner, and permits access to the shared information 7. Further, when there is an access request from the terminal 2, access is permitted because the connection is set with the owner but not the owner. On the other hand, when there is an access request from the terminal 3, the access to the shared information is denied because it is not the owner and the connection with the owner is not set. This state is shown in FIG. 20 is authorized access to shared information,
21 is a denied access.

Further, by providing the shared information provider (owner) or the conference server 5 with a function of restricting access to the shared information 7, it becomes possible to select a terminal that can access. The flow of the determination is shown in FIG. When an access request is generated (step 701), it is determined whether the access request source is the owner (step 70).
2) If the owner, access is permitted (step 70).
3) If it is not the owner, it is judged whether or not the connection with the owner is set (step 704), and if it is not set, the access is denied (step 70).
5) If it is set, it is judged whether access (writing, reading) is restricted (step 70).
6) If it is restricted, the access is denied (step 705), and if it is not restricted, the access is permitted (step 703).

Here, the terminals 1, 2, 4 and the conference server 5
An example of a case where a connection is set between them and the terminal 4 is subject to access restriction is shown below. In other words, considering the case where there is shared information provided from the terminal 1, as shown in FIG. 8, when there is an access request from the terminal 1, access is permitted because the owner is the owner. Also, when there is an access request from the terminal 2, a connection is set although it is not the owner, and
Access is permitted because there is no access restriction. On the other hand, when there is an access request from the terminal 3, the access is denied because it is not the owner and the connection with the owner is not set. Also, the terminal 4
When there is an access request from, the access is denied because the connection is set with the owner but not the owner but access is restricted. Further, an ID code, a password or the like can be used to restrict access to the terminals 1 to 4 that issue an access request. That is, the ID code and password are set in the shared information 7, and the ID code and password are notified only to the terminals 1 to 4 that are permitted to access. In this case, the shared information provider (owner) or the conference server 5 manages the access right. FIG. 9 shows a flow of access control in the conference server 5 at this time. When there is an access request from a certain terminal (step 901), it is determined whether the access request source is the owner (step 902), and if the owner is the owner, the access is permitted (step 903). It is judged whether the connection is set (step 904). If it is not set, the access is denied (step 905). If it is set, the ID code and password are requested and the correctness is judged ( If it is correct, the access is permitted (step 903), and if it is incorrect, the access is denied (step 905).

For example, for the shared information 7 provided by the terminal 1, the ID code "ABCDEFG" and the password "12"
34 "is set. It is assumed that the ID code and the password have been notified to the terminal 4 and the terminal 2 has not.

In this case, as shown in FIG. 10, when the terminal 1 makes an access request to the shared information 7, access is permitted because it is the owner. On the other hand, when the terminal 2 issues an access request, access is denied because the connection with the owner is set but not the owner but the ID code and password are not known. When the terminal 3 issues an access request, the access is denied because it is not the owner and the connection with the owner is not set. On the other hand, when the terminal 4 issues an access request, the access is permitted because the connection is set with the owner but not the owner and the ID code and password are notified.

By controlling write access and read access separately for access to shared information,
Shared information can be displayed in the terminal window other than the owner, but it can be set so that it cannot be written. The control flow at this time is shown in FIG.

When there is an access request from a certain terminal (step 1101), it is judged whether or not it is the owner (step 1102), and if it is the owner, write access and read access are permitted (steps 1103 and 110).
4). On the other hand, if it is not the owner, it is judged whether the connection with the owner is set (step 11).
05), if not set, write access and read access are denied (step 1106). If it is set, it is judged whether it is a write request or a read request (step 1107). Then, when it is a write request, it is judged whether or not there is a write restriction (step 1108). When there is a restriction, write access and read access are denied (step 1106), and when there is no restriction, only write access is permitted. (Step 1103). On the other hand, when it is a read request, it is judged whether or not there is a read restriction (step 1109). When there is a restriction, write access and read access are denied (step 1106), and when there is no restriction, only read access is permitted. (Step 1104).
There may be a case where it is desired to write shared information for which writing is prohibited. In such a case, each terminal 1 to 4 can store a separate file in a form related to the shared information without rewriting the shared information file. FIG. 12 shows an example at this time. In FIG. 12, 2
1 is shared information (stored in a shared information file in the conference server), 22 is write information (stored in each terminal in a file different from shared information), and 23 is a combination of shared information and write information. is there. In the shared information, "ABCDE AIUEO" is written as a material, and the writing information is underlined in the text of the shared information.
It is possible to write to the shared information without modifying the original shared information file.

When the shared information is provided from the terminal 1, not only the information shown in FIG. 4 but also the transfer date and time, the serial number, the copyright mark, etc. can be written in the shared information to distinguish the owner from the others. In addition, when there is writing from a terminal that is allowed to write, etc., it is possible to check at any time who has made the rewriting by providing a function to automatically write the rewriting date and time, the rewriter, and the copyright mark. .

The functions described in the above embodiments may be realized not only by the conference server but also by having the same function on the shared information provider side. In this case, it is necessary for all terminals capable of providing shared information to have some or all of the above functions, but a dedicated conference server is not required.

[0026]

As described above, according to the present invention,
In addition to the owner of the shared information, by setting the connection, writing and reading restrictions, setting the ID code and password, controlling read access and write access separately, and storing the write file separately. There is an advantage that it can protect against modification of shared information. When collaborative work such as a meeting is realized by displaying and writing shared information in the shared window, the provided shared information may be rewritten unnecessarily, or when the conference is started, the shared information is compared with the previous shared information without permission. It is possible to avoid situations such as changes being made in.

[Brief description of drawings]

FIG. 1 is a diagram showing a configuration of a system according to an embodiment of the present invention.

FIG. 2 is a diagram showing a connection setting range according to an embodiment of the present invention.

FIG. 3 is a diagram illustrating a shared window on a display of a terminal according to an exemplary embodiment of the present invention.

FIG. 4 is a diagram showing contents of shared information according to an embodiment of the present invention.

FIG. 5 is a flow chart of determination as to whether or not there is a connection with an owner when accessing shared information according to an embodiment of the present invention.

FIG. 6 is a diagram showing access from each terminal when following the flow chart of FIG. 5;

FIG. 7 is a flow chart for determining access when access restriction is provided according to an embodiment of the present invention.

FIG. 8 is a diagram showing access from each terminal when the flow chart of FIG. 7 is followed.

FIG. 9 is a flow chart of access determination control when an ID code and a password are added to shared information according to an embodiment of the present invention.

FIG. 10 is a diagram showing access from each terminal when the flow of FIG. 9 is followed.

FIG. 11 is a flowchart when controlling access separately for writing and reading according to an embodiment of the present invention.

FIG. 12 is an explanatory diagram when another file is used when writing to write-protected shared information according to an embodiment of the present invention.

[Explanation of symbols]

 1 to 4 ... Terminal 5 ... Conference server 6 ... Network 7 ... Shared information (provided by terminal 1) 8 ... Information storage unit 9 ... Access right management unit 10 ... Filing process Part 11 ……… Connection setting range 12 to 15 ……… Terminal display 16 to 19 ……… Shared window

─────────────────────────────────────────────────── ─── Continuation of front page (51) Int.Cl. ⁶ Identification code Office reference number FI technical display location // H04M 3/42 Z

Claims (4)

[Claims] 1. A shared information processing system in which a plurality of terminals are connected via a network, and each terminal can access and rewrite shared information between these terminals, wherein the terminals access the shared information. When there is, a means for managing information on whether or not to permit access to the terminal, and a means for permitting access to the shared information only to terminals permitted to access based on this management information. A shared information processing system, which comprises: 2. A shared information processing system in which a plurality of terminals are connected via a network, and each terminal can access and rewrite shared information between these terminals, wherein the terminals access the shared information. When there was
A means for determining whether the terminal is the owner of the shared information; a means for determining whether the terminal has a connection with the owner when the terminal is not the owner of the shared information; When there is a connection with
A means for determining the correctness of the ID code or password entered from the terminal, and permitting access to the shared information only when the terminal is the owner of the shared information or the correct ID code or password is entered from the terminal. A shared information processing system comprising: 3. The shared information processing system according to claim 1, wherein writing and reading are separately performed for managing whether or not to permit access to the shared information. 4. The shared information processing system according to claim 1, wherein the rewritten shared information is managed separately from the pre-rewritten shared information.