JP2001101015A - Method for sharing software data - Google Patents

Abstract

PROBLEM TO BE SOLVED: To extend the kind of sharable data by operating the data of an application through the application in a method for copying and sharing and operating data between apparatuses connected with each other on a network. SOLUTION: This method comprise a step for managing the state of each shared component data, a step for selecting update processing, based on the state of the component data, a step for transferring the processing to the other apparatus, a step for converting the transferred processing, based on the state of the component data, and a step for executing the converted update processing.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a technology for sharing, editing, and editing component software data between a plurality of information communication devices interconnected by a network.
The present invention relates to a data management method for enabling a change.

[0002]

2. Description of the Related Art In recent years, with the spread of OA equipment represented by personal computers, digitization of document information created and used in daily office work has rapidly spread. In addition, as personal computers have become more sophisticated, the document information that has been digitized has changed from a conventional table consisting only of text and text to a table with higher quality tables and graphs. I am doing it. Since it is difficult for application software for handling these data to have the ability to handle all the required data formats, each function is divided individually and these functions are used in combination. It is becoming. The technology for realizing the function division, combination, and mutual use of software is called software componentization or component software technology. component·
The software receives user input on its own and provides user output, as well as other components
A function of the software is called, and a function of the own component software is called from another component software. This realizes a software function as a component. component·
One of the representative software technologies is Microsoft
OLE provided by ft (book "INSIDE")
OLE2 "ISbN4-7561-0237-9) and activeX / COM (book" Unders "
standing activeX and OLE "I
SbN4-7561-1706-6).

[0003] At present, data used on a daily basis is not handled by a single application software, but by a component software technology, a set of component software data which is shared and handled by each component software. Moving to the body. The document data illustrated in FIG. 1 is an aggregate of component software data of a text, a table, and a diagram.

On the other hand, networks are rapidly being introduced into offices. Office networks initially spread from the use of file sharing and e-mail, and recently interest in data conferencing systems has increased.

[0005] A data conferencing system uses a computer network to transfer materials that have been distributed and exchanged in paper at a conventional conference between information and communication devices, that is, between users of the information and communication devices. Is a device and method for realizing an effect that data can be shared and a change can be made to the data in real time, and the change is reflected in all information communication devices. In a data conferencing system, in addition to being able to share and operate data dedicated to the system, conventional application software for single users (hereinafter referred to as "conventional applications") used by users in their daily work. It is strongly desired that data can be shared and manipulated.

The following methods already exist for sharing and manipulating the conventional application data in the data conference system.

(A) The data conferencing system itself can handle and operate the conventional application data independently of the conventional application.

(B) A conventional application for handling the conventional application data is executed on one of the information communication devices for performing a data conference, and the other information communication device executes the screen during the execution. Is displayed on the screen of each information communication device through the network. The input to the screen from each information communication device is delivered to the information communication device executing the conventional application via the network, and the information is input to the information communication device as if the information communication device is inputting to the conventional application. Passed to the native application and executes the native application based on the input.

In the method (a), since the data conference system itself can operate and manage the data, there is an advantage that all the functions provided by the data conference system can be used for arbitration of operations by a plurality of users at the same time. On the other hand, the disadvantage is that for traditional applications that increase daily,
Updating the data conferencing system to accommodate the application data is very difficult in terms of work costs. Data conferencing system
The ability to handle software data can greatly reduce the cost of responding to new application data. However, since the component software itself does not support the necessary operation / update synchronization in the data conference system, it is necessary to have a method for sharing component software data on the data conference system side. Regarding data sharing attempts for component software, please refer to Intel
ligentPad ("Synthetic Media System IntelligentP
Realization of a Cooperative Workplace in Ad ", Sho Nagasaki, Joe Tanaka, IPSJ Journal Vol.34 No.5 pp.1177
-Pp. 1187, 1993). Intelligen
In the work environment at tPad, the input event for the component software is distributed to a plurality of communication devices, transmitted, and executed by the component software on each device. This method is based on the premise that the shared environment can always acquire the user event for the component ahead of time.
In Pad, it can be used because it is implemented as such. However, similar components
In the framework of OLE, which is software, user events cannot be acquired and distributed by the shared environment prior to the component.

In the method (b), since the screen is shared instead of sharing the application and its data, there is an advantage regardless of the type of the application actually used. However, when a plurality of users simultaneously handle a conventional application that was originally assumed to be handled by one user, the operations from the plurality of users do not collide.
It is necessary to limit the number of users who can perform the operation to be always one at any time. In addition, it is inevitable that this limitation affects the entire application to be used. In the case of the conventional application data composed of the component software data described above, each operation of the component data can be operated by a different component, and the operation of each data has mutual influence. Has no effect. However, in the conventional application, the operation on the component data is unified by the user input means of the conventional application, and a plurality of component data constituting the shared conventional application data are stored in a plurality. Of users could not operate each separately at the same time. In this regard, the benefits of component software data could not be exploited.

[0011]

As described above, in the conventional data conferencing system, a plurality of components constituting data shared by the system are used.
There has been no way for multiple users to manipulate software data independently and simultaneously. For this reason,
Conventionally, operability when sharing and operating application data was greatly impaired.

[0012] Further, when a data conference system cannot acquire a user event for a component software prior to the component software, an operation for the component software data cannot be easily shared.

