JP4127566B2 - Electronic conference system - Google Patents

Description

  The present invention relates to a server / client type electronic conference system in which a plurality of clients are connected to one server and each client can view or edit information stored in the server. This technique is also suitable for a server / client type education system that can be viewed or edited.

  Conventionally, AT & T's VNC (Virtual Network Computing) is a software that allows a single client to simultaneously display the screen data of both the server screen buffer in the shared screen mode and the server screen buffer in the individual screen mode in multiple windows. ) With this software, if a file system is used in which a plurality of application processes can be opened multiple times for one document file, one document can be displayed simultaneously on the shared screen window and the individual screen window of the client. In addition, separate editing operations can be performed on individual screens (windows).

  Another prior art is Microsoft's NetMeeting. This NetMeeting has a function (application sharing function) for sharing an application executed on one terminal or server with a plurality of other terminals. When the OS of each terminal is Microsoft Windows, documents displayed in the application sharing function of NetMeeting and documents in the shared folder of other terminals can be simultaneously displayed in separate windows using the folder sharing function. Can be displayed.

Nikkei Computer 1991.3.11.

  However, in the conventional technique described above, for example, when performing copy processing between two windows, the user needs to specify the position of the copy source, the area, and the position of the copy destination, and there is a problem that the operation becomes complicated. It was. In the former case, the contents edited in the document displayed in the individual screen window cannot be automatically reflected in the same document displayed in the shared screen window, or cannot be reflected by the operation of one button. . Similarly, even in the latter technique, the contents edited in the document displayed using the folder sharing function are automatically applied to the same document displayed using the application sharing function of NetMeeting or by the operation of one button. Cannot be reflected.

  Further, for example, in electronic conferences and the like, electronic cooperative work is conventionally performed in which a plurality of terminals share one document (conference material), and the document is created, edited, and viewed jointly. However, since all of the postscript and editing work processes for shared documents at each terminal are shared, for example, typographical errors when entering text from the keyboard and corrections are displayed on other terminals. End up. Therefore, terminal users who perform additional writing, editing, and the like are required not to share work that they do not want others to see.

The present invention has been made in view of the above problems,
It is an object of the present invention to add to each shared document when a plurality of terminals share a document and perform electronic collaborative work such as a conference while jointly creating, editing, and browsing the document. It is an object of the present invention to provide an electronic conference system that prevents all terminals from sharing parts that are unnecessary to others or that are not desired to be seen by others during work processes such as editing.

  Another object of the present invention is to add data such as text created on each terminal to a shared document without specifying the copy source position and area and the copy destination position, thereby improving operability. It is to provide an electronic conference system.

  1 (a) and 1 (b) are diagrams for explaining the basic concept of the present invention. In the figure, window type A is a shared screen, and the screen data is the same on the large screen and all terminals. And the editing and editing performed in one terminal is reflected in real time on the display screens of all other terminals. Window type B is an individual screen, and the same screen data as the shared screen can be displayed and added and edited individually, but this screen data is not shared.

  On the individual screen B of the terminal 1 (FIG. 1A), by adding a handwritten drawing such as “important” and pressing a predetermined button, the same handwritten drawing is added to the shared screen A of the terminal 2 and the terminal 3 Is displayed (FIG. 1B).

  In the present invention, in a process of adding and editing a shared document in each terminal, a part unnecessary for others or not desired to be seen by others is not shared by all terminals, and a predetermined number corresponding to the work is determined. At every timing, the work results up to that point are shared by all terminals.

  In the present invention, a sentence being created is input until an end-of-sentence symbol such as “.” (In Japanese), “. (Period)” or “?” (In English) is input on each terminal. When a sentence terminator is input without being shared by all terminals, a sentence including the sentence terminator created so far is shared by all terminals.

  In the present invention, the text being created is not shared by all the terminals until one terminal or a plurality of predetermined lines are input at each terminal, and when a predetermined number of lines are input, it is generated up to that point. Share the text on all devices.

  In the present invention, when handwriting input is performed using a mouse or an electronic pen on each terminal, a predetermined time elapses without starting the next stroke (not pen-down) from the end of the stroke (pen-up). Until then, the handwritten data input so far is not shared by all terminals, and when a predetermined time elapses without starting the next stroke from the end of the stroke, To share with.

  In the present invention, when handwriting input is performed using an electronic pen on each terminal, input is performed until it is determined that the movement of the electronic pen is a gesture operation for a predetermined inter-screen copy command. Do not share the handwritten data with all terminals, and share the handwritten data input so far with all terminals when the movement of the electronic pen is determined to be a gesture operation for a predetermined inter-screen copy command To.

  In the present invention, until a predetermined button displayed on the display or a predetermined function key on the keyboard is selected on each terminal, the editing process up to that point is not shared by all terminals but displayed on the display. When a predetermined button or a predetermined function key on the keyboard is selected, the editing contents up to that point are shared by all terminals.

  The same document data is stored in both the screen buffer of the server in the shared screen mode and the screen buffer of the server in the individual screen mode, but each screen data displayed on one client must be in the same location of the document There is no. For example, if the second page of a document is displayed in the shared screen window of the client and the third page of the same document is displayed in the individual screen window of the same client, and the third page is edited, the page is shared. The third page of the document stored in the screen buffer of the server in the screen mode is similarly edited. That is, the client user can edit any location of the document displayed in the shared screen window regardless of the display of the shared screen window.

  By the way, in many cases, it is convenient that the position of the document displayed in the client individual window is always the same as the position of the document displayed in the shared window.

  Accordingly, in the present invention, data from the same position of the same document is displayed in the shared screen window and the individual screen window of the client, and it can be added to others in the process of adding and editing the shared document in one client. Do not share unnecessary parts that you do not want to be seen by other people on all terminals, and add data such as text created on the client to the shared document by specifying the location of the copy source, the area, and the location of the copy destination. Improve the convenience of the system by making it possible to execute without specifying.

  Sometimes it is useful to know who the text or handwritten drawing added to a shared document belongs to. Therefore, in the present invention, the data added to the shared document is displayed separately for each client on which the addition operation has been performed.

As described above, according to the present invention, the following effects can be obtained.
(1) When adding or editing a shared document on an individual terminal, parts that are not needed by others or that are not wanted to be seen by others are not shared by all terminals, so they can be shared without worrying about the eyes of others. Additional writing and editing can be performed on the document, improving convenience for users such as conference participants.
In addition, the same document displayed on the shared screen is displayed on an individual screen that can be referred to only by you, and you can edit the document displayed on the shared screen on this individual screen regardless of the content displayed on the shared screen. Since it can implement, a user's convenience improves.
Furthermore, since data such as texts created by individual terminals can be added to the shared document without specifying the copy source area and the copy destination position, the burden on the user is reduced.
(2) When a sentence terminator is entered, the sentence created so far is shared by all terminals, so it is possible to enter a sentence without worrying about the eyes of others, and to add to a shared document Becomes unnecessary and the burden on the user is reduced.
(3) When one line or a predetermined number of lines are input, the text created so far is shared by all the terminals, so that it is possible to input text without worrying about the eyes of others, and to share documents No additional operation is required and the burden on the user is reduced.
(4) When a predetermined time elapses without the next stroke being started after the end of the handwritten stroke, all the handwritten data that has been input so far is shared by all the terminals. In addition to being able to perform handwriting input, no additional operation to the shared document is required, reducing the burden on the user.
(5) When it is determined that the movement of the electronic pen is a gesture operation for a predetermined inter-screen copy command, the handwritten data input so far is shared by all terminals, so that the eyes of others are not minded. In addition, handwriting input can be performed, and an additional operation to the shared document is not necessary, thereby reducing the burden on the user.
(6) When a predetermined button displayed on the display or a predetermined function key on the keyboard is selected, the editing contents up to that point are shared by all terminals, so that editing can be done without worrying about the eyes of others. Can do. In addition, since the editing can be reflected in the shared document with a single button operation for a plurality of editing operations, the burden on the user is reduced.
(7) Since the display position of the document displayed on the individual screen is always the same as the display position of the document displayed on the shared screen, the user does not need to adjust the display position of the document, improving user convenience. To do.
(8) Since the data added or edited in the shared document is displayed separately for each terminal on which the addition or editing operation has been performed, identification of who (or which terminal) is the added or edited data And the convenience of the system is improved.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

(Server / client type electronic conference system)
As an embodiment of the present invention, a server / client type electronic conference system in which a conference is held while a plurality of clients view and edit a conference material document stored in the server will be described as an example.

  FIG. 2 shows a configuration example of a server / client type electronic conference system according to the present invention. The system of the present invention comprises a server 1, a large display device 2 connected thereto, and clients 3 to 6 used by each conference participant. These devices are connected to a wireless LAN (for example, IEEE (Institut of Electrical and Industrial). (Electronics Engineers) 802.11b).

The server 1 is, for example, a computer having a PC-AT (The Personal Computer for Advanced Technologies) architecture (IBM), and a wireless LAN PC card (MC) via a PCI adapter board connected to the PCI (Peripheral Component Interconnect) bus. (Compliant with Personal Computer Memory Card International Association) standard). Further, Linux (registered trademark) is installed in the server 1 as an OS, and an X window is installed as a window system. In FIG. 1, the keyboard connected to the server 1 is not shown.

  The large display device 2 has a touch panel attached to a display surface of a PDP (Plasma Display Panel), for example, and is connected to the server 1 by a VGA cable and an RS-232C cable, and functions as the display device of the server 1. Functions as a touch input device. The VGA cable outputs a screen display signal from the server 1 to the PDP, and the RS-232C cable inputs touch input coordinate data detected by the touch panel to the server 1. Further, the server 1 processes the input touch input coordinate data in the same manner as the mouse input data.

  The clients 3 to 6 are portable display pads specialized in the function of transmitting text data and handwritten data input by the user to the server 1 and displaying screen data received from the server 1. Pens 7 to 10 are attached.

