JPH11272591A - Transfer quantity assurance system in shared application - Google Patents

Abstract

PROBLEM TO BE SOLVED: To evade delay to be caused when updated data is loaded as suppressing quantity of data to be transferred in one time of data transmission and the number of computers and to assure that the data is always the latest one. SOLUTION: Unnecessary data transfer is prevented by transferring no changed data to a computer by which the data changed on its desktop is not at a visible state and transferring the data by defining the changed data changed to a visible state as a trigger. In addition, the data is loaded without causing delay time when the changed data becomes the visible state by introducing a concept of cooccurrence and transferring the changed data even when cooccurrence data is changed to statistically digitize relation between the pieces of respective shared applications.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an inter-group cooperative work support system for sharing applications and data on a network, in which changed data is simultaneously transferred to all computers on the network. The present invention relates to preventing traffic from increasing and preventing delays that occur when data is loaded on each client computer.

[0002]

2. Description of the Related Art In a shared application, the following three methods can be considered as a method of reflecting a change in data to another computer. The first is a method of mutually exchanging all data with each shared application in real time each time data is changed. This is a method of monitoring user events transmitted to a shared application and exchanging information between all computers each time a user event occurs.

[0003] A second method is a method in which data is transferred in a batch at a fixed time interval or triggered by the end of editing by a user. This is a method of transferring a set of data in response to a time interval or the end of a user event. The third method is a method of requesting data transfer triggered by a trigger of a user activating a shared application. When the shared application is iconified or not displayed on the top, the data change is not reflected, and only the data of the shared application displayed on the top is requested to be transferred.

[0004]

The above-mentioned method of transferring the changed data in real time each time the data is changed has the merit that the data consistency is always ensured in each computer, but the change is not guaranteed. Even in the case of handling frequently occurring data or in the case of data change that is not important for a specific user, the data is transferred to all the computers, so that there is a problem that network traffic increases intermittently.

Similarly, when data transfer is executed with a time interval or when the user finishes editing, data traffic is not intermittent, but network traffic temporarily increases when data is transferred. There is.
Also, in this case, a certain amount of data is transferred, and as the number of computers sharing the application increases, the time required to complete the data transfer for each computer tends to be shifted or delayed. is there.

In a method of requesting data transfer triggered by a user activating a shared application, data of a shared application that has not been activated is not changed. Therefore, active data is referenced while referring to data of another shared application. There is a problem that work such as editing data of various shared applications cannot be performed.

As described above, when the data of the shared application is reflected on the shared application on another computer by using the conventional technology, the amount of data to be transferred in one data communication and the number of computers are reduced to reduce network traffic. Introduce a method that does not occur,
The challenge is to avoid delays that occur when loading update data, and to ensure that the data required by the user is always the latest data.

The present invention divides data of a shared application into a plurality of segments, transfers data only to a computer in which a segment including changed data is in a visible state, and limits a computer to which the data is transferred by limiting network traffic. It is an object of the present invention to provide a data transfer amount assurance system capable of avoiding an increase in data transfer.

A data transfer amount assurance system capable of reducing the number of data load delays caused by mouse operation, scrolling, size change, etc., by simultaneously transferring other data which is likely to be in a visible state at the same time. The purpose is to provide.

Another object of the present invention is to provide a data transfer amount guarantee system that can guarantee that the latest data is always provided when the data becomes visible.

[0011]

SUMMARY OF THE INVENTION An object of the present invention is to provide a network system in which a specific application is shared by a plurality of computers connected to a network, wherein a server computer receives change data from each client computer, It has data sharing program means capable of reflecting the changed data on a computer different from the computer that made the change, and the client computer realizes an environment in which it is possible to cooperate with other connected client computers. A communication management program means for determining whether to permit transfer of change data from the data sharing program, receiving the change data, and transferring the change data of the shared application added on the desktop to the data sharing program; desk Monitor desktop user events, such as mouse operations, scrolling, and resizing, to determine which shared applications are visible on the desktop and which parts of the data are being referenced. Desktop management program means for updating management information, and the desktop management program means has management information serving as a criterion for judging whether or not the communication management program means permits the transfer of change data. When you change,
Monitors data change events for all open data in all shared applications running on the desktop to detect data changes and sends the changed data to another computer when a data change occurs. It consists of data management program means that sends change data to the communication control program so that it can be reflected, monitors the ratio of the display area of the entire screen on the desktop and the visible area of the shared application, and calculates the calculated ratio Is set as an index expressing the importance of the data displayed by the shared application by each connected client, and is achieved by preferentially transferring data that is likely to become visible.