Therefore, for each component software data that makes the shared data fair, the user can operate the shared data, and the data conferencing system directly obtains and distributes a user event for the component software data. If not possible, there is a need for a data sharing method that does not depend on the data format to be handled and that provides an alternative updating method.

[0014]

To solve the above problems, the following means will be described.

According to the present invention, data is distributed and replicated between a plurality of information communication devices (hereinafter referred to as "devices") which can communicate with each other via a network, and a change operation for each data copy is performed by the device. The present invention relates to a data sharing method for mutually exchanging data and reflecting the change operation to maintain the same contents of the data copy between devices. Each of the devices is associated with a component,
A component status management unit that sequentially tracks and manages information on a status and a status change due to a user operation or update to the software data, and whether the component software data update process is necessary through the component status management unit. Component update processing determining means for determining whether to select component update processing, component update processing executing means for executing component update processing selected by the component update processing determining means, and receiving an update notification from another device At this time, the component receiving side update processing determining means for determining the component receiving side update processing for the component data with reference to the component state management means, and the component receiving side update processing determining means. Has been to run the component receiving side update process, a component software data sharing method and a component receiving side update execution means.

According to the sharing method of the present invention, when component software data shared among a plurality of devices is changed by a user input or the like in one device, an update notification to another device can be made. Waiting for the status, notifying the update and the update content in a format suitable for the data, and in the device receiving the update notification, referring to the status of the component data in the receiving device, An actual update process can be selected and executed.

That is, based on the operation state of the component software data in each device, each component software data is updated without interrupting the operation of the component data, and the contents are constantly shared. Becomes possible.

Further, according to the present invention, in the above component data sharing method, the component update processing determining means allows the user to switch the procedure of update processing determination according to a component update processing table defined by the user. Things.

According to the sharing method of the present invention, when component software data is changed in a certain device by a user input or the like, a state in which an update notification can be made to another device and an updating method are made by the user's will. You can choose
Necessary operations and unnecessary operations can be added / deleted according to the purpose of sharing.

The present invention also relates to the above component data sharing method, wherein the user can switch the procedure of update process determination by the component receiving side update process determining means according to a component update process table defined by the user. It is made possible.

According to the sharing method of the present invention, when an update notification of component software data is received in a certain device, an update method can be selected by the user on the receiving side based on the current state of the device. Necessary operations and unnecessary operations can be added / deleted according to the purpose of sharing.

The present invention also relates to the above component data sharing method, wherein the component receiving side update process determining means determines the update process by using the component software required for operating the component data to be updated. In the case where the component software does not have the above, after the necessary component software is transferred from another device, the operation is performed by the component software.

According to the sharing method of the present invention, when sharing certain component data and updating them together, the device also acquires component software for operating the component data, and if necessary, acquires the component software. The function of the device can be extended.

[0024]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Prior to the embodiment, first, the configuration of an information communication device on which the present method operates will be described, and after referring to the present method and defining some data to be operated and its format, Each procedure in the conventional example will be described.

A plurality of information communication devices (hereinafter, referred to as "devices") appearing in this embodiment form a network and can communicate with each other as shown in FIG. The figure shows a state in which three devices are interconnected by a bus-like network. However, this method is irrelevant to the configuration of the network, and only needs to be able to communicate with each other.

A configuration diagram of a device on which the present embodiment operates will be described with reference to FIG.

The device includes a transmission unit 1, a reception unit 2, an input unit 3, an output unit 4, a component execution unit 5, a component status monitoring unit 6, a component update determination unit 7, a component update execution unit 8, a component update unit. Determining unit 9, component receiving side update executing unit 10, component software 11, component software data 12, component type table 13, component reference table 14, component data status table 15, component update procedure table 16, component reception Side update procedure table 17.

The transmission unit 1 transmits a packet containing the update difference information created by the component update execution unit to another device. The receiving unit 2 receives the packet including the update difference information transmitted from the other device, and passes the packet to the component receiving side update determining unit.

The input unit 3 passes input information from the user to the component execution unit through input devices such as a keyboard, a mouse, and a pen.

The output unit 4 outputs output information of each component software to a user through screen display or voice.

The component execution unit 5 executes the component execution means, receives a user input and a request for executing a component procedure from another input means, and calls the component procedure indicated by the request in accordance with the request.

The component / data state monitoring unit 6
The component data state monitoring means is executed, the state of component software data notified from the component software and the change of the state are recorded in the component data state table 15, and are notified to the component update determination unit.

The component update determining unit 7 executes a component update determining unit, refers to the component data status table 15 and the component update procedure table 16, and selects an update procedure for the component for which a status change notification has been given. The update procedure is notified to the component update execution unit 8.

The component update execution unit 8 executes the component update execution unit, generates update difference information based on the update procedure notified by the component update determination unit, and passes the update difference information to the transmission unit 1.

The component receiving side update determining unit 9 executes the component receiving side update determining unit, receives the update difference information from the receiving unit 2, and refers to the component data state table 15 and the component receiving side updating procedure table 17. , Selects the receiving side update procedure for the component indicated by the update difference information, and notifies the component receiving side update execution unit 10 of the receiving side update procedure.

The component receiving side update execution unit 10
The component receiving side update execution procedure is executed, and the component software data is updated directly or by calling the procedure through the component execution unit 5 in accordance with the receiving side updating procedure notified from the component receiving side update determining procedure.

