Screen sharing system, screen sharing method, display device, display control method, and program

Abstract

A screen sharing system, screen sharing method, display device, display control method, and program are provided to individually set user editing permissions for handwritten input data. [Solution] A screen sharing system 1 includes display devices 10A, 10B, and 10C located at each of multiple locations (location A and location B) and a communication management device, wherein a display device 10A used by user A and a display device 10B or display device 10C used by user B or user C share a handwriting input screen, wherein the display device 10A sets editing rights for user B or user C to the first handwriting input data entered by user A, and the display device 10B or display device 10C restricts editing of the first handwriting input data based on the editing rights set in the display device 10A.

Description

Technical Field

[0001] The present disclosure relates to a screen sharing system, a screen sharing method, a display device, a display control method, and a program.

Background Art

[0002] In meetings, etc. in companies, educational institutions, administrative organizations, etc., display devices that allow multiple users to perform handwritten input are used. Also, in remote meetings, etc. between different bases, a method is known in which while sharing the display screens displayed at each base, handwritten input is performed on the same screen from each base.

[0003] Also, a method of performing editing restrictions is known in order to prevent unintentional editing operations on the handwritten input content shared by multiple users. For example, Patent Document 1 discloses a method in which, in a system that shares data having a plurality of objects between a plurality of base terminals, the editing authority of an object is acquired by the base terminal that last selected the object. Also, Patent Document 2 discloses a method of prohibiting operations from other electronic blackboards on a stroke image specified by a group operation request for the purpose of preventing an operation different from the intention of the user from being performed.

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, the conventional method has a problem in that the editing authority of the user with respect to the handwritten input data input to the shared handwritten input screen cannot be set individually.

Means for Solving the Problems

[0005] To solve the above-mentioned problems, the invention according to claim 1 is a screen sharing system for sharing a handwriting input screen between a first display device used by a first user and a second display device used by a second user, wherein the first display device includes setting means for setting editing rights for the second user with respect to first handwriting input data entered by the first user, and the second display device includes editing restriction means for restricting editing of the first handwriting input data based on the editing rights set on the first display device. [Effects of the Invention]

[0006] According to the present invention, the ability to individually set user editing permissions for handwritten input data is achieved. [Brief explanation of the drawing]

[0007] [Figure 1] This figure shows an example of the overall configuration of a screen sharing system. [Figure 2] This is a diagram illustrating how to use an interactive whiteboard. [Figure 3] This diagram shows an example of the hardware configuration of an interactive whiteboard. [Figure 4] This diagram shows an example of a PC hardware configuration. [Figure 5] This figure shows an example of the hardware configuration of a communication management device. [Figure 6] This is a schematic diagram illustrating the relationship between a shared area shared by multiple display devices and the display screen shown on those devices. [Figure 7] This figure shows an example of data input using a virtual keyboard. [Figure 8] This diagram shows an example of the functional configuration of a screen sharing system. [Figure 9] This is a conceptual diagram showing an example of a user information management table. [Figure 10] This is a conceptual diagram showing an example of an event information management table. [Figure 11]This is a diagram showing an example of a metadata file. [Figure 12] There is a diagram showing an example of a handwritten input data file. [Figure 13] This is a conceptual diagram showing an example of an authority information management table. [Figure 14] This is a sequence diagram showing an example of screen display processing at the start of an event. [Figure 15] This is a diagram showing an example of a shared area. [Figure 16] This is a sequence diagram showing an example of authority setting processing for other users. [Figure 17] (A) is a diagram showing an example of a display screen, and (B) is a diagram showing an example of an authority setting screen. [Figure 18] This is a diagram showing an example of an authority setting screen. [Figure 19] This is a diagram showing another example of an authority setting screen. [Figure 20] This is a flowchart showing an example of the display processing of handwritten input data entered by other users. [Figure 21] (A) to (C) are diagrams showing examples of display screens displayed on each display device. [Figure 22] (A) is a diagram showing an example of a non - sharing notice, and (B) is a diagram showing an example of a viewing restriction notice. [Figure 23] This is a diagram showing another example of a non - sharing notice. [Figure 24] This is a diagram showing another example of a non - sharing notice. [Figure 25] This is a sequence diagram showing an example of viewing request processing for other users. [Figure 26] (A) is a diagram showing another example of a viewing restriction notice, and (B) is a diagram showing an example of a viewing request notice. [Figure 27] (A) is a diagram showing an example of a viewing permission notice, and (B) is a diagram showing an example of a viewing rejection notice. [Figure 28] This is a flowchart showing an example of the editing processing of handwritten input data entered by other users. [Figure 29]It is a diagram showing an example of an editing restriction notice. [Figure 30] It is a sequence diagram showing an example of a process for requesting editing authority from other users. [Figure 31] (A) is a diagram showing another example of an editing restriction notice, and (B) is a diagram showing an example of an editing authority request notice. [Figure 32] (A) is a diagram showing an example of an editing permission notice, and (B) is a diagram showing an example of a rejection notice for editing authority. [Figure 33] It is a flowchart showing an example of an editing restriction process for handwritten input data entered by other users. [Figure 34] It is a diagram showing another example of an editing restriction notice. [Figure 35] It is a diagram showing another example of an authority setting screen. [Figure 36] It is a diagram showing an example of a recommended authority change screen. [Figure 37] It is a diagram for explaining an example of an overlapping display of writing layers for each user. [Figure 38] It is a diagram showing an example of an editing operation selection screen. [Figure 39] It is a diagram showing another example of an editing operation selection screen. [Figure 40] It is a diagram for explaining an example of switching editing operations based on pen pressure. [Figure 41] It is a diagram showing an example of the functional configuration of a screen sharing system according to a second embodiment. [Figure 42] It is a flowchart showing an example of a browsing restriction process for handwritten input data entered by other users according to a second embodiment. [Figure 43] It is a sequence diagram showing an example of a browsing request process for other users according to a second embodiment. [Figure 44] It is a flowchart showing an example of an editing restriction process for handwritten input data entered by other users according to a second embodiment. [Figure 45] It is a sequence diagram showing an example of a process for requesting editing authority from other users according to a second embodiment. [Figure 46] This is a schematic diagram illustrating an example of the display state of a shared area in a display device according to a modified embodiment. [Figure 47] This figure provides a schematic explanation of an example of display screen information related to a modified embodiment. [Figure 48] This figure shows an example of a metadata file relating to a modified embodiment. [Figure 49] This figure shows an example of an object data file relating to a modified embodiment. [Figure 50] This is a conceptual diagram showing an example of a screen information management table related to a modified embodiment. [Modes for carrying out the invention]

[0008] The embodiments for carrying out the invention will be described below with reference to the drawings. In the description of the drawings, the same elements will be denoted by the same reference numeral, and redundant explanations will be omitted.

[0009] ●First Embodiment● ● System Configuration First, an overview of the configuration of the screen sharing system according to the first embodiment will be described using Figure 1. Figure 1 is a diagram showing an example of the overall configuration of the screen sharing system. The screen sharing system 1 shown in Figure 1 is a system that can share displayable data among multiple display devices 10.

[0010] As shown in Figure 1, the screen sharing system 1 includes display devices 10A1, 10B, and 10C located at each of multiple locations (location A and location B), and a communication management device 50A. The display devices 10A1, 10B, and 10C, and the communication management device 50A that constitute the screen sharing system 1 can communicate via a communication network 5. The communication network 5 is constructed using the Internet, a mobile communication network, a LAN (Local Area Network), etc. In addition to wired communication, the communication network 5 may also include wireless communication networks such as 3G (3rd Generation), 4G (4th Generation), 5G (5th Generation), Wi-Fi (Wireless Fidelity) (registered trademark), WiMAX (Worldwide Interoperability for Microwave Access), or LTE (Long Term Evolution).

[0011] Display devices 10A1, 10B, and 10C are computers equipped with handwriting input, communication, and display functions. Display device 10A1 is, for example, an electronic whiteboard installed at site A, display device 10B is a portable notebook PC (Personal Computer) at site B, and display device 10C is a portable tablet PC at site C. Display devices 10A1, 10B, and 10C communicate remotely while sharing handwritten input objects. Users A, B, and C can hold events such as remote meetings while viewing a display screen with shared content at each site. Note that events are not limited to remote meetings, but may include remote lessons, remote medical consultations, meetings, consultations, or even simple conversations.

[0012] Display devices 10A1, 10B, and 10C communicate with each other with screen data such as handwritten input data. The handwritten input data is the data necessary to display (reproduce) a display screen containing objects that users A, B, and C have handwritten on display devices 10A1, 10B, and 10C, respectively. The handwritten input data includes coordinate data, line width data, line color data, vector data, and data indicating the pen pressure when the stroke was drawn.

[0013] The display devices 10A1, 10B, and 10C transmit and receive handwritten input data for displaying shared objects, allowing users of the screen sharing system 1 to share the same object. The object is an image representing lines, etc., drawn by the user using an electronic pen or the like. The object is displayed by handwritten input data that indicates points that specify coordinates on the display.

[0014] The display device 10 is not limited to an electronic whiteboard or a PC; it can be any device on which a software application that performs handwriting input, communication, and display functions is installed. Furthermore, the PC may be, for example, a smartphone, a wearable device or smartwatch, a car navigation terminal, a game console, a telepresence robot, or a medical device.

[0015] Figure 1 shows an example of a system constructed with display devices 10 (10A1, 10B, 10C) located at three locations (location A, location B, and location C). However, the screen sharing system 1 may also have a configuration that includes multiple display devices 10 at a single location. Furthermore, the number of locations constituting the screen sharing system 1 may be two or four or more locations, each with a display device 10, or it may be just one location if multiple display devices 10 are located at a single location. Hereafter, the display devices 10A1, 10B, and 10C will be collectively referred to as "display device 10".

[0016] The communication management device 50A is a server computer that centrally manages login authentication from the display devices 10A1, 10B, and 10C, the communication status of the display devices 10A1, 10B, and 10C, and shared screen data. The communication management device 50A also relays shared screen data between the multiple display devices 10A1, 10B, and 10C.

[0017] The communication management device 50A may consist of a single server computer or multiple server computers. Furthermore, although the communication management device 50A is described as a server computer located in a cloud environment, it may also be a server operating on a display device 10 such as an electronic whiteboard, or a server located in an on-premises environment.

[0018] ○Image of how an electronic whiteboard is used○ Here, using Figure 2, we will explain the usage image of an electronic whiteboard, which is an example of the display device 10. Figure 2 is a diagram for explaining the usage image of the electronic whiteboard. The electronic whiteboard, which is an example of the display device 10, consists of legs 251 with multiple casters on the lower side, a support column 252 provided on the upper side of the legs 251, the main body 253 of the electronic whiteboard provided on the upper side of the support column 252, and a display 280 provided on the front of the main body 253. The main body 253 has a CPU 201, etc., which will be described later built in. The user can then input (draw) objects such as characters on the display 280 using an electronic pen 290. The display 280 is an example of a display unit.

[0019] ● Hardware configuration Next, the hardware configuration of the device or terminal constituting the screen sharing system according to the first embodiment will be described with reference to Figures 3 to 5. Note that the hardware configuration shown in Figures 3 to 5 may have components added or removed as needed.

[0020] ○Hardware configuration of the electronic whiteboard○ First, using Figure 3, we will explain the hardware configuration of an electronic whiteboard, which is an example of a display device 10. Figure 3 is a diagram showing an example of the hardware configuration of an electronic whiteboard. Each hardware component of the electronic whiteboard, which is an example of a display device 10, is indicated by a code in the 200s. As shown in Figure 3, the electronic whiteboard is equipped with a CPU (Central Processing Unit) 201, ROM (Read Only Memory) 202, RAM (Random Access Memory) 203, SSD (Solid State Drive) 204, network I / F (Interface) 205, and external device connection I / F 206.

[0021] Of these, CPU201 controls the operation of the entire interactive whiteboard. ROM202 stores programs used to drive CPU201, such as CPU201 and IPL (Initial Program Loader). RAM203 is used as the work area for CPU201. SSD204 stores various data, such as programs for the interactive whiteboard. Network I / F205 controls communication with communication network 5. External device connection I / F206 controls communication with external devices such as USB (Universal Serial Bus) memory 230, PC270, microphone 240, speaker 250, or camera 260.

[0022] The electronic whiteboard also includes a capture device 211, a GPU (Graphics Processing Unit) 212, a display controller 213, a contact sensor 214, a sensor controller 215, an electronic pen controller 216, a short-range communication circuit 219, an antenna 219a for the short-range communication circuit 219, a power switch 222, and selector switches 223.

[0023] Of these, the capture device 211 acquires image data displayed on the display 280, which is an example of a display unit, via the display controller 213, and stores it in RAM 203, etc. The GPU 212 is a semiconductor chip (processor) that specializes in graphics. The display controller 213 controls and manages the screen display in order to output the output image from the capture device 211 or GPU 212 to the display 280, etc. The contact sensor 214 detects when an electronic pen 290 or the user's hand H, etc., touches the display 280. The sensor controller 215 controls the processing of the contact sensor 214. The contact sensor 214 performs coordinate input and coordinate detection using an infrared blocking method. This method of coordinate input and coordinate detection involves two light-emitting and receiving devices installed at both upper ends of the display 280 emitting multiple infrared rays parallel to the display 280, and receiving the light that is reflected by reflective members provided around the display 280 and returns along the same optical path as the light emitted by the light-receiving element. The contact sensor 214 outputs the infrared ID emitted by two light-receiving devices that are blocked by an object to the sensor controller 215, which then identifies the coordinate position of the object's contact. The electronic pen controller 216 communicates with the electronic pen 290 to determine whether the pen tip or the pen's end has touched the display 280. The near-field communication circuit 219 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The power switch 222 is a switch for turning the electronic whiteboard's power ON / OFF. The selection switches 223 are a group of switches for adjusting, for example, the brightness and color of the display 280.

[0024] Furthermore, the electronic whiteboard is equipped with a bus line 210. The bus line 210 is an address bus, data bus, etc., for electrically connecting each component, such as the CPU 201 shown in Figure 3.

