JPH06103143A - Joint work supporting system - Google Patents

Abstract

PURPOSE:To prevent a duplicate use permission by preparing a use declaration file, and permitting the use of data, when the generated use declaration file is for the own use request by waiting for a prescribed period of time after the generation is completed. CONSTITUTION:In a state that use of resources A, B is permitted already, when a use request for the resources B is executed from a user Z, its request is refused (a). In this case, plural resources (A-C) 111 are subjected to centralized control, a use declaration 115 is executed for necessary resources 111, reconfirmation 116 of its answer is executed, and in the case a user does not exist else to the same resources 111, they are used as they are (b). On the other hand, in the case a user who execute the use declaration exists else, permission or non-permission of its use is determined by a prescribed reference. In such way, resources for service increase without increasing a burden of a resources superintendent.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a collaborative work support system used when a plurality of workers use a network to jointly create and update data by using a personal computer or a workstation. Is.

[0002]

2. Description of the Related Art Conventionally, the following four methods have been realized as technologies for supporting collaborative work on a network.

(1) As shown in FIG. 11, data 100
In order to centrally manage the data, a specific server device X is made to manage the data 100 exclusively, and a program called a server program 101 is executed on the device X, and on the client devices a, b, c operated by a worker. The window function 10 of the server program 101 for inputting / outputting data from the program executed by the server 103 via the network 103.
2, the data 100 is passed to the client.
At that time, the server program 101 controls duplicated update of data as its own function.

Since this system has only one window, it has the advantage of being easy to implement. (2) As shown in FIG. 12, as many server programs 101 as the number of clients are provided on the server device X that manages the data 100, the number of acceptance windows from the clients is increased, and the input / output requests of the data 100 from the clients are accepted. A system that distributes processing.

(3) As shown in FIG. 13, when data is distributed in a plurality of locations on the network 103,
In order that the data A managed by the server device X can be operated at the same level as the data B managed by the server Y, the server device Y manages the data A as if it has the data A (the network file system function provided by the system). ), The server device Y is requested to input the data A. However, it is not possible to control data duplication operations.

(4) As shown in FIG. 14, in the system configuration of FIG. 13, the usage declaration file 13 of the file α
A method of preventing duplicate use by using 0 and prohibiting the update of data for the file α for which a use declaration is made until the use declaration is withdrawn.

[0007]

However, as shown in FIG.
In this system, the window on the server program 101 is 1
Since the window function 102 sequentially processes the processing request from the client,
When the number of clients issuing a request is large, there is a problem that the window function 102 of the server apparatus X waits for an empty space, the request from the client cannot be processed, and the processing capacity of the entire system decreases. Furthermore, the server program 101 on the server device X side must constantly monitor whether or not there is a processing request from the client during execution. Further, the client side also needs to execute processing in response to the response from the server device X, and has to have a program structure that synchronizes with the server program 101. The program 101 on the server device X side, the client device a,
Both the programs on the b and c sides have complicated program structures, and it is necessary to develop a network-conscious program.

Further, when there are a plurality of grouped server devices and the data to be managed are distributed among these server devices, the programs on the server devices are installed in the plurality of server devices and the programs between the server devices are installed. A mechanism for coordinating and servicing data on any server device in the same way is required, and in this case also the program structure becomes complicated.

(2) In the system shown in FIG. 12, the number of windows is different for each client than in FIG. 11, so there is no need to wait for an empty window, but a window function corresponding to all clients is provided on the server device. Need to run,
The number of programs running on the server device increases. Therefore, the load on the server device increases, the processing capacity of the window function decreases, and the performance of the entire system decreases. Further, when there are a plurality of server devices, it is necessary to deal with the same as in the system of FIG.

(3) In the system shown in FIG.
Data can be requested from U. However, since the file management function of the operating system on the server device Y side treats the file in the data A as a part of the data B, the duplicate update control is realized only under its own control. However, at the same time, when another user makes an acquisition request for the file of data A to the server device X, even if someone is using the file of data A on the server device Y, the server device X will The use of the file in the data A is permitted. Therefore, duplicated update of data occurs and a collaborative work environment in which data is shared cannot be realized.

(4) In the system of FIG. 14, in order to overcome the drawbacks of the system of FIG. 13, when the file in the data A is used, it is declared that the file α in the data A is used. , Create a usage declaration file for file α. However, if a plurality of users try to use the file α in the data A at the same time, as in the time chart shown in FIG. May be allowed. Therefore, duplicated data update occurs and a collaborative work environment cannot be realized.

An object of the present invention is to provide a collaborative work support system capable of supporting a collaborative work by sharing one data by a plurality of workers and simultaneously updating the same data in duplicate. That is.

[0013]

In order to achieve the above object, the present invention creates a usage declaration file in response to a data usage request, and waits for a certain period of time after the creation is completed. It is confirmed whether the request is for its own use request, and only when the request is for its own use, the use of the data is permitted.

In this case, the usage declaration file can be created in a dedicated usage declaration directory, or can be configured by adding the target file name to the name of the usage declaration file instead of the usage declaration directory.

[0015]