FIG. 3 shows a hardware configuration of the portable display pad 20 that is the clients 3 to 6. The portable display pad 20 includes a CPU 21, a clock 22, a main memory 23, a ROM 24, an RTC 25, a wireless LAN controller 26, an antenna 27, an LCD display controller 28, an LCD 29, a touch panel controller 30, a touch panel 31, a USB controller 32, and a USB I / F 33. , System bus 34, battery 35, DC-DC converter 36, charging circuit 37, AC adapter 38, and the like. The CPU 21 executes and processes a control processing program, OS, and various application programs stored in a ROM (Read Only Memory) 24. The clock 22 is composed of a crystal oscillator and a frequency dividing circuit, and generates a clock for controlling the operation timing of the CPU 21 and the system bus 34. The main memory 23 is composed of a DRAM (Dynamic Random Access Memory) and is used in the work area of the CPU 21 and the like. In the ROM 24, a program for controlling the entire system is written in advance. An RTC (Real Time Clock) 25 is a date clock, and is backed up by a dedicated battery (not shown). The wireless LAN controller 26 executes and controls wireless communication conforming to the IEEE 802.11b standard. The LCD display controller 28 performs D / A (Digital / Analog) conversion on characters and graphic data, and screen data received from the server 1, and performs control for displaying these data on the LCD 29. The touch panel controller 30 detects a portion where the pen tip of the touch pen 7 contacts on the touch panel 31 and takes in the position information. The touch panel 31 is overlapped and in close contact with the LCD 29. A USB (Universal Serial Bus) controller 32 executes and controls data transfer conforming to the USB standard. The battery 35 is, for example, a lithium ion battery that can be charged. The DC-DC converter 36 converts the power supplied from the AC adapter 38 or the battery 35 into a predetermined voltage and supplies it to the portable display pad 20, and from the battery 35 when there is no power supply from the AC adapter 38. Switch to the power supply. The charging circuit 37 charges the battery 35 when power is supplied from the AC adapter 38. The AC adapter 38 is integrated with a detachable power cable, and an AC power source is converted into a direct current of a predetermined voltage by a built-in AC-DC converter. The portable display pad 20 is mounted with Linux (registered trademark) as an OS and an X window as a window system.

  Next, the operation of server / client software in which screen data in the server 1 is transmitted to the clients 3 to 6 and user input data is transmitted from the clients 3 to 6 to the server 1 will be described. A case where the above-described VNC is used as the server / client software will be described below.

  When the VNC server process (hereinafter referred to as VNC server) starts up, it generates one screen buffer for storing desktop display screen data or document display screen data. The VNC client process (hereinafter referred to as VNC client) The screen data in the screen buffer is displayed on the display of its own device. Screen data transmitted from the VNC server to the VNC client and user input data transmitted from the VNC client to the VNC server are transferred using an RFB (Remote Frame Buffer) protocol. The RFB protocol has a function of dividing data of one screen into small areas (rectangles), and further compressing and transmitting the image data of the small areas. The minimum block of this small area is called a tile and is 16 × 16 pixels. In this way, since the VNC server can divide and transmit the data of one screen, only the changed area in one screen can be selected and transmitted. The VNC server process existing in the server 1 and the VNC client processes existing in the clients 3 to 6 can communicate with each other through sockets.

  The VNC server processes user input data received from the VNC client as a key event or a pointer event. Upon receiving these events, the VNC server operates as an X server and notifies the X client of the X event, so that the VNC client can operate an application (X client) running on the server 1. . The relationship between the VNC protocol (RFB protocol) and the X protocol is shown in FIG.

Next, an operation sequence until the clients 3 to 6 connect to the server 1 and operate an application (X window) running on the server 1 to display a document will be described. In the server 1, first, VNC server processes are started for the required number of screen buffers. In order to prevent this screen buffer from being shared by a plurality of clients, that is, to set only one client to be attached, only the screen number is specified in the startup command of the VNC server. For example, when the screen number is 2, the startup command for the VNC server is as follows.
vncserver: 2

When the screen buffer of the server 1 is shared by a plurality of clients, an option for instructing sharing is designated in addition to the screen number in the start command of the VNC server. For example, the start command of the VNC server when screen number 1 is shared is as follows.
vncserver-alwaysshared: 1

In this way, the VNC server process is started so that the server 1 shares screen number 1 and the clients 3 to 6 individually attach screen numbers 2 to 5. Then, each of the clients 3 to 6 starts the VNC client process by designating the IP (Internet Protocol) address of the server 1 and the screen number to be attached. An example of a startup command for the VNC client when the screen number to be attached is 3 is shown below.
vncviewer 192.168.1.1:3
Here, 192.168.1.1 is an IP address.

  FIG. 5 shows an example of a screen buffer secured on the main memory of the server. Each client 3 to 6 activates a VNC client for a shared screen (screen number 1) and a VNC client for one individual screen (screen numbers 2 to 5). In each of the clients 3 to 6, a window for displaying the shared screen and a window for displaying the individual screen are displayed on the LCD 29. In the server 1, in order to display the shared screen on the large display device 2, the VNC client process is started by designating the IP address and screen number 1 of the own device. In this way, only the shared screen is displayed on the large display device 2, and the shared screen and the individual screen are displayed on each of the clients 3 to 6, respectively.

  Next, when one client displays an arbitrary document in the shared screen display window using a predetermined application among the clients 3 to 6, the same document is displayed on the large display device 2 and the other clients 3 to 6. Displayed in the shared screen display window. Subsequently, each of the clients 3 to 6 displays the same document as the document displayed in the shared screen display window by using the same application used to display the document in the shared screen display window. Display in window.

  The above processing can be realized by using known VNC server / client software.

The processing described below is a processing operation related to the present invention.
In the invention, when the same document is displayed in the shared screen display window and the individual screen display window and the display position of the document in the two windows is the same, that is, the same document data is displayed in the shared screen display window and the individual screen display. When the document displayed in the window is displayed and the document displayed in the individual screen display window is edited, the same editing as described above is executed for the document displayed in the shared screen display window after a predetermined timing. Is done.

  The VNC server managing the individual screen stores all the key event data and pointer event data received from the VNC client when the document displayed in the individual screen display window is being edited. Then, these stored events are sequentially notified to the VNC server that manages the shared screen at a predetermined timing. The VNC server that manages the shared screen performs the same processing as that received from the VNC client for the key event and the pointer event received from the VNC server that manages the individual screen. In other words, the VNC server that manages the shared screen executes the same processing as the processing that the VNC server that manages the individual screens executes in real time for the key event and the pointer event received from the VNC client after a predetermined timing period. Delivery of key event data and pointer event data between the two VNC servers is performed by inter-process communication using a socket.

  In the present invention, the above-described editing operation is prohibited from being simultaneously executed by a plurality of clients (or terminals). That is, according to the present invention, the processing is executed based on the exclusive control of the operation right. Therefore, for example, when adding a sentence, it is possible to prevent a problem that a sentence near the addition position is deleted by another client (or terminal) immediately before the addition and the sentence is added to an unintended position. The exclusive control of the operation right is, for example, MERMAID (see Non-Patent Document 1) or ITU-T recommendation T.264. 124, ITU-T Recommendation T.24. A known technique such as described in 125 is used.

(Example 1)
Example 1 is an example in which input of sentence end symbols is used as the above-described predetermined timing.

  The clients 3 to 6 may display a keyboard window on the LCD 29 and input characters (text) using an electronic pen, or connect a USB keyboard to the USB I / F 33 and input characters from the USB keyboard. it can.