The details of the above-described component executing means, component status monitoring means, component update determining means, component update executing means, component receiving side update determining means, and component receiving side update executing means will be described later.

With reference to the present embodiment, data to be operated and words and phrases will be sequentially described.

Component software data 1
1 (hereinafter, “component data”) includes a data identifier, a type identifier, and a data body. The data identifier is information for distinguishing from other component data. The type identifier is
This is information for identifying the type of data. The type identifier is uniquely defined for each type. The data body is information unique to the component data, and its format and content differ depending on the component data or type.

FIG. 4 shows an example. In this example, the type identified by the data identifier "35E32b97"
HYO-KEISaN "component data whose content is" ZZZZZ ", as well as type" MOVIE "component data identified by the data identifier" 821bKW99 ".
This indicates that the content is “The Movie Show”.

The component data accepts user input such as mouse and key input, as well as procedure calls from other component data. The procedure call is actually made to the component software, and the component software publishes the procedure to an external program. To publish,
It is divided into basic procedures common to component software and external procedures specific to each component software. These procedures are acquired from the component by a “procedure list” procedure, which is itself a basic procedure of the component, and the external program refers to the procedure list and calls a procedure for the component.

The component software 11 (hereinafter, “component”) is software for operating component data. The component accepts a user input, operates corresponding component data, outputs a user output, and discloses a procedure that can be called from another program, and the other program can operate the component through the procedure.
The procedure includes a basic procedure provided as standard for all components and an extended procedure specific to each component. The basic procedures include, for example, the “procedure list” procedure, the “operation” procedure, and the “end” procedure.

These are a procedure for obtaining a list of procedures provided in the component, a procedure for shifting the component to the operating state and receiving user input, and a procedure for terminating the component in the operating state.
The extended procedure includes, for example, a “playback” procedure, a “stop” procedure, a “fast-forward” procedure, and a “rewind” procedure in the case of a “movie” display component. The names of these procedures are common to each data type, not to each component, and different components that have a common procedure name for a data type are compatible in their functions.

The component type table 13 includes pairs of a type identifier and a component identifier. The component identifier is uniquely defined for each component. FIG. 5 shows an example of the component type table. In this example, the component data of the “HYO-KEISaN” type is replaced with the component identifier “E29”.
2b2KW3238 ". Similarly, the" MOVIE "type is set to" 75PI23C251 ".
99 "component and" TEXT "type is" EW29 "
W212ba35 "component and" SHASHI
The "N" type indicates that it is associated with the "23b2395bWD95" type.

The component reference table 14 is composed of a pair of a component identifier and a path name where the entity of the component is located. FIG. 6 shows an example of the component reference table. In this example, the component identifier "E292b
The path name of the entity of the component software identified by “2KW3238” is “/ app / spreadsh
eet. exe ". Similarly," 7 "
5PI23C25199 "Component is" / User
/ Movieplay. exe "," EW29W212
ba35 "component is" / Suite / editw
ord. exe "component with" 23b2395b
WD95 "component is" / app / photovi
ew. exe "component.

The component data status table 15 is composed of a pair of a data identifier and a status identifier. As the status identifier, a status value unique to each data type can be given in addition to a status value common to all data types. The component data status table 15 contains the component data
Managed by data state monitoring means, component update processing determination means, component update processing execution means,
It is referred to by the component receiving side update processing determining means and the component receiving side update processing executing means. Each component always notifies its operation status and its change to the component data status monitoring means, and the component data status monitoring table 15 reflects the status.

The state values include a common state that each component has in common and a special state that each component has independently. The common state refers to the state that the component moves to in common, such as the "not running" state, "starting operation", "operating", "ending operation", and "operation stopped" state in the operation of the component . Here, for example, the non-operation state is a state before the component corresponding to the component data is activated, the operation start state is a transition state when the component is activated, and the operation state is a state where the component is activated. And
The state in which user input or procedure calls from external programs can be accepted, the operation end state indicates the transition state when the component ends operation, and the operation stop state indicates the component ends operation and restarts. The states of waiting are shown. A special state is a running state that each component or component data type has. For example, for the "video" data type, the operational state of the component can be stop, play, fast forward, rewind,
One of the operating states is assigned. These special states can be treated as states independent of the common state, or for example, as a sub-type of the "running" common state. For example, data identifier "35
“HYO-KEISAN” type data of “E32b97” and “MOVI of data identifier“ 821bKW99 ”
The E "type data is represented as shown in FIG.

The component update procedure table 16 includes a pair of a type identifier and an update procedure script. The update procedure script describes an update procedure for component data of the type classified by the type identifier, and is composed of a set of a conditional expression and an execution expression.
Actual conditional expressions and execution expressions will be described later. The component update procedure table is referred to by the component update process determining means.

The component receiving side update procedure table 17 is as follows.
The configuration is the same as the component update procedure table. Actual conditional expressions and execution expressions will be described later. It is referenced in the component receiving side update process determination procedure.

As a conventional example, a description will be given of a procedure in which a user operates component data using component software from a conventional application using a single device. This procedure includes a component data state monitoring unit and a component execution unit, and both units are executed in parallel.