[0025] Furthermore, the contact sensor 214 is not limited to the infrared blocking method. Various detection means may be used, such as a capacitive touch panel that identifies the contact position by detecting changes in capacitance, a resistive touch panel that identifies the contact position by voltage changes between two opposing resistive films, or an electromagnetic induction touch panel that identifies the contact position by detecting electromagnetic induction caused by contact between an object and the display. In addition, the electronic pen controller 216 may be configured to determine whether or not there is touch not only at the tip and end of the electronic pen 290, but also at the part of the electronic pen 290 held by the user or other parts of the electronic pen.

[0026] ○PC Hardware Configuration○ Next, the hardware configuration of a PC, which is an example of the display device 10, will be described using Figure 4. Figure 4 is a diagram showing an example of the hardware configuration of a PC. Each hardware component of the PC, which is an example of the display device 10, is indicated by a code in the 300s. As shown in Figure 4, the PC is equipped with a CPU 301, ROM 302, RAM 303, HD (Hard Disk) 304, HDD (Hard Disk Drive) controller 305, display 306, external device connection I / F 307, network I / F 308, bus line 310, keyboard 311, pointing device 312, sound input / output I / F 313, microphone 314, speaker 315, camera 316, DVD-RW (Digital Versatile Disk Rewritable) drive 317, and media I / F 319.

[0027] The CPU 301 controls the operation of the entire PC. The CPU 301 is an arithmetic unit that realizes the various functions of the PC by reading programs or data stored in ROM 302 or HD 304, etc., onto RAM 303 and executing processing. ROM 302 is a non-volatile memory that stores programs used to drive the CPU 301, such as IPL. RAM 303 is a volatile memory used as the work area of ​​the CPU 301. HD 304 stores various data such as programs. The HDD controller 305 controls the reading or writing of various data to HD 304 according to the control of the CPU 301. The display 306 displays various information such as cursors, menus, windows, characters, or images. Note that the display 306 may be a touch panel display equipped with input means. Display 306 is an example of a display unit. The external device connection I / F 307 is an interface for connecting various external devices. In this case, external devices are, for example, USB memory or printers. The network I / F 308 is an interface for data communication using the communication network 5. Bus line 310 is an address bus or data bus, etc., for electrically connecting each component, such as the CPU 301 shown in Figure 4.

[0028] Furthermore, the keyboard 311 is a type of input means equipped with multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 312 is a type of input means for selecting or executing various instructions, selecting a processing target, or moving a cursor, etc. Note that the input means may not be limited to the keyboard 311 and the pointing device 312, but may also be a touch panel or an audio input device, etc. The audio input / output I / F 313 is a circuit that processes the input and output of audio signals between the microphone 314 and the speaker 315 according to the control of the CPU 301. The microphone 314 is a type of built-in sound collection means for inputting sound. The speaker 315 is a type of built-in output means for outputting audio signals. The camera 316 is a type of built-in imaging means for capturing images of a subject and obtaining image data. Note that the microphone 314, speaker 315, and camera 316 may be external devices instead of being built into the PC. The DVD-RW drive 317 controls the reading or writing of various data to the DVD-RW 318, which is an example of a removable recording medium. The removable recording medium is not limited to DVD-RW; it may also be DVD-R or Blu-ray® Disc, etc. The media I / F 319 controls the reading or writing (storage) of data to or from the recording medium 321, such as flash memory.

[0029] ○Hardware configuration of the communication management device○ Next, the hardware configuration of the communication management device will be described using Figure 5. Figure 5 is a diagram showing an example of the hardware configuration of the communication management device. Each hardware component of the communication management device 50A is indicated by a code in the 500s. The communication management device 50A is built by a computer and, as shown in Figure 5, includes a CPU 501, ROM 502, RAM 503, HD 504, HDD controller 505, display 506, external device connection I / F 508, network I / F 509, bus line 510, keyboard 511, pointing device 512, DVD-RW drive 514, and media I / F 516.

[0030] The CPU 501 controls the operation of the entire communication management device 50A. The CPU 501 is an arithmetic unit that realizes each function of the communication management device 50A by reading programs or data stored in the ROM 502 or HD 504, etc., onto the RAM 503 and executing processing. The ROM 502 is a non-volatile memory that stores programs used to drive the CPU 501, such as IPL. The RAM 503 is a volatile memory used as the work area of ​​the CPU 501. The HD 504 stores various data such as programs. The HDD controller 505 controls the reading or writing of various data to the HD 504 according to the control of the CPU 501. The display 506 displays various information such as cursors, menus, windows, characters, or images. The external device connection I / F 508 is an interface for connecting various external devices. In this case, external devices are, for example, USB memory. The network I / F 509 is an interface for data communication using the communication network 5. Bus line 510 is an address bus or data bus, etc., for electrically connecting each component, such as the CPU 501 shown in Figure 5.

[0031] The keyboard 511 is a type of input means equipped with multiple keys for inputting characters, numbers, and various instructions. The pointing device 512 is a type of input means for selecting or executing various instructions, selecting processing targets, or moving a cursor. The DVD-RW drive 514 controls the reading or writing of various data to the DVD-RW 513, which is an example of a removable recording medium. Note that the removable recording medium is not limited to DVD-RW, but may also be DVD-R or Blu-ray Disc, etc. The media interface 516 controls the reading or writing (storage) of data to the recording medium 515, such as flash memory.

[0032] The above programs may be distributed as installable or executable files recorded on a computer-readable recording medium. Examples of recording media include CD-R (Compact Disc Recordable), DVD (Digital Versatile Disk), Blu-ray Disc, SD card, and USB memory. The recording media can also be provided domestically or internationally as a program product. For example, the display device 10 implements the display control method according to the present invention when the program according to the present invention is executed.

[0033] ● Overview Next, using Figure 6, we will explain the relationship between the shared area shared among the display devices 10A1, 10B, and 10C, and the display screens shown on each of the display devices 10A1, 10B, and 10C. Figure 6 is a schematic diagram illustrating the relationship between the shared area shared by multiple display devices and the display screens shown on each device.

[0034] In Figure 6, the display devices 10A1, 10B, and 10C share objects drawn on their respective display units as a shared area to execute events such as remote meetings. The shared area is a handwriting input area that can be shared and used by multiple users for handwriting input. The shared area is also referred to as a whiteboard, shared canvas, handwriting input area, drawing area, or writing area. The shared area is shared in a state that can be displayed on the display screen by sending and receiving handwriting input data to each other for displaying objects drawn on the display devices 10A1, 10B, and 10C.

[0035] Furthermore, the shared area is an expandable area with no limitations on the area where handwriting input is possible. The shared area includes, for example, a so-called infinitely distant canvas or a finitely distant canvas. In other words, the shared area is a larger area than the area that can be displayed on the display screen of the display device 10. Therefore, as shown in Figure 6, the display devices 10A1, 10B, and 10C each display at least a portion of the shared area on their respective display screens. By displaying only a portion of the shared area rather than the entire area, the display devices 10A1, 10B, and 10C can make it easier for the user to perform handwriting input and to understand the content of the handwritten object. In addition, since the display devices 10A1, 10B, and 10C can each display different areas of the shared area, the user can be allowed to view a desired area during event execution.

[0036] When multiple users collaborate using a shared area, simultaneous writing to the same area can lead to overlapping content. If this happens unintentionally, it becomes necessary to move or delete one of the entries. However, if both entries can be manipulated, this process becomes cumbersome, reducing the efficiency of collaborative work. To prevent such unintentional editing in collaborative work with multiple users, users were restricted in their ability to use a large area for writing, or it was difficult to use other users' entries to make changes. Furthermore, the inability to individually set editing permissions for handwritten input data on the handwriting input screen, or the complicated method for setting editing restrictions, resulted in usability issues for users.

[0037] Therefore, the screen sharing system 1 can set permissions such as editing and viewing rights for other users regarding the handwritten input data (written content) entered by the user, and only users with the necessary permissions can perform editing or viewing operations. The screen sharing system 1 restricts editing or viewing operations on the entered handwritten input data for users who do not have the necessary permissions. In this way, the screen sharing system 1 can individually set user permissions for the entered handwritten input data. Furthermore, the screen sharing system 1 can prevent accidental editing while allowing users to widely use the handwritten input screen without worrying about other users' operations.

[0038] Furthermore, in the screen sharing system 1, data input may be performed using input means such as a keyboard in place of or in addition to handwritten input data. Figure 7 shows an example of data input using a virtual keyboard. First, a text editor application is launched on the display device 10A1 capable of displaying a shared area (handwritten input area) as shown in Figure 6. At this time, a predetermined text editor area 1111 is displayed on the display screen 100A of the display device 10A1. This text editor can be a commonly known one. In this state, a predetermined selection is accepted by operating the setting button 150 displayed on the display screen 100A, and a virtual keyboard 1121 as shown in Figure 7 is displayed at any position on the display screen 100A. Specifically, the CPU 201 shown in Figure 3 may control the GPU 212 and the display controller 213 to read a virtual keyboard template that has been stored in advance in a predetermined area of ​​the ROM 202 or SSD 204, and display it as a virtual keyboard 1121 in any area of ​​the display 280.

[0039] Next, when a user of the display device 10A1 inputs a desired word, string, number, sentence, etc. via the virtual keyboard 1121, the desired word, string, number, sentence, etc. may be entered onto the cursor in the text editor area 1111 in synchronization with the timing of the input. Alternatively, when a predetermined selection is accepted by operating the setting button 150 displayed on the display screen 100A, the system may be configured to launch a predetermined text editor area 1111 and display the virtual keyboard 1121 in parallel. The data input using the keyboard or other input means described above is not limited to site A using the display device 10A1, but may also be implemented at other sites C, for example, as shown in Figure 1.

[0040] Furthermore, if the display device 10B and the display device 10A1 shown in Figure 6 are connected by wire or wireless connection, the keyboard of the display device 10B may function as an input means for the text editor area 1111 instead of the virtual keyboard 1121 shown in Figure 7. Specifically, each key on the keyboard provided on the display device 10B may be synchronized with each key on the virtual keyboard 1121 displayed on the display device 10A1, so that desired words, strings, numbers, sentences, etc., entered on the display device 10B are entered onto the cursor in the text editor area 1111 displayed on the display device 10A1. By providing such a UI (User Interface), the user may be allowed to set predetermined editing permissions.

[0041] ●Functional Configuration Next, the functional configuration of the screen sharing system according to the first embodiment will be described using Figures 8 to 13. Figure 7 is a diagram showing an example of the functional configuration of the screen sharing system. Figure 8 shows the devices or terminals shown in Figure 1 that are related to the processing or operation described later.

[0042] ○Functional Configuration of Display Device○ First, the functional configurations of the display devices 10A1, 10B, and 10C will be explained using Figure 8. Since the functions of the display devices 10A1, 10B, and 10C are the same, they will be described here as the functions of the display device 10. The display device 10 includes a transmitting / receiving unit 11, a receiving unit 12, a display control unit 13, a judgment unit 14, a shared area generation unit 15, a screen data generation unit 16, a setting unit 17, an editing restriction unit 18, a non-shared notification unit 19, a viewing request notification unit 21, an editing permission request notification unit 22, a recommendation notification unit 23, a selection unit 24, a detection unit 25, an external device communication unit 26, and a storage / reading unit 29. Each of these units is a function or means realized by the operation of one of the components shown in Figure 3 or Figure 4 by instructions from the CPU 201 according to a program deployed from the SSD 204 onto the RAM 203, or by instructions from the CPU 301 according to a program deployed from the HD 304 onto the RAM 303. Furthermore, the display device 10 has a storage unit 1000 constructed from a ROM 202, SSD 204, or USB memory 230 shown in Figure 3, or a ROM 302, HD 304, or recording media 321 shown in Figure 4.

[0043] The transmitting / receiving unit 11 is mainly implemented by the processing of the CPU 201 for the network I / F 205, or the processing of the CPU 301 for the network I / F 308, and transmits and receives various data or information with other devices or terminals via the communication network 5.

[0044] The reception unit 12 is mainly implemented by the CPU 201 processing the contact sensor 214 and the electronic pen controller 216, or by the CPU 301 processing the pointing device 312 or the touch panel 309, and accepts various inputs from the user.

[0045] The display control unit 13 is primarily implemented by the processing performed by the CPU 201 or CPU 301 on the display controller 213, and displays images on the display 280 or display 306, and accesses the communication management device 50A using a web browser or the like to display various screen data. Specifically, the display control unit 13 starts and executes various applications that run on the OS (Operating System), and displays various screens drawn by the API (Application Programming Interface) provided by the OS on the display 280 or display 306.

[0046] The determination unit 14 is mainly implemented by the processing of CPU 201 or CPU 301 and performs various determinations. The shared area generation unit 15 is mainly implemented by the processing of CPU 201 or CPU 301 and generates a shared area that can be displayed in conjunction with other display devices 10.

[0047] The screen data generation unit 16 is mainly implemented by the processing of CPU 201 or CPU 301 and generates screen data that constitutes the shared area. The screen data generation unit 16 generates handwritten input data and object images based on handwritten input received by the reception unit 12. The screen data generation unit 16 also generates object images based on handwritten input data received by the transmission / reception unit 11. For example, the screen data generation unit 16 performs a process to convert objects obtained by handwritten input on the display by a user into coordinate data. For example, when a display device 10 at any location transmits coordinate data to a display device 10 at another location, the display device 10 at the other location displays an object with the same content on its own device's display based on the coordinate data. Furthermore, the screen data generation unit 16 generates metadata related to the display history of the display screen. Here, the metadata and handwritten input data generated by the screen data generation unit 16 are examples of history data that show the execution history of executed events.

[0048] The setting unit 17 is primarily implemented by the CPU 201 or CPU 301 and sets various permissions for other users of other display devices 10 regarding handwritten input data entered by a user of the display device 10. For example, the setting unit 17 sets editing permissions for other users regarding handwritten input data entered by a user of the display device 10. The setting unit 17 also sets viewing permissions for other users regarding handwritten input data entered by a user of the display device 10. Furthermore, the setting unit 17 sets editing permissions for a user of the display device 10 regarding handwritten input data entered by other users of other display devices 10.