(1) When the document display position is the same;
First, if the same document is displayed in the shared screen display window and the individual screen display window of all clients and the document display position in these two windows is the same, for example, the shared screen display window and the individual screen display A case where the window is displayed from the top of the first page of the same document will be described.

  For example, it is assumed that the user of the client 3 inputs characters (text) using the electronic pen on the keyboard window in order to add a sentence to a certain position of the document displayed in the individual screen display window. At this time, until the sentence end symbol “.” (Japanese), “.” Or “?” (English) is input, the added sentence is displayed only in the individual screen display window of the client 3. Has been. When the sentence end symbol is input, the character string (text) input so far and the sentence end symbol are added from the same position of the document displayed in the shared screen display window. That is, the contents of the document displayed in the shared screen display window of the client 3 and the contents of the document displayed in the individual screen display window are different from when the character input is started until the sentence end symbol is input. When the sentence end symbol is input, the contents of the document displayed in the individual screen display window are reflected in the contents of the document displayed in the shared screen display window, and the contents of both documents become the same.

  When a sentence terminator is input from the client 3 and the document displayed in the shared screen display window is updated, the updated document is also displayed in the shared screen display window and the large display device 2 of the other clients 4 to 6. Is displayed. Furthermore, the updated document is also displayed in the individual screen display windows of the other clients 4 to 6.

  The above operation will be described in detail. The internal process of the server 1 and the data flow between each process and the clients 3 to 6 are shown in FIG. 8 and 9 show an operation flow of the VNC server 2 when the user of the client 3 inputs a character (text) in the individual screen display window in the screen display of each client (FIG. 7).

  Hereinafter, a description will be given with reference to FIGS. 6, 8, and 9. In the server 1, the VNC server 1 that manages the shared screen (screen number 1), each VNC server (VNC server 2 to 5) that manages the individual screens (screen numbers 2 to 5) of the clients 3 to 6, and the client 3 Document editing application 1 activated by operating any one of the shared screens 1 to 6, Document editing applications 2 to 5 activated by operating the individual screens of the clients 3 to 6, and the shared screen (screen number 1) Each process of the VNC client 1 that displays the screen data on the large display device 2 is activated.

  In the client 3, the process of the VNC client 3-A that displays and operates the shared screen with the screen number 1 and the process of the VNC client 3-B that displays and operates the individual screen with the screen number 2 are started. Yes. In the client 4, the process of the VNC client 4-A that displays and operates the shared screen with the screen number 1 and the process of the VNC client 4-B that displays and operates the individual screen with the screen number 3 are activated. In the client 5, the process of the VNC client 5-A that displays and operates the shared screen with the screen number 1 and the process of the VNC client 5-B that displays and operates the individual screen with the screen number 4 are activated. In the client 6, the process of the VNC client 6-A that displays and operates the shared screen with the screen number 1 and the process of the VNC client 6-B that displays and operates the individual screen with the screen number 5 are activated.

  When the electronic pen 7 points to move the cursor to a position where a character (text) is input to the document displayed in the individual screen display window of the client 3, the VNC client 3-B of the client 3 Data (coordinate data) is transmitted to the VNC server 2 of the server 1 (arrow 41 in FIG. 6). The VNC server 2 receives the coordinate data as a pointer event (YES in step 101), passes the coordinate data to the document editing application 2 (arrow 42, step 102), and places the event data in a queue (queue 2) (step 2). 103). This queue is an array defined in the program.

  Next, the document editing application 2 moves the cursor to the position of the received coordinate data and issues a drawing request to the VNC server 2 (arrow 43). When the VNC server 2 receives the drawing request (YES in step 104), it changes the display position of the cursor and transmits the updated screen data to the client 3 (arrow 44, step 105).

  Subsequently, when a character (text) is input in the individual screen display window of the client 3, the VNC client 3-B transmits this character code to the VNC server 2 (arrow 41). The VNC server 2 receives these character codes as key events (YES in step 106), passes these character codes to the document editing application 2 (arrow 42) (step 107), and puts the event data in the queue 2 (Step 108).

  Upon receiving these character codes, the document editing application 2 adds these character codes to the document data and issues a drawing request to the VNC server 2 (arrow 43). When receiving the drawing request (YES in step 109), the VNC server 2 displays the character font corresponding to each character code at the cursor position and transmits the updated screen data to the client 3 (arrow 44, step 110). .

  As described above, when a character string is input by a user and a sentence end symbol is input, the VNC server 2 receives the sentence end symbol (YES in step 111), and uses the sentence end symbol (character code) as a document editing application. 2 (arrow 42), and this event data (sentence symbol) is put into the queue 2 (step 112).

  Upon receiving the sentence end symbol (character code), the document editing application 2 adds the sentence end symbol (character code) to the document data and issues a drawing request to the VNC server 2 (arrow 43). When receiving the drawing request (YES in step 113), the VNC server 2 displays a character font corresponding to the sentence end symbol (character code) at the cursor position and transmits the updated screen data to the client 3 (arrow 44). Step 114).

  The VNC server 2 sequentially transmits the event data stored in the queue 2 to the VNC server 1 and the VNC servers 3 to 5 in the order of first-in first-out (step 115). Before and after sending event data in queue 2, an event including data indicating the start of these event data groups (event group start data) and data indicating the end (event group end data) Data is also transmitted to the VNC server 1 and the VNC servers 3 to 5 (arrows 45 to 48).

  The VNC server 1 passes these event data between the event group start data and the event group end data to the document editing application 1 (arrow 49). The document editing application 1 performs processing corresponding to these event data (arrow 50), that is, performs the same processing as the document editing application 2 executed previously. The VNC server 1 does not transmit the updated screen data (shared screen data) to the clients 3 to 6 until the event group end data is received after the event group start data is received. When the VNC server 1 receives the event group end data, the VNC server 1 transmits the screen data at that time to the client 3 (arrow 51). As a result, the content of the document displayed in the shared screen display window of the client 3 and the content of the document displayed in the individual screen display window become the same. In addition, the VNC server 1 transmits the updated shared screen data to the clients 4 to 6 (arrows 52 to 54) and also transmits to the VNC client 1 (arrow 55). The clients 4 to 6 display these shared screen data on the LCD 29, and the VNC client 1 displays them on the large display device 2.

  The VNC servers 3 to 5 perform the same processing as the VNC server 1, and accordingly, the display screens of the individual screen display windows of the clients 4 to 6 are updated (arrows 56 to 64), and the shared screen display windows of the clients 3 to 6 are displayed. The contents of the displayed document and the document displayed in the individual screen display window are all the same document contents.

(2) When the display position of the document is different;
Next, if the same document is displayed in the shared screen display window and the individual screen display window of each client, but the display positions of the documents in these two windows are different, that is, the shared screen display window and the individual screen display window A case where the document data displayed on the screen is different will be described.

  For example, the first page is displayed on the shared screen display windows of the clients 3 to 6, the second page is displayed on the individual screen display windows of the clients 3 and 5, and the third page is displayed on the individual screen display window of the client 4. It is assumed that the fourth page is displayed in the six individual screen display windows. FIG. 7 shows a screen display example of the clients 3 to 6 at this time.

  When the user of the client 3 moves the cursor to a position of the document on the second page displayed in the individual screen display window and inputs a character (text) using the electronic pen on the keyboard window to add a sentence, The VNC client 3-B of the client 3 transmits the point position data (coordinate data) and the character code to the VNC server 2 of the server 1 (arrow 41).

  The VNC server 2 receives this coordinate data as a pointer event, receives a character code as a key event, passes the coordinate data and the character code to the document editing application 2 (arrow 42), and puts these event data in the queue 2 . When the document editing application 2 receives the coordinate data, it moves the cursor to that position on the second page and issues a drawing request to the VNC server 2 (arrow 43). When the document editing application 2 receives the character codes (arrow 42), it adds these character codes to the document data and issues a drawing request to the VNC server 2 (arrow 43). The VNC server 2 changes the display position of the cursor and transmits the updated screen data to the client 3 (arrow 44), displays the character font corresponding to each character code at the cursor position, and displays the updated screen data. It transmits to the client 3 (arrow 44).

  As described above, when the user inputs a character string and a sentence end symbol, the VNC server 2 receives the sentence end symbol and sends the sentence end symbol (character code) to the document editing application 2 (arrow 42). At the same time, the event data (sentence symbol) is put in the queue 2.

  Upon receiving the sentence end symbol (character code), the document editing application 2 adds the sentence end symbol (character code) to the document data and issues a drawing request to the VNC server 2 (arrow 43). Upon receiving the drawing request, the VNC server 2 displays a character font corresponding to the sentence end symbol (character code) at the cursor position and transmits the updated screen data to the client 3 (arrow 44).

  The VNC server 2 sequentially transmits the event data in the queue 2 to the VNC server 1 and the VNC servers 3 to 5 in the first-in first-out order. Before and after sending event data in queue 2, an event including data indicating the start of these event data groups (event group start data) and data indicating the end (event group end data) Data is also transmitted to the VNC server 1 and the VNC servers 3 to 5. (Arrows 45-48).

  The VNC server 1 passes these event data between the event group start data and the event group end data to the document editing application 1 (arrow 49). The document editing application 1 performs processing corresponding to these event data (arrow 50), that is, performs the same processing as the document editing application 2 executed previously.

  The VNC server 1 does not transmit the updated screen data (shared screen data) to the clients 3 to 6 until the event group end data is received after the event group start data is received. When the VNC server 1 receives the event group end data, the VNC server 1 transmits the screen data at that time to the client 3 (arrow 51). Therefore, the contents of the document displayed in the shared screen display window of the client 3 and the document displayed in the individual screen display window are the same. In addition, the VNC server 1 transmits the updated shared screen data to the clients 4 to 6 (arrows 52 to 54) and also transmits to the VNC client 1 (arrow 55). The clients 4 to 6 display these shared screen data on the LCD 29, and the VNC client 1 displays them on the large display device 2.

  The VNC server 3 passes the event data received from the VNC server 2 to the document editing application 3 (arrow 56). The document editing application 3 performs processing corresponding to these event data, that is, performs the same processing as the previously executed document editing application 2, but displays the processed page (second page) on the client 4. Therefore, no drawing request is issued to the VNC server 3. In this case, when receiving the event group end data, the VNC server 3 does not transmit the screen data at that time to the client 4 because there is no change in the screen data. Therefore, the display content of the individual screen display window of the client 4 does not change.

  The VNC server 4 passes the event data received from the VNC server 2 to the document editing application 4 (arrow 59). The document editing application 4 performs processing corresponding to these event data, that is, performs the same processing as the previously executed document editing application 2, and adds a cursor drawing request at the position instructed to the VNC server 4. A drawing request for the designated character is issued (arrow 60). The VNC server 4 changes the display position of the cursor and displays the character font corresponding to each character code at the cursor position. When the VNC server 4 receives the event group end data, the VNC server 4 transmits the screen data at that time to the client 5 (arrow 61). Accordingly, the display content of the individual screen display window of the client 5 is updated to be the same as the content of the document displayed in the individual screen display window of the client 3.

  The VNC server 5 passes the event data received from the VNC server 2 to the document editing application 5 (arrow 62). The document editing application 5 performs processing corresponding to these event data, that is, performs the same processing as the previously executed document editing application 2, but displays the processed page (second page) on the client 6. Therefore, no drawing request is issued to the VNC server 5. In this case, when receiving the event group end data, the VNC server 5 does not transmit the screen data at that time to the client 6 because there is no change in the screen data. Therefore, the display content of the individual screen display window of the client 6 does not change.

  In the above-described embodiment, the operation when a character (text) is input in the individual screen display window of the client 3 has been described. However, the character (text) in any individual screen display window of the clients 4 to 6 has been described. When the corresponding VNC server (3 to 5) executes the same operation as that of the VNC server 2, the screen display content of each client can be displayed in the same manner as described above.

