KR19980045022A - User event control device and control method using the same - Google Patents

Abstract

The present invention relates to a user event control apparatus and a control method using the same, using a technique for locking a user event synchronization problem for objects under a fully distributed control structure that takes advantage of a centralized control structure and a duplicated control structure. To improve synchronization productivity by resolving synchronization issues, recognizing user input events on the client, substituting them for message operations by referring to the user event mapping table, and passing message operations directly to Windows for processing. There is an effect that can be used as a distributed object control engine in areas such as improving and other groupware, Computer Supported Cooperative Work (CSCW).

Description

User event control device and control method using the same

The present invention relates to a user event control apparatus and a control method using the same, and to a user event control apparatus and a control method using the same, which can solve the problem of synchronization of events to the network traffic, event processing load and shared objects of the node in a distributed environment It is about.

In general, the RTCAL system is a replica type system that shares and controls each other's information by building a shared information space from the participants' real time schedules. Cantata allows a participant to share access to a serial port through a terminal emulator rather than sharing a standard application running on a shared view sub-system called a switch board. Shared-X allows you to select and share one or more shared windows displayed via window sharing rather than full screen sharing, and one participant displays both a personal window and a shared window on his screen. It is based on the X Window System and uses a centralized approach. Dialogs have a clone structure that replicates each application to every workstation. The Rendezvous system uses a centralized structure as a system configured for synchronization of multi-user events for collaboration. However, there is a need to provide an appropriate user interface for end users, and many of the problems that arise for collaboration do not provide a clear way of sharing. Sepia is a system that supports collaboration using hypertext authoring tools among hypertext workers, providing object locking and using a centralized control structure. MERMAID is a replication system, a desktop conferencing system for distributed, multi-user users that aims to provide broad support for group collaboration. The problem of synchronization between events is floor passing. ) You are using control. The above systems support view sharing under either a replicated or centralized structure. The replica architecture uses an event sharing method, but all sites to collaborate must have an application to share. In addition, centralized systems do not need to load applications at every site, but use a method of communicating screen-captured image information about applications to be shared. Currently, in Korea, the user event processing method according to mouse movement by screen image capturing under centralized structure is used, and the synchronous event processing mechanism is in the research stage. Therefore, the method calculates the input coordinates of the mouse for the user event and delivers them to the server, and the server processes the coordinate values by mapping them to user interface actions.

The user event control structure for domestic collaborative processing has a problem in real time processing due to the increased network traffic and processing load to the central node by using a centralized control structure. The replication control structure does not have the disadvantage of the centralized control structure, but there is a problem that all nodes have the same execution environment. In addition, there is a problem of synchronization processing of objects for solving the integrity of resources in all nodes according to simultaneous user event processing.

Therefore, the present invention solves the problem of synchronizing user events to objects using a locking scheme under a fully distributed control structure that takes advantage of the centralized control structure and the duplicated control structure, and recognizes the user input event in the client. It is an object of the present invention to provide a user event control apparatus and a control method using the same, which replaces a recognized event with a message manipulation with reference to a user event mapping table, and delivers the message manipulation directly to Windows.

A user event processing apparatus according to the present invention for realizing the above object includes an event classifier for calling an event transmitted from an interpreter to a corresponding action module, and a message information manager for inspecting a new window of an object to be shared and registering the information. And a user event action module including a message mapper that supports retrieval, a window manager that manages the ID of the window, a window ID table that stores window handle information, and reference information that converts events into messages. A message mapping table that stores synchronization control information for a shared object, a user object synchronization controller that handles actual synchronization with respect to a shared object by referring to the message mapping table, and generates a window command using the window handle and the message. With the Windows command generator By passing a command to the Windows window comprises a presence mutator that the operation for the real shared object.