The component data state monitoring means includes:
It is represented by the flowchart shown in FIG. 8 and includes the following steps. (Step a0) Wait for notification of a state change from the component. (Step a1) The component is notified of a state change. (Step a2) The status value corresponding to the component data is obtained by searching the component data status table. (Step a3) If the status value corresponding to the component data can be obtained, the process proceeds to Step a5. If the status value can be obtained, the process proceeds to Step a4. (Step a4) A state value corresponding to the component data is generated and added to the component data state table. (Step a5) The state value corresponding to the component data is updated to the notified state after the change. Go to step a0.

The component execution means is represented by a flowchart shown in FIG. 9 and comprises the following steps. (Step b0) Wait for an operation request to be transmitted to a certain component data through a user input. (Step b1) For the component data,
From the type information of the component data, the component type table is searched to obtain a corresponding component identifier. (Step b2) If the component identifier can be obtained, go to Step b3; otherwise, go to Step b.
To 0. (Step b3) Based on the component identifier,
The component reference table is searched to obtain a component entity corresponding to the component data. (Step b4) If the entity of the component can be obtained, go to step b5, otherwise go to step b0. (Step b5) Check whether the component has an operation procedure required by the operation request. (Step b6) If provided, go to step b7. Otherwise, go to step b0. (Step b7) Referring to the component data status table, if the status of the component data is "not operating", go to step b8, otherwise go to step b10
F. (Step b8) The component is activated. (Step b9) Monitor the component data status table, and if the status of the component data is "operating", go to step b10, otherwise go to step b9. (Step b10) The operation procedure of the component is called. Go to step b0.

As a conventional example, a data sharing method used in a conventional data conference system which does not handle component data will be described.

One method is described in (2.
b) As shown in the example, one specific device manages data, other devices including the specific device transfer user input to the specific device, and output a user from the specific device, that is, output a screen. This is a “screen sharing” method that receives and displays the received screen. However, as a conventional example of the present invention, there is a problem already described in the "prior art", and in the present invention, data management based on "distributed replication" is performed.

Here, the "distributed replication" method will be briefly described. For the shared data, a copy of the data is created in each of the plurality of devices and managed by each device. Once the copy is created and the shared data managed by each device, each device accepts a user operation on the data copy and notifies the other device of the operation content as an "update difference". By operating the data copy based on the update difference, the content of the shared data copy is maintained identical between the devices. When operating on certain data for the purpose of data sharing,
To ensure that the operation does not “collide” between the devices and that the data changes resulting from the operation are performed “equally” in each copy, the order of operations on the data from multiple devices must be Must be unique. Regarding the order maintaining method for this purpose, the inventor has hitherto described "Network system and information communication equipment and information communication method used therefor" (Japanese Patent Application No. 7-32).
1871), “Data Delivery Method” (Japanese Patent Application No. Hei 8-069)
578), and the present invention can also be applied to the order arrangement of update differences exchanged between devices. The present invention is a method for handling component software data in this sharing method by distributed duplication. (First Embodiment) A data sharing method according to a first embodiment will be described.

Each of the component / data state monitoring means, the component update determining means, the component update executing means, the component receiving side update determining means, and the component receiving side update executing means which constitute the sharing method shown in the present embodiment, As each of the programs operating on the devices, each of these devices operates in parallel with each other,
By the operation described below, component data sharing is realized between devices on the network.

The component / data state monitoring means includes:
Change as follows. Steps a0 to a5 are the same as in the related art. This is represented by the flowchart shown in FIG. (Step a0) Wait for notification of a state change from the component. (Step a1) The component is notified of a state change. (Step a2) The status value corresponding to the component data is obtained by searching the component data status table. (Step a3) If the status value corresponding to the component data can be obtained, the process proceeds to Step a5. If the status value can be obtained, the process proceeds to Step a4. (Step a4) A state value corresponding to the component data is generated and added to the component data state table. (Step a5) The state value corresponding to the component data is updated to the notified changed state. (Step a6) The component data and the state after the change are notified to the component update determination procedure. Go to step a0.

The component update processing determining means is shown in FIG.
1 and is composed of the following steps. (Step c0) Wait for notification of a change in the state of component data from the component data state monitoring means. (Step c1) A component update procedure table is searched based on the type identifier of the component data and the status value of the component data to obtain an update procedure for the component data. (Step c2) If the update procedure is obtained, step c3
What. Otherwise, go to step c0. (Step c3) The update procedure is notified to the component update processing execution procedure.

Here, a component update procedure table is shown. As described above, the component update procedure table lists pairs of component data type identifiers and update procedure scripts, and the update procedure script includes a conditional expression and an execution expression. The conditional expression describes an operating condition for executing the script, and the content is an integer expression based on the state value of the component data and its logical sum, logical product, and logical negation. The execution expression is an execution content for exchanging the update difference between the devices, and the content is a procedure name indicating a method of generating and notifying the update difference. These contents can be variously changed within the scripting ability depending on the type of component data and the purpose of data sharing for the user.

FIG. 12 shows an example. The state (X) indicates that the state value of the component data of the data type is the common state X. The state (X: Y)
The state value of the component data of the data type indicates that the common state is X and the special state is Y. The transfer (C) indicates that the update difference having the content C is transferred to another device. * A indicates that the procedure a of the component corresponding to the data type is executed.