(Example 2)
In the first embodiment described above, when the VNC server 2 receives a sentence end symbol from the client 3, the event data (including the sentence end symbol) received so far is transmitted to the VNC server 1 and the VNC servers 3 to 5. In this embodiment, the document editing applications 1 to 5 execute the same editing process. In this embodiment, when the VNC server 2 receives a line feed code from the client 3, the same processing as that in the first embodiment is executed. To do. The operation of the second embodiment is obtained by replacing the sentence end symbol of the first embodiment described with reference to FIGS.

  That is, the timing at which the VNC server 2 transmits the event data stored in the queue 2 to the VNC server 1 and the VNC servers 3 to 5 is not when the sentence end symbol is received from the client 3 but when the line feed code is received. Therefore, in the second embodiment, the contents of the document displayed in the shared screen display window and the individual screen display window are different until the user inputs a line of characters (text) and a line break is made, but the line break is made. The contents of the documents displayed in these windows are the same.

  The second embodiment described above is an example of inputting characters (text) for one line, but the present invention is not limited to this, and when the user inputs characters (text) for a plurality of lines, that is, the VNC server 2. When a plurality of line feed codes are received, it can be executed in the same manner as in the second embodiment.

(Example 3)
The third embodiment is an embodiment where a client user performs handwriting input instead of text input. In the present embodiment, whether or not the user is performing a writing operation is determined from the duration of the state in which the electronic pen is up.

  Assuming that the screen display of each client is FIG. 7, the third embodiment will be described with reference to FIGS. 6 and 10 (operation flowchart of the VNC server 2).

  When the touch panel controller 30 of the client 3 detects that the electronic pen has touched the touch panel 31 (FIG. 3), the client 3 transmits the contact coordinates to the VNC server 2 at predetermined time intervals for coordinate detection ( Arrow 41). The VNC server 2 receives the coordinate data as a pointer event, and passes the coordinate data to the document editing application 2 (arrow 42).

  The document editing application 2 uses the coordinate data as the position data of the cursor or the drawing position data for free line drawing. Now, the document editing application 2 is in a mode in which the received coordinate data is used as drawing position data for free line drawing, and executes a function of drawing the received coordinates with lines during one stroke (from pen down to pen up). is doing. At the start of this free line drawing function, the document editing application 2 transmits setting information such as the color and thickness of the drawing line to the VNC server 2. This is a request from the X client to the X server in the X protocol.

  When the VNC server 2 receives the drawing line setting information (YES in step 201), it operates as a handwriting input mode (step 202). When the VNC server 2 enters the handwriting input mode, the time between pointer events received from the client 3 is measured (steps 203 and 204). If the measurement time is within the predetermined time, the VNC server 2 passes the coordinate data to the document editing application 2 (arrow 42, step 205) and puts the pointer event data into the queue 2 (step 206). This queue is an array defined in the program.

  When the document editing application 2 receives the coordinate data, it issues a request to the VNC server 2 to draw a line between the previously received coordinates (arrow 43). When the VNC server 2 receives the drawing request (YES in step 207), the VNC server 2 draws the coordinates between the lines and transmits the updated screen data to the client 3 (arrow 44, step 208). If the measurement time between the pointer events exceeds a predetermined time, that is, if the timer started upon receiving the pointer event times out (YES in step 209), the VNC server 2 stores the event data in the queue 2 Are sequentially transmitted to the VNC server 1 and the VNC servers 3 to 5 in the order of first-in first-out (step 210).

  Before and after sending event data in queue 2, an event including data indicating the start of these event data groups (event group start data) and data indicating the end (event group end data) Data is also transmitted to the VNC server 1 and the VNC servers 3 to 5 (arrows 45 to 48).

  The VNC server 1 passes these event data between the event group start data and the event group end data to the document editing application 1 (arrow 49). The document editing application 1 performs processing corresponding to these event data (arrow 50), that is, performs the same processing as the document editing application 2 executed previously. The VNC server 1 does not transmit the updated screen data (shared screen data) to the clients 3 to 6 until the event group end data is received after the event group start data is received. When the VNC server 1 receives the event group end data, the VNC server 1 transmits the screen data at that time to the client 3 (arrow 51).

  Therefore, the content of the document displayed in the shared screen display window of the client 3 is the same as that of the document displayed in the individual screen display window. In addition, the VNC server 1 transmits the updated shared screen data to the clients 4 to 6 (arrows 52 to 54) and also transmits to the VNC client 1 (arrow 55). The clients 4 to 6 display these shared screen data on the LCD 29, and the VNC client 1 displays them on the large display device 2.

  The VNC server 3 passes the event data received from the VNC server 2 to the document editing application 3 (arrow 56). The document editing application 3 performs processing corresponding to these event data, that is, performs the same processing as the previously executed document editing application 2, but displays the processed page (second page) on the client 4. Therefore, no drawing request is issued to the VNC server 3. In this case, when receiving the event group end data, the VNC server 3 does not transmit the screen data at that time to the client 4 because there is no change in the screen data. Therefore, the display content of the individual screen display window of the client 4 does not change.

  The VNC server 4 passes the event data received from the VNC server 2 to the document editing application 4 (arrow 59). The document editing application 4 performs processing corresponding to these event data, that is, performs the same processing as the previously executed document editing application 2, and issues a line drawing request between coordinates to the VNC server 4 (arrow 60). . The VNC server 4 performs line drawing according to this request. When the VNC server 4 receives the event group end data, the VNC server 4 transmits the screen data at that time to the client 5 (arrow 61). In this way, the display content of the individual screen display window of the client 5 is updated to be the same as the content of the document displayed in the individual screen display window of the client 3.

  The VNC server 5 passes the event data received from the VNC server 2 to the document editing application 5 (arrow 62). The document editing application 5 performs processing corresponding to these event data, that is, performs the same processing as the previously executed document editing application 2, but displays the processed page (second page) on the client 6. Therefore, no drawing request is issued to the VNC server 5. In this case, when receiving the event group end data, the VNC server 5 does not transmit the screen data at that time to the client 6 because there is no change in the screen data. Therefore, the display content of the individual screen display window of the client 6 does not change.

Example 4
In the fourth embodiment, in the individual screen display window of the client, the user performs handwriting input using the electronic pen and performs a predetermined gesture operation on the touch panel 31, so that the handwritten drawing input so far is displayed on the shared screen. It is an Example in the case of being copied.

  11 and 12 are operation flowcharts of the VNC server 2 according to the fourth embodiment. Hereinafter, the fourth embodiment will be described. The document editing application 2 transmits setting information such as the color and thickness of a drawing line to the VNC server 2 at the start of the free line drawing function. This is a request from the X client to the X server in the X protocol.

  When the VNC server 2 receives the drawing line setting information (YES in step 301), it operates as a handwriting input mode (step 302). When the VNC server 2 enters the handwriting input mode, the current time is obtained as a time stamp for each pointer event received from the client 3 (steps 303 and 304). The VNC server 2 cyclically adds the coordinate data together with the time stamp to the coordinate array existing on the main memory 23 (step 305), and matches the predetermined pattern for the copy command between the screens from the data in the coordinate array. It is determined whether or not to perform (step 306). At this point, since it is not determined whether the data is the drawing data or the copy command, the screen data is transmitted to the client 3 and displayed once in the individual screen display window as in the third embodiment.

  FIG. 13 shows an example pattern for an inter-screen copy command. In FIG. 13, point A is a pen-down position, point D is a pen-up position, and the pen tip moves from point A to point B, from point B to point C, and from point C to point D. Parameters to be compared with this pattern are the lengths of line segment AB, line segment BC, line segment CD, time from point A to point D (stroke time), vector AB (A → B), vector BC (B → C) and the direction of the vector CD (C → D) (angles formed with the X axis and Y axis of the display screen).

  In FIG. 13, the angle between the vector AB and the Y axis is α, the angle between the vector BC and the Y axis is β, and the angle between the vector CD and the X axis is γ. In order to determine that the movement of the pen tip is a pattern for an inter-screen copy command, a predetermined range is defined for each parameter value other than the stroke time among the reference parameters. The stroke time and the upper and lower limits of these parameters are stored in advance in the ROM 24. Then, the stroke start point (point A in FIG. 13) and end point (point D in FIG. 13) are determined from the coordinate sequence received from the client 3 (stored in the coordinate array) based on the time stamp, When the time until D is equal to or less than a predetermined value, a vector between coordinates in one stroke is obtained, a point (point B or point C in FIG. 13) where the direction of the vector changes greatly is detected, and a line segment AB , Line segment BC and line segment CD are obtained, and the three angles α, β, and γ shown in FIG. 13 are obtained, and these parameter values are within a predetermined value range stored in advance in the ROM 24. If all the conditions are satisfied, it is determined that the command is an inter-screen copy command (YES in step 307).

  When the inter-screen copy command is detected, among the event data stored in the queue 2, the number of coordinates satisfying the above condition in the direction from the latest to the past (that is, the coordinates of FIG. 13 corresponding to the copy command). (Data) is transferred to the document editing application 2 together with the drawing erasure instruction information, and the passed event data is deleted from the queue 2 (step 308).

  In order to erase the designated drawing line, the document editing application 2 sends a request for redrawing the background portion of the drawing line (overwriting the drawing line) to the VNC server 2, and when the VNC server 2 receives the request ( Step 309), the designated line drawing portion is overwritten with the background data to delete the line, and the updated screen data is transmitted to the client 3 (step 310).

  As described above, the movement of the pen tip for gesture is once drawn in the individual screen display window of the client 3, but this drawing is canceled when the VNC server 2 recognizes the gesture action. Then, the VNC server 2 sequentially transmits the event data stored in the queue 2 to the VNC server 1 and the VNC servers 3 to 5 in the first-in first-out order (step 311). The subsequent operation is the same as that of the third embodiment described above. Further, when the condition is not satisfied in step 307, the same operation as in the third embodiment is performed (steps 312 to 315).