According to the above means, the collaborative work support system creates a usage declaration file for the file in the data required by the user, and waits for a certain period of time after the creation is completed. It is confirmed whether it is for the request, and only when it is for its own use request, the data is allowed to be used, so it is possible to prevent duplicate use permission for use requests from multiple users and share the data. It is possible to build a collaborative work environment, and collaborative work can be performed smoothly. Further, in introducing this collaborative work support method, it is possible to introduce the program used by the user without changing the contents of the program.

[0016]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described in detail below with reference to illustrated embodiments.

FIG. 1 is an explanatory view for explaining the technical idea of the present invention, so that a plurality of resources (A, B, C) 11 are not used by a plurality of users (X, Y, Z) 112 in duplicate. When providing a service, conventionally, as shown in FIG.
A manager 113 who manages 11 stores the resource to whom the resource is permitted to be stored in the storage device 114 in some form, and the resource 111 is used by the user while retrieving and updating the stored content. Was controlling permission and denial. Figure 1
In (a), when the use request of the resource B is made by the user Z while the use of the resources A and B is already permitted, the request is rejected.

On the other hand, according to the present invention, a plurality of resources (A, B, C) 111 are not centrally managed, but instead, as shown in FIG.
As shown in (b), the use declaration 115 is made for the required resource 111, the answer is reconfirmed 116, and if no other user exists for the same resource 11, it is used as it is, If there is a user who declares the usage to exist, the usage permission or non-permission is determined based on a certain standard.

By doing so, the resources to be serviced are increased without increasing the burden on the resource manager.

FIG. 2 shows a hardware configuration for operating this system and a network environment configuration. 6 in the figure
01, 602, and 608 are CPUs called client devices a, b, and c that do not have data.
Reference numerals 604 and 604 denote CPUs called server devices X and Y that hold data.

605 is data A managed by the server device X603, and 606 is data B managed by the server device Y604.

These client devices a601 and b6
02, c608 and server devices X603 and Y604 are connected by a network 607.

FIG. 3 is a diagram conceptually showing the usage status of data, and 701 is a network file system of the operating system as if it is connected to itself so that the client apparatus a 601 can use the data A 605. Is virtual data that is connected using. Reference numeral 702 is a virtual connection of data B606.

This is the client device b602, c6
The same applies to 08.

FIG. 4 is a diagram showing an image of the internal structure of the data A 605, 801 is a directory for hierarchically managing the data, and 802 is a file.

FIG. 5 is a diagram for explaining the environment in which this system creates a usage declaration file to support collaborative work. Reference numeral 901 denotes a usage declaration directory for creating a usage declaration file for shared use of the file α 802. is there. Reference numeral 902 is a usage declaration file for the file α.

FIG. 6 is a functional block diagram of the collaborative work support system of the present invention.

In FIG. 6, 1010 is the main body of the collaborative work support system. Reference numeral 1011 is a usage request acceptance window that receives a usage request for a specific file from the program 1013 or the command 1031 and receives a file name 1023 to be used.

Reference numeral 1012 searches the usage declaration directory 902 for the file name 1023 that has received the usage request,
A search unit 1016 that stores a list of usage declaration files (i) for the created file α in the usage declaration file name list 1021 of the memory 1020 is the memory 102.
0 is used to search the usage declaration file name list 1021 to determine the usage permission. A usage permission determination unit 1013 creates a usage declaration file 902. A usage declaration file creation unit 1015 creates a usage declaration file name creation unit 1015. The usage declaration file name 1022 is used to create a usage declaration file 902 in the usage declaration directory 901.

The usage declaration file name creation unit 1015 creates a usage declaration file name in accordance with the usage declaration file name creation rule, and creates a usage declaration file name 10 in the memory 1020.
It stores in 22.

Reference numeral 1014 is a deletion unit of the usage declaration file 902, which deletes the usage declaration file 902 when the usage is stopped or terminated.

FIG. 7A is a flow chart showing the procedure for creating a usage declaration file.

Here, first, in step 1101, the usage request acceptance window 1011 accepts the usage request. Then, in step 1102, the usage declaration file search unit 1012 checks whether or not there is already a usage declaration file in the usage declaration directory 901.

Then, in step 1103, the usage permission judging section 1016 judges whether or not the usage declaration file exists, and if the usage declaration file already exists, it is returned to the request source that it is in use (step 110).
4) and end.

However, if there is no usage declaration file,
The usage declaration file name creation unit 1015 is used to create a usage declaration file name, and this is stored in the usage declaration file name 1022 in the memory 1020 (step 110).
5).

Next, the usage declaration file creation unit 1013 is used to create a usage declaration file 902 in the usage declaration directory 901 (step 1106). In this case, since there is a possibility that a plurality of users are creating the usage declaration file at the same time, the process waits until all users have created the usage declaration file (step 1107).

The waiting time in this case is set to an appropriate value depending on the performance of the device to be executed.

Next, the use declaration file 902 is searched by the search unit 1012 to see if the use declaration file 902 exists in the use declaration directory 901. And
The check result is stored in the usage declaration file name list 1021 in the memory 1020 (step 1108).