[0049] The editing restriction unit 18 is mainly implemented by the processing of CPU 201 or CPU 301 and restricts editing of handwritten input data entered by other users who do not have editing privileges, based on the permission information set by the setting unit 17. In addition, if the editing restriction unit 18 does not have editing privileges for handwritten input data entered by another user, for example, it displays an editing restriction notification on the display screen indicating that the user does not have such editing privileges. Here, editing refers to selecting, inputting, adding, changing, deleting, enlarging, shrinking, or moving images, text, or handwritten input data displayed on the display screen of the display device 10, in accordance with input operations received by the reception unit 12.

[0050] The non-shared notification unit 19 is mainly implemented by processing by the CPU 201 or the CPU 301 on the display controller 213, and displays a non-shared notification on the display screen indicating that the handwritten input data entered by a user using the display device 10 is not shared with other users using other display devices 10.

[0051] The viewing request notification unit 21 is mainly implemented by processing by the CPU 201 or CPU 301 on the display controller 213, and displays a viewing request notification on the display screen indicating that a viewing request has been sent from another display device 10 for handwritten input data entered by a user of the display device 10.

[0052] The editing permission request notification unit 22 is mainly implemented by the CPU 201 or the CPU 301 processing the display controller 213, and displays an editing permission request notification on the display screen indicating that an editing permission request has been sent from another display device to the handwritten input data entered by a user using the display device 10.

[0053] The recommendation notification unit 23 is mainly implemented by the processing of the CPU 201 or the CPU 301 on the display controller 213. When an overlap occurs between handwritten input data entered by a user using the display device 10 and second handwritten input data entered by another user using another display device 10, it displays a permission change recommendation notification on the display screen, recommending a change in editing permissions.

[0054] The selection unit 24 is mainly implemented by the processing of CPU 201 or CPU 301, and selects the handwritten input data to be edited for each user who entered the handwritten input data.

[0055] The detection unit 25 is mainly implemented by the processing of CPU 201 or CPU 301 and detects the pen pressure applied to the display screen which serves as the handwriting input screen.

[0056] The external device communication unit 26 is implemented by processing by the CPU 201 for the external device connection I / F 206, or by processing by the CPU 301 for the external device connection I / F 307, and receives various data or information input from external devices connected to the display device 10.

[0057] The memory / read unit 29 is mainly implemented by the CPU 201 or CPU 301, and stores various data (or information) in the memory unit 1000 and reads various data (or information) from the memory unit 1000.

[0058] ○Functional Configuration of Communication Management Device○ Next, the functional configuration of the communication management device 50A will be described using Figure 7. The communication management device 50A includes a transmitting / receiving unit 51, an authentication unit 52, an event information generation unit 53, a shared area generation unit 54, an event information management unit 55, an authority information management unit 56, and a storage / reading unit 59. Each of these units is a function or means realized by the operation of any of the components shown in Figure 5 by instructions from the CPU 501 according to a communication management device program deployed from HD 504 onto RAM 503. The communication management device 50A also has a storage unit 5000 constructed from ROM 502, HD 504, or recording media 515 as shown in Figure 5.

[0059] The transmitting / receiving unit 51 is mainly implemented by the processing of the network interface 509 by the CPU 501, and transmits and receives various data or information with other devices or terminals via the communication network 5.

[0060] The authentication unit 52 is implemented by the CPU 501 and performs authentication processing for users participating in events using the display device 10.

[0061] The event information generation unit 53 is mainly implemented by the CPU 501 and generates event information related to events performed by the user.

[0062] The shared area generation unit 54 is mainly implemented by the processing of the CPU 501 and generates a shared area that can be shared and displayed among multiple display devices 10.

[0063] The event information management unit 55 is primarily implemented by the processing of the CPU 501 and manages the event information generated by the event information generation unit 53.

[0064] The authorization information management unit 56 is mainly implemented by the CPU 501 and manages authorization information that indicates the various permissions of other users to handwritten input data entered by a designated user.

[0065] The memory / read unit 59 is mainly implemented by the CPU 501, and stores various data (or information) in the memory unit 5000 and reads various data (or information) from the memory unit 5000.

[0066] ○User information management table Figure 9 is a conceptual diagram showing an example of a user information management table. The user information management table manages user information to identify users participating in an event. The storage unit 5000 has a user information management DB 5001 constructed, which is composed of the user information management table shown in Figure 9. This user information management table manages user information associated with a user ID to identify the user, a username and password, and an email address, which is an example of destination information indicating the user's destination.

[0067] ○Event Information Management Table Figure 10 is a conceptual diagram showing an example of an event information management table. The event information management table manages event information related to events performed by users. The storage unit 5000 has an event information management DB 5002 constructed, which is composed of the event information management table shown in Figure 10. This event information management table manages event information that associates the event ID and event name that identify the event, the date and time of the event, the participating users who will take part in the event, and the storage location of various event files generated by the event.

[0068] Of these, the event date and time indicates, for example, the date and time when the event file was last updated. Note that the event date and time may also be the date and time when the event was first held, or the start date and time and end date and time of the event may be stored separately. In addition, the participating users indicate the usernames of the users who participated in the event. Furthermore, the file storage location indicates the information of the storage location where the various event files are stored. Note that the file storage location may be an internal data path of the communication management device 50A, or it may be an external URL (Uniform Resource Locator) or URI (Uniform Resource Identifier), etc. Event files stored in the file storage location include, for example, a metadata file 500, a handwritten input data file 550, and shared area data of events generated by the shared area generation unit 54, etc.

[0069] ○ Metadata file Figure 11 shows an example of a metadata file. The metadata file 500 shown in Figure 11 is an event file generated during an executed event. The metadata file 500 shows the operation history of the display screen, such as moving, zooming in or out of the display area, as metadata for each user. The metadata file 500 shown in Figure 11 includes the event name (Name), the event's start time (Start) and end time (End), and the user's operation history (OperationLog). The operation history includes area information indicating the coordinate position (X,Y) and size (Width,Height) of the display area (ViewArea) for each user, as well as display history data indicating the display time (Time).

[0070] The example shown in Figure 11 indicates that an event named "Theme A Regular Meeting 1" was held on "2021 / 01 / 15 13:00~15:00". It also shows that participant "userA" initially displayed an area with a width of 100 pixels and a height of 80 pixels, with (X,Y)=(10,310) as the top-left point, for 100 seconds, and then moved to the area at (X,Y)=(100,210). The last area displayed by "userA" was the area at (X,Y)=(150,130). The last area displayed by "userB" was the area at (X,Y)=(105,1200), and the last area displayed by "userC" was the area at (X,Y)=(130,1300). Metadata file 500 stores this operation history for each user. Note that while Figure 10 shows an example of metadata file 500 in JSON (JavaScript Object Notation) format, the data format of metadata file 500 is not limited to this.

[0071] ○Handwritten input data file Figure 12 shows an example of a handwriting input data file. The handwriting input data file 550 shown in Figure 12 is an event file generated during an executed event. The handwriting input data file 550 shows the operation history of handwritten input objects such as strokes or stamps as object data. The handwriting input data file 550 shown in Figure 12 includes the background color of the shared area (BackgroundColor) and object data (Objects) that shows the input history of handwritten input objects. The object data includes the object type (Type), data details (Data) that show the contents of the object, the username of the user who entered the object (User), and the date and time of entry (Data). The object type is, for example, a stroke or a stamp. The data details also include, for example, if the object type is a stroke, data on the stroke's coordinate position (Point), line thickness (Thin), and line color (Color). Furthermore, if the object type is a stamp, the data details also include data on the stamp's coordinate position (Point), size (Size), and image file (Image).

[0072] In the example shown in Figure 12, a 5-pixel thick black stroke was entered by "userA" on "2021 / 01 / 15 13:32" from (X,Y)=(10,10) to (X,Y)=(30,30) in a shared area with a white background color (BackgroundColor). Subsequently, a 20-pixel x 20-pixel image file "Circle.jpg" was entered by "userB" on "2021 / 01 / 15 13:40" with (X,Y)=(100,200) as the top left corner. The handwriting input data file 550 stores such object data for each entered object. Note that while the handwriting input data file 550 shown in Figure 12 is an example of a JSON data format, the data format of the handwriting input data file 550 is not limited to this. Furthermore, the form of the object is not limited to strokes or stamps, but also includes text processed by OCR (Optical Character Reader) as letters or numbers or other symbols, system-generated characters such as dates or times, predetermined shapes such as triangles, stars or circles, or lines such as arrows, line segments or Bézier curves.

[0073] Furthermore, the metadata file 500 and the handwritten input data file 550 may be stored together with the communication management device 50A in the storage unit 1000 of the display device 10 participating in the event. In this case, the display device 10 stores in the storage unit 1000 history data, including metadata and handwritten input data that show the operation history of users using the display device 10. In addition, if the display device 10 has server functionality, it may be configured to store in the storage unit 1000 metadata and handwritten input data, including the operation history of all users participating in the event.

[0074] ○ Authority Information Management Table Figure 13 is a conceptual diagram showing an example of an authorization information management table. The authorization information management table manages authorization information that indicates the various permissions other users have over handwritten input data entered by a given user. The storage unit 5000 has an authorization information management DB 5003 constructed, which is composed of the authorization information management table shown in Figure 13. This authorization information management table manages authorization information associated with each event ID that identifies an event, including the user ID and username that identify the user who entered the handwritten input data, as well as various permissions such as editing permission and viewing permission for the handwritten input data. The authorization information managed in the authorization information management DB 5003 is shared as common authorization information among the display devices 10 used by users participating in the event, and is stored in the storage unit 1000 of the display device 10 during the execution of the event.

[0075] Figure 13 shows a configuration where, for example, no user has editing privileges (null) for handwritten input data entered by "userA," and only "userB" has viewing privileges. Also, Figure 13 shows a configuration where, for example, only "userC" has editing and viewing privileges for handwritten input data entered by "userB." Furthermore, Figure 12 shows a configuration where, for example, no user has editing or viewing privileges (null) for handwritten input data entered by "userC."

[0076] ●Processing or operation of the embodiment ○Processing at the start of the event○ Next, the processing or operation of the screen sharing system according to the first embodiment will be described using Figures 14 to 40. In the following description, the processing will be described using the display device 10A1 used by user A and the display device 10B used by user B, but the same processing will be performed for the display device 10C used by user C, as shown in Figure 1. First, the display screen that is shown on the display device 10 at the start of an event will be described using Figures 14 and 15. Figure 14 is a sequence diagram showing an example of the screen display processing at the start of an event.

[0077] First, when user A operates a predetermined input means on the display device 10A1, the receiving unit 12A of the display device 10A1 accepts the input of a user ID and password (step S11). Next, the transmitting / receiving unit 11A transmits login request information to the communication management device 50A (step S12). This login request information includes the user ID and password received in step S11. As a result, the transmitting / receiving unit 51 of the communication management device 50A receives the login request information transmitted by the display device 10A1.

[0078] Next, the authentication unit 52 of the communication management device 50A performs user authentication using the user ID and password received in step S12 (step S13). Specifically, the storage / reading unit 59 searches the user information management DB 5001 (see Figure 9) for a user ID and password pair corresponding to the user ID and password pair received in step S12. If a corresponding pair is found, the authentication unit 52 determines that the requesting user A is a legitimate user. If no corresponding pair is found, the authentication unit 52 determines that the requesting user A is an illegitimate (unauthorized) user. If the user is not legitimate, the transmitting / receiving unit 51 notifies the display device 10A1 that the user is not legitimate, but here we will continue the explanation for the case where the user is legitimate.

[0079] Next, the shared area generation unit 54 generates a new shared area, which is a handwriting input area that can be shared and displayed among multiple display devices (step S14). Next, the event information management unit 55 generates event information related to the event to be started (step S15). Here, the generated event information includes an event ID that identifies the event, an event name, the start time of the event, and information indicating the storage location of the event file generated by the event. The event information management unit 55 stores the generated event information in the event information management DB 5002 (see Figure 10) via the storage and reading unit 59.

[0080] Furthermore, the authorization information management unit 56 generates authorization information indicating each user's editing and viewing permissions for the handwritten input data entered during the event (step S16). For example, at the start of the event, the authorization information is set so that all users have editing and viewing permissions for other users' handwritten input data. The authorization information management unit 56 stores the generated authorization information in the authorization information management DB 5003 (see Figure 13) via the storage and reading unit 59.

[0081] Next, the transmitting / receiving unit 51 transmits the shared area data generated in step S14, the event information generated in step S15, and the authorization information generated in step S16 to the display device 10A1 (step S17). As a result, the transmitting / receiving unit 11A of the display device 10A1 receives the shared area data, event information, and authorization information transmitted by the communication management device 50A.

[0082] Then, the display control unit 13A of the display device 10A1 displays the shared area 700, which is composed of the shared area data received in step S17, on the display unit (for example, display 280 or display 306) (step S18). Figure 15 is a diagram showing an example of a shared area. The shared area 700 shown in Figure 15 is a handwriting input screen that is shared and displayed with other display devices 10 during an event. The shared area 700 is a state in which multiple objects have been input by users participating in the event by performing handwriting input on the display screen. Since the shared area 700 is larger than the display area of ​​the display screen of the display device 10, at least a portion of the shared area 700 is displayed as the display area on the display screen of the display device 10. Users participating in the event display a desired area of ​​the shared area 700 during the event to perform handwriting input and viewing of objects.

[0083] Furthermore, similar to the processing by the display device 10A1, when user B operates a predetermined input means of the display device 10B, the receiving unit 12B of the display device 10B accepts user information, including the user ID and password (step S19). Next, the transmitting / receiving unit 11B transmits login request information to the communication management device 50A (step S20). This login request information includes the user ID and password received in step S19. As a result, the transmitting / receiving unit 51 of the communication management device 50A receives the login request information transmitted by the display device 10A1.

[0084] Next, the authentication unit 52 of the communication management device 50A performs user authentication using the user ID and password received in step S20, similar to the process in step S13 (step S21). Next, if the authentication of user B by the authentication unit 52 is completed, the event information management unit 55 reads the event information generated in step S15 from the event information management DB 5002 via the storage / reading unit 59 (step S22). Also, the authorization information management unit 56 reads the authorization information generated in step S16 from the authorization information management DB 5003 via the storage / reading unit 59 (step S23).