(Example 5)
In the fifth embodiment, the user performs an editing operation using an electronic pen or a USB keyboard on a document displayed in the individual screen display window of the client, and a predetermined button displayed on the LCD 29 is selected. This is an embodiment in the case where the editing process up to that point is executed for a document displayed on the shared screen.

  FIG. 14 is an operation flowchart of the VNC server 2 according to the fifth embodiment. The fifth embodiment will be described below. Buttons (edit synchronization buttons) are displayed on the display screen of the LCD 29 in an area other than the shared screen display window and the individual screen display window.

  The edit synchronization button is a button for causing the same editing process as that performed on the document displayed on the individual screen display window to be performed on the document displayed on the shared screen display window.

  When various editing operations such as character (text) input, handwriting input, sentence deletion, sentence copy, and the like are performed on the document displayed in the individual screen display window of the client 3, the VNC client 3-B of the client 3 The key code (character / symbol code, line feed code, etc.) and point position data (coordinate data) are transmitted to the VNC server 2 of the server 1. The VNC server 2 passes these received event data (key code, coordinate data) to the document editing application 2 (steps 401 and 402), and enters the queue 2 (step 403). This queue is an array defined in the program.

  If the edit synchronization button is not selected (NO in step 404), the document editing application 2 performs processing according to the received event data, and if the display data on the screen needs to be changed, it is rendered on the VNC server 2. Make a request. The VNC server 2 receives the drawing request (YES in step 405), performs the instructed drawing, and transmits the updated screen data to the client 3 (step 406).

  When the user selects the edit synchronization button, the application 2 issues a request for instructing edit synchronization to the VNC server 2, and when the VNC server 2 receives a request for instructing edit synchronization (YES in step 404), the application 2 enters the queue 2. The event data contained therein are sequentially transmitted to the VNC server 1 and the VNC servers 3 to 5 in the order of first-in first-out (step 407). Before and after sending event data in queue 2, an event including data indicating the start of these event data groups (event group start data) and data indicating the end (event group end data) Data is also transmitted to the VNC server 1 and the VNC servers 3 to 5.

  The VNC server 1 passes these event data between the event group start data and the event group end data to the document editing application 1, and the document editing application 1 performs processing corresponding to these event data. The same processing as that performed by the document editing application 2 is performed. The VNC server 1 does not transmit the updated screen data (shared screen data) to the clients 3 to 6 until receiving the event group start data and before receiving the event group end data. When the VNC server 1 receives the event group end data, the VNC server 1 transmits the screen data at that time to the clients 3 to 6 and the VNC client 1. Then, the contents of the document displayed in the shared screen display window of the client 3 and the document displayed in the individual screen display window are the same. When the VNC servers 3 to 5 also receive the event data from the server 2, the VNC servers 3 to 5 execute the same processing as in the above-described embodiment, and the document editing applications 3 to 5 also perform the same processing as the document editing application 2 previously executed. The content of the document displayed in the shared screen display window of the clients 3 to 6 (the same as the document displayed on the large display device 2) and the content of the document displayed in the individual screen display window are the same.

(Example 6)
Example 6 is an example according to the shared screen mirroring mode. The shared screen mirroring mode is an operation mode in which the display data of the shared screen and the display data of the individual screens of the clients 3 to 6 are always the same. This mode is set by touching a shared screen mirroring mode setting button (not shown) displayed on the large display device 2 before the start of the conference, or any terminal that can operate the shared screen during the conference (for example, This is set by selecting a shared screen mirroring mode setting button displayed on the shared screen from the client 3).

  In the shared screen mirroring mode, the shared screen display data and the individual screen display data of the clients 3 to 6 always have the same contents. Operate to do.

  The operation in the shared screen mirroring mode will be described with reference to FIG. The VNC server 1 existing in the server 1 receives the event data of key events and pointer events received from the VNC clients 1 and 6 -A existing in the VNC client 1 and the clients 3 to 6. Also transmit to 2-5.

  When character input is performed on the shared screen of the client 3, the VNC client 3-A transmits a character code to the VNC server 1 of the server 1 (arrow 71). The VNC server 1 receives this character code as a key event, passes this character code to the document editing application 1 (arrow 72), and when the document editing application 1 receives this character code, it adds this character code to the document data. At the same time, a drawing request is issued to the VNC server 1 (arrow 73).

  The VNC server 1 displays a character font corresponding to the character code at the cursor position and sequentially transmits the updated screen data to the client 3, the VNC client 1, and the clients 4 to 6 (arrows 74 to 78). Then, the VNC server 1 transmits the previously received key event data to the VNC servers 2 to 5 (arrows 79 to 82).

  When the VNC server 2 receives the event data, it passes the character code to the document editing application 2 (arrow 83). When the document editing application 2 receives the character code, it adds the character code to the document data and draws it to the VNC server 2. A request is made (arrow 84). The VNC server 2 displays the character font corresponding to the character code at the cursor position and transmits the updated screen data to the VNC client 3-B of the client 3 (arrow 85). The VNC servers 3 to 5 perform the same operation as the VNC server 2, and the display of the individual screens of the clients 4 to 6 is updated (arrows 86 to 94). The display data and the individual screens of the shared screen display windows of the clients 3 to 6 are updated. All display data in the display window has the same contents.

  When the electronic pen 7 is used to move the cursor or select a menu on the shared screen of the client 3, the character code is replaced with the point position data (coordinate data) and the key event is replaced with the pointer event. Thus, the same operation as described above is executed. Since all operations on the shared screen are automatically performed on the individual screens of all clients, the document display position on the shared screen always matches the document display position on all client individual screens. To do.

  An example of an operation on a document displayed on the individual screen of the clients 3 to 6 set in the shared screen mirroring mode as described above will be described. Here, the first embodiment described above is used as an example of the operation. That is, text is input to the document displayed in the individual screen display window of the client 3, and the document displayed in the shared screen display window of the clients 3 to 6 and the individual screen display window are displayed every time the sentence terminator is input. A description will be given of the operation in which all the contents of the read documents are the same.

  Hereinafter, a description will be given with reference to FIG. The operation of the VNC server 2 is the same as that of the first embodiment as shown in the flowcharts of FIGS.

  When the electronic pen 7 points to the document displayed in the individual screen display window of the client 3 to move the cursor to a position for inputting characters (text), the VNC client 3-B of the client 3 Point position data (coordinate data) is transmitted to the VNC server 2 of the server 1 (arrow 41). The VNC server 2 receives the coordinate data as a pointer event, passes the coordinate data to the document editing application 2 (arrow 42), and places the event data in a queue (queue 2). This queue is an array defined in the program. Then, the document editing application 2 moves the cursor to the position of the received coordinate data and issues a drawing request to the VNC server 2 (arrow 43).

  The VNC server 2 changes the display position of the cursor and transmits the updated screen data to the client 3 (arrow 44). Subsequently, when a character (text) is input in the individual screen display window of the client 3, the VNC client 3-B transmits this character code to the VNC server 2 (arrow 41). The VNC server 2 receives these character codes as key events, passes these character codes to the document editing application 2 (arrow 42), and places the event data in the queue 2. Upon receiving these character codes, the document editing application 2 adds these character codes to the document data and issues a drawing request to the VNC server 2 (arrow 43). The VNC server 2 displays the character font corresponding to each character code at the cursor position and transmits the updated screen data to the client 3 (arrow 44).

  In this way, when the user inputs a character string and a sentence end symbol, the VNC server 2 sequentially stores event data including the sentence end symbol in the queue 2 in the order of first-in first-out. , To the VNC server 1 and the VNC servers 3 to 5. Before and after sending event data in queue 2, an event including data indicating the start of these event data groups (event group start data) and data indicating the end (event group end data) Data is also transmitted to the VNC server 1 and the VNC servers 3 to 5 (arrows 45 to 48).

  The VNC server 1 passes these event data between the event group start data and the event group end data to the document editing application 1 (arrow 49). The document editing application 1 performs processing corresponding to these event data (arrow 50), that is, performs the same processing as the document editing application 2 executed previously. The VNC server 1 does not transmit the updated screen data (shared screen data) to the clients 3 to 6 until the event group end data is received after the event group start data is received.

  When receiving the event group end data, the VNC server 1 transmits the screen data at that time to the client 3 (arrow 51). Then, the content of the document displayed in the shared screen display window of the client 3 is the same as that of the document displayed in the individual screen display window. In addition, the VNC server 1 transmits the updated shared screen data to the clients 4 to 6 (arrows 52 to 54) and also transmits to the VNC client 1 (arrow 55). The clients 4 to 6 display these shared screen data on the LCD 29, and the VNC client 1 displays them on the large display device 2.

  The VNC servers 3 to 5 perform the same processing as the VNC server 1, and the display screens of the individual screen display windows of the clients 4 to 6 are updated (arrows 56 to 64) and displayed on the shared screen display windows of the clients 3 to 6. The contents of the displayed document and the document displayed in the individual screen display window are all the same.

  In addition, although the example which used the sentence termination symbol was demonstrated as a predetermined | prescribed timing, this invention is not limited to this, For example, the text shown in Example 2-Example 5 mentioned above, for example, one line of text or predetermined | prescribed Applicable when multiple lines are input, when a predetermined time has elapsed since the end of handwritten stroke (pen-up), when it is determined that the gesture operation is for an inter-screen copy command, or when a predetermined button is selected. is there.