The contents of the update procedure shown in the table are, for example, “H
In the case of "YO-KEISAn" type data, when shifting to the "operation stopped" state, it is necessary to acquire the contents of the component data, generate an update difference for transferring all the contents, and transfer the difference to another device. Is shown. "MOVI
In the case of data of type "E", when the state shifts to the "operating": "playing" state, an update difference of the content for executing the "playing" procedure of the component is generated and transferred to another device. I have. In the case of the data of the “MOVIE” type, when the state is shifted to the “operating”: “stopping” state, an update difference of the content for executing the “stop” procedure of the component is generated and transferred to another device. ing.

The component updating process executing means is shown in FIG.
It is represented by the flowchart shown in FIG. 3 and includes the following steps. (Step d0) Wait for a notification of an update procedure for specific component data from the component update processing determination means. (Step d1) Execute the update procedure for the component data.

More specifically, since the update procedure selected in the component update decision procedure is executed, the content executed in step d1 varies depending on the type of component data and the content of the update procedure. Can change.

The update difference information finally generated by the component update processing executing means and transmitted to the other device includes an identifier indicating an update difference, a component data identifier to be updated, and the update content. Is done.

The component receiving side update process determining means is represented by a flowchart shown in FIG. 14, and comprises the following steps. (Step e0) Wait for reception of an update difference transmitted from another device. (Step e1) Based on the type identifier of the component data specified by the update difference, the status value of the component data, and the content of the update difference of the component data, update the reception side update procedure table from the component reception side update procedure table. Search for a procedure. (Step e2) If the receiving-side update procedure is obtained, go to step e3. Otherwise, go to step e0. (Step e3) The component data and the obtained update procedure are notified to the component receiving side update execution procedure. Go to step e0.

FIG. 15 shows an example of the component receiving side update procedure table. The component receiving side update procedure table, compared with the component update procedure table, includes the content of the update difference in the conditional expression, and sets the update procedure for the update difference according to the state of the component data at that time, You can also choose.

Here, the replacement (all contents) indicates that all the contents of the component data are replaced with the contents of the transferred update difference. [ALL] in the type identifier column
Indicates for all type identifiers.

The contents shown in the example are as follows. If the difference update notification for transferring the entire contents arrives when the data of the "HYO-KEISaN" type is not in the "active" state or the "non-operation" state, the current component is terminated and the transferred contents are Then, an operation of replacing the component data is performed.
For "HYO-KEISaN" type data,
When the difference update notification for transferring the entire contents arrives in the "activity stopped" state or the "non-operation" state, an operation of replacing the component data with the transferred contents is executed. When the difference update notification by the "playback" command arrives in a state other than the common state "operating" and the special state "playing" for the "MOVIE" type data, the component starts operating, and Perform an operation to execute the "play" command. "MO
For the "VIE" type data, the common state "operating"
If the special update status is other than "Stopped", "Operation stopped", "Operation stopped", or "Not running", and the difference update notification by the "Stop" command arrives, Perform an operation that executes the "stop" command. If the difference update notification for transferring the entire contents of the "TEXT" type data is not in the "operation stopped" state or the "non-operation" state, no operation is performed. For all other types of data, if the operation status is "stopped" or "not running" and a difference update notification that transfers the entire content arrives, replace the component data with the transferred content Execute

The component receiving side update processing executing means is represented by a flowchart shown in FIG. 16 and comprises the following steps. (Step f0) Wait for notification of the update procedure on the receiving side for specific component data from the component receiving side updating process determining means. (Step f1) Execute the receiving side update procedure for the component data.

Specifically, since the receiving side updating procedure selected in the above component receiving side updating determining procedure is executed, it is executed in step f1 depending on the type of component data and the content of the receiving side updating procedure. Content can vary in many ways.

As described above, when these means are operated in each device, the operation on certain component data and the change in the state due to the operation are constantly monitored, and the necessary update processing is determined according to the change in the state. The update process is transmitted to other devices, and each device determines and executes an update process according to the status of each device. FIG. 17 shows the relationship between the processes performed by these units. (1 of Modification Example of First Embodiment) In the first embodiment, the component data state monitoring unit notifies the component update determination unit of the change in the state of the component data. However, by referring to the component data state table as needed by its own means, for example, at predetermined time intervals,
Update means may be selected. In this case,
The component update determining means needs to know whether or not the state of the component data has changed. In order to realize this, a status change field is provided for each data identifier in the component data status table, and the component / data status monitoring means sets the field according to the notification of the status change from the component, The component update determining means checks the field when referring to the component data state table, and resets the field if it is set. If the field is reset at the time of the check, the component
Assuming that the data has not changed,
Does not determine the update procedure for the data. As described above, the component update determining means can select the updating means by referring to the component data state table at a predetermined time interval, for example, as required by its own means. (Modification 2 of the first embodiment) In the first embodiment,
Actually, the component data is updated by the processing of the received update difference information. However, the update procedure is selected based on a change in state due to the update, and the update difference information is transmitted. That is, the change and update of the state of the component data are repeated indefinitely by one piece of update difference information. In order to avoid this, whether the change in the state of the component data is due to an operation request of a user input, a component update decision procedure, a component update execution procedure, a component receiver update decision procedure, a component receiver update execution procedure It is necessary to identify whether the change is caused by calling the component procedure, and to generate and transmit the update difference information to another device only for the change in the state of the component data due to the operation request of the user input.