Next, in the use permission decision unit 1016,
It is judged whether the name of the retrieved usage declaration file 902 is a usage declaration file created by itself (step 110).
9). If the file is not created by itself, since the use is permitted to the other user who created the use declaration file 902 at the same time, the request source returns a reply that the other user is using the file and ends the process. (Step 1110).

In the case of the use declaration file created by itself, the request source is replied that the use is permitted (step 1111).

To cancel the use, the use declaration file 902 is deleted as shown in FIG. 7B (step 1112).

FIG. 8 shows a usage declaration file 9 in this system.
It is a time chart when 02 is created. Here, a plurality of users A1201 and B1202 are in the system 1
The case where the same file is requested to be used for 203 is shown.

First, the user A 1201 waits after creating the usage declaration file 902 until confirming whether there is another user (1204). Similarly, user B120
After creating the usage declaration file 902, the number 2 waits until it is confirmed whether there is another user (1205). As a result, when the user A 1201 confirms whether there is another user, the usage declaration file 9 created by the user B 1202.
Since 02 has been created, it is possible to determine whether the use is permitted to the user (1207), and if the use is permitted to the user, the update processing (1208) is performed on the file.

If the user is not permitted, wait until the permission is granted or perform another process (120).
6).

FIG. 9 is a file name configuration diagram showing the creation criteria of the usage declaration file 902. 1301 is the user name of the user who creates the usage declaration file 902;
2 is a process number added in consideration of the possibility that the user executes a plurality of processes and makes a usage request for a plurality of files, and a unique number is set. Thirteen
Reference numeral 03 is a code (underbar) for separating the user name and the process number.

FIG. 10 shows a structure of a usage declaration file name 1401 used in place of creating the usage declaration directory 901 when the name of the usage declaration file 902 is not limited.

Target file name 1402 for which usage declaration is made
To the usage declaration file name in FIG. 1403 is a target file name, a user name 1301, and a process number 130
It is a separation code (period) for distinguishing from 2. 1
Reference numeral 404 is an identification code indicating the usage declaration file 902, and is separated by a separation code 1405 (a period in this case) so that the usage declaration file 902 can be easily searched.

When the usage declaration file 902 is searched, the search file name 1406 in FIG. 10B is designated, and the user name 1301 and the process number 1302 are designated by the code "*" 1407. The usage declaration file 902 is searched.

By doing so, the search can be performed efficiently, and the labor for creating the directory for the use declaration file can be saved.

[0050]

As described above, in the present invention, in a collaborative work system in which a plurality of computers are connected by a network and one data is shared by a plurality of workers, in response to a data use request, Create a usage declaration file, wait for a certain period of time after the creation is completed, and make the created usage declaration file confirm whether it is for its own usage request, and use the data only when it is for its own usage request. Since it is allowed, a plurality of users can jointly use the data connected through the network at the same time without duplicate updating.

[Brief description of drawings]

FIG. 1 is an explanatory diagram for explaining a technical idea of the present invention.

FIG. 2 is a system configuration diagram showing a network environment for implementing the present invention.

FIG. 3 is an explanatory diagram that conceptually expresses the usage status of data of the present invention.

FIG. 4 is an explanatory diagram showing an image of an internal structure of data.

FIG. 5 is an explanatory diagram illustrating an environment in which the system creates a usage declaration file to support collaborative work.

FIG. 6 is a functional configuration diagram of a collaborative work support system.

FIG. 7 is a flowchart showing a procedure for creating a usage declaration file.

FIG. 8 is a time chart when a usage declaration file is created in this system.

FIG. 9 is a configuration diagram of a file name showing a creation standard of a usage declaration file.

FIG. 10 is a configuration diagram of a usage declaration file name when a usage declaration file directory is not created.

FIG. 11 is a configuration diagram showing a conventional support method in the case where there is one server program.

FIG. 12 is a configuration diagram showing a conventional support method in the case where the server programs are present by the number corresponding to the programs on the client side.

FIG. 13 is a configuration diagram of a conventional support method when data on multiple servers is used in a network file system.

FIG. 14 is an explanatory diagram of a conventional technique for creating a usage declaration file and sharing data.

FIG. 15 is a time chart for explaining a problem of the conventional technique of creating a usage declaration file.

[Explanation of symbols]

111 ... Resources, 112 ... Users, 115 ... Use declaration, 6
01, 602, 608 ... Client device, 603, 6
04 ... Server device, 605, 606 ... Data, 901 ...
Usage declaration directory, 902 ... Usage declaration file.

Claims (3)

[Claims] 1. In a collaborative work system in which a plurality of computers are connected by a network and one data is shared by a plurality of workers, a use declaration file is created in response to a data use request, and after the creation is completed. Collaborative work support characterized by allowing a certain period of time to confirm whether the created use declaration file is for its own use request, and permitting the use of data only when it is for its own use request method. 2. The collaborative work support method according to claim 1, wherein the usage declaration file is created in a dedicated usage declaration directory. 3. The collaborative work support method according to claim 1, wherein the usage declaration file is created by adding the name of the usage target data to the name of the usage declaration file for each usage target data.