(Example 7)
Example 7 is an example in which the discriminability of added data is improved. That is, at each predetermined timing shown in the first to sixth embodiments, the text or handwritten drawing data added in the individual screen display window of one client is added to the document displayed in the shared screen display window. When doing this, the attributes such as the display colors of the text and handwritten drawing data are made different so that each client is displayed and identified.

  Hereinafter, the operation of the seventh embodiment will be described with reference to FIGS. 6 and 16 (operation flowchart of the VNC server 1).

  The document editing application 1 adds data such as text and handwritten drawing data to the document displayed in the shared screen display window. Therefore, the VNC server 1 passes the event data received from the VNC servers 2 to 5 to the document editing application 1 together with a number for identifying each VNC server (steps 501 and 502). As numbers for identifying the VNC servers, for example, numbers 1 to 4 are assigned to the VNC servers 2 to 5, respectively.

  The document editing application 1 adds the character code and handwritten data received as event data to the document data, and sends a drawing request for drawing the added data in a color corresponding to the VNC server identification number to the VNC server 1. put out. For example, red, blue, green, and yellow are associated with VNC server identification numbers 1 to 4, respectively.

  Upon receiving the drawing request, the VNC server 1 displays the character font and handwritten drawing line corresponding to each character code in the designated color, and transmits the updated screen data to the clients 3 to 6 and the VNC client 1. (Steps 503, 504, 505). That is, text and handwritten drawing data added in the individual screen display window of the client 3 are displayed in red on the shared screen, and text and handwritten drawing data added in the individual screen display window of the client 4 are displayed in blue on the shared screen. Is displayed.

  In each of the above-described embodiments, the case where the editing operation is performed by the client 3 has been described.

In each of the above-described embodiments, an example in which a wireless LAN is used as a communication unit between the server 1 and the clients 3 to 6 has been described. However, Bluetooth (registered trademark) , wired LAN (Ethernet) (registered trademark), and the like are used. Other communication means may be used. Further, although the description has been given using the example in which the clients 3 to 6 are portable display pads, the present invention is not limited to this, and a terminal such as a notebook PC or PDA that can implement the VNC client software and can communicate with the server 1. May be used.

(Inter-terminal data communication type electronic conference system)
The following embodiment is an electronic conference system when terminals constitute a data communication system. That is, in the electronic conference system of the present invention, a plurality of terminals having displays are connected to a network, and a meeting is held while browsing and editing documents shared by all terminals and documents individually owned for each terminal. .

  FIG. 17 shows a network configuration example composed of a plurality of terminals. This network is composed of terminals 1000, 1010, 1020, 1030, 1040 used by each conference participant, and these terminals are connected by a wireless LAN. Terminals 1000 to 1040 are portable display pads with a built-in hard disk, and electronic pens 1050 to 1090 are attached.

FIG. 18 shows a hardware configuration of the portable display pad 20a which is the terminals 1000 to 1040. In FIG. 18, CPU 21, clock 22, main memory 23, ROM 24, RTC 25, wireless LAN controller 26, antenna 27, LCD display controller 28, LCD 29, touch panel controller 30, touch panel 31, USB controller 32, USB I / F 33, system bus 34, the battery 35, the DC-DC converter 36, the charging circuit 37, and the AC adapter 38 are the same components as those described in FIG. In the portable display pad 20a of the present embodiment, an HD (Hard Disc) controller 39 and a hard disk 40 are further provided. The portable display pad 20a is mounted with Linux (registered trademark) as an OS and an X window as a window system.

  Next, a method for executing an electronic conference while transmitting and receiving data between the terminals 1000 to 1040 will be described. As a communication protocol for executing this electronic conference, for example, ITU-T recommendation T.264. Use 120 series. This protocol configuration is shown in FIG.

  The conference application 1200 is a set of applications for executing an application sharing function, a whiteboard function, a file transfer function, and the like. An ASCE (Application Sharing Conference Entity) 1210 is an entity for sharing an application among all the terminals participating in the conference. An operation conforming to 128 is executed. A SICE (Still Image Conferencing Entity) 1220 is an entity for transmitting and receiving bitmap data, handwritten drawing data, and the like. An operation conforming to 126 is executed. The SICE 1220 is mainly used for the whiteboard function.

  A BFTE (Binary File Transfer Entity) 1230 is an entity for performing file transfer. The operation | movement based on 127 is performed. A node controller 1240 and a GCC (Generic Conference Control) 1250 are conference control applications in which a terminal connected to the network executes a conference according to the control of the chairman and manages a list of terminal information such as capabilities and attributes of each terminal. ITU-T Recommendation T. The operation conforming to 124 is executed.

  An MCS (Multipoint Communication Service) 1260 executes a session layer protocol between a plurality of terminals, and is an ITU-T recommendation T.264. An operation conforming to 125 is executed. A TCP (Transmission Control Protocol) 1270 executes transport layer protocols such as retransmission control and flow control. An IP (Internet Protocol) 1280 executes a network layer protocol that controls transmission and reception of data packets. The wireless LAN driver 1290 operates as an interface between the IP 1280 and the wireless LAN controller 26.

  Communication operations of the MCS 1260, GCC 1250, and node controller 1240 will be described.

  The MCS 1260 is called an MCS provider, and a wireless network composed of terminals 1000 to 1040 as a network between MCS providers is called an MCS domain. In the network configuration of FIG. 17, when the terminal 1000 is the chairman terminal, the MCS domain has a hierarchical structure as shown in FIG. The MCS provider of the terminal 1000 serving as the chairperson is the top MCS provider, and is positioned higher than the MCS providers of other terminals. Each terminal attaches to the MCS domain after the MCS connection is established. By this attachment, each terminal acquires an MCS user ID that is a terminal identifier in the MCS domain.

  Each terminal then subscribes to the MCS channel. The MCS channel is an address in the MCS domain, and all terminals that have joined the same channel receive data sent to that channel. Here, when terminal 1010 transmits data to a channel to which all terminals have subscribed, this data is transferred to terminal 1000 which is the top MCS provider. Terminal 1000 transfers this data to terminals 1020 to 1040. In this way, data can be transmitted to all terminals by all terminals joining the same channel. The MCS user ID, which is a terminal identifier in the MCS domain, is also used as an MCS channel number, and is used as an MCS channel number when transmitting data to an individual destination.

  The GCC 1250 is called a GCC provider, and the GCC provider of a terminal that is a top MCS provider is called a top GCC provider. When each GCC provider participates in the conference, the terminal information (conference node list) such as a list of conference applications such as an application sharing function, a whiteboard function, a file transfer function, and an MCS user ID that is a terminal identifier in the MCS domain is obtained. Send to all other GCC providers. This broadcast transmission is realized by transmitting data to the MCS channel to which all terminals are subscribed.

  Such terminal information is received by each terminal and managed by the node controller 1240. The GCC also controls the assignment of chairmanship, etc., and the top GCC provider has the chairmanship at the start of the conference. The node controller 1240 issues various primitives to the GCC 1250 according to a request from the user, and manages an application list, a conference node list, and the like of its own terminal and all other terminals.

  Next, a method of sharing a document held by one terminal with all terminals connected to the wireless network will be described. This document sharing is described in ITU-T Recommendation T.30. 128 using an application sharing function according to 128. Now, a case will be described in which the terminal 1000 as the chairman terminal has a shared document and the terminals 1010 to 1040 share this document.

  The display data of the shared window (host window) on which the terminal 1000 displays the shared document is transmitted to all other terminals (terminal 1010 to terminal 1040) by the protocol between the ASCEs 1210, and the terminal 1010 to terminal 1040 transmits this data. Display in the shared window (shadow window) of your terminal.

  When the display data of the shared window (host window) is changed, the terminal 1000 transmits the display data of the changed portion to all other terminals. When text input or handwriting input is performed on the shared window (shadow window), the terminal 1010 to the terminal 1040 transmit key events and pointer events to the terminal 1000, and the terminal 1000 transmits these events to the shared window (host window). Process as an event for. That is, when text input or handwriting input is performed on a shared window (shadow window) of the terminals 1010 to 1040, the input data is transmitted to the terminal 1000, and the terminal 1000 shares the data with the data. Add to The terminal 1000 displays these characters and handwritten drawing lines on a shared window (host window), and transmits the updated display data to the terminals 1010 to 1040. Terminals 1010 to 1040 display the updated display data in a shared window (shadow window).

  As described above, since key data (keyboard input data) and pointer data (pen input coordinate data) input to the shared window (shadow window) of the terminals 1010 to 1040 are all transmitted to the terminal 1000, the shared document It is possible to edit a shared document even in a terminal that does not have the. Up to this point, the operation is performed using the conventional technique.

  Next, an application that manages a shared window and an individual window in each terminal will be described. An application that manages a shared window (hereinafter referred to as a shared Win application) and an application that manages individual windows (hereinafter referred to as an individual Win application) are X clients, and these are an X server and an X protocol that perform screen display, key input, and pointer input. To exchange data. The shared Win application is an application that executes an application sharing function. That is, the shared Win application also has an interface with the ASCE 1210. The individual Win application has an interface with the shared Win application and BFTE 1230, and exchanges event data with these. FIG. 21 shows the relationship among the individual Win application, shared Win application, X server, ASCE 1210, and BFTE 1230.