Another object of the present invention is to provide a data transfer amount assurance system, in which a visible area of a specific shared application is changed by a mouse operation, scrolling, size change, etc. This can be achieved by using the cumulative value of the ratio of the area that is newly visible as an index representing the data reference frequency, and transferring data with a high reference frequency with priority.

Still another object of the present invention is to provide a data transfer amount guarantee system, in which, when data of a shared application is changed on a specific computer, an inquiry is made as to whether the data is visible on another computer,
This can be achieved by transferring the modified data only to the computer where the data is visible and to a particular server computer.

Still another object of the present invention is to provide a data transfer amount assurance system in which a data change is notified.
Computers to which update data has not been transferred because the data is not visible, requesting the update data from a specific server computer triggered by the data becoming visible, when the data becomes necessary This can be achieved by requesting the server computer to transfer the updated data.

Still another object of the present invention is to provide a data transfer amount assurance system, wherein when the data held by each shared application is changed, the expected value of the maximum data transfer amount from the computer that changed the data to another computer is changed. The application data is divided into segments to reduce the number of times the update data is transferred during window scrolling while keeping the data below a certain value, so that the data transfer amount is constant even if the data changes It can be achieved by setting the value.

Still another object of the present invention is to provide a data transfer amount guarantee system, in which, when a plurality of segmented data are simultaneously visible between each shared application, a combination of simultaneously visible data is co-occurred. This can be achieved by defining the data set as the data set and reconstructing the set of co-occurring data as individual data sets.

Still another object of the present invention is to provide a data transfer amount assurance system, which holds a table in which the probability of co-occurrence of data is calculated for each client computer, and is used when data of a specific shared application is changed. Alternatively, this can be achieved by simultaneously transferring data in the co-occurring data set in the table whose probability exceeds a certain threshold.

[0018]

DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below with reference to the drawings. FIG. 1 shows the system configuration of the present embodiment. The system includes a terminal device 11 including a CPU 11A and a memory 11B, a data sharing program 1
A server computer 1 comprising an external storage device 12 in which the storage device 12A is stored and a communication port 13;
1A, a terminal device 21 including a memory 21B, a communication management program 22A, a desktop management program 22B,
A client computer 21 consisting of an external storage device 22 storing a data management program 22C and a communication port 23, a terminal device 31 consisting of a CPU 31A and a memory 31B, a communication management program 32A, a desktop management program 32B, and a data management program 32C are stored. It comprises a client computer 3 comprising an external storage device 32 and a communication port 33, and a network 4 for communicating data transmitted and received between the computers.

Here, the function of each program will be described. When the data sharing program 12A receives the type of the shared application, the changed position of the data, and the changed data as the changed data of the shared application from the communication control program running on each client computer, the data sharing program 12A The data at the corresponding change position of the application is updated with the transferred change data.

The data sharing program 12A manages a data update frequency table including a data position, a data change frequency, and a data change probability for each data of each shared application, and each time the change data is received, the corresponding data position is updated. Are added, and the data change probabilities at all positions are recalculated.

Further, in the present system, data is not transferred to a client whose change data area is not visible on the desktop, but data is transferred when the change data area changes to a visible state on the desktop. .
At this time, if the visible area of the data is frequently changed by the user's scroll operation, the frequency of data transfer increases, and the delay time of the scroll processing increases. To deal with this situation, the data is divided into relatively large areas called segments, and the changed data is not visible,
The data is transferred to the client computer in which the segment including the area of the changed data is visible.

The data sharing program 12A re-segments the data each time the data update frequency table is updated. The segmentation method is performed by dividing the data so that the product of the data size and the data change probability is equal to or less than a predetermined threshold so that the expected value of the maximum data transfer amount at one time is equal to or less than a predetermined value. It is required by going. Similarly, the data sharing program 12A manages a segment table including a segment type, a segment change probability, and a segment length for each data of each shared application, and the segment table is updated every time the data update frequency table is updated. , Distributed to communication control programs running on each client computer. When the change data of the shared application is transferred to each client computer after distributing the segment table, the type of the shared application and the changed position of the data are transmitted to the communication control program in order to inquire whether to transfer the change data. The change data is transferred only to the communication control program of the client computer for which the response result from the communication control program is transfer permission, and the change data is not transferred to other computers. The processing described above is executed for all client computers. This eliminates the need to transfer the change data to all client computers, and has the effect of preventing an increase in network traffic.

The communication management program 32A manages the segment table distributed from the data sharing program 12A, and when receiving the type of the shared application and the changed position of the data as an update data transfer inquiry from the data sharing program, Referring to the segment table, search for the segment to which the changed data belongs.