[0085] Next, the transmitting / receiving unit 51 transmits the shared area data generated in step S14, the event information read in step S22, and the authorization information read in step S23 to the display device 10B (step S24). As a result, the transmitting / receiving unit 11B of the display device 10B receives the shared area data, event information, and authorization information transmitted by the communication management device 50A. Then, the display control unit 13B of the display device 10B displays the shared area 700, which is composed of the received shared area data, on the display unit, similar to the processing of the display device 10A1 in step S17 (step S25).

[0086] In this way, the screen sharing system 1 can share and display a shared area 700 that constitutes a handwriting input screen among multiple display devices 10 participating in an event.

[0087] ○Permission setting process○ Next, using Figures 16 to 19, we will explain the process of setting editing or viewing permissions for other users to handwritten input data entered by a user. Figure 16 is a sequence diagram showing an example of the permission setting process for other users.

[0088] First, the reception unit 12A of the display device 10A1 accepts the selection of the setting button 150 displayed on the display screen 100A shown on the display unit (step S51). Figure 17(A) is a diagram showing an example of the display screen. The display screen 100A shown in Figure 17(A) is a screen displayed on the display unit of the display device 10A1, and displays at least a portion of the shared area 700 shown in Figure 15. The display screen 100A also includes a setting button 150 that is pressed when setting permissions. The reception unit 12A accepts the selection of the setting button 150 by, for example, an input operation by user A on the display screen 100A.

[0089] Next, if the selection of the setting button 150 in step S51 is accepted, the display control unit 13A displays the permission setting screen 400 on the display screen 100A (step S52). Figure 17(B) is a diagram showing an example of the permission setting screen. The display screen 100A shown in Figure 17(B) displays the permission setting screen 400, which allows user A to set editing or viewing permissions for other users to handwritten input data. The permission setting screen 400 includes an editing permission setting button 410 to set editing permissions for other users to handwritten input data entered by user A, and a user information input area 415 for entering users who will not be restricted from editing the handwritten input data entered by user A. The permission setting screen 400 also includes a viewing permission setting button 430 to set viewing permissions for other users to view the handwritten input data entered by user A, and a user information input area 435 for entering users who will not be restricted from viewing the handwritten input data entered by user A.

[0090] In the example in Figure 17(B), users other than User B are restricted from editing the handwritten input data entered by User A. Also in the example in Figure 17(B), there are no restrictions on viewing the handwritten input data entered by User A, and all users can view the handwritten input data entered by User A. Users who are set to not restrict editing or viewing can edit or view User A's handwritten input data (written content). On the other hand, users who are set to restrict editing or viewing cannot edit or view User A's handwritten input data (written content). User A can set their own writing permissions by performing input operations on the permission settings screen 400.

[0091] Furthermore, as shown in Figure 18, the user information input area 415 of the permission setting screen 400 is set with a user or user group selected by user A from among candidates for user groups composed of other users or multiple users, which are searched from the list of event participants. If a user group is set, all users belonging to that user group are included. Note that users or user groups may also be set in the user information input area 415 by searching by direct input into the user information input area 415. The same applies to the user information input area 435. Also, although Figures 17(B) and 18 illustrate an example of entering users who are not restricted in the user information input area 415 or user information input area 435 when editing or viewing is restricted, the configuration may also be such that users who are restricted are entered when editing or viewing is permitted.

[0092] Next, when user A performs a predetermined input operation on the permission setting screen 400, the setting unit 17A sets the permissions for other users to the handwritten input data entered by user A (step S53). The permission settings changed by the setting unit 17A are stored in the storage unit 1000A as permission information for the event being executed. Then, the setting unit 17A generates setting change data related to the permissions changed in step S53 (step S54). The setting change data is generated, for example, in JSON format, in the format {"authority":[{"userA":[{"edit":[null],"view":["userB","userC"]}]}]}. Specifically, the setting unit 17A specifies the user who will make the setting change in ""userA"", and specifies the users who will be restricted from viewing and editing in ""edit"" and ""view"", respectively.

[0093] Then, the transmitting / receiving unit 11A transmits the configuration change data generated in step S54 to the communication management device 50A (step S55). This configuration change data includes an event ID that identifies the event currently in progress, and authorization information indicating the authorization set in step S53. As a result, the transmitting / receiving unit 51 of the communication management device 50A receives the configuration change data transmitted by the display device 10A1.

[0094] Next, the authorization information management unit 56 of the communication management device 50A searches the authorization information management DB 5003 (see Figure 13) using the event ID included in the configuration change data received in step S55 as a search key, and updates the authorization information associated with the same event ID as the received event ID (step S56). The transmitting / receiving unit 51 also transmits (transmits) the configuration change data received in step S55 to the display device 10B (step S57). As a result, the transmitting / receiving unit 11B of the display device 10B receives the configuration change data transmitted by the display device 10A1.

[0095] The setting unit 17B of the display device 10B changes the permission settings based on the permission information contained in the setting change data received in step 57 (step S58). The permission settings changed by the setting unit 17B are stored in the storage unit 1000B as permission information for the event being executed.

[0096] Thus, the screen sharing system 1 can set various permissions for other users using the permission setting screen 400, allowing only specific users to view or edit handwritten input data (written content). Furthermore, the screen sharing system 1 can share permission information set on the display device 10 with other display devices 10 using the setting change data, so that permission settings for handwritten input data in an event can be shared among users participating in the event. In addition, the screen sharing system 1 can set permissions using the permission setting screen 400 displayed on the display screen 100, improving user operability in permission settings. As mentioned above, the screen sharing system 1 can share permission information set on the display device 10 with other display devices 10 via the communication management device 50A. Thus, a configuration in which another device such as the communication management device 50A acts as an intermediary between each display device is also possible.

[0097] Furthermore, the display device 10A1 can set viewing and editing permissions for other users regarding the handwritten input data entered by user A, thereby preventing other users from seeing the writing and modification process, and preventing other users from editing user A's own writing. User A can, for example, remove the restrictions once the work is completed, allowing other users to view and edit the data, thus flexibly switching the content of the handwritten input data shared with other users.

[0098] Here, we will use Figure 19 to illustrate another example of the permission settings screen 400a. Figure 19 illustrates another example of the permission settings screen. The permission settings screen 400a shown in Figure 19 is a screen that allows users to set permissions for handwritten input data entered by user A on a per-user basis. The permission settings screen 400a includes an editing permission setting area 410a for setting editing permissions for other users to the handwritten input data entered by user A, and a viewing permission setting area 430a for setting viewing permissions for other users to the handwritten input data entered by user A. The editing permission setting area 410a also includes a batch setting button 420 for setting editing permissions for all users at once, and individual setting buttons 421 and 422 for setting editing permissions for each user. Furthermore, the viewing permission setting area 430a includes a batch setting button 440 for setting viewing permissions for all users at once, and individual setting buttons 441 and 442 for setting viewing permissions for each user. In the example in Figure 19, all users are restricted from editing user A's handwritten input data, while only user B is restricted from viewing user A's handwritten input data. Note that, similar to the permission setting screen 400, the permission setting screen 400a is displayed on the display screen 100A when user A presses the setting button 150 on the display screen 100A shown in Figure 17(A).

[0099] If there is a main user, such as the event administrator or owner, among the multiple users participating in an event, the permission settings screens 400 and 400a may be configured so that only the main user can view them, and the main user can set various permissions. In this case, for example, in an event such as a class in which the main user (a teacher) and multiple other users (students) are participating, the teacher can restrict students from viewing and editing each other's work. That is, while editing and viewing are restricted, the content written by students will not be shared with other students, and only the teacher will be able to see it. This allows the main user (the teacher) to, for example, lift the viewing restriction to allow students to share and review each other's work, while keeping editing restricted to prevent other students from making unintentional edits.

[0100] ○Display of handwritten input data○ Next, using Figures 20 to 27, we will explain the process of displaying handwritten input data entered by other users on the display screen according to each user's viewing permissions. Figure 20 is a flowchart showing an example of the process for displaying handwritten input data entered by other users. Figure 20 explains the process when user C receives handwritten input data entered on display device 10A1 used by user A on display device 10C used by user C, but the combination of display devices 10 that send and receive handwritten input data is not limited to this, and similar processing is performed in other combinations of display devices 10 used by users participating in the event.

[0101] First, the transmitting / receiving unit 11C of the display device 10C receives the handwritten input data transmitted by the display device 10A1 (step S71). This handwritten input data is the handwritten input data entered by user A. As shown in Figure 21(A), the display screen 100A of the display device 10A1 displays the handwritten input data entered by user A.

[0102] Next, the determination unit 14C determines whether or not it has permission to view the handwritten input data received in step S71 (step S72). Specifically, the determination unit 14C refers to the permission information set by the setting unit 17C and determines whether or not it has permission to view the received handwritten input data for user A who entered it. If the determination unit 14C determines that it has permission to view the received handwritten input data (YES in step S72), it moves the process to step S73. Then, the display control unit 13C displays the received handwritten input data on the display screen 100C (step S73).

[0103] On the other hand, if the determination unit 14C determines that there is no permission to view the received handwritten input data (NO in step S72), it proceeds to step S74. The display control unit 13C then restricts viewing of the received handwritten input data by not displaying it on the display screen 100C (step S74). The display control unit 13C also displays a viewing restriction notification on the display screen 100C indicating that viewing of the handwritten input data entered by user A is restricted (step S75).

[0104] Figure 21(B) shows the display screen 100B of the display device 10B as an example of a case where user A has permission to view the handwritten input data. The display screen 100B shown in Figure 21(B) displays the same handwritten input data as the display screen 100A shown in Figure 21(A), because user B has permission to view user A's handwritten input data. In addition, the display screen 100B displays a user display image 170 to identify the user who entered the displayed handwritten input data, along with the handwritten input data.

[0105] Figure 21(C) shows the display screen 100C of the display device 10C as an example of a case where user C does not have permission to view the handwritten input data entered by user A. In the display screen 100C shown in Figure 21(C), the handwritten input data shown on the display screen 100A in Figure 21(A) is not displayed because user C does not have permission to view user A's handwritten input data. As a result, user C's ability to view the handwritten input data entered by user A is restricted.

[0106] In this way, when the display device 10 receives handwritten input data entered on another display device 10, it checks whether it has permission to view the received handwritten input data, and only displays the handwritten input data on the display screen if it has permission to view it. This allows the screen sharing system 1 to prevent users without viewing permission from seeing its own handwritten content. Furthermore, if the display device 10 does not have permission to view the received handwritten input data, it displays a viewing restriction notification on the display screen, as described below.

[0107] Here, using Figures 22 to 24, we will explain the various notifications that appear on the display screen when access to certain handwritten input data is restricted. Figure 22(A) is an example of a non-sharing notification, and Figure 22(B) is an example of an access restriction notification.

[0108] The display screen 100A shown in Figure 22(A) is a display screen displayed on the display device 10A1 as an example of restricting other users (other display devices) from viewing the entered handwritten input data. The display screen 100A shown in Figure 22(A) includes a non-sharing notification 350 indicating that the handwritten input data entered by user A has not been shared with other users. The non-sharing notification unit 19A of the display device 10A1 displays the non-sharing notification 350 on the display screen 100A if any of the other users participating in the event do not have permission to view the entered handwritten input data.

[0109] The display screen 100C shown in Figure 22(B) is an example of a display screen shown on the display device 10C when viewing of handwritten input data entered by user A is restricted. The display screen 100C shown in Figure 22(B) includes a viewing restriction notification 450 indicating that viewing of the handwritten input data entered by user A is restricted. This viewing restriction notification 450 is displayed on the display screen 100C of the display device 10C, for example, during the processing in step S75.

[0110] If a user does not have viewing privileges and therefore cannot share the content written by other users, the user who entered the content (e.g., User A) will not know whether the content has been shared, and the restricted user (e.g., User C) will not know what other users are working on. Therefore, screen sharing system 1 displays a notification on the screen of the user who has restricted viewing (e.g., screen 100A) informing them that the handwritten input data (content written) has not been shared with other users, and displays a notification on the screen of the user whose viewing is restricted (e.g., screen 100C) informing them that another user is entering (writing) handwritten input data. In this way, screen sharing system 1 can share the status of operations occurring in an event with each user, even when viewing restrictions are in place between users.

[0111] Figures 23 and 24 show another example of a non-shared notification displayed on the display screen 100A. The non-shared notification 360 displayed on the display screen 100A shown in Figure 23 includes an permission edit button 365 that is pressed when editing the permissions of other users for user A's handwritten input data. The non-shared notification unit 19A of the display device 10A1 displays the non-shared notification 360 on the display screen 100A if any of the other users participating in the event do not have permission to view the entered handwritten input data. When user A presses the permission edit button 365, the display control unit 13A of the display device 10A1 displays the permission setting screen 400, for example, shown in Figure 18. This allows the display device 10A1 to allow user A to change the permissions of other users.

[0112] The non-sharing notification 370 shown on the display screen 100A in Figure 24 includes a viewing permission button 375 that is pressed to allow other users whose viewing is restricted to view the data. The non-sharing notification unit 19A of the display device 10A1 displays the non-sharing notification 370 on the display screen 100A if any of the other users participating in the event do not have permission to view the entered handwritten input data. When user A presses the viewing permission button 375, the setting unit 17A of the display device 10A1 changes the viewing permissions to allow other users whose viewing of user A's handwritten input data is restricted to view it. In the case of the non-sharing notification 370 shown in Figure 24, compared to the non-sharing notification 360 shown in Figure 23, viewing permissions can be changed directly from the non-sharing notification 370 without performing permission setting processing using the permission setting screen 400, thus simplifying the process for user A.