For this purpose, the component execution history table 1
8 is newly provided. This identifies the component procedure executed by the component execution procedure as a component data identifier, whether the procedure call was by user input,
Procedure names are arranged in chronological order.

In the component execution procedure, when the procedure is called, the contents are added to the component execution history table 18.

The component / data state monitoring means includes:
Upon receiving the notification of the status change from the component, the component execution history table 18 is referred to, and the oldest history regarding the component data is deleted from the table in chronological order. The status change based on the history is based on the user input. And whether it is based on the component update selection procedure, the component update execution procedure, the component receiver update decision procedure, and the component receiver update execution procedure related to the method of sharing component data. Then, the status change is notified to the component update determination means.

As a result, the device does not generate and transmit a new update difference by processing the update difference from another device, and the device generates and transmits update difference information due to a change in the state of component data caused by a user input. It can be performed.

FIG. 18 shows a device configuration diagram based on this modified example.
An example of the component execution history table 18 is shown in FIG. 20 and 21 show flowcharts of the component execution unit and the component state monitoring unit based on this modification. (Step b0) Wait for an operation request to be transmitted to a certain component data through a user input. (Step b1) For the component data,
From the type information of the component data, the component type table is searched to obtain a corresponding component identifier. (Step b2) If the component identifier can be obtained, go to Step b3; otherwise, go to Step b.
To 0. (Step b3) Based on the component identifier,
The component reference table is searched to obtain a component entity corresponding to the component data. (Step b4) If the entity of the component can be obtained, go to step b5, otherwise go to step b0. (Step b5) Check whether the component has an operation procedure required by the operation request. (Step b6) If provided, go to step b7. Otherwise, go to step b0. (Step b7) Referring to the component data status table, if the status of the component data is "not operating", go to step b8, otherwise go to step b10
F. (Step b8) The component is activated. (Step b9) Monitor the component data status table, and if the status of the component data is "operating", go to step b10, otherwise go to step b9. (Step b10) The operation procedure of the component is called. (Step b11) Update the component execution history table, and go to step b0. (Step a0) Wait for notification of a state change from the component. (Step a1) The component is notified of a state change. (Step a2) The status value corresponding to the component data is obtained by searching the component data status table. (Step a3) If the status value corresponding to the component data can be obtained, the process proceeds to Step a5. If the status value can be obtained, the process proceeds to Step a4. (Step a4) A state value corresponding to the component data is generated and added to the component data state table. (Step a5) The state value corresponding to the component data is updated to the notified state after the change, and the process proceeds to Step a11. (Step a11) Referring to the component execution history table, if the change in the state of the component data is due to a procedure call by a user input, go to step a6. Otherwise, that is, if it is due to a procedure call by other means, go to step a0. (Step a6) The component data and the state after the change are notified to the component update determination procedure. Go to step a0. (Third Modification of First Embodiment) In the above example, when each device generates update difference information in accordance with a change in the state of component data and transmits it to another device, each device transmits the update difference information. The updated difference information obtained is, according to the premise of the distributed and distributed data sharing method, specifically "network system and information communication equipment and information communication method used therefor" (Japanese Patent Application No. 7-318771), According to the "data delivery method" (Japanese Patent Application No. 8-69578), the data arrives at the receiving units between the devices in the same order, and undergoes processing by the component receiving side update determining means in the same order.

However, the devices that have transmitted the update difference information have already been updated when the update difference information is generated, and this may prevent the state and the contents of the component data in each device from matching. For example, "video"
A change in state due to data reproduction / stop does not involve a change in the content of component data, whereas a change in state due to editing of "spreadsheet" data causes a change in the content of component data before transmission of update difference information. ing. Therefore, if an update difference from another device is received and applied before the update difference, the contents of the “spreadsheet” data in the device and the other device may differ.

There are the following two methods for solving this problem.

(1) When operating a component data, a certain device makes an operation reservation for the data to another device and, after the operation reservation is obtained, adds a user input to the data. be able to. In addition, exclusive control of user access for each component data is performed such that another device cannot add a user input of the other device to the data unless the device cancels the operation reservation. (2) In the case where the component has the “cancellation of the immediately preceding operation” procedure, the component update execution means includes the “cancellation of the immediately preceding operation” procedure in the updating procedure, and updates the update difference information with the own device. After transmitting to the device, the device executes the “cancellation of the immediately preceding operation” procedure, and the own device receives the update difference information at the receiving unit, and the component receiving side update determining unit and the component receiving side update executing unit Then, the component data is updated by the receiving-side update processing in the same manner as the other devices.

In the case of the method (2), the generation and transmission of new update difference information in accordance with the change in the state caused by the processing of the update difference information from another device according to the above second modification example. It is necessary to use the prevention method together. (Second Embodiment) In the second embodiment, there is no change in the component status monitoring means, the component update execution means, and the component reception side update execution means.

A user-defined updating procedure table and a user-defined receiving-side updating procedure table having the same configuration as the component updating procedure table and the component receiving-side updating procedure table referred to by the component updating process determining means and the component receiving-side updating determining means are provided. It is assumed that the user-defined updating procedure table and the user-defined receiving-side updating procedure table can be changed by the user of each device.