In addition, the user event processing method according to the present invention for realizing the above object is to receive an event from the event interpreter to classify the user event type, and from the step whether the classified event is a window for a new shared object Search and register a new window ID in the window ID table if the window is for a new shared object and receive a new window ID, and retrieve the window ID from the window ID table if the window ID is already registered; If the assigned window ID and the event are not found in the message mapping table by searching the message mapping table, the event is converted into a message and stored in the message mapping table and the number of related users are stored. If the window ID is in the message mapping table, Retrieve the message and then window Reducing the number of message users of the ID by one; and checking whether the number of users is zero to resolve synchronization with the shared object from the above step, unlocking if the number of users is zero and deleting the object from the message mapping table, If the number of users is not zero, ending the action on the message; generating a window command using the window ID and the message from the step; and transmitting the generated window command to the window from the step to the actual object. The presentation consists of a presentation.

1 is a block diagram of an information communication system software joint development platform according to the present invention.

2 is a block diagram of a joint operation distributed control engine according to the present invention.

3 is a block diagram of a user event handler according to the present invention;

4 is a flow chart of a user event handler applying a synchronization technique for shared objects in accordance with the present invention.

* Description of the symbols for the main parts of the drawings *

1 and 6: Message dispatcher 2 and 7: Interpreter

3 and 8: Application Sharing Event Handlers 4 and 9: Distributors

5: application 11: UIMS

12: Communication System 13: Shared Work Environment

14: event engine 20: CORBA

51: Event Categorizer 52: User Event Action

53: message information manager 54: message mapper

55: user object synchronization controller 56: window instruction generator

57: Presence Tate 58: Window Manager

59: window ID table 60: message mapping table

Hereinafter, a user event control apparatus and a control method using the same according to the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram of an information communication system software co-development platform according to the present invention, wherein a distributed control engine is operated around a distributed environment, and an environment of a user system for collaborating under a distributed environment is effective for collaboration. A user interface management system (UIMS) 11 for supporting use, a communication system 12 for exchanging multi-party information in a distributed environment, and a shared work environment as a work space for supporting collaboration (13) ), An event engine 14 that supports application sharing when collaborating and handles events of shared applications, and CORBA 20 for supporting distributed computing environments between user systems. Tools for collaboration (15, 17, 17, 31, 32, 33, 41, 42, and 43) are distributed to all users In this environment, it is possible to provide a collaborative environment by sharing tools for the purpose of joint development. The operation of this system is to set up the collaboration environment by selecting the appropriate tools and users for the purpose of collaboration in the UIMS (11), when the shared application is present in its system to drive the event engine (14) Create a server node and run the application in the shared work environment 13. In addition, by requesting collaboration to the collaborative participants and distributing application sharing information to users who approved the request, the collaboration environment is set up, and user events during the collaboration process are provided through the event engine 14. To be shared.

Fig. 2 is a block diagram showing a collaborative distributed control engine according to the present invention, in which a node owning an application 5 to collaborate serves as a server. The message dispatcher (1) interprets the patched messages through the message dispatcher (1), which retrieves the messages delivered from the server and clients in the order in which they are stored, and shares user events (UE), system events (SE), and applications. There is an interpreter (2) that is classified as an event (ASE: Application Shuring Event), and when the interpreted message is delivered to a user event processor (UEP) 3, the user event processor 3 according to the type of the message The window manager defines the ID (IDentifier) structure of the running windows of the node. Mapping information of the window ID currently being executed by the server with the window ID to be performed by the client in the message sent from the server. Is converted to the window handle of the node to be presented. This window handle is used to create a Windows command using the information in the message mapping table to create a window command to be sent to the User Event Action Module (UEA) and Windows. When generating a Windows command, information about the object to be presented is stored in the window message mapping table, which is used by the objects to control synchronization. At the end of the presentation, that is, all sharing of the object has been completed, the message mapping table is also stored so that users of other nodes can use the object. If the presentation of the object is input while presenting the object, the lock processing module is activated to delay the presentation, thereby ensuring the integrity of the object. When the presentation of the object is finished, the distributor 4 delivers the message to all nodes by COVA, which is a distributed object reference model, and the received nodes go through the above process. That is, the presentation of the object on the client is made through the client engine's message dispatcher 6, the interpreter 7 and the application sharing event handler 8. When the presentation ends, a termination message is sent to the server for use as information for the lock process.