[0113] ○ Processing of viewing requests Next, we will explain the process for requesting access to restricted handwritten input data using Figures 25 and 26. Figure 25 is a sequence diagram showing an example of the process for requesting access to another user. In Figure 25, we explain an example in which a request for access to user A's handwritten input data is made from display device 10C used by user C, whose access to user A's handwritten input data is restricted, to display device 10A1 used by user A. However, the combination of display devices 10 that send and receive the access request is not limited to this, and similar processing is performed in other combinations of display devices 10 used by users participating in the event.

[0114] The display control unit 13C of the display device 10C causes the viewing restriction notification 480 to be displayed on the display screen 100C (step S91). Figure 26(A) shows an example of the viewing restriction notification 480. The viewing restriction notification 480 shown in Figure 26(A) includes a viewing request button 485 that is pressed when requesting to view restricted handwritten input data.

[0115] Next, the reception unit 12C accepts the selection of the viewing request button 485 included in the viewing restriction notification 480 in response to the input operation of user C (step S92). The transmitting / receiving unit 11C transmits viewing request information to the communication management device 50A indicating that it requests viewing of restricted user A's handwritten input data (step S93). This viewing request information includes the user ID of the user to whom the viewing request is being made. In this case, the transmitting / receiving unit 11C transmits viewing request information including user A's user ID. As a result, the transmitting / receiving unit 51 of the communication management device 50A receives the viewing request information transmitted by the display device 10C. The transmitting / receiving unit 51 of the communication management device 50A then transmits (forwards) the viewing request information transmitted by the display device 10C to the display device 10A1 used by user A, who is the recipient of the viewing request (step S94). As a result, the transmitting / receiving unit 11A of the display device 10A1 receives the viewing request information transmitted by the requesting display device 10C.

[0116] Then, if the viewing request notification unit 21A of the display device 10A1 receives viewing request information in step S94, it displays a viewing request notification 380 on the display screen 100A indicating that a viewing request has been made by user C (step S95).

[0117] Next, the reception unit 12A of the display device 10A1 accepts various button operations (step S96). Figure 26(B) shows an example of a viewing request notification 380. The viewing request notification 380 shown in Figure 26(B) includes an individual viewing permission button 381 pressed to allow viewing by user C, the requester, an individual viewing rejection button 382, ​​and a batch viewing permission button 383 pressed to allow viewing by all users. When user A presses the individual viewing permission button 381 or the batch viewing permission button 383, the setting unit 17A of the display device 10A1 changes the viewing permissions so that the user corresponding to the selected button is allowed to view user A's handwritten input data. The display device 10A1 may also be configured to display permission setting screens 400, 400a when user A presses the individual viewing permission button 381 or the batch viewing permission button 383.

[0118] On the other hand, when user A presses the individual viewing rejection button 382, ​​the setting unit 17A of the display device 10A1 rejects user A's access to the handwritten input data for the user corresponding to the selected button, thereby maintaining the access permission status. In this case, the reason or condition for user A pressing the individual viewing rejection button 382 may be, for example, that user A, based on their own judgment considering the handwritten input content, rejects the viewing request made by another user (e.g., user C) who made the viewing request. Furthermore, user A, based on their own judgment, may reject the viewing request made by another user who made the viewing request, considering the attributes of the other user who sent the viewing request (e.g., department, assigned duties, position, etc.) and the content of the handwritten strokes. Furthermore, in addition to or instead of user A's judgment, the judgment unit 14A of the display device 10A1 may make the rejection of the above viewing request based on the attributes of the other user who sent the viewing request (e.g., department, assigned duties, position, etc.) and the content of the handwritten strokes. Depending on the result of that judgment, the editing authority unit 18A may reject viewing requests from other users who have made viewing requests. Based on the individual viewing rejection information generated by the individual viewing rejection button 382 pressed according to these judgment criteria, the setting unit 17A of the display device 10A1 rejects the viewing of user A's handwritten input data for the user corresponding to the selected button and maintains the viewing permission status. Note that if the individual viewing rejection button 382 is pressed, a transition to the permission setting screen 400, 400a does not need to occur.

[0119] Returning to Figure 25, the transmitting / receiving unit 11A of the display device 10A1 transmits browsing response information to the communication management device 50A as a response to the browsing request information received in step S94 (step S97). As a result, the transmitting / receiving unit 51 of the communication management device 50A receives the browsing response information transmitted by the display device 10A1. Then, the transmitting / receiving unit 51 transmits the browsing response information received in step S97 to the display device 10C (step S98). As a result, the transmitting / receiving unit 11C of the display device 10C receives the browsing response information transmitted by the communication management device 50A. Subsequently, the display control unit 13C of the display device 10C displays the result of the browsing request (step S99). As a result, the display device 10C can notify user C of the result of the browsing request.

[0120] Figure 27(A) shows an example of a viewing permission notification. The viewing permission notification 481 shown in Figure 27(A) includes a confirmation button 486 that is pressed to confirm that the requesting user C has been granted permission to view the content. Figure 27(B) shows an example of a viewing rejection notification. The viewing rejection notification 482 shown in Figure 27(B) includes a confirmation button 486 that is pressed to confirm that the requesting user C has been denied permission to view the content.

[0121] ○Editing handwritten input data○ Next, using Figures 28 to 32, we will explain the process of editing handwritten input data entered by other users on the display screen according to each user's viewing permissions. Figure 28 is a flowchart showing an example of the process of editing handwritten input data entered by other users. Figure 28 explains the process when user B edits handwritten input data entered on display device 10A1 used by user A on display device 10B used by user B, but the combination of display devices 10 is not limited to this, and the same process is performed in other combinations of display devices 10 used by users participating in the event.

[0122] First, the receiving unit 12B of the display device 10B accepts an editing operation for the handwritten input data displayed on the display screen 100B in response to a predetermined input operation by user B to the display screen 100B (step S101).

[0123] Next, the determination unit 14B determines whether or not it has editing authority over the handwritten input data that is the target of the editing operation received in step S101 (step S102). Specifically, the determination unit 14B refers to the authority information set by the setting unit 17B and determines whether or not it has editing authority over user A who entered the handwritten input data to be edited. If the determination unit 14B determines that it has editing authority over the handwritten input data to be edited (YES in step S102), it moves the process to step S103. Then, the display control unit 13B executes the editing operation on the handwritten input data and displays the edited handwritten input data on the display screen 100B (step S103).

[0124] On the other hand, if the determination unit 14B determines that there is no editing authority for the handwritten input data to be edited (NO in step S102), it moves the process to step S104. Then, the editing restriction unit 18B restricts editing of the handwritten input data to be edited (step S104). The editing restriction unit 18B also displays an editing restriction notification on the display screen 100B indicating that editing of the handwritten input data entered by user A is restricted (step S105).

[0125] Thus, when the display device 10 receives an editing operation on the displayed handwritten input data, it checks whether the user has editing privileges for the target handwritten input data, and only executes the editing operation if the user has editing privileges. This allows the screen sharing system 1 to prevent unintentional editing of handwritten input data by restricting editing of the handwritten input data (written content) to users without editing privileges. Furthermore, if the display device 10 does not have editing privileges for the received handwritten input data, it displays an editing restriction notification on the display screen, as described below.

[0126] Figure 29 shows an example of an editing restriction notification. The display screen 100B shown in Figure 29 is a display screen shown on the display device 10B as an example of a case where editing of handwritten input data entered by user A is restricted. The display screen 100B shown in Figure 29 includes user display images 170a and 170b that identify the user who entered the handwritten input data, and an editing tool 190 used when editing the handwritten input data. The editing tool 190 is, for example, an erase tool used when erasing handwritten input data. The display screen 100B shown in Figure 29 also includes an editing restriction notification 650 that indicates that editing of the handwritten input data entered by user A is restricted. In the example in Figure 29, the editing restriction notification 650 is displayed on the display screen 100C of the display device 10B, for example, when user B tries to erase the handwritten input data entered by user A using the editing tool 190. This allows the display device 10B to let user B know why they cannot edit by displaying the editing restriction notification 650 when they do not have editing privileges.

[0127] ○ Processing of editing permission requests Next, we will explain the process for requesting editing permission for handwritten input data that has editing restrictions, using Figures 30 to 32. Figure 30 is a sequence diagram showing an example of the editing permission request process for another user. Figure 30 illustrates an example in which a request for editing permission is made from display device 10B, used by user B, whose editing of user A's handwritten input data is restricted, to display device 10A1, used by user A. However, the combination of display devices 10 that send and receive the editing permission request is not limited to this, and similar processing is performed in other combinations of display devices 10 used by users participating in the event.

[0128] The editing restriction unit 18B of the display device 10B displays an editing restriction notification 660 on the display screen 100B (step S111). Figure 31(A) shows an example of the editing restriction notification 660. The editing restriction notification 660 shown in Figure 31(A) includes an editing permission request button 665 that is pressed when requesting editing permission for handwritten input data that has been restricted for editing.

[0129] Next, the reception unit 12B accepts the selection of the editing permission request button 665 included in the editing restriction notification 660 in response to the input operation of user B (step S112). The transmitting / receiving unit 11B sends editing permission request information to the communication management device 50A indicating that it is requesting editing permission for the restricted handwritten input data of user A (step S113). This editing permission request information includes the user ID of the user to whom the editing permission request is being made. In this case, the transmitting / receiving unit 11B sends editing permission request information including the user ID of user A. As a result, the transmitting / receiving unit 51 of the communication management device 50A receives the editing permission request information sent by the display device 10B. The transmitting / receiving unit 51 of the communication management device 50A then transmits (forwards) the editing permission request information sent by the display device 10B to the display device 10A1 used by user A, who is the recipient of the viewing request (step S114). As a result, the transmitting / receiving unit 11A of the display device 10A1 receives the editing permission request information sent by the requesting display device 10B.

[0130] Then, if the editing permission request notification unit 22A of the display device 10A1 receives editing permission request information in step S114, it displays an editing permission request notification 560 on the display screen 100A indicating that an editing permission request has been made by user B (step S115).

[0131] Next, the reception unit 12A of the display device 10A1 accepts various button operations (step S116). Figure 31(B) shows an example of an editing permission request notification 560. The editing permission request notification 560 shown in Figure 31(B) includes an individual editing permission button 561 pressed to allow editing by the requesting user B, an individual editing rejection button 562, and a batch editing permission button 563 pressed to allow editing by all users. When user A presses the individual editing permission button 561 or the batch editing permission button 563, the setting unit 17A of the display device 10A1 changes the editing permission so that the user corresponding to the selected button is allowed to edit user A's handwritten input data. The display device 10A1 may also be configured to display permission setting screens 400, 400a when user A presses the individual editing permission button 561 or the batch editing permission button 563.

[0132] On the other hand, when user A presses the individual edit rejection button 562, the setting unit 17A of the display device 10A1 rejects the editing of user A's handwritten input data for the user corresponding to the selected button, thereby maintaining the state of editing privileges. In this case, the reason or condition for user A pressing the individual edit rejection button 562 may be, for example, that user A, based on their own judgment considering the handwritten input content, rejects the editing privilege request from another user (e.g., user B) who requested editing privileges. Furthermore, user A may, based on their own judgment, reject the editing privilege request from another user who requested editing privileges, considering the attributes of the other user who sent the editing privilege request (e.g., department, assigned duties, position, etc.) and the content of the handwritten strokes. Furthermore, in addition to or instead of user A's judgment, the judgment unit 14A of the display device 10A1 may make the rejection of the above editing privilege request based on the attributes of the other user who sent the editing privilege request (e.g., department, assigned duties, position, etc.) and the content of the handwritten strokes. Depending on the result of that judgment, the editing authority unit 18A may reject editing authority requests from other users who have requested editing authority. Based on the individual editing rejection information generated by the individual editing rejection button 562 pressed according to these judgment criteria, the setting unit 17A of the display device 10A1 rejects the editing of user A's handwritten input data for the user corresponding to the selected button and maintains the editing authority status. Note that if the individual viewing rejection button 382 is pressed, the transition to the authority setting screens 400 and 400a does not need to occur.

[0133] Returning to Figure 30, the transmitting / receiving unit 11A of the display device 10A1 transmits edit permission response information to the communication management device 50A as a response to the edit permission request information received in step S114 (step S117). As a result, the transmitting / receiving unit 51 of the communication management device 50A receives the edit permission response information transmitted by the display device 10A1. Then, the transmitting / receiving unit 51 transmits the edit permission response information received in step S117 to the display device 10B (step S118). As a result, the transmitting / receiving unit 11B of the display device 10B receives the edit permission response information transmitted by the communication management device 50A. Subsequently, the display control unit 13B of the display device 10B displays the result of the edit permission request (step S119). As a result, the display device 10B can notify user B of the result of the edit permission request.

[0134] Figure 32(A) shows an example of an editing permission grant notification. The editing permission grant notification 661 shown in Figure 32(A) includes a confirmation button 668 that is pressed when the user B, the requester, confirms that editing permission has been granted. Figure 32(B) shows an example of an editing permission rejection notification. The editing permission rejection notification 662 shown in Figure 32(B) includes a confirmation button 668 that is pressed when the user B, the requester, confirms that their viewing permission has been rejected.

[0135] ○Restrictions on editing other users' handwritten input data○ Next, Figures 33 to 37 will be used to explain the process of setting editing permissions for handwritten input data entered by other users. Figure 33 is a flowchart showing an example of the editing process for handwritten input data entered by another user. Figure 33 explains the process of setting editing permissions for handwritten input data entered by another user (for example, user B) on the display device 10A1 used by user A, but the same process is performed on other display devices 10 used by users participating in the event.

[0136] First, the receiving unit 12A of the display device 10A1 accepts an editing operation for the handwritten input data displayed on the display screen 100A in response to a predetermined input operation on the display screen 100A by user A (step S151).

[0137] Next, the determination unit 14A determines whether or not editing of the handwritten content of the handwritten input data that was received in step S151 is restricted (step S152). If the determination unit 14A determines that editing of the handwritten content of the handwritten input data to be edited is restricted (YES in step S152), it moves the process to step S153. The display device 10A1 then displays a predetermined notification on the display screen 100A (step S153). On the other hand, if the determination unit 14A determines that editing of the handwritten content of the handwritten input data to be edited is not restricted (NO in step S152), it moves the process to step S154. The display control unit 13A then executes the editing operation on the handwritten input data and displays the edited handwritten input data on the display screen 100A (step S154).