Component update processing determining means;
The component receiving side update process determining means has been changed as follows, and when searching for the updating procedure and the receiving side updating procedure, the user-defined updating procedure table and the user-defined updating procedure table have priority over the component updating procedure table and the component receiving side updating procedure table. Search from the definition receiving side update procedure table. (Step c1 ′) Based on the type identifier of the component data and the status value of the component data, a user-defined update procedure table and then a component update procedure table are searched to obtain an update procedure for the component data. (Step e1 ′) The type identifier of the component data specified by the update difference and the component data
Based on the data state value and the contents of the update difference of the component data, the receiving side updating procedure is searched from the user-defined receiving side updating procedure table and then the component receiving side updating procedure table.

Thus, for example, an update means can be selected for each user according to the user's desire, such as ignoring the update for a specific data type. (Third Embodiment) The third embodiment corresponds to the third claim.

An update procedure is included in the update content of the update difference exchanged between devices. That is, the description shown in FIG. 22 can be made in the execution formula part of the component update procedure table.

Assuming that the procedure (X / Y) is an update procedure composed of a conditional expression X and an execution expression Y, the following is called “MOVIE”.
If the data is in the "operating" or "playing" state, "execute the" stop "procedure if the component data is in the" operating "or" playing "state for another device" This indicates that the update procedure is transmitted as an update difference. In this case, the M
The reproduction of the OVIE data is stopped.

The generation and interpretation of such an update difference are changed as follows so that each procedure can be performed.

The component update determining means only needs to select an update procedure, so that no modification is necessary. Since the component receiving side update executing means only executes the receiving side updating procedure, there is no need for modification.

The component update execution means converts the update procedure into, for example, a character string in the generation of the update difference information, and transfers it as difference information.

The component receiving side update determining means is changed as follows. The flowchart is shown in FIG. (Step e0) Wait for reception of an update difference transmitted from another device. (Step e11) If the update difference includes an update procedure, go to Step 2. Otherwise, go to step e1. (Step e12) If the device satisfies the conditional expression indicated by the update procedure, the update procedure is selected, and step e3 is performed.
F. Otherwise, go to step e0. (Step e1) Based on the type identifier of the component data specified by the update difference, the status value of the component data, and the content of the update difference of the component data, update the reception side update procedure table from the component reception side update procedure table. Search for a procedure. (Step e2) If the receiving-side update procedure is obtained, go to step e3. Otherwise, go to step e0. (Step e3) The component data and the obtained update procedure are notified to the component receiving side update execution procedure. Go to step e0. (Modification) In step 2, when the update procedure does not include the update procedure, if the update procedure does not include the update procedure, the update procedure is selected according to the update procedure table of the device. You may move to

As described above, the update can be performed on the receiver side based on the intention of the updater without depending on the difference in the update procedure of the receiver between the devices. (Fourth Embodiment) The fourth embodiment corresponds to the fourth claim. The component receiving side update executing means shown in the above embodiment is modified as follows. The flowchart is shown in FIG. (Step f0) Wait for notification of the update procedure on the receiving side for specific component data from the component receiving side updating process determining means. (Step f11) The presence or absence of a component for the component data is determined by a component type table,
Search based on the component lookup table. (Step f12) If there is the component, go to step f13. If not, go to step f15. (Step f13) It is checked whether the component has a procedure included in the execution of the notified update procedure on the receiving side. (Step f14) If yes, go to Step f16.
If not, go to step f15. (Step f15) A component distribution requesting unit is executed for the type of the component data and the procedure name which the device does not have and waits for distribution. (Step f16) As a result of execution of the component distribution requesting means, if component software can be obtained, go to step f17. Otherwise, step f0
What. (Step f17) Execute the receiving side update procedure for the component data.

The component distribution requesting means is called from the component receiving side update executing means and comprises the following steps. FIG. 25 shows a flowchart. (Step g1) A component distribution request packet is created from a set of the type identifier corresponding to the component data and the procedure name specified by the component receiving side update executing means, and transmitted to all other devices. (Step g2) Wait for a response from the other device to the component distribution request packet. (Step g3) If there is a response within a predetermined time, go to step g4. Otherwise go to step g7. (Step g
4) If the response is a component distribution, go to step g5. Otherwise go to step g7. (Step g5) The distributed component is stored in a state where the device can be used, and the component type table and the component reference table are updated. (Step g6) “Success” is notified to the calling component updating means, and the processing ends. (Step g7) A "failure" is notified to the component updating means of the caller, and the processing ends.

The device has a component software distribution means comprising the following steps. FIG. 26 shows a flowchart. (Step h0) Wait for reception of a component distribution request from another device. (Step h1) The entity of the component is searched based on the type identifier indicated by the component distribution request.

(Step h2) If the entity of the component is obtained, the process proceeds to step h3. Otherwise, step h
Go to 6. (Step h3) The “procedure list” procedure of the component is executed, and it is confirmed whether or not the procedure indicated by the component distribution request is present. (Step h4) If the procedure is included, go to Step h5. Otherwise, go to step h6. (Step h5) The component is transmitted to the requesting device and distributed. Go to step h0. (Step h6) Notify to the requesting device that it does not have it and notify it. Go to step h0.

As for a series of procedures for performing distribution, in addition to the example shown here, the "information transfer method" (Japanese Patent Application No. Hei 6-205460), which has been filed, can be used.

[0095]