If the corresponding segment is visible on the desktop, a response permitting the transfer of the changed data is returned to the data sharing program. Even if the corresponding segment is not in the visible state, if the following conditions are satisfied, a response permitting transfer of the changed data is returned to the data sharing program.

In this case, there are two conditions. The first condition is to refer to the application priority table managed by the desktop management program 32B and to determine the fixed display area coefficient and the accumulated display area coefficient of the corresponding shared application. Either one of them exceeds a preset threshold.

The second condition satisfies the first condition,
In addition, a segment co-occurrence probability table managed by the desktop management program is searched. In other words, search for all co-occurrence probabilities related to the segment including the changed data, and for co-occurrence whose co-occurrence probability exceeds a preset threshold, there is a co-occurrence where the co-occurring segment is It is that you are.

[0027] The above two conditions are that a shared application frequently referred to is searching for segment data having a high probability that two segments are simultaneously referred to. As a result, even if the change data is not visible, if the data that is likely to be referred to at the same time as the change data is referred to, the change data is transferred in advance so that the This has the effect of reducing the delay time due to data transfer.

When the communication management program 32A returns a response for permitting the transfer of the update data to the data sharing program, the changed data is transferred from the data sharing program. In order to reflect the received change data to the shared application on the desktop, the type of the shared application, the changed position of the data, and the change data are sent to the data management program as the change data, and the actual change process is performed by the data management program. Entrust it to When data is changed by the shared application on the desktop, on the other hand, the type of the shared application, the changed position of the data, and the changed data are received as the changed data from the data management program, and the data is shared with the data sharing program. The same information is transferred as change data.

The desktop management program 32B manages the display state of the shared application so that the communication management program can determine the data of the shared application that is visible on the desktop. For this reason, the desktop management program manages an application priority table including an application type, a fixed display area coefficient, and an accumulated display area coefficient.

The fixed display area coefficient means the ratio of the visible area in the display area of the shared application to the desktop area. A shared application having a large value has a large area on the desktop where data can be referred to, which means that the shared application is easy for the user to refer to.

The cumulative display area coefficient means the ratio of the cumulative total of the changed area to the desktop when the visible area in the display area of the shared application changes due to mouse operation, scrolling, and size change. I do. A shared application with a large value indicates that there are many areas that become visible or invisible, which means that data that is frequently referred to is held.

A shared application having a large fixed display area coefficient or a large accumulated display area coefficient is determined to be an application frequently used by a user, and a data change notification is received from another computer. Ensure that changed data is transferred, even if it is not displayed. The application priority table is generated on the desktop, mouse operation,
Updated each time a user event such as scrolling or resizing occurs. In addition, the desktop management program manages a data reference time table describing the time during which data of two different shared applications is displayed at the same time. A state in which data of two different shared applications are displayed simultaneously is defined as co-occurrence.

Similarly, the data reference time table is updated each time a user event such as a mouse operation, scrolling, and size change occurs on the desktop. In addition, it manages a segment co-occurrence probability table that holds the probability that two segments in two shared applications are simultaneously visible. When the data reference time table is updated, the desktop management program uses the data reference time table and the segment table to calculate a conditional probability that two segments are simultaneously visible when two shared applications are simultaneously visible. Calculate and update the segment co-occurrence probability table.
The segment co-occurrence probability table associates data between different shared applications, so that even if the data of a shared application that is not visible is changed on another computer, it is related to the changed data If the data of the shared application is visible, it is guaranteed that the changed data will be transferred. By transferring related data in advance, data transfer occurs every time a user event occurs, which has an effect of preventing a delay in data loading from occurring.

The desktop management program 32B is generated on the desktop in order to manage the application priority table and the segment co-occurrence probability table.
It is necessary to monitor user events such as mouse operations, scrolling, and size changes, and update the table each time an event occurs.

The data management program 32C updates the data at the corresponding position of the corresponding shared application when the type of the shared application, the changed position of the data, and the changed data are received as changed data from the communication management program. There are three methods for updating.

The first case is where the segment to which the change data belongs is not visible on the desktop. In this case, the data management program can change the data without notifying the user of the change. Second, the segment to which the change data belongs is visible on the desktop, but the shared application is not displayed on the foreground as an active window. In this case, the data management program notifies the user of the change using a dialog box or reverse display. Third, the segment to which the change data belongs belongs to the shared application displayed on the foreground as the active window. In this case, the data management program
Since the segment to which the changed data belongs and the segment being edited by the user are the same, it is necessary to prohibit the user from editing the old data.

In order to maintain data consistency in all client computers, control is performed so that editing is not permitted until data is updated. Specifically, the user keeps prompting the user to update data in a dialog box or the like at regular intervals.