[0138] Here, using Figures 34 to 36, a predetermined notification displayed on the display screen 100A in step S153 will be explained in detail. Figure 34 is a diagram showing an example of an editing restriction notification 830 displayed in step S153. The display screen 100A shown in Figure 34 is a display screen displayed on the display device 10A1 as an example of a case where user A does not have editing rights over user B's handwritten input data that is the target of an editing operation performed by user A. The display screen 100A shown in Figure 34 includes user display images 170a and 170b that identify the user who entered the handwritten input data, and displays the handwritten input data entered by user A and user B. In the display screen 100A shown in Figure 34, if user A uses the editing tool 190 to perform an editing operation to erase the handwritten input data entered by user B, the editing restriction unit 18A displays an editing restriction notification 830 on the display screen 100A indicating that editing of the handwritten data entered by user B is restricted. This editing restriction notification 830 includes a permission edit button 835 that is pressed when editing the permissions for user B's handwritten input data.

[0139] When user A presses the permission editing button 835, the display control unit 13A of the display device 10A1 displays, for example, the permission setting screen 800 shown in Figure 35. This allows the display device 10A1 to change the permissions for handwritten input data entered by other users. Alternatively, the display device 10A1 may be configured to directly remove editing restrictions when user A presses the permission editing button 835. In this case, the setting unit 17A changes the editing permissions for the user who entered the relevant handwritten input data so that user A is allowed to edit it.

[0140] This allows the display device 10A1 to display an editing restriction notification 830 when the user does not have editing privileges, thereby allowing user A to understand, for example, the user's attributes described above (e.g., department, assigned duties, job title, etc.) and the content of handwritten strokes as reasons why editing is not possible. At the same time, it allows the user to change their editing privileges for handwritten input data entered by other users.

[0141] Figure 35 shows an example of a permission setting screen. The permission setting screen 800 shown in Figure 35 includes, in addition to the contents of the permission setting screen 400 shown in Figure 17, an edit permission setting button 810 for setting editing permissions for other users' handwritten input data (written content), and a user information input area 815 for entering users whose editing is not restricted by user A. In the example in Figure 35, user A is restricted from editing handwritten input data entered by users other than user C. The setting unit 17A changes user A's editing permissions for other users' writings based on user A's input operation on the permission setting screen 800.

[0142] In this way, the screen sharing system 1 can use the permission setting screen 800 to set not only various permissions for other users regarding its own writing, but also its own editing permissions for other users' writing. This prevents the screen sharing system 1 from unintentionally editing the content written by other users. The permission setting screen 800 may also be a screen that allows each user to set their own editing permissions for other users' handwritten input data, similar to the permission setting screen 400a shown in Figure 19. Furthermore, the permission setting screen 800 may be configured to be displayed on the display screen 100A when user A presses the setting button 150 on the display screen 100A shown in Figure 17(A), as described above.

[0143] Figure 36 shows an example of the permission change recommendation notification 850 displayed in step S153. The display screen 100A shown in Figure 36 is the display screen that is displayed on the display device 10A1 when an editing operation performed by user A overlaps with handwritten input data of another user. When an overlap between user A's editing operation and user B's handwritten input data is detected, the recommendation notification unit 23A displays a permission change recommendation notification 850 on the display screen 100A, recommending that user A change their permissions.

[0144] One method for detecting overlap between user A's editing operations and user B's handwritten input data is to define a path (trajectory) between the points (coordinate positions) that make up an object each time a coordinate position (Point) of an object included in the handwritten input data file is added. If an intersection of the defined path is detected, the overlap of the handwritten input data is detected. Alternatively, if the object is a stamp or similar rather than a stroke, the overlap of the handwritten input data can be detected by checking whether a sequence of points has been added within the area of ​​the object, which is identified by the stamp's coordinate position (Point) and size (Size).

[0145] This permission change recommendation notification 850 includes an edit restriction button 855 that is pressed when user A wants to restrict user A's editing of handwritten input data entered by another user that has been detected to overlap. When user A presses the edit restriction button 855, the setting unit 17A changes the editing permissions so that user A's editing of handwritten input data entered by another user that has been detected to overlap is restricted. The display device 10A1 may also be configured to display the permission setting screen 800 when user A presses the edit restriction button 855. This allows the display device 10A1 to display the permission change recommendation notification 850 when an overlap with another user's handwritten input data is detected, enabling user A to input (write) a new object without affecting other users' writing.

[0146] Furthermore, if it is desired to distinguish between user-specific writing, as shown in Figure 36, the display screen 100A may be constructed by distinguishing the writing layers that allow handwritten input for each user, as shown in Figure 37, and superimposing each writing layer. In the example of Figure 37, the display screen 100A is shown with User A's writing layer, which includes User A's writing, and other users' writing layers, which include other users' writing, superimposed. In this case, the display device 10A1 applies the user-specific permission information set by the setting unit 17A to each user's writing layer. The editing restriction unit 18 restricts editing of the writing layers of users whose editing is restricted for users who do not have editing privileges.

[0147] Thus, the screen sharing system 1 can set various permissions for other users regarding the handwritten input data entered by the user, as well as editing permissions for handwritten input data entered by other users, thereby preventing unintentional editing of other users' writings.

[0148] ○Examples of editing operations○ Next, we will explain examples of editing operations applied to handwritten input data using Figures 38 to 40. First, we will explain an example where the editing target can be selected using an editing tool, using Figures 38 and 39. Figures 38 and 39 are diagrams showing examples of editing operation selection screens.

[0149] The display screen 100 shown in Figure 38 includes an editing operation selection screen 900 for selecting handwritten input data to be erased. The editing operation selection screen 900 is displayed when the user selects an editing tool 190a displayed on the display screen 100. The editing tool 190a is, for example, a selection tool used to select handwritten input data to be erased. The editing operation selection screen 900 includes a selection area 901, which is selected when performing an erase operation on all entered handwritten input data; a selection area 903, which is selected when performing an erase operation on only the handwritten input data entered by the user; and a selection area 905, which is selected when performing an erase operation on only the handwritten input data entered by other users. The selection unit 24 of the display device 10 switches, for example, from a writing mode to a mode for erasing written content when the user selects one of the selection areas 901, 903, or 905, and selects the handwritten input data to be erased based on the selected condition. For example, if you select selection area 901, you can select all handwritten input data to be erased. If you select selection area 903, you can select only the handwritten input data you entered to be erased. If you select selection area 905, you can select only the handwritten input data entered by other users to be erased.

[0150] The display screen 100 shown in Figure 39 includes an editing operation selection screen 910 for selecting handwritten input data to be selected in bulk. The editing operation selection screen 910 is displayed when the user selects an editing tool 195 displayed on the display screen 100. The editing tool 195 is a selection tool used, for example, to select handwritten input data to be edited. The editing operation selection screen 910 includes a selection area 911, which is selected when performing a selection operation on all entered handwritten input data; a selection area 913, which is selected when performing a selection operation on only the handwritten input data entered by the user; and a selection area 915, which is selected when performing a selection operation on only the handwritten input data entered by other users. The selection unit 24 of the display device 10 switches, for example, from a writing mode to a mode for selecting writing content when the user selects one of the selection areas 911, 913, or 915, and selects the handwritten input data to be selected based on the selected conditions. For example, if you select selection area 911, you can select all handwritten input data as the selection target. If you select selection area 913, you can select only the handwritten input data that you have entered. Also, if you select selection area 915, you can select only the handwritten input data that other users have entered as the selection target.

[0151] Thus, when the display device 10 performs editing operations such as erasing or selecting handwritten input data entered on the display screen 100, it can use the desired editing tools 190a and 195 to switch the handwritten input data to be edited for each user who entered the handwritten input data.

[0152] Next, Figure 40 will be used to explain the process of switching editing operations according to the pen pressure applied to the display screen 100. Figure 40 is a diagram illustrating an example of switching editing operations based on pen pressure. When a user attempts to erase handwritten input data entered on the display screen 100, if the pen pressure applied to the display screen 100 is weak, only the user's own handwritten input data will be erased. If the pen pressure applied to the display screen 100 is strong, all handwritten input data, including that of other users, will be erased.

[0153] Figure 40(A) shows the editing operation when the display screen 100 is touched with light pressure. The detection unit 25 of the display device 10 detects the pressure applied by the user to the display screen 100. As shown in the left diagram of Figure 40(A), if the pressure detected by the detection unit 25 is light, the display screen 100 displays a small editing area 180a. Then, by performing an operation using the editing tool 190, only the user's own handwritten input data is erased. On the other hand, Figure 40(B) shows the editing operation when the display screen 100 is touched with strong pressure. As shown in the left diagram of Figure 40(B), if the pressure detected by the detection unit 25 is strong, the display screen 100 displays a large editing area 180b. Then, by performing an operation using the editing tool 190, all handwritten input data, including the handwritten input data of other users, is erased. Furthermore, the size of the above editing areas 180a and 180b may be varied in proportion to the pen pressure (for example, the length of the radius).

[0154] If the detected pen pressure is weak, the display device 10 displays a small erase circle, such as in editing area 180a, and erases only the user's handwritten input data. On the other hand, if the detected pen pressure is strong, the display device 10 displays a large erase circle, such as in editing area 180b, and erases all handwritten input data. Here, pen pressure is detected, for example, by using a device that supports pen pressure input and acquiring the pen pressure as a numerical input between "0" and "1". When the input is first acquired, the detection unit 25 processes it as weak pen pressure, and switches to strong pen pressure when the pen pressure exceeds "0.6". The detection unit 25 switches to weak pen pressure when the pen pressure falls below "0.4". Note that when detecting pen pressure, the display device 10 may set a pen pressure detection threshold (such as "0.6" or "0.4" in the above example) for each user performing handwritten input. This is because the pen pressure used when handwriting differs from user to user. In this way, by setting a pressure sensitivity threshold for each user, it becomes possible to perform editing operations on handwritten input data according to the pressure each user intends. Therefore, it becomes possible to avoid situations such as unintentional deletion of handwritten input data or being unable to delete handwritten input data even when trying to do so.

[0155] As a result, the display device 10 can switch the handwritten input data to be edited according to the pen pressure entered on the display screen 100, which is the handwritten input screen. Note that the editing operation is not limited to erasing the handwritten input data, but may also include other editing content such as selecting handwritten input data. Furthermore, the display device 10 may be configured to switch the handwritten input data to be edited according to other operation content such as the contact time with the display screen 100, in addition to pen pressure.

[0156] ● Main effects of the first embodiment As described above, according to this embodiment, the screen sharing system 1 can set editing permissions for other users regarding handwritten input data entered by a user, and can allow only users with editing permissions to perform editing operations. Furthermore, the screen sharing system 1 can set viewing permissions for other users regarding handwritten input data entered by a user, and can allow only users with viewing permissions to view the handwritten input data. As a result, the screen sharing system 1 can set permissions for handwritten input data entered by each user, preventing unintentional editing and allowing users to widely use the handwritten input screen without worrying about other users' operations.

[0157] Furthermore, the screen sharing system 1 can enable users to set permissions for handwritten input data by displaying permission setting screens 400, 400a, and 800 on the display device 10, which allow for user-specific permission settings. This improves the user experience when setting permissions for the screen sharing system 1.

[0158] In the above embodiment, the process of restricting viewing and editing of handwritten input data on the display device 10 was described, but the viewing and editing restriction process for handwritten input data may also be performed by the communication management device 50A. In this case, the communication management device 50A restricts viewing and editing of handwritten input data to be displayed on the display device 10 used by each user, based on the user's authority information stored in the authority information management DB 5003.

[0159] ●Second Embodiment● Next, a second embodiment will be described. In the second embodiment, the communication management device 50B determines whether to grant or deny the viewing request and editing permission request made by the user. The overall configuration of the screen sharing system according to the second embodiment is the same as the overall configuration of the screen sharing system according to the first embodiment, so the description of each device constituting the system will be omitted. Similarly, the hardware configuration is the same as the hardware configuration of the devices or terminals constituting the screen sharing system according to the first embodiment, so the description of the hardware resources of each device or terminal will be omitted.

[0160] ●Functional Configuration Next, the functional configuration of the screen sharing system according to the second embodiment will be described. Figure 41 is a diagram showing an example of the functional configuration of the screen sharing system according to the second embodiment. Note that Figure 41 shows the following functions from the functional configuration shown in Figure 8 swapped between the display device 10A2 and the communication management device 50B. That is, the judgment unit 14A, setting unit 17A, and editing restriction unit 18A that were in the display device 10A1 have been replaced by the judgment unit 57, setting unit 58, and editing restriction unit 60 in the communication management device 50B, respectively. Note that the functional configuration of each function in the display device 10A2 and the communication management device 50B, including the swapped functions, is the same as that described in the first embodiment, except for the judgment unit 57, setting unit 58, and editing restriction unit 60, so a detailed explanation will be omitted.

[0161] The determination unit 57 is mainly implemented by the CPU 501 and performs various decisions in the communication management device 50B. The setting unit 58 is mainly implemented by the CPU 501 and sets various permissions for other users using other display devices 10 to handwritten input data entered by a user using the display device 10. For example, the setting unit 58 sets the viewing permission for other users to handwritten input data entered by a user using the display device 10. The setting unit 58 also sets the editing permission for other users to handwritten input data entered by a user using the display device 10. Furthermore, the setting unit 58 sets the editing permission for a user using the display device 10 to handwritten input data entered by another user using another display device 10.

[0162] The editing restriction unit 60 is mainly implemented by the CPU 501 and restricts editing of handwritten input data entered by other users who do not have editing privileges, based on the permission information set by the setting unit 17 of the display device 10. In addition, if the editing restriction unit 60 does not have editing privileges for handwritten input data entered by another user, for example, it edits an editing restriction notice to be displayed on the display screen of the display device 10 indicating that the user does not have such editing privileges.Here, editing refers to controlling operations such as selection, input, addition, modification, deletion, enlargement, reduction, or movement of images, text, or handwritten input data displayed on the display screen of the display device 10, in accordance with input operations received by the receiving unit 12 of the display device 10.