(Example 8)
The terminal 1000 serving as the chairman terminal has a shared document shared between all the terminals and a local document generated by copying this document (the data content is the same as the shared document). The shared document owned by the terminal 1000 is acquired by file transfer or the like. The shared document is displayed in the shared window of the terminal 1000, the copy file of the shared document is displayed in the individual window, and the shared document owned by the terminal 1000 is displayed in the shared window of the terminals 1010 to 1040. In the individual window, the same file as the shared document acquired by file transfer or the like is displayed.

  Now, the files to be displayed in the windows of all the terminals are opened, and the shared windows and individual windows of the terminals 1000 to 1040 are displayed from the top of the first page of the shared document and the file having the same data content. And Here, a case where text input in the individual window of the terminal 1010 is added to the shared document and this additional display of the text is performed on the shared window of the terminals 1000 to 1040 will be described.

  FIG. 22 shows a data flow between individual processes of the individual Win app, the shared Win app, the X server, the ASCE 1210, and the BFTE 1230 of the terminal 1000 and the terminal 1010. FIG. 23 is an operation flowchart of the individual Win application of the terminal 1010.

  Hereinafter, Example 8 will be described with reference to FIGS. When the electronic pen 1060 is used to move the cursor to a position where characters (text) are input with respect to the document displayed in the individual window of the terminal 1010, the X server of the terminal 1010 displays this point position data (coordinates). Data) to the individual Win application of the terminal 1010 (arrow a). The individual Win application receives this coordinate data as a pointer event (step 601), moves the cursor to the position of this coordinate data, and issues a drawing request to the X server of the terminal 1010 (arrow b, step 602). The event data is put into a queue (queue 101) (step 603). This queue is an array defined in the program.

  The X server of the terminal 1010 performs drawing in the individual window according to the received drawing request, and the cursor is displayed at the pointed position on the LCD 29 of the terminal 1010. Subsequently, when a character (text) is input in the individual window of the terminal 1010, the X server of the terminal 1010 passes this character code to the individual Win application of the terminal 1010 (arrow a). The individual Win application receives these character codes as key events (YES in step 604), adds these character codes to the document data, and issues a drawing request to the X server of the terminal 1010 (arrow b, step 605). The received event data is put in the queue (queue 101) (step 606). The X server of the terminal 1010 performs drawing in the individual window according to the received drawing request, and the input characters are displayed on the LCD 29 of the terminal 1010.

  Here, when the sentence end symbol is input by the user, the X server of the terminal 1010 passes this symbol code to the individual Win application of the terminal 1010 (arrow a). The individual Win application receives this symbol code as a key event, adds this symbol code to the document data, issues a drawing request to the X server of the terminal 1010 (arrow b), and queues the received event data (queue) 101) (steps 607 and 608). If it is determined that this symbol code is a sentence end symbol, the individual Win application sequentially passes the event data in the queue 101 to the shared Win application in the order of first-in / first-out (arrow c). Event data is transmitted to terminal 1000 and terminal 1020 to terminal 1040 via BFTE 1230 (arrows d and e, step 609).

  The shared Win application of the terminal 1010 passes these event data to the ASCE 1210 (arrow f), and the ASCE 1210 transmits these event data to the ASCE 1210 of the terminal 1000 (arrow g). These event data are included in the Input PDU (Input Protocol Data Unit) and transmitted between the ASCEs 1210. This Input PDU is transmitted in the MCS layer by including the MCS user ID, which is the terminal identifier of the terminal 1000, in the SDrq MCSPDU (MCS Protocol Data Unit) in which the MCS channel number is set.

  The ASCE 1210 of the terminal 1000 passes the received event data to the shared Win application (arrow h), and the shared Win application executes processing according to these event data and issues a drawing request to the X server of the terminal 1000 (arrow i). At the same time, a drawing update request for the shared window of the terminals 1010 to 1040 is issued to the ASCE 1210 (arrow j). The X server of the terminal 1000 executes the drawing process designated by the drawing request, and the document data displayed in the individual window of the terminal 1010 and the document data displayed in the shared window of the terminal 1000 at this time have the same contents. . When the ASCE 1210 of the terminal 1000 receives a drawing update request for the shared window of the terminal 1010 to the terminal 1040 from the shared Win app, the terminal 1010 to the terminal 1040 receives an update PDU (Update Protocol Data Unit) including bitmap data of the update area. (Arrow k). This Update PDU is transmitted in the MCS layer by including the MCS user ID, which is the terminal identifier of each destination terminal, in the SDrq MCSPDU set in the MCS channel number. The ASCE 1210 of the terminal 1010 passes the received bitmap data to the shared Win application (arrow m), and the shared Win application issues a drawing request for the bitmap data to the X server of the terminal 1010 (arrow n). Then, the X server of the terminal 1010 updates the display data of the shared window. Similarly, the ASCE 1210 of the terminal 1020 to the terminal 1040 passes the received bitmap data to the shared Win application, and the shared Win application issues a drawing request for the bitmap data to the X server of each terminal, and the X server of each terminal shares Update the display data of the window.

  When the terminal 1000 and the BFTE 1230 of the terminal 1020 to the terminal 1040 receive event data from the BFTE 1230 of the terminal 1010, the event data is passed to the individual Win application (arrow p), and the individual Win application executes processing according to the event data. Then, a drawing request is issued to the X server of each terminal (arrow q). The X servers of the terminal 1000 and the terminals 1020 to 1040 update the display data of the individual windows.

  Therefore, all the document data displayed in the shared window and the individual windows of the terminals 1000 to 1040 have the same contents.

  As described above, in the eighth embodiment, when text is input to the individual window of the terminal 1010 and the sentence end symbol is input, the text input up to that point including the sentence end symbol is displayed in the shared window of the terminals 1000 to 1040. Also displayed in the individual window of the terminal 1000 and the individual windows of the terminal 1020 to the terminal 1040.

Example 9
In the above-described eighth embodiment, when the individual Win application of the terminal 1010 receives the sentence end symbol from the X server, the event data (including the sentence end symbol) received so far is received via the shared Win application. To the shared Win app of the terminal 1000, and to the individual Win apps of the terminal 1000 and the terminal 1020 to the terminal 1040 via the BFTE 1230, and the document data displayed in the shared window and the individual window of the terminal 1000 to the terminal 1040 are all the same content. In the present embodiment, when the individual Win application receives a line feed code from the X server, the same operation as in the eighth embodiment is executed. In the ninth embodiment, the sentence end symbol in the eighth embodiment described with reference to FIGS. 22 and 23 is replaced with a line feed code.

  That is, the timing at which the individual Win application of the terminal 1010 transmits the event data stored in the queue 101 to the terminal 1000 and the terminals 1020 to 1040 is not when the sentence terminator is received from the X server but when the line feed code is received. is there. Therefore, the contents of the document displayed in the shared window and the individual window are different until the user inputs a line of characters (text) and a line break is made, but when the line break is made, it is displayed in these windows. The contents of the documents are the same.

  Even when the user inputs characters (text) for a plurality of lines, that is, when the individual Win application of the terminal 1010 receives a plurality of line feed codes, the operation can be executed in the same manner as in the above-described eighth embodiment. .

(Example 10)
Example 10 is an example when the user of each terminal performs handwriting input instead of text input. In the present embodiment, whether or not the user is performing a writing operation is determined from the duration of the state in which the electronic pen is up. FIG. 24 shows an operation flowchart of the individual Win application of the terminal 1010 in the handwriting input mode.

  With reference to FIGS. 22 and 24, Example 10 in the case of handwriting input will be described. When the touch panel controller 30 of the terminal 1010 detects that the electronic pen has touched the touch panel 31, the X server passes the contact coordinates to the individual Win application at predetermined time intervals for coordinate detection (arrow a). The individual Win application receives this coordinate data as a pointer event, and uses this coordinate data as cursor position data or free line drawing drawing position data (YES in step 701).

  Now, the individual Win application is in a mode (handwriting input mode) that uses the received coordinate data as drawing position data for free line drawing, and during one stroke (from pen down to pen up), the received coordinates are drawn with lines. The free line drawing function is executed. When the individual Win application enters the handwriting input mode, the time between pointer events received from the X server is measured (step 702). If this measurement time is within a predetermined time, the individual Win application issues a request to the X server to draw a line between the coordinates received now and the coordinates received earlier (arrow b) (step 703). The pointer event data is put into the queue 101 (step 704). This queue is an array defined in the program.

  When the measurement time between the pointer events exceeds a predetermined time, that is, when the timer started upon receiving the pointer event times out (YES in step 705), the individual Win application of the terminal 1010 enters the queue 101. Event data is sequentially passed to the shared Win application in the order of first-in first-out (arrow c), and the event data is transmitted to the terminal 1000 and the terminal 1020 to the terminal 1040 via the BFTE 1230 (arrows d and e). Step 706).

  The shared Win application of the terminal 1010 passes these event data to the ASCE 1210 (arrow f), and the ASCE 1210 transmits these event data to the ASCE 1210 of the terminal 1000 (arrow g). These event data are included in the Input PDU and transmitted between the ASCEs 1210. This Input PDU is transmitted in the MCS layer by including the MCS user ID, which is the terminal identifier of the terminal 1000, in the SDrq MCS PDU set in the MCS channel number.

  The ASCE 1210 of the terminal 1000 passes the received event data to the shared Win application (arrow h), and the shared Win application issues a request for drawing a line between coordinates from these event data (coordinate data) to the X server of the terminal 1000 ( Along with the arrow i), a drawing update request for the shared window of the terminals 1010 to 1040 is issued to the ASCE 1210 (arrow j).

  The X server of the terminal 1000 executes line drawing instructed by the drawing request, and at this time, the document data displayed in the individual window of the terminal 1010 and the document data displayed in the shared window of the terminal 1000 have the same contents. .

  When the ASCE 1210 of the terminal 1000 receives a drawing update request for the shared window of the terminal 1010 to the terminal 1040 from the shared Win application, the ASCE 1210 transmits an Update PDU including bitmap data of the update area to the terminal 1010 to the terminal 1040 (arrow k). ). This Update PDU is transmitted in the MCS layer by including the MCS user ID, which is the terminal identifier of each destination terminal, in the SDrq MCSPDU set in the MCS channel number.

  The ASCE 1210 of the terminal 1010 passes the received bitmap data to the shared Win application (arrow m), and the shared Win application issues a drawing request for the bitmap data to the X server of the terminal 1010 (arrow n). Then, the X server of the terminal 1010 updates the display data of the shared window. Similarly, the ASCE 1210 of the terminal 1020 to the terminal 1040 passes the received bitmap data to the shared Win application, and the shared Win application issues a drawing request for the bitmap data to the X server of each terminal, and the X server of each terminal shares Update the display data of the window.

  When the terminal 1000 and the BFTE 1230 of the terminal 1020 to the terminal 1040 receive the event data from the BFTE 1230 of the terminal 1010, the event data is passed to the individual Win application (arrow p), and the individual Win application uses the event data (coordinate data). A request to draw a line between coordinates with a line is sent to the X server (arrow q). The X servers of the terminal 1000 and the terminals 1020 to 1040 update the display data of the individual windows.

  As described above, the document data displayed in the shared window and the individual windows of the terminals 1000 to 1040 all have the same contents.

  As described above, when handwriting is input in the individual window of the terminal 1010, if a predetermined time elapses without starting the next stroke (not pen-down) from the end of the stroke (pen-up), the drawing that has been input until then. The line is also displayed in the shared window of the terminal 1000 to the terminal 1040, the individual window of the terminal 1000, and the individual window of the terminal 1020 to the terminal 1040.