Since the data management program 32C needs to reflect the data change of the shared application made by the user on the desktop to another computer, the data management program 32C is opened by all the shared applications running on the desktop. It keeps handles to all the data that it has, monitors the data change event, and when the event occurs, sends it to the communication management program as change data.
Send the type of shared application, the location where the data was changed, and the changed data.

FIG. 2 shows a configuration example in which a plurality of shared applications are shared in the desktop area 201 of a specific client. In this example, six shared applications are activated on the desktop, and App1
(202), App2 (203), App3 (20
4), App4 (205) is overlapped and opened. Also, App5 (206), App6 (20
7) is shared in an iconified state. Among the four shared applications, App1 (202) is displayed in an active state in the foreground, and the user is notified that App1 (202) is
While working in an environment where p1 (202) can be changed, App2 (20) is displayed on the screen of another shared application.
3), the screens of App3 (204) and App4 (205) are partially visible, and it is possible to edit the data of App1 (201) while referring to these display data.

An area 208 indicated by a halftone dot in the figure represents the ratio of the screen of the shared application to the desktop. Here, the ratio of the screen of each shared application to the ratio of the desktop region is defined as the fixed display region coefficient. Since the fixed display area coefficient is an index indicating a shared application that is frequently accessed on the desktop, App5 (20)
6), the fixed display area coefficient of App6 (207) is “0”
Becomes

FIG. 4A shows a case where a plurality of shared applications are shared in the desktop area 211 of a specific client, similarly to FIG. 3, and six shared applications are activated on the desktop similarly. , The trajectory of App1 (212), which was opened as a shared application active in the foreground until immediately before.

In another shared state, App2
(213), App3 (214), App4 (215)
Are open on top of each other. Also, just before Ap
Since p1 has been iconized by the user, App1 (216), App5 (217), and Ap in the icon state are displayed.
p6 (218) is shared as an icon at the right corner of the screen. In the example shown in the figure, App2, App3, A
Although pp4 is displayed in the foreground, the area (219) painted with a halftone dot in the figure is an area of the shared application that is newly visible due to the iconization of App1. Frequently accessed shared applications can be evaluated using only the fixed display area coefficients, but important data cannot be evaluated as reference data because they are not accessed frequently.

Therefore, a value obtained by adding a change amount of the display area each time the visible state of the application changes is defined as a cumulative display area coefficient. By introducing the cumulative display area coefficient, the frequency of referring to the data of the shared application can be evaluated.

FIG. 3B is an application priority table managed by the desktop management program and used when the communication management program requests data transfer to the data sharing program. In the table, the application type 221, the fixed display area coefficient defined in FIG.
The cumulative display area coefficients defined in (b) are listed.
FIG. 5 shows an example of the application priority table when four applications are shared on the desktop. The table is defined separately for each computer sharing the application, and the threshold value in the table uses a value predefined in the entire system. The fixed display area coefficient is calculated by setting the screen area of the entire desktop to Area (des).
k), each shared application i ｛i = 1, 2, 3,
Area where 4｝ is visible at time t is Area
(T), when the fixed display area coefficient is SA (i) and the time interval for updating the application priority table is T, it is expressed by the following “Equation 1”.

[0045]

(Equation 1)

It is possible to set a constant value for T in advance, or to use the time difference between the time when the user changed the visible state of the shared application and the time when the previous change was made.

In addition, the method of calculating the cumulative display area coefficient is the same as that of calculating the screen area of the entire desktop by Area (d
esk), each shared application i ｛i = 1, 2, 2,
The area where 3,4} is newly visible is New (i),
If the cumulative display area coefficient at the time of the nth application priority table change is DAn (i) and the time interval for updating the application priority table is T, it is represented by the following “Equation 2”.

[0048]

(Equation 2)

In the figure, the threshold value of the fixed display area coefficient is "0.5
00, and the threshold of the cumulative display area coefficient is “0.250”, and the fixed display area coefficient 224 of “application 1” and the cumulative display area coefficient 225 of “application 4” exceed the threshold. Therefore, when the data of “application 1” and “application 4” are changed, the data is preferentially transferred regardless of whether the data is in a visible state.

FIG. 4A shows an example of a configuration in which the data sharing program divides the data of each shared application into a plurality of segments. In the figure, when “application 1” 301 holds “1000 bytes” of data and “application 2” 307 holds half of “500 bytes” of data, the data of “application 1” is "Segment 1" 302, "Segment 2" 303, "Segment 3" 304, "Segment 4" 305, and "Segment 5" 306, and the data of "Application 2" 307 is divided into "Segment 1" 308, It is divided into “segment 2” 309. The two segments painted with halftone dots in the figure have a high probability of being referred to at the same time, indicating that they are defined as one data set.