[0163] Furthermore, the screen sharing system 1 may have functions of both the display device 10A1 (display device 10) shown in the first embodiment (see Figure 8) and the communication management device 50B shown in the second embodiment (see Figure 41). That is, for the judgment unit, setting unit, and editing restriction unit in the screen sharing system 1, a functional configuration may be constructed in which each of the judgment unit 14A and judgment unit 57, setting unit 17A and setting unit 58, and editing restriction unit 18A and editing restriction unit 60 is assigned to perform each function. Moreover, not limited to the judgment unit, setting unit, and editing restriction unit, a functional configuration may be constructed in which each of the other functions is assigned to perform each function between the display device 10A2 (display device 10) and the communication management device 50B.

[0164] ●Processing or operation of the embodiment Next, the processing or operation of the screen sharing system according to the second embodiment will be described using Figures 42 to 45. Note that the processing at the start of an event and the permission setting process described in the first embodiment are the same, so the explanation of each process will be omitted.

[0165] ○Request to display handwritten input data○ First, using Figure 42, we will explain the process of displaying handwritten input data entered by other users on other display devices according to each user's viewing permissions. Figure 42 is a flowchart of an example of the viewing restriction process for handwritten input data entered by other users according to the second embodiment. In Figure 42, we explain the process when the display device 10C used by user C receives handwritten input data entered on the display device 10A2 used by user A, but the combination of display devices 10 that send and receive handwritten input data is not limited to this, and the same process is performed in other combinations of display devices 10 used by users participating in the event.

[0166] First, the transmitting / receiving unit 51 of the communication management device 50B receives the handwritten input data transmitted by the display device 10A2 (step S211). This handwritten input data is the handwritten input data entered by user A. As shown in Figure 20(A) of the first embodiment, the display screen 100A of the display device 10A2 displays the handwritten input data entered by user A.

[0167] Next, the determination unit 57 determines whether or not it has permission to view the handwritten input data received in step S211 (step S212). Specifically, the determination unit 57 refers to the permission information set by the setting unit 58 and determines whether or not it has permission to view the received handwritten input data for user A who entered it. If the determination unit 57 determines that it has permission to view the received handwritten input data (YES in step S212), it moves the process to step S213. Then, the transmission / reception unit 51 sends display permission information to the display device 10C indicating permission to display the handwritten input data so that the received handwritten input data is displayed on the display screen 100C of the display device 10C (step S213).

[0168] On the other hand, if the determination unit 57 determines that there is no permission to view the received handwritten input data (NO in step S212), it moves the process to step S214. The editing restriction unit 60 then restricts viewing of the handwritten input data (step S214). The editing restriction unit 60 then transmits viewing restriction display request information to the display device 10C via the transmission / reception unit 51, indicating a request to display a viewing restriction notification that viewing of the handwritten input data entered by user A is restricted (step S215). Note that each example screen displayed on the display device 10 can be implemented in the same way as shown in Figures 21 to 24 of the first embodiment, so examples and explanations are omitted.

[0169] In this way, when the communication management device 50B receives the displayed handwritten input data, it determines whether or not it has permission to view the handwritten input data in question, and only sends permission information to display the handwritten input data to the display device 10 if it has permission to view it. This allows the screen sharing system 1 to restrict viewing of the handwritten input data (written content) to users who do not have permission to view it, thereby preventing unauthorized viewing of handwritten input data. Furthermore, if the display device 10 does not have permission to view the received handwritten input data, it displays a viewing restriction notification on the display screen. Thus, in this second embodiment, since the communication management device 50B controls the determination of whether or not viewing permission exists and whether or not to allow execution, it is possible to reduce the processing burden on the display device 10.

[0170] ○ Processing of viewing requests Next, we will explain the process for requesting access to restricted handwritten input data using Figure 43. Figure 43 is a sequence diagram showing an example of the access request process for another user according to the second embodiment. Figure 43 explains an example in which a access request is made from display device 10C, used by user C, whose access to user A's handwritten input data is restricted, to display device 10A2, used by user A. However, the combination of display devices 10 that send and receive access requests is not limited to this, and similar processing is performed in other combinations of display devices 10 used by users participating in the event.

[0171] First, the display control unit 13C of the display device 10C displays the browsing restriction notice 480 on the display screen 100C (step S221). The browsing restriction notice 480 is as shown in Figure 26(A).

[0172] Next, the reception unit 12C accepts the selection of the viewing request button 485 included in the viewing restriction notification 480 in response to the input operation of user C (step S222). The transmitting / receiving unit 11C transmits viewing request information to the communication management device 50B indicating that it is requesting to view the restricted handwritten input data of user A (step S223). This viewing request information includes the user ID of the user to whom the viewing request is being made. In this case, the transmitting / receiving unit 11C transmits viewing request information including the user ID of user A. As a result, the transmitting / receiving unit 51 of the communication management device 50B receives the viewing request information transmitted by the display device 10C.

[0173] Next, the determination unit 55 of the communication management device 50B makes a decision regarding the viewing request information received in step S223 (step S224). Specifically, the determination unit 55 considers the attributes of the user using the display device 10C that sent the viewing request (for example, department, assigned duties, position, etc.) and the content of the handwritten strokes displayed on the display device 10A2, and determines whether or not the user using the display device 10C is allowed to view the information.

[0174] Next, the transmitting / receiving unit 51 of the communication management device 50B transmits (transfers) the judgment result information for the viewing request transmitted by the display device 10C to the display device 10A2 used by user A, the recipient of the viewing request (step S225). As a result, the transmitting / receiving unit 11A of the display device 10A2 receives the judgment result information for the viewing request transmitted by the requesting display device 10C.

[0175] Then, if the viewing request notification unit 21A of the display device 10A2 receives judgment result information regarding the viewing request in step S225, it displays a viewing request notification 380 on the display screen 100A indicating that a viewing request has been made by user C (step S226). Then, the reception unit 12A of the display device 10A2 accepts various button operations (step S227).

[0176] The transmitting / receiving unit 11A of the display device 10A2 transmits judgment response information to the viewing request to the communication management device 50B as a response to the judgment result information for the viewing request received in step S225 (step S228). As a result, the transmitting / receiving unit 51 of the communication management device 50B receives the judgment response information for the viewing request transmitted by the display device 10A2. The transmitting / receiving unit 51 then transmits viewing response information to the display device 10C that corresponds to the judgment response information for the viewing request received in step S228 (step S229). As a result, the transmitting / receiving unit 11C of the display device 10C receives the viewing response information transmitted by the communication management device 50B. Subsequently, the display control unit 13C of the display device 10C displays the result for the viewing request (step S230). As a result, the display device 10C can notify user C of the result for the viewing request.

[0177] ○Request to edit handwritten input data○ Next, using Figure 44, we will explain the process of editing handwritten input data entered by other users on the display screen according to each user's viewing permissions. Figure 44 is a flowchart of an example of editing restriction processing for handwritten input data entered by other users according to the second embodiment. In Figure 44, we explain the process when editing handwritten input data entered on display device 10A2 used by user A on display device 10B used by user B, but the combination of display devices 10 is not limited to this, and the same processing is performed on other combinations of display devices 10 used by users participating in the event.

[0178] First, the transmitting / receiving unit 51 of the communication management device 50B receives the handwritten input data transmitted by the display device 10A2 (step S231). This handwritten input data is the handwritten input data entered by user A. As shown in Figure 20(A) of the first embodiment, the display screen 100A of the display device 10A2 displays the handwritten input data entered by user A.

[0179] Next, the determination unit 57 determines whether or not it has editing authority over the handwritten input data received in step S231 (step S232). Specifically, the determination unit 57 refers to the authority information set by the setting unit 58 and determines whether or not it has editing authority over user A who entered the received handwritten input data. If the determination unit 57 determines that it has editing authority over the received handwritten input data (YES in step S232), it moves the process to step S233. Then, the transmission / reception unit 51 sends execution permission information to the display device 10C indicating permission to perform an editing operation on the received handwritten input data (step S233).

[0180] On the other hand, if the determination unit 57 determines that there is no editing authority for the handwritten input data to be edited (NO in step S232), it moves the process to step S234. The editing restriction unit 60 then restricts the editing of the handwritten input data to be edited (step S234). The editing restriction unit 60 then transmits editing restriction display request information to the display device 10C via the transmission / reception unit 51, indicating a request to display an editing restriction notification that editing of the handwritten input data entered by user A is restricted (step S235).

[0181] In this way, when the communication management device 50B receives editing operation information for the displayed handwritten input data, it determines whether or not the user has editing rights for the target handwritten input data, and only sends information granting permission to execute the editing operation to the display device 10 if the user has editing rights. This allows the screen sharing system 1 to prevent unauthorized editing of handwritten input data by restricting editing of the handwritten input data (written content) to users without editing rights. Furthermore, if the display device 10 does not have editing rights for the received handwritten input data, it displays an editing restriction notification on the display screen. Thus, in this second embodiment, since the communication management device 50B controls the determination of whether or not editing rights exist and whether or not execution is permitted, the processing burden on the display device 10 can be reduced.

[0182] ○ Processing of editing permission requests Next, we will explain the process for requesting editing permission for handwritten input data whose editing is restricted, using Figure 45. Figure 45 is a sequence diagram showing an example of the editing permission request process for another user according to the second embodiment. In Figure 45, we explain an example in which a request for editing permission is made from display device 10B, used by user B whose editing of user A's handwritten input data is restricted, to display device 10A2, used by user A. However, the combination of display devices 10 that send and receive the editing permission request is not limited to this, and similar processing is performed in other combinations of display devices 10 used by users participating in the event.

[0183] First, the display control unit 13B of the display device 10B displays an editing operation permission or editing restriction notification 660 on the display screen 100B (step S241). The editing restriction notification 660 is as shown in Figure 31(A).

[0184] Next, the reception unit 12B accepts the selection of the editing permission request button 665 included in the editing restriction notification 660 in response to the input operation of user B (step S242). The transmitting / receiving unit 11B transmits editing permission request information to the communication management device 50B indicating that it is requesting editing permission for the restricted handwritten input data of user A (step S243). This editing permission request information includes the user ID of the user to whom the editing permission request is being made. In this case, the transmitting / receiving unit 11B transmits editing permission request information including the user ID of user A. As a result, the transmitting / receiving unit 51 of the communication management device 50B receives the editing permission request information transmitted by the display device 10B.

[0185] Next, the determination unit 55 of the communication management device 50B makes a decision regarding the editing permission request information received in step S243 (step S244). Specifically, the determination unit 55 considers the attributes of the user using the display device 10B who sent the editing permission request (for example, department, assigned duties, job title, etc.) and the content of the handwritten strokes displayed on the display device 10A2, and determines whether or not editing permission is granted to the user using the display device 10B.

[0186] Next, the transmitting / receiving unit 51 of the communication management device 50B transmits (transfers) the judgment result information for the editing permission request transmitted by the display device 10B to the display device 10A2 used by user A, who is the recipient of the viewing request (step S245). As a result, the transmitting / receiving unit 11A of the display device 10A2 receives the judgment result information for the editing permission request transmitted by the requesting display device 10B.

[0187] Then, if the editing permission request notification unit 22A of the display device 10A2 receives judgment result information regarding the editing permission request in step S245, it displays an editing permission request notification 560 on the display screen 100A indicating that an editing permission request has been made by user B (step S246). Then, the reception unit 12A of the display device 10A2 accepts various button operations (step S247).

[0188] The transmitting / receiving unit 11A of the display device 10A2 transmits judgment response information to the editing permission request to the communication management device 50B as a response to the judgment result information for the editing permission request received in step S245 (step S248). As a result, the transmitting / receiving unit 51 of the communication management device 50B receives the judgment response information for the editing permission request transmitted by the display device 10A2. Then, the transmitting / receiving unit 51 transmits the editing permission response information to the display device 10B in response to the editing permission request received in step S248 (step S249). As a result, the transmitting / receiving unit 11B of the display device 10B receives the editing permission response information transmitted by the communication management device 50B. Subsequently, the display control unit 13B of the display device 10B displays the result for the editing permission request (step S250). As a result, the display device 10B can notify user B of the result for the editing permission request.

[0189] The allocation of functions in the display device 10 and the communication management device 50B related to the screen sharing system 1 shown in the second embodiment is not limited to the example described above.

[0190] ● Main effects of the second embodiment As described above, according to this embodiment, the screen sharing system 1 is configured to have the various decision-making functions for viewing requests and editing permission requests from other display devices 10 (10B or 10C), which were previously handled by the display device 10, on the communication management device 50B side. As a result, various decision-making processes on the display device 10 become unnecessary, and the display device 10 can concentrate mainly on screen display and data communication processing. By adopting such a system configuration, the processing load on the display device 10 can be reduced, making it possible to provide a comfortable user environment for users of the display device 10, for example.

[0191] ● Modified examples of embodiments Next, a modified example of the screen sharing system according to the embodiment will be described with reference to Figures 46 to 50. Note that components and functions identical to those in the above embodiment are denoted by the same reference numerals, and their descriptions are omitted. The modified screen sharing system 1 is an example of a system in which a shared area, displayed and shared among multiple display devices 10, is composed of multiple pages.

[0192] Figure 46 is a schematic diagram illustrating an example of the display state of a shared area in a display device according to a modified embodiment. In Figure 46, the display devices 10A, 10B, and 10C share a shared area divided into multiple pages to perform events such as remote conferences. Each of the display devices 10A, 10B, and 10C displays a desired page from among the multiple pages included in the shared area on its display screen. Furthermore, since each of the display devices 10A, 10B, and 10C can display a different page, the user can be allowed to view a desired page during event execution. Note that each page constituting the shared area may be an area the same size as the display screen of the display device 10, or, as in the embodiment described above, the page itself may be an expandable area without limitations on the area where handwritten input is possible.