(Example 11)
In the eleventh embodiment, a user performs handwriting input using an electronic pen in an individual window of each terminal, and a predetermined gesture operation is performed on the touch panel 31, whereby the handwritten drawing input so far is copied to the shared window. This is an example of the case.

  FIG. 25 is an operation flowchart of the individual Win application of the terminal 1010 according to the eleventh embodiment. When the individual Win application of the terminal 1010 operates in the handwriting input mode, the current time is obtained as a time stamp for each pointer event received from the X server. Then, the coordinate data is cyclically added to the coordinate array existing on the main memory 23 together with the time stamp (steps 801 to 803). Then, it is determined from the data in this coordinate array whether or not it matches a predetermined pattern for a copy command between windows (step 804). This determination method is the same as the method of the fourth embodiment described above.

  When a copy command between windows is detected from the data in this coordinate array (YES in step 805), the event data stored in the queue 101 satisfy the above conditions in the direction from the latest to the past. Are deleted (step 806). Then, the individual Win application sends a request for redrawing the background portion of the drawing line (overwriting the drawing line) to the X server in order to erase the drawing line corresponding to the deleted event data (step 807). Then, the data corresponding to the deleted event data is deleted from the coordinate data managed as the handwritten input data by the individual Win application (step 808).

  Since the X server overwrites the specified line drawing portion with the background data, the drawing line of the overwriting portion is deleted. (Once the movement of the pen tip for the gesture is drawn, the drawing is canceled when it is recognized as a gesture action.) Then, the individual Win application of the terminal 1010 firstly outputs the event data in the queue 101 first-in first-out. Are sequentially passed to the shared Win application, and these event data are transmitted to the terminal 1000 and the terminals 1020 to 1040 via the BFTE 1230 (step 809). Since the subsequent operation is the same as that of the tenth embodiment, the description thereof is omitted.

(Example 12)
In the twelfth embodiment, a user performs an editing operation using an electronic pen or a USB keyboard on a document displayed in an individual window of each terminal, and a predetermined button displayed on the LCD 29 is selected. This is an embodiment in which the editing process up to is executed for a document displayed in a shared window.

  FIG. 26 is an operation flowchart of the individual Win application of the terminal 1010 according to the twelfth embodiment. In the following, the twelfth embodiment will be described. On the display screen of the LCD 29, an edit synchronization button is displayed in an area other than a window such as a shared window or an individual window.

  The edit synchronization button is a button for causing the same editing process as that performed on the document displayed on the individual window to be performed on the document displayed on the shared window.

  When various editing operations such as character (text) input, handwriting input, sentence deletion, sentence copy, and the like are performed on the document displayed in the individual window of the terminal 1010, the X server of the terminal 1010 displays a key code (character / character). (Symbol code, line feed code, etc.) and point position data (coordinate data) are passed to the individual Win application. The individual Win application that has received the coordinate data puts the event data in the queue 101 (steps 901 and 902), performs processing according to the event data (step 903), and the display data on the screen needs to be changed. (YES in step 904), a drawing request is issued to the X server (step 905). The X server performs the instructed drawing.

  Here, when an edit synchronization button is selected by the user, a desktop application (not shown) that manages a screen area other than the window issues a request for instructing edit synchronization to the individual Win application. When the individual Win application receives this request (YES in Step 906), the event data in the queue 101 are sequentially passed to the shared Win application in the first-in first-out order, and these event data are passed through the BFTE 1230. To terminal 1000 and terminal 1020 to terminal 1040 (step 907). Subsequent operations are the same as those in the tenth embodiment.

  In the above-described eighth to twelfth embodiments, the case where the editing operation is performed on the terminal 1010 has been described, but the same applies to the case where the editing operation is performed on the terminal 1020 to the terminal 1040. Also, when an editing operation is performed on the terminal 1000, the same operation as described above is performed except that the shared Win app receives event data from the individual Win app of its own terminal instead of receiving event data from another terminal. It is.

In the above-described eighth to twelfth embodiments, an example in which a wireless LAN is used as a communication unit between the terminal 1000 to the terminal 1040 has been described. However, Bluetooth (registered trademark) or wired LAN (Ethernet) (registered trademark ) is used. Other communication means such as ) may be used. Further, although the example in which the terminals 1000 to 1040 are portable display pads has been described, the present invention is not limited to this, and a terminal capable of executing the above-described operation, such as a notebook PC, may be used.

It is a figure explaining the fundamental view of the present invention. 1 shows a configuration example of a server / client type electronic conference system according to the present invention. The hardware configuration of the portable display pad 20 is shown. The relationship between VNC protocol (RFB protocol) and X protocol is shown. An example of the screen buffer secured on the main memory of the server is shown. The internal process of the server 1 and the data flow between each process and the clients 3-6 are shown. A screen display example of each client is shown. 6 is an operation flowchart of the VNC server 2 according to the first embodiment. FIG. 9 is a flowchart continued from FIG. 8. FIG. 12 is an operation flowchart of the VNC server 2 according to the third embodiment. 12 is an operation flowchart of the VNC server 2 according to the fourth embodiment. FIG. 12 is a flowchart continued from FIG. 11. An example pattern for an inter-screen copy command is shown. 12 is an operation flowchart of the VNC server 2 according to the fifth embodiment. It is a figure explaining operation | movement of a shared screen mirroring mode. 18 is an operation flowchart of the VNC server 1 according to the seventh embodiment. 1 shows a configuration of an electronic conference system of the present invention in which a plurality of terminals constitute a network. 1 shows a hardware configuration of a portable display pad with a built-in hard disk. The protocol configuration of conference communication is shown. The hierarchical structure of a MCS domain when the terminal 1000 is a chairman terminal is shown. The relationship between an individual Win application, a shared Win application, an X server, an ASCE 1210, and a BFTE 1230 is shown. The flow of data between each process of the individual Win application, the shared Win application, the X server, the ASCE 1210, and the BFTE 1230 of the terminal 1000 and the terminal 1010 is shown. FIG. 20 is an operation flowchart of an individual Win application of the terminal 1010 according to the eighth embodiment. FIG. 25 is an operation flowchart of an individual Win application of the terminal 1010 according to the tenth embodiment. It is an operation | movement flowchart of the separate Win application of the terminal 1010 based on Example 11. FIG. 20 is an operation flowchart of an individual Win application of the terminal 1010 according to the twelfth embodiment.

Explanation of symbols

1 server 2 large display device 3-6 client 7-10 electronic pen

Claims (6)

An inter-terminal data communication type electronic conferencing system in which a chairman terminal and a plurality of non-chairman terminals equipped with a display are connected to a network, and transmit and receive data between the non-chairman terminals,
A shared window in which the display of the document and editing operations performed on the document can be shared on the display of all the non-chairperson terminals, and the same document as the document displayed in the shared window is displayed for each non-chairperson terminal. Individual windows that can be individually displayed or edited can be displayed simultaneously or alternately,
When an editing operation is performed on the individual window of one non-chairman terminal (hereinafter referred to as a first non-chairman terminal), the first non-chairman terminal performs an event of the editing operation at a predetermined timing. Transmitting data to the non-chairman terminal (hereinafter referred to as non-chairman terminal group) excluding the chairman terminal and the first non-chairman terminal;
Upon receiving the event data of the editing operation, the chairperson terminal executes processing according to the event data on the document data displayed in the shared window, and all the data including bitmap data of the update area for the shared window To the non-chairperson ’s terminal,
When all the non-chairperson terminals receive data including bitmap data of the update area from the chairperson terminal, the display data of the shared window is updated and displayed based on the received data at each terminal,
When receiving the event data of the editing operation, the non-chairperson terminal group updates and displays the display data of the individual window based on the received event data at each terminal.
Terminal between data communication electronic conference system, characterized in that. 2. The inter-terminal data communication type electronic conference according to claim 1, wherein the predetermined timing is a timing when a sentence end symbol is input to document data displayed in an individual window of the non-chairperson terminal. system. 2. The predetermined timing is a timing when text is input to document data displayed in an individual window of the non-chairperson terminal and one or a predetermined number of line feed codes are input. The terminal-to-terminal data communication type electronic conference system. The predetermined timing is a timing at which a predetermined time elapses without starting the next stroke from the end of the stroke when handwritten input is performed on the document data displayed in the individual window of the non-chairperson terminal. The inter-terminal data communication type electronic conference system according to claim 1 . The predetermined timing is a gesture for an inter-screen copy command in which handwriting input is performed with respect to the document data displayed in the individual window of the non-chairperson terminal using an electronic pen, and the movement of the electronic pen is determined in advance. The inter-terminal data communication type electronic conference system according to claim 1, wherein the timing is an operation timing . 2. The inter-terminal data communication type electronic conference system according to claim 1, wherein the predetermined timing is a timing when an editing operation is performed on an individual window of the non-chairperson terminal and a predetermined button is selected. .

Images