When one data is updated, it means that the data is always transferred as a data set. For example, when a specific computer refers to “segment 3” 304 of the shared application 1 but does not reference “segment 2” 309 of the shared application 2, when another computer refers to “segment 2” of the shared application 2, When the data of the line 309 is changed, the changed data is not transferred. However, in the case where two data have a co-occurrence relationship, even if one of the data is not referred to, if one of the data is referred to, it is guaranteed that the data is transferred.

FIG. 4B shows an example of the configuration of a data update frequency table managed by the data sharing program and dividing data into segments. The table is 100
The 0-byte data is divided into 100-byte units, the data position 311 indicating the position of the data, the data change frequency 31
2, data change probability 313. By dividing the data into segments independent of the data size of each shared application and independent of the frequency of data change, it is possible to keep the data transfer volume per data change below a certain value at all times. Become.

The area shaded with halftone dots in the figure indicates a portion that becomes the segment 1 of the data when the threshold value is set so that the expected value of the maximum transfer amount is 50 bytes. The method of determining the segment is as follows, when the segment length is S, the data change probability when the segment length is S is P (0 <n <S), the change position is n, and the threshold value is C, It is represented by

[0054]

(Equation 3)

In the case of the example shown in the figure, S = 100 * n (n = 1,
2,...) And C = 50. When the segment 2 is determined, the same calculation can be performed using a table obtained by removing the segment 1 from the data update frequency table. The size of the segment is dynamically changed each time data is changed, and is notified to each computer.

FIG. 5 shows a case where the data sharing program manages
3 shows a configuration example of a segment table created based on a data update frequency table. Table 4 (b)
Are determined, and the segment type 321, the segment change probability 322, and the segment length 3
23. The segment table is created from the data update frequency table every time data is changed, and distributed to each client.

When the update data is transferred from each computer, the data sharing program searches the distributed segment table for the segment to which the update data belongs, and determines whether the area of the corresponding segment is visible or not. You can ask the computer. Since other computers are distributed with the segment table, it is possible to determine whether the segment data is visible.

FIG. 6A shows a configuration example of a data reference time table managed by the desktop management program and updated when display data of the shared application changes due to a user event. In the figure, a specific application divides 1000-byte data into 100-byte units, and indicates a data position 401 indicating the position of the data; a non-display 402 indicating that the shared application is not visible or iconified; It consists of the total time 403 during which the application is visible.

In the figure, 0 of the shared application App1
The column data 4 is the time during which both the data from bytes to 100 bytes and the data from 401 bytes to 500 bytes of the shared application App2 are visible.
04 is described as a value “0”. The desktop management program calculates the difference between the time when the data reference time table was last updated and the current time when the user changes the visibility of the data by mouse operation, scrolling, resizing, etc. Add a value to the column of data that co-occurs. An area 405 indicated by a halftone dot in the figure is a set of columns corresponding to the segment 1 of the shared application App1 and the segment 1 of the shared application App2.

Since the segment table shown in FIG. 5 is distributed from the data sharing program, each client computer stores the segment 1 of App1 from the beginning of the data by 30 minutes.
In the area up to 0 bytes, it can be known that the segment 1 of App2 is the area up to 200 bytes from the beginning of the data.

FIG. 6B shows a configuration example of the segment co-occurrence probability table managed by the desktop management program and recalculated when the data reference time table is updated. The table has a column 41 indicating the segment.
1, a non-display 412 indicating that the segment is not visible or iconified, and a total time 413 during which the segment is visible.

All co-occurrence relationships of the shared application data can be calculated from the segment table of FIG. 5 and the data reference time table of FIG. The calculation method is as follows: the segment M of App1 and the segment N of App2.
Is Pmn, the segment M of App1
Are defined as M (min), M (max),
The start position and the end position of the segment N of App2 are set to N (m
in), N (max), data at position i of App1 and A
When the time when the data at the position j of pp2 is simultaneously visible is T (i) (j), and the total time when App1 and App2 are simultaneously visible is T (all), expressed.

[0063]

(Equation 4)

A region 414 indicated by a halftone dot in the figure indicates a probability that the segment 1 of the shared application App1 and the segment 1 of the shared application App2 co-occur.

Hereinafter, the operation of the present embodiment will be described with reference to a flowchart. FIG. 7 is a flowchart showing an operation when a data sharing program running on a server computer is notified of a change in data of a shared application from a communication control program running on each client computer. The data sharing program waits for a data change notification of the shared application from the communication control program running on another client computer (step 501), and receives the changed data position as the data change notification (step 502). The value of the data change frequency at the changed position in the data update frequency table is added, the data change probability is recalculated by the method shown in FIG. 4B, and the data update frequency table is updated (step 503).