As described above, according to the present invention, a plurality of component software data shared on the system, which cannot be realized by the conventional data conferencing system, can be independently and simultaneously processed. The method of updating the component data between a plurality of devices for the user to operate is described. As a result, without expanding the data conferencing system itself, the data of component software used in
It is available through component software, can handle new types of component data, can delegate the details of manipulating the data to component software, and support data types as before, It can be realized at low cost without expanding the conference system itself.

Also, by applying the present invention as a method for sharing component software on a distributed replication type data conferencing system, each device, that is, each user, can be used as necessary on the data conferencing system. It is now possible to operate on the same or different component data independently and in parallel. This is the traditional
At present, the operation of the screen sharing data conferencing system, which is currently mainstream, is limited to one of the devices at the same time, ie, one of the conference members, and a set of component data that can be operated independently. The conventional application data configured as a body is restricted by the conventional application, that is, in the conventional application, component data that can be operated by user input is limited to one at the same time. The present invention solves the problem of losing the feature that can handle the component, and greatly improves the operability of the user for the data shared in the data conference.

[Brief description of the drawings]

FIG. 1 shows document data composed of component software data.

FIG. 2 shows an example of a network of information communication devices on which the method operates.

FIG. 3 is a configuration diagram of an information communication device on which the method operates.

FIG. 4 is an example of component software data.

FIG. 5 is an example of a component type table.

FIG. 6 is an example of a component reference table.

FIG. 7 is an example of a component data state table.

FIG. 8 is a flowchart of a component data state monitoring unit.

FIG. 9 is a flowchart of a component execution unit.

FIG. 10 is a flowchart of a component data state monitoring unit.

FIG. 11 is a flowchart of a component update determining unit.

FIG. 12 is an example of a component update procedure table.

FIG. 13 is a flowchart of a component update execution unit.

FIG. 14 is a flowchart of a component receiving side update determining unit.

FIG. 15 is an example of a component receiving side update procedure table.

FIG. 16 shows an example of a component receiving side update execution unit.

FIG. 17 shows relationships between procedures.

FIG. 18 is a configuration diagram of a device according to a second modification of the first embodiment.

FIG. 19 is an example of a component execution history table.

FIG. 20 is a flowchart of a component execution unit according to a second modification of the first embodiment;

FIG. 21 is a flowchart of a component / data state monitoring unit according to a second modification of the first embodiment;

FIG. 22 is an example of a component update procedure table including an update procedure in an update difference.

FIG. 23 is a flowchart of a component receiving side update determining unit in the third embodiment.

FIG. 24 is a flowchart of a component receiving side update execution unit in the fourth embodiment.

FIG. 25 is a flowchart of a component software distribution requesting unit according to the fourth embodiment.

FIG. 26 is a flowchart of a component software distribution unit according to the fourth embodiment.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Transmission part 2 Receiving part 3 Input part 4 Output part 5 Component execution part 6 Component status monitoring part 7 Component update determination part 8 Component update execution part 9 Component reception side update determination part 10 Component reception side update execution part 11 Component software 12 Component software data 13 Component type table 14 Component reference table 15 Component data status table 16 Component update procedure table 17 Component receiver update procedure table 18 Component execution history table

Claims (5)

[Claims] 1. A method for maintaining the same data content including at least one component software data that is distributed and managed between a plurality of information communication devices communicable with each other via a network. A component state management means for managing a state of component software data included in the data in a component software data sharing method for updating the data based on update information for the data exchanged with the component; A component update process determining means for selecting an update process for the component software data from a plurality of update process candidates prepared in advance based on a state of the software data and a change in the state, and the selected component ·software A component update process executing means for executing a data update process, a status of component software data of the information communication device and a change in the status, and a component software program which is update information transmitted from another information communication device. A component receiving-side update process determining unit that selects a component software data update process from a plurality of update process candidates prepared in advance based on the data update process notification; and a component software data update process. A method for sharing software data, comprising: a component receiving-side update process executing means to be executed. 2. A method for distributing and managing data between a plurality of information communication devices that can communicate with each other via a network, exchanging update information for each data copy between the devices, and A component state that updates each data copy based on the data copy method and maintains a state of each component software data included in the data copy in a data sharing method for maintaining the same data copy content between devices. Management means and components
Based on software data state and state change,
A component update process determining unit that selects an update process for the component data from a plurality of update process candidates prepared in advance, and a component update process execution unit that executes an update process of the selected component software data And the state of component software data of the information communication device and a change in the state, and update information transmitted from another information communication device,
A component receiving side update process determining means for selecting component software data update process from a plurality of update process candidates prepared in advance, based on the component software data update process notification; A method for sharing software data, comprising: a component receiving-side update process executing unit that executes an update process. 3. The component update processing determination means and the component reception side update processing determination means refer to an update procedure table and a reception side update procedure table defined by a user of each information communication device, and determine update process candidates in the tables. 3. The software according to claim 1, wherein the software is selected.
How to share data. 4. The update information selected by the update process determining means, the update information exchanged between the devices by the update process executing means includes a component update process candidate table, and the receiving side update process selecting means is included in the update information. 4. The software data sharing method according to claim 1, wherein an update process is selected based on a component update process candidate table. 5. If the component software necessary for updating any component software data is not present in the device, the component software is updated by the component receiving side update processing determining means. 5. The software data sharing method according to claim 1, wherein the information is obtained from the information communication device and the update process is continued.