[0193] Figure 47 is a diagram illustrating an example of display screen information related to a modified embodiment. Figure 47 shows an image of an example of the state of the display screen displayed on the display device 10. In the example of Figure 47, the display screen has a hierarchical structure of "events," "pages (pages 1-3)," and "objects (objects 1-5)." "Objects" correspond to handwritten input data and are managed by "pages." A "page" refers to an image for one page displayed on the display screen. Furthermore, "events" refer to information about events being executed by the display device 10. For example, object 1 includes an object ID (id=sr001) that identifies object 1, information for identifying page 1 on which object 1 exists (parent=pag01), and the gid (global id) "g001" of object 1. For example, if an operation such as moving is performed on the image represented by object 1, the object ID (id=sr001) is retained, but the gid "g001" of object 1 is updated.

[0194] The display device 10 allows for page switching, and each "page" corresponds to a page of the display device 10. For example, page 1 contains a page ID (id=pag01) to identify page 1, information to identify the "event" being executed on the display device 10 (parent=G001), and the gid "g01" of page 1. An "event" corresponds to an event being executed on the display device 10 and is managed by an event ID (id=G001) to identify the event and the gid "g1" of the event. The gids shown at each level are assigned by the communication management device 5 when sharing screen data with other display devices 10. Furthermore, the hierarchical structure of display screen information shown in Figure 39 is shared among multiple display devices 10 when sharing screen data.

[0195] Figure 48 shows an example of a metadata file relating to a modified embodiment. The metadata file 500a shown in Figure 48 is stored in the storage unit 5000 of the communication management device 50, similar to the metadata file 500 shown in Figure 11. Unlike the metadata file 500 shown in Figure 11, the metadata file 500a includes page number information along with the coordinate position (X,Y) and size (Width,Height) of the display area (ViewArea) as area information shown for each user.

[0196] Figure 49 shows an example of a handwritten input data file according to a modified embodiment. The handwritten input data file 550a shown in Figure 49 is stored in the storage unit 5000 of the communication management device 50, similar to the handwritten input data file 550 shown in Figure 12. Unlike the handwritten input data file 550 shown in Figure 12, the handwritten input data file 550a includes information on the page number on which the object was entered as data details (Data) shown in the object data (Objects).

[0197] Figure 50 is a conceptual diagram showing an example of a screen information management table according to a modified embodiment. The storage unit 5000 of the communication management device 50 has a screen information management DB constructed in it, which is composed of a screen information management table as shown in Figure 50. This screen information management table stores and manages various data related to the display screen shared among the display devices 10 for each event ID that identifies an event executed on each display device 10. The data shown in the screen information management table corresponds to the state of the display screen (see Figure 47) described as display screen information in the display device 10.

[0198] The data shown in the screen information management table includes an ID to identify each data item, a sequence number indicating the order in which each data item occurred, information indicating the content of the data (body), and information to identify the parent data (parent). The screen information management table also includes, for example, an event ID to identify the event being executed, and information indicating the pages generated by the event (children). For example, in the case of page data, the screen information management table includes a page ID to identify the page (page data), and information to identify the parent event (parent).

[0199] Furthermore, in the case of object data, for example, the screen information management table includes an object ID that identifies the object data generated by the event, information indicating the content of the object data, and information (parent) to identify the parent page (page data). In this case, the information indicating the content of the object data (body) includes the color of the input object, the width indicating the line thickness of the input object, the vertices (x,y) of the input object, and the name of the user who input the object. The object color is represented in RGBA (Red Green Blue Alpha) data format, with each element being a numerical value from 0 to 255. The width of the object's line thickness is expressed in pixels. In addition, the vertices of the object are represented by XY coordinates, and connecting each vertex with a Bézier curve creates a line segment that represents the stroke.

[0200] Thus, the modified screen sharing system 1 can execute events using multiple display devices 10 even when the shared area is composed of multiple pages.

[0201] ●Summary● As described above, the screen sharing system according to one embodiment of the present invention is a screen sharing system 1 that shares a handwriting input screen between a first display device (e.g., display device 10A) used by a first user (e.g., user A) and a second display device (e.g., display device 10B or display device 10C) used by a second user (e.g., user B or user C). The first display device sets the editing rights of the second user to the first handwriting input data entered by the first user, and the second display device restricts editing of the first handwriting input data based on the editing rights set on the first display device. In this way, the screen sharing system 1 can individually set the editing rights of users to the handwriting input data.

[0202] Furthermore, in a screen sharing system according to one embodiment of the present invention, a first display device (e.g., display device 10A) used by a first user (e.g., user A) sets the viewing rights of a second user (e.g., user B or user C) to first handwritten input data entered by the first user, and a second display device (e.g., display device 10B or display device 10C) used by the second user displays the first handwritten input data based on the viewing rights set on the first display device. As a result, the screen sharing system 1 can individually set the viewing rights of users to handwritten input data.

[0203] Furthermore, in a screen sharing system according to one embodiment of the present invention, a first display device (e.g., display device 10A) used by a first user (e.g., user A) sets the first user's editing rights for second handwritten input data entered by a second user (e.g., user B or user C), and based on the set editing rights, restricts editing of the second handwritten input data if the first user does not have editing rights for the second handwritten input data. As a result, the screen sharing system 1 can set editing rights for handwritten input data entered by other users, in addition to the rights of other users for handwritten input data entered by the user, thereby preventing unintentional editing of content written by other users.

[0204] ●Additional Information● Each function of the embodiment described above can be realized by one or more processing circuits. Here, "processing circuit" in this embodiment includes processors programmed to execute each function by software, such as processors implemented by electronic circuits, as well as devices such as ASICs (Application Specific Integrated Circuits), DSPs (digital signal processors), FPGAs (field programmable gate arrays), SOCs (System on a chip), GPUs (Graphics Processing Units), and conventional circuit modules designed to execute each of the functions described above.

[0205] Furthermore, the various tables in the embodiments described above may be generated by the learning effect of machine learning, and tables may not be used if the data of each related item is classified by machine learning. Here, machine learning is a technique for enabling computers to acquire human-like learning abilities, and it refers to a technique in which a computer autonomously generates algorithms necessary for judgments such as data identification from pre-incorporated training data, and applies these to new data to make predictions. The learning method for machine learning may be supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, or deep learning, or a combination of these learning methods may be used, and the learning method for machine learning is not limited.

[0206] While a screen sharing system, screen sharing method, display device, display control method, and program according to one embodiment of the present invention have been described so far, the present invention is not limited to the embodiments described above. It can be modified to the extent that a person skilled in the art can imagine, such as by adding, changing, or deleting other embodiments, and any embodiment that achieves the function and effect of the present invention is included within the scope of the present invention. [Explanation of Symbols]

[0207] 1. Screen sharing system 5. Communication Network 10 Display device 10A1 Display device (an example of a first display device) 10A2 Display device (an example of the first display device) 10B Display device (an example of a second display device) 10C Display Device (An example of a second display device) 11A Transmitting / receiving unit (an example of a means for transmitting authorization information) 11B Transmitting and Receiving Unit (Example of means for sending editing permission requests, example of means for sending viewing requests, example of means for receiving) 11C Transmitting and Receiving Unit (Example of means for sending editing permission requests, example of means for sending viewing requests, example of means for receiving) 13A Display Control Unit (An example of a second display control means) 13B Display Control Unit (Example of Display Control Means) 13C Display Control Unit (An example of display control means) 17A Setting section (an example of setting means) 18A Editing restriction unit (an example of a second editing restriction means) 18B Editing restriction section (an example of editing restriction means) 18C Editing restriction section (an example of editing restriction means) 19A Non-sharing notification section (an example of non-sharing notification means) 21A Viewing Request Notification Unit (An example of a viewing request notification means) 22A Editing permission request notification unit (an example of an editing permission request notification means) 23A Recommendation Notification Section (Example of Recommendation Notification Method) 25 Selection section (an example of a selection means) 26 Detection unit (an example of a detection means) 50A communication management device 50B Communication management device 100(100A,100B,100C) display screen 350,360,370 Unshared notifications 380 Viewing Request Notification 400, 400a, 800 Permissions Settings Screen (Example of a settings screen) 450,480 Access restriction notification 560 Editing permission request notification 650,660,830 Editing restriction notification 700 Shared Area 850 Permission Change Recommendation Notification [Prior art documents] [Patent Documents]

[0208] [Patent Document 1] Japanese Patent Publication No. 2009-93274 [Patent Document 2] Japanese Patent Publication No. 2020-156085

Claims

1. A screen sharing system for sharing a handwriting input screen between a first display device used by a first user and a second display device used by a second user, The first display device is The system includes setting means for setting the editing rights of the second user to the first handwritten input data entered by the first user, The second display device is, Editing restriction means that restrict editing of the first handwritten input data based on the editing privileges set on the first display device. A screen sharing system equipped with the following features.

2. A screen sharing system according to claim 1, The first display device further The system includes a means for transmitting permission information that transmits permission information indicating the set editing permission, The editing restriction means is a screen sharing system that restricts editing of the first handwritten input data based on the permission information transmitted by the first display device.

3. The screen sharing system according to claim 1 or 2, wherein the setting means sets the editing permissions in response to input to a setting screen that accepts the setting of editing permissions for each user.

4. The screen sharing system according to any one of claims 1 to 3, wherein the editing restriction means restricts editing of the first handwritten input data if the second user does not have editing rights to the first handwritten input data.

5. The screen sharing system according to any one of claims 1 to 4, wherein the editing restriction means displays an editing restriction notice indicating that the second user does not have editing privileges over the first handwritten input data.

6. A screen sharing system according to claim 5, The editing restriction means accepts an editing permission request for the first handwritten input data in response to the input for the displayed editing restriction notification. The aforementioned second display device further, A screen sharing system comprising an editing permission request transmission means for transmitting an editing permission request for the first handwritten input data to the first display device.

7. A screen sharing system according to claim 6, The first display device further, A screen sharing system comprising editing permission request notification means for causing the second display device to display an editing permission request notification indicating that it has sent the editing permission request.

8. The screen sharing system according to claim 7, wherein the setting means changes the editing privileges of the second user in response to the displayed editing privilege request notification.

9. A screen sharing system according to any one of claims 1 to 8, The setting means sets the second user's viewing rights to the first handwritten input data entered by the first user, The second display device is, A screen sharing system comprising display control means for displaying the first handwritten input data based on the viewing permissions set on the first display device.

10. The screen sharing system according to claim 9, wherein the display control means causes the second user to display the first handwritten input data if the second user has permission to view the first handwritten input data.

11. The screen sharing system according to claim 9 or 10, wherein the display control means causes the second user to display a viewing restriction notice indicating that viewing of the first handwritten input data is restricted if the second user does not have permission to view the first handwritten input data.

12. A screen sharing system according to claim 11, The display control means accepts a request to view the first handwritten input data in response to the input regarding the displayed viewing restriction notice. The aforementioned second display device further, A screen sharing system comprising a viewing request transmission means for transmitting a viewing request for the first handwritten input data to the first display device.

13. A screen sharing system according to claim 12, The first display device further, A screen sharing system comprising a viewing request notification means for causing the second display device to display a viewing request notification indicating that it has sent the viewing request.

14. The screen sharing system according to claim 13, wherein the setting means changes the viewing permissions of the second user in response to the displayed viewing request notification.

15. A screen sharing system according to any one of claims 9 to 14, The first display device further, A screen sharing system comprising a non-sharing notification means that displays a non-sharing notification indicating that the first handwritten input data is not shared with the second user if the second user does not have the right to view the first handwritten input data.

16. A screen sharing system according to claims 1 to 15, The setting means sets the first user's editing rights over the second handwritten input data entered by the second user, The first display device further, A screen sharing system comprising a second editing restriction means that restricts editing of the second handwritten input data if the first user does not have editing privileges for the second handwritten input data based on the set editing privileges.

17. A screen sharing system according to claim 16, The first display device further, The system includes a first layer containing the writing of the first user and a second layer containing the writing of the second user, and a second display control means for displaying them superimposed on each other. The second editing restriction means is a screen sharing system that restricts editing to the second layer if the first user does not have editing privileges for the second user's writing.

18. The screen sharing system according to claim 17, wherein the second editing restriction means causes the first user to display a second editing restriction notification indicating that editing is restricted if the first user does not have editing privileges for the second handwritten input data.

19. The screen sharing system according to claim 18, wherein the setting means changes the editing permissions for the second handwritten input data in response to the displayed second editing restriction notification.

20. A screen sharing system according to any one of claims 16 to 19, The first display device further, A screen sharing system comprising a notification means for displaying a notification recommending a change in editing permissions when the first handwritten input data and the second handwritten input data overlap.

21. The screen sharing system according to claim 20, wherein the setting means changes the editing permissions for the second handwritten input data in response to the displayed permission change recommendation notification.

22. A screen sharing system according to any one of claims 1 to 21, The first display device further, A screen sharing system that includes a selection mechanism for selecting handwritten input data to be edited, for each user who entered the handwritten input data.

23. A screen sharing system according to any one of claims 1 to 22, The first display device further, The system includes a detection means for detecting pen pressure applied to the handwriting input screen, A screen sharing system that switches the handwritten input data to be edited according to the detected pen pressure.

24. A screen sharing method performed by a screen sharing system that shares a handwriting input screen between a first display device used by a first user and a second display device used by a second user, The first display device is The setting step is performed to set the editing rights of the second user to the first handwritten input data entered by the first user, The second display device is, Editing restriction step that restricts editing of the first handwritten input data based on the editing privileges set on the first display device. How to share your screen to perform this action.

25. A display device that shares a handwriting input screen with other display devices used by other users, A receiving means for receiving permission information indicating editing rights for handwritten input data entered by the aforementioned other user, Based on the received authorization information, editing restriction means restrict editing of the handwritten input data, A display device equipped with the following features.

26. A display control method performed by a display device that shares a handwriting input screen with other display devices used by other users, A receiving step, which includes receiving permission information indicating editing rights for handwritten input data entered by the aforementioned other user, Based on the received permission information, an editing restriction step is taken to restrict editing of the handwritten input data, A display control method that executes [this].

27. A display device that shares a handwriting input screen with other display devices used by other users, A receiving step, which includes receiving permission information indicating editing rights for handwritten input data entered by the aforementioned other user, Based on the received permission information, an editing restriction step is taken to restrict editing of the handwritten input data, A program that executes the command.

Images