Based on the updated data update frequency table, the shared application data changed by the method shown in FIG. 5 is re-segmented (step 504), and the segment table is updated (step 505). The updated segment table is distributed to the communication control program running on each client computer (step 506). When the process is completed up to step 506, the process is repeated from step 501.

FIG. 8 is a flowchart showing the operation when the data sharing program running on the server computer transfers the change data of the shared application from the communication control program running on each client computer.

The data sharing program waits for transfer of changed data of the shared application from the communication control program running on another client computer (step 5).
11), the changed data is transferred from the client computer, and when the transfer of all the changed data is completed (step 512), the changed data is stored in the disk on the server computer (step 513).

When the storage in the disk is completed, the communication control program running on another client computer is inquired as to whether or not the update data needs to be transferred (step 514). To send the position. The communication control program running on each client computer incorporates logic to determine whether data transfer is necessary, and when a request is made to transfer update data from the communication control program on the client computer ( Step 5
15), the update data stored in the disk of the server computer is transferred to the client computer that requested it (step 516).

When the client does not request the transfer of the update data, or when the transfer of the update data is completed, it is checked whether or not there is a client computer which does not inquire whether the transfer of the update data is necessary (step 516) If it exists, repeat from step 514. If not, the process is repeated from step 511. FIG. 9 is a flowchart showing the operation when the communication control program running on each client computer receives an inquiry from the data sharing program running on the server computer as to whether transfer of the change data of the shared application is necessary.

The communication control program running on each client computer waits for an inquiry from the data sharing program as to whether the change data of the shared application needs to be transferred (step 601), and inquires whether the change data needs to be transferred. When the data type and the position where the data is changed are received (step 6)
02), referring to the segment table shown in FIG. 5, it is searched which segment belongs to the updated one (step 603).

Check whether the updated segment is visible on the desktop (step 60).
4) If the segment is visible, request the data sharing program to transfer the update data (step 605), and repeat from step 601. Figure 3 if the updated segment is not visible on the desktop
Referring to the corresponding application column in the application priority table shown in (b) (step 60).
6) Check whether one of the fixed display area coefficient defined in FIG. 2 and the cumulative display area coefficient defined in FIG. 3B exceeds a preset threshold (step 607), and the fixed display is performed. If both the area coefficient and the cumulative display area coefficient do not exceed the threshold, step 601
Repeat from

If one of the fixed display area coefficient and the cumulative display area coefficient exceeds the threshold value, all segments related to the data segment displayed by the visible shared application and the changed data segment are changed. The co-occurrence is retrieved from the segment co-occurrence probability table shown in FIG. 6B (step 608).

It is checked whether the co-occurrence probability of the searched co-occurrence segments exceeds a preset threshold value (step 609). If the co-occurrence probability exceeds the threshold value, the data sharing program on the server is checked. (Step 611), and the process is repeated from step 601.

If the co-occurrence probability does not exceed the threshold, it is checked whether there is a co-occurrence to be searched next (step 61).
0) If there is a co-occurrence to be searched, step 608
Repeat from If there is no co-occurrence to be searched, the process is repeated from step 601. FIG. 10A is a flowchart showing the operation when the communication control program running on each client computer transfers update data from the data sharing program running on the server computer.

The communication control program waits for transfer of update data from the data sharing program running on the server computer (step 621), transfers the update data from the data sharing program, and completes the transfer of all update data (step 621). 622), the type of the updated data, the updated position, and the updated data are transmitted to the data management program running on the client computer (step 623).

When step 623 is completed, step 62
Repeat from 1. FIG. 10B is a flowchart showing an operation when the communication control program running on each client computer distributes the segment table from the data sharing program running on the server computer.

The communication control program waits for the distribution of the segment table from the data sharing program running on the server computer (step 631), and transfers the segment table data from the data sharing program (step 632). Replace with the received data (step 633). Step 63
When 3 is completed, the process is repeated from step 631.

FIG. 10C is a flow chart showing the operation when the communication control program running on each client computer transmits changed data added by the user from the data management program running on the same computer. .

The communication control program waits for transmission of changed data from the data management program (step 64).
1) the type of shared application that has been changed from the data management program, the location of the changed data,
When the changed data is transmitted (step 642), the type of the shared application and the position of the changed data are transmitted as a change notification to the data sharing program running on the server computer (step 643).

When the data change notification is completed, the actual change data is transferred to the data sharing program (step 644). When step 643 ends, step 641
Repeat from