3 is a diagram illustrating a user event handler, an event classifier 51 for calling an event transmitted from an interpreter to a corresponding action module, and a message information manager for inspecting a new window of an object to be shared and registering its information ( 53) and a user event action module 52 composed of a message mapper 54 supporting search, a window manager 58 that manages the IDentifier (ID) of the corresponding window, and window handle information (application name and window ID). A message mapping table that stores reference information (window ID, event, message) for converting an event into a message, and stores synchronous control information (number of users) for a shared object. 60), the user object synchronization controller 55 which processes the actual synchronization with respect to the shared object with reference to the message mapping table 60, the window handle and the message. Use is configured to command the window generator 56 and, and the resulting window command to create a window command, passing to windows in the presence mutator 57 to make the operation for the real shared object. The synchronization process on the shared object uses the information in the message mapping table 60 to enable the transformation of the shared object after the work of all nodes is finished.

FIG. 4 is a flow chart showing a processing flow based on the module of the user event processor shown in FIG. 3. In step S1, an event is received from the event interpreter 2 to classify a user event type. In step S2, it is checked whether the classified event is a window for a new shared object. If the window is for a new shared object, a new window ID is registered in the window ID table in step S3 and a new window ID is assigned. If the window ID is already registered, the window ID is found in the window ID table in step S4. In step S5, if the window ID and the event are allocated, the message mapping table is searched for, and if the message mapping table is not found, the event is converted into a message and stored in the message mapping table in step S6, and the number of related users is stored. If the window ID is in the message mapping table, the message corresponding to the event is retrieved in step S7, and the number of corresponding message users of the window ID is decreased by one in step S8. In step S9, to resolve the synchronization with respect to the shared object, it is checked whether the number of users is 0. If the number of users is 0, the lock is released in step S10 and the object is deleted from the message mapping table. If the number of users is not 0, the action on the message is terminated in step S11. In step S12, a window command is generated using a window ID and a message, and in step S13, the generated window command is transmitted to the windows to present and finish the actual object. Each node that collaborates on a shared object sends a termination message to the server after the presentation of the object is finished, and the server uses the corresponding window ID and message information until the number of users reaches zero. Disallowing access solves the shared object synchronization problem.

As described above, the present invention provides a fully distributed control structure that can reduce the processing load of nodes by distributing the processing load between nodes for minimizing network traffic and real-time processing in order to maximize the efficiency of collaboration. To improve the productivity of collaboration by using the synchronization control method between shared objects in presentations to solve the coherency problem of shared objects that occur simultaneously and simultaneously. There is an effect that can be used as a distributed object control engine in the field of.

Claims (2)

In the user event control device, An event classifier for calling the event delivered from the parser to the corresponding action module, A user event action module comprising a message information manager that inspects a new window of an object to be shared and registers the information, and a message mapper that supports retrieval; A window manager that manages the ID of the window; A window ID table for storing window handle information; A message mapping table that stores reference information for converting events into messages and stores synchronous control information for shared objects; A user object synchronization controller which processes the actual synchronization with respect to the shared object by referring to the message mapping table; A window command generator for generating a window command using the window handle and a message; And a presenter which transmits the generated window command to the windows to operate on a substantially shared object. In the user event control method, Classifying a user event type by receiving an event from an event interpreter; From the step, it is examined whether the classified event is a window for a new shared object, and if a window is for a new shared object, a new window ID is registered in the window ID table and a new window ID is assigned. Retrieving the ID from the window ID table; If the window ID and the event obtained from the step are not found in the message mapping table by searching the message mapping table, the event is converted into a message and stored in the message mapping table, and the number of related users is stored. Retrieving the message corresponding to and decreasing the number of message users of the window ID by 1; In order to solve the synchronization for the shared object from the above step, it is checked whether the number of users is 0, and if the number of users is 0, the lock is released, and the object is deleted from the message mapping table, and if the number of users is not 0, the action on the message is terminated. Steps, Generating a window command using the window ID and the message from the step; And presenting the actual object by transmitting the generated window command to the window from the step.