FIG. 11 is a flowchart showing the operation of updating a table to be managed when a desktop management program running on each client computer monitors a user event and detects a window or data display area change event. It is.

The desktop management program monitors user events such as mouse operation, scrolling, and size change occurring on the desktop (step 701), and the events issued by the user are stored in an event queue.
When the desktop management program captures an event stored in the event queue (step 70)
2) Check whether the event is an event that changes the display area of the shared application window (step 703). If the event is a change in the visible state of the shared application, a fixed display area related to the shared application whose display area has changed. The values of the coefficient and the cumulative display area coefficient are recalculated by the method shown in FIGS. 2 and 3A (step 704).

When the calculation of the fixed display area coefficient and the cumulative display area coefficient is completed, the value of the corresponding item in the application priority table defined in FIG. 3B is replaced (step 705). In step 703, when the display area of the window has not changed, and when the display area of the window has changed and the processing has ended up to step 705, whether the captured event has changed the segment area of the display data in the shared application. Check (step 706). If the segment of the data referenced in the shared application has not changed, the process is repeated from step 701.

When the segment of the data referred to in the shared application changes, the item of the corresponding data position of the corresponding shared application in the data reference time table shown in FIG. The difference of the current time is added (step 707).
For all items of the updated data reference time table, the data area is re-segmented using the segment table shown in FIG. 5, and the co-occurrence probabilities for the individual segments are recalculated (step 708). .

The corresponding item in the segment co-occurrence probability table shown in FIG. 6B is replaced with the recalculated co-occurrence probability (step 709). When the update of the table is completed, the captured event is passed to the window to execute a user event (step 710). Upon completion of the processing, the processing is repeated from step 801.

FIG. 12 is a flow chart showing the operation when the data management program running on each client computer sends changed data from the communication management program running on the same computer.

The data management program waits for transmission of the change data from the communication management program running on the same computer (step 801), and the type of the shared application, the position where the change was made, and the change data are transmitted as the change data. (Step 802), it is checked whether the data of the changed position of the shared application is visible on the desktop (Step 80).
3) If the data is not visible, replace the original data with the changed data (step 804).

When the data update is completed, the process is repeated from step 801 without notifying the user of the change. If the change data is visible on the desktop, it is checked whether the shared application reflecting the change data is displayed on the desktop as the active window on the foreground (step 805).

If the shared application reflecting the changed data is not active, the original data is replaced with the changed data (step 806). When the data update is completed, the active shared application is notified to notify the user that the data has been updated. (Step 807). When the notification is completed, the process is repeated from step 801. If the shared application reflecting the change data is active, the user is asked whether the original data can be replaced with the change data (step 808). If the user does not approve,
In order to maintain data consistency, the process is interrupted for a certain period of time (step 809), and the process is repeated from step 808 to ask the user again whether the original data can be replaced with the changed data.

If the user approves the replacement of the original data with the changed data, the original data is replaced with the changed data (step 810). When the data update is completed, the process is repeated from step 801.

FIG. 13 is a flowchart showing the operation when the data management program running on each client computer detects a change in the shared application data on the desktop and reflects it on another computer. The data management program holds handles to all data opened by all shared applications running on the desktop and monitors data change events (step 811). When the user changes the data, the data change event is stored in the event queue, and the data management program captures the event stored in the event queue (step 81).
2) The type of the shared application, the location where the data was changed, and the change data are transmitted as change data to the communication management program running on the same computer (step 813). When the change data transmission is completed, the process is repeated from step 811.

[0093]

As described above, according to the present invention, in a system in which a plurality of computers share a specific application and cooperate with each other, data modified by a user on the specific computer can be used for other systems. Data into multiple segments to prevent intermittent increases in network traffic when transferring changed data to all other computers when reflected in a shared application on one computer. Since data is transferred in units of segments and data is transferred only to computers in which the segments are visible, network traffic can be suppressed to a certain value or less.

In addition, since data having a high probability of being in a visible state at the same time among the shared applications is collected into one data set, and the data is transferred for each data set, the visible state can be changed by mouse operation, scrolling, size change, and the like. When the data segment is changed, there is an effect that the number of occurrences of the load delay of the segment data can be reduced.

[Brief description of the drawings]

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

FIG. 2 is a diagram showing an area of a shared application in a visible state on a target desktop when a desktop management program calculates a fixed display area coefficient.

FIG. 3 is a diagram showing a changed display area when a visible area on the desktop changes when a desktop management program calculates a cumulative display area coefficient, and an application priority managed by the desktop management program. It is a figure showing the composition of a degree table.

FIG. 4 is a diagram illustrating a configuration of a data segment when a data sharing program divides data of each shared application into a plurality of segments, and a diagram illustrating a configuration of a data update frequency table managed by the data sharing program.

FIG. 5 is a diagram showing a configuration of a segment table managed by a data sharing program and distributed to each client computer.

FIG. 6 is a diagram showing a configuration of a data reference time table managed by the desktop management program, and a diagram showing a configuration of a segment co-occurrence probability table managed by the desktop management program.

FIG. 7 is a flowchart illustrating an operation when the data sharing program is notified of a data change of the shared application from the communication control program.

FIG. 8 is a flowchart illustrating an operation when a data sharing program transfers change data of a shared application from a communication control program.

FIG. 9 is a flowchart illustrating an operation when the communication control program receives an inquiry from the data sharing program as to whether transfer of change data of the shared application is necessary.

FIG. 10 illustrates an operation when the communication control program transfers update data from the data sharing program, an operation when the communication control program distributes a segment table from the data sharing program, 9 is a flowchart showing an operation when the change data added by the user is transmitted.

FIG. 11 is a flowchart showing an operation when the desktop management program monitors a window or data display area change event and updates the management table.

FIG. 12 is a flowchart showing an operation when the data management program transmits a change data from the communication management program.

FIG. 13 is a flowchart illustrating an operation when the data management program monitors a change in shared application data and reflects the change on another computer.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... Server computer, 2, 3 ... Client computer, 4 ... Network, 11, 21, 31 ... Terminal device, 12, 22, 32 ... External storage device, 12A ... Data sharing program, 22A, 32A ... Communication management program, 22B , 32B ... Desktop management program, 2
2C, 32C: Data management program, 42A: Task request program.

Claims (7)

[Claims] In a network system in which a specific application is shared on a plurality of computers connected to a network, a server computer receives change data from each client computer, and a computer different from the computer that made the change. Transfer data from the data sharing program to realize an environment in which the client computer can cooperate with other connected client computers. Communication management program means for determining whether to permit the change, receiving the change data, and transferring the change data of the shared application made on the desktop to the data sharing program, and which shared application on the desktop Monitors desktop user events, such as mouse operations, scrolling, and size changes, to determine if the application is visible and which part of the data is being referenced, and updates management information when an event occurs The desktop management program means and the desktop management program means have management information that is used as a criterion for the communication management program means to determine whether to permit the transfer of the changed data. Monitors data change events for all data opened by all shared applications running on the desktop to detect changes, and reflects the changed data to other computers when a data change occurs To send change data to communication control program Monitors the ratio of the display area of the entire screen on the desktop to the visible area of the shared application, and the calculated ratio is the data displayed by each connected client by the shared application. A data transfer amount guarantee system for a shared application, wherein data that tends to be in a visible state is transferred preferentially as an index expressing the importance of the data. 2. When the visible area of a specific shared application changes due to mouse operation, scrolling, size change, etc., the cumulative value of the ratio of the entire screen area on the desktop to the newly visible area is calculated as: 2. The data transfer amount guarantee system according to claim 1, wherein an index representing the data reference frequency is used, and data with a high reference frequency is transferred with priority. 3. When data of a shared application is changed on a specific computer, another computer inquires whether the data is visible, and changes the data only on the computer on which the data is visible and on a specific server computer. 3. The data transfer amount guarantee system according to claim 2, wherein the transferred data is transferred. 4. A computer which has been notified of a change in data but has not received update data because the data is not in a visible state, sends the update data in response to the data being in a visible state as a trigger and sends the update data to a specific server. 4. The data transfer amount guarantee system according to claim 3, wherein by requesting the computer, the data can be updated when the data becomes necessary, and the server computer is requested to transfer the updated data. 5. When data held by each shared application is changed, window scroll processing is performed while an expected value of a maximum data transfer amount from a computer that has changed the data to another computer is equal to or less than a certain value. 5. The data transfer amount guarantee system according to claim 4, wherein the application data is segmented so as to reduce the number of times the update data is transferred at the time of the data transfer. 6. When a plurality of segmented data are simultaneously visible in each shared application, a combination of data that is simultaneously visible is defined as co-occurred data, and the co-occurred data set is defined as a co-occurred data. 7. The data transfer amount guarantee system according to claim 5, wherein the data transfer amount is reconstructed as individual data sets. 7. A table in which the probability of co-occurrence of data is calculated for each client computer, and when data of a specific shared application is changed,
7. The data transfer amount guarantee system according to claim 6, wherein data having a probability exceeding a specific threshold value is simultaneously transferred among the co-occurring data sets in the table.