Screen sharing system, screen sharing method, display device, display control method, and program
The screen sharing system addresses the lack of user-specific editing authority by allowing permission-based editing restrictions, improving user operability and preventing unintended edits in collaborative screen sharing.
Patent Information
- Application Number
- JP2021182282
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-03-16
- Filing Date
- 2021-11-09
- Publication Date
- 2026-01-06
- Estimated Expiration
- 2041-11-09
AI Technical Summary
Conventional methods fail to allow individual setting of editing authority for each user on shared handwritten input data, leading to issues with unintended editing operations in collaborative screen sharing systems.
A screen sharing system that enables setting user editing authority on a first display device and restricts editing on a second display device based on these settings, allowing individual permission management for handwritten input data.
Enables individual user editing authority settings, preventing unintended editing and enhancing user operability in collaborative screen sharing environments.
Smart Images

Figure 0007793946000001 
Figure 0007793946000002 
Figure 0007793946000003
Abstract
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 technology]
[0002] Display devices that allow multiple users to input handwriting are used in conferences and the like at companies, educational institutions, government agencies, etc. Also, in remote conferences and the like between different locations, a method is known in which display screens displayed at the different locations are shared and handwriting input is performed on the same screen from each location.
[0003] Also, methods for restricting editing to prevent unintended editing operations on handwritten input content shared by multiple users are known. For example, Patent Document 1 discloses a method in which, in a system in which data having multiple objects is shared among multiple base terminals, the base terminal that last selected the object acquires the editing authority for the object. Furthermore, Patent Document 2 discloses a method for prohibiting operations from other electronic whiteboards on a stroke image specified in a group operation request in order to prevent operations that are not intended by the user from being performed. Summary of the Invention [Problem to be solved by the invention]
[0004] However, the conventional method has a problem in that it is not possible to individually set the editing authority of each user for the handwritten input data entered on the shared handwritten input screen. [Means for solving the problem]
[0005] In order to solve the above-mentioned problem, the invention of claim 1 is a screen sharing system that shares a handwritten 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 is equipped with a setting means for setting the second user's editing authority for first handwritten input data entered by the first user, and the second display device is equipped with an editing restriction means for restricting editing of the first handwritten input data based on the editing authority set on the first display device. [Effects of the Invention]
[0006] According to the present invention, it is possible to individually set the editing authority of each user for handwritten input data. [Brief explanation of the drawings]
[0007] [Figure 1] FIG. 1 illustrates an example of the overall configuration of a screen sharing system. [Figure 2] FIG. 10 is a diagram for explaining an image of how an electronic whiteboard is used. [Figure 3] FIG. 1 is a diagram illustrating an example of a hardware configuration of an electronic whiteboard. [Figure 4] FIG. 2 is a diagram illustrating an example of a hardware configuration of a PC. [Figure 5] FIG. 2 is a diagram illustrating an example of a hardware configuration of a communication management device. [Figure 6] 1 is a schematic diagram illustrating the relationship between a shared area shared by a plurality of display devices and a display screen displayed on the display device. [Figure 7] FIG. 10 is a diagram illustrating an example of data input using a virtual keyboard. [Figure 8] FIG. 1 illustrates an example of a functional configuration of a screen sharing system. [Figure 9] FIG. 10 is a conceptual diagram illustrating an example of a user information management table. [Figure 10] FIG. 10 is a conceptual diagram illustrating an example of an event information management table. [Figure 11]FIG. 10 is a diagram illustrating an example of a metadata file. [Figure 12] 10 is a diagram showing an example of a handwritten input data file. [Figure 13] FIG. 10 is a conceptual diagram illustrating an example of an authority information management table. [Figure 14] FIG. 10 is a sequence diagram illustrating an example of a screen display process at the start of an event. [Figure 15] FIG. 10 is a diagram illustrating an example of a shared area. [Figure 16] FIG. 10 is a sequence diagram illustrating an example of a process for setting authority for another user. [Figure 17] FIG. 10A is a diagram showing an example of a display screen, and FIG. 10B is a diagram showing an example of an authority setting screen. [Figure 18] FIG. 10 is a diagram illustrating an example of an authority setting screen. [Figure 19] FIG. 10 is a diagram illustrating another example of the authority setting screen. [Figure 20] 10 is a flowchart illustrating an example of a display process for handwritten input data input by another user. [Figure 21] 5A to 5C are diagrams showing examples of display screens displayed on the respective display devices. [Figure 22] FIG. 10A is a diagram showing an example of a non-sharing notification, and FIG. 10B is a diagram showing an example of a viewing restriction notification. [Figure 23] FIG. 10 is a diagram illustrating another example of a non-sharing notification. [Figure 24] FIG. 10 is a diagram illustrating another example of a non-sharing notification. [Figure 25] FIG. 10 is a sequence diagram illustrating an example of a process for making a view request to another user. [Figure 26] 10A is a diagram showing another example of a viewing restriction notification, and FIG. 10B is a diagram showing an example of a viewing request notification. [Figure 27] FIG. 10A is a diagram showing an example of a viewing permission notification, and FIG. 10B is a diagram showing an example of a viewing rejection notification. [Figure 28] 10 is a flowchart illustrating an example of a process for editing handwritten input data input by another user. [Figure 29]FIG. 10 is a diagram illustrating an example of an editing restriction notification. [Figure 30] FIG. 10 is a sequence diagram illustrating an example of a process for requesting editing authority from another user. [Figure 31] 10A is a diagram showing another example of an editing restriction notification, and FIG. 10B is a diagram showing an example of an editing authority request notification. [Figure 32] 10A is a diagram showing an example of an editing permission notification, and FIG. 10B is a diagram showing an example of an editing authority denial notification. [Figure 33] 10 is a flowchart illustrating an example of an editing restriction process for handwritten input data input by another user. [Figure 34] FIG. 10 is a diagram showing another example of an editing restriction notification. [Figure 35] FIG. 10 is a diagram illustrating another example of the authority setting screen. [Figure 36] FIG. 10 is a diagram illustrating an example of an authority change recommendation screen. [Figure 37] FIG. 10 is a diagram illustrating an example of superimposed display of writing layers for each user. [Figure 38] FIG. 10 is a diagram illustrating an example of an editing operation selection screen. [Figure 39] FIG. 10 is a diagram showing another example of the editing operation selection screen. [Figure 40] FIG. 10 is a diagram illustrating an example of switching of editing operations based on pen pressure. [Figure 41] FIG. 10 is a diagram illustrating an example of a functional configuration of a screen sharing system according to a second embodiment. [Figure 42] 10 is a flowchart showing an example of a viewing restriction process for handwritten input data input by another user according to the second embodiment. [Figure 43] FIG. 11 is a sequence diagram illustrating an example of a process of making a view request to another user according to the second embodiment. [Figure 44] 10 is a flowchart showing an example of an edit restriction process for handwritten input data input by another user according to the second embodiment. [Figure 45] FIG. 11 is a sequence diagram illustrating an example of a process of requesting editing authority from another user according to the second embodiment. [Figure 46] 10A and 10B are schematic diagrams illustrating an example of a display state of a shared area on a display device according to a modified example of the embodiment. [Figure 47] FIG. 10 is a diagram for schematically explaining an example of display screen information according to a modified example of the embodiment. [Figure 48] FIG. 10 is a diagram illustrating an example of a metadata file according to a modified example of the embodiment. [Figure 49] FIG. 10 is a diagram illustrating an example of an object data file according to a modified example of the embodiment. [Figure 50] FIG. 10 is a conceptual diagram illustrating an example of a screen information management table according to a modified example of the embodiment. DETAILED DESCRIPTION OF THE INVENTION
[0008] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In the description of the drawings, the same elements are given the same reference numerals, and duplicated explanations will be omitted.
[0009] First embodiment ●System configuration First, an outline of the configuration of a screen sharing system according to the first embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of the overall configuration of a screen sharing system. The screen sharing system 1 shown in Fig. 1 is a system in which data that can be displayed on a plurality of display devices 10 can be shared among them.
[0010] As shown in FIG. 1, screen sharing system 1 includes display devices 10A1, 10B, and 10C located at multiple locations (location A, location B), and a communication management device 50A. The display devices 10A1, 10B, and 10C and the communication management device 50A that constitute 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 local area network (LAN), or the like. Note that communication network 5 may include not only wired communication networks but also 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] The display devices 10A1, 10B, and 10C are computers equipped with handwriting input functions, communication functions, and display functions. For example, the display device 10A1 is an electronic whiteboard installed at site A, the display device 10B is a portable notebook PC (Personal Computer) at site B, and the display device 10C is a portable tablet PC at site C. The display devices 10A1, 10B, and 10C perform remote communication while sharing objects input by handwriting. Users A, B, and C can hold events such as remote conferences while viewing display screens on which display content is shared at each site. Note that the event is not limited to a remote conference and may be a remote lesson, a remote medical examination, a meeting, a consultation, or a simple conversation.
[0012] Display devices 10A1, 10B, and 10C communicate screen data such as handwritten input data. The handwritten input data is data necessary to display (reproduce) a display screen including objects handwritten by user A, user B, and user C on display devices 10A1, 10B, and 10C, respectively. The handwritten input data includes coordinate data, line width data, line color data, vector data, data indicating the pen pressure used when a stroke was drawn, and the like.
[0013] Display devices 10A1, 10B, and 10C transmit and receive handwritten input data for displaying a shared object, thereby allowing users of screen sharing system 1 to share the same object. An object is an image showing lines or the like drawn by a user through handwritten input using an electronic pen or the like. An object is displayed using handwritten input data that indicates a point specifying its coordinates on the display.
[0014] The display device 10 is not limited to an electronic whiteboard or a PC, but may be any device on which a software application for executing handwriting input, communication, and display functions is installed. The PC may also be, for example, a smartphone, a wearable device or smartwatch, a car navigation device, a game console, a telepresence robot, or a medical device.
[0015] While FIG. 1 shows an example constructed by display devices 10 (10A1, 10B, 10C) located at three locations (location A, location B, location C), the screen sharing system 1 may also be configured to include multiple display devices 10 at one location. The number of locations constituting the screen sharing system 1 may be two locations, four or more locations with a display device 10 located at each location, or may be only one location where multiple display devices 10 are located at one location. Hereinafter, 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, shared screen data, etc. 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 be configured by one server computer or multiple server computers. Although the communication management device 50A is described as a server computer existing in a cloud environment, it may be a server that operates on a display device 10 such as an electronic whiteboard, or may be a server that exists in an on-premise environment.
[0018] ○Image of how to use the electronic whiteboard○ Here, an image of how an electronic whiteboard, which is an example of the display device 10, is used will be described with reference to FIG. 2. FIG. 2 is a diagram for explaining an image of how an electronic whiteboard is used. As shown in FIG. 2, the electronic whiteboard, which is an example of the display device 10, is composed of legs 251 having a plurality of casters on the lower side, support columns 252 provided on the upper side of the legs 251, a main body 253 of the electronic whiteboard provided on the upper side of the support columns 252, and a display 280 provided on the front side of the main body 253. The main body 253 incorporates a CPU 201, which will be described later, and the like. A user can 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 devices or terminals that make up the screen sharing system according to the first embodiment will be described with reference to Figures 3 to 5. Note that components may be added or deleted from the hardware configurations shown in Figures 3 to 5 as necessary.
[0020] ○Hardware configuration of electronic whiteboard○ First, the hardware configuration of an electronic whiteboard, which is an example of the display device 10, will be described with reference to Fig. 3. Fig. 3 is a diagram showing an example of the hardware configuration of an electronic whiteboard. Each piece of hardware configuration of the electronic whiteboard, which is an example of the display device 10, is indicated by a reference number in the 200s. As shown in Fig. 3, the electronic whiteboard includes a CPU (Central Processing Unit) 201, a ROM (Read Only Memory) 202, a RAM (Random Access Memory) 203, an SSD (Solid State Drive) 204, a network I / F (Interface) 205, and an external device connection I / F 206.
[0021] Of these, the CPU 201 controls the overall operation of the electronic whiteboard. The ROM 202 stores the CPU 201 and programs used to drive the CPU 201, such as an IPL (Initial Program Loader). The RAM 203 is used as a work area for the CPU 201. The SSD 204 stores various data, such as programs for the electronic whiteboard. The network I / F 205 controls communication with the communication network 5. The external device connection I / F 206 controls communication with external devices, such as a USB (Universal Serial Bus) memory 230, a PC 270, a microphone 240, a speaker 250, or a 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 of the short-range communication circuit 219, a power switch 222, and selection switches 223.
[0023] Of these, the capture device 211 acquires image data displayed on a display 280, which is an example of a display unit, via a display controller 213 and stores the image data in a RAM 203 or the like. The GPU 212 is a semiconductor chip (processor) that specializes in graphics. The display controller 213 controls and manages screen display to output an output image from the capture device 211 or the GPU 212 to the display 280 or the like. The contact sensor 214 detects contact of the electronic pen 290, the user's hand H, or the like on the display 280. The sensor controller 215 controls the processing of the contact sensor 214. The contact sensor 214 inputs and detects coordinates using an infrared blocking method. This coordinate input and coordinate detection method involves two light receiving and emitting devices installed at both ends of the upper side of the display 280 emitting multiple infrared rays parallel to the display 280, which are reflected by reflecting members installed around the periphery of the display 280 and return along the same optical path as the light emitted by the light receiving element. The contact sensor 214 outputs the ID of the infrared light emitted by the two light receiving and emitting devices that has been blocked by an object to the sensor controller 215, and the sensor controller 215 identifies the coordinate position of the contact position of the object. The electronic pen controller 216 communicates with the electronic pen 290 to determine whether the pen tip or the pen tail has touched the display 280. The short-range 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 switching the power of the electronic whiteboard on and off. The selection switches 223 are a group of switches for adjusting, for example, the brightness and color of the display 280.
[0024] The electronic whiteboard further includes a bus line 210. The bus line 210 is an address bus, a data bus, or the like for electrically connecting the components such as the CPU 201 shown in FIG.
[0025] The contact sensor 214 is not limited to an infrared blocking type, and various detection means may be used, such as a capacitive touch panel that identifies the contact position by detecting a change in capacitance, a resistive film touch panel that identifies the contact position by a change in voltage between two opposing resistive films, or an electromagnetic induction touch panel that identifies the contact position by detecting electromagnetic induction caused by an object touching the display unit. Also, the electronic pen controller 216 may determine whether or not the part of the electronic pen 290 that the user grips or other parts of the electronic pen have been touched, in addition to the pen tip and pen butt.
[0026] ○PC hardware configuration○ Next, the hardware configuration of a PC, which is an example of the display device 10, will be described with reference to Fig. 4. Fig. 4 is a diagram showing an example of the hardware configuration of a PC. Each piece of hardware in the PC, which is an example of the display device 10, is indicated by a reference numeral in the 300s. As shown in Fig. 4, the PC includes a CPU 301, a ROM 302, a RAM 303, a hard disk (HD) 304, a hard disk drive (HDD) controller 305, a display 306, an external device connection I / F 307, a network I / F 308, a bus line 310, a keyboard 311, a pointing device 312, an audio input / output I / F 313, a microphone 314, a speaker 315, a camera 316, a digital versatile disk rewritable (DVD-RW) drive 317, and a media I / F 319.
[0027] The CPU 301 controls the overall operation of the PC. The CPU 301 is a computing device that realizes various functions of the PC by loading programs or data stored in the ROM 302, HD 304, or the like onto the RAM 303 and executing the processes. The ROM 302 is a non-volatile memory that stores programs used to run the CPU 301, such as an IPL. The RAM 303 is a volatile memory used as a work area for the CPU 301. The HD 304 stores various data, such as programs. The HDD controller 305 controls the reading and writing of various data from and to the HD 304 under the control of the CPU 301. The display 306 displays various information, such as a cursor, menus, windows, characters, or images. The display 306 may be a touch panel display equipped with input means. The 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, the external device is, for example, a USB memory or a printer. The network I / F 308 is an interface for data communication using the communication network 5. The bus line 310 is an address bus or a data bus for electrically connecting the components such as the CPU 301 shown in FIG.
[0028] The keyboard 311 is a type of input unit equipped with multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 312 is a type of input unit for selecting or executing various instructions, selecting a processing target, moving a cursor, etc. The input unit may be not only the keyboard 311 and the pointing device 312, but also a touch panel, 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 under the control of the CPU 301. The microphone 314 is a type of built-in sound collection unit that inputs audio. The speaker 315 is a type of built-in output unit that outputs audio signals. The camera 316 is a type of built-in imaging unit that captures an image of a subject and obtains image data. The microphone 314, speaker 315, and camera 316 may be external devices rather than built into the PC. The DVD-RW drive 317 controls the reading and writing of various data from and to a DVD-RW 318, which is an example of a removable recording medium. The removable recording medium is not limited to DVD-RW, but may be DVD-R or Blu-ray (registered trademark) Disc, etc. Media I / F 319 controls reading and writing (storing) of data from and to recording medium 321, such as flash memory.
[0029] ○Hardware configuration of 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 piece of hardware configuration of the communication management device 50A is indicated by a reference number in the 500 series. The communication management device 50A is constructed by a computer, and as shown in Figure 5, includes a CPU 501, a ROM 502, a RAM 503, a HD 504, a HDD controller 505, a display 506, an external device connection I / F 508, a network I / F 509, a bus line 510, a keyboard 511, a pointing device 512, a DVD-RW drive 514, and a media I / F 516.
[0030] The CPU 501 controls the overall operation of the communication management device 50A. The CPU 501 is a computing device that realizes each function of the communication management device 50A by loading programs or data stored in the ROM 502 or HD 504, etc., onto the RAM 503 and executing the processing. The ROM 502 is a non-volatile memory that stores programs used to run the CPU 501, such as an IPL. The RAM 503 is a volatile memory used as a work area for the CPU 501. The HD 504 stores various data such as programs. The HDD controller 505 controls the reading and writing of various data from and to the HD 504 under the control of the CPU 501. The display 506 displays various information such as a cursor, menus, windows, characters, or images. The external device connection I / F 508 is an interface for connecting various external devices. In this case, the external device is, for example, a USB memory. The network I / F 509 is an interface for data communication using the communication network 5. The bus line 510 is an address bus or a data bus for electrically connecting the components such as the CPU 501 shown in FIG.
[0031] The keyboard 511 is a type of input means having multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 512 is a type of input means for selecting or executing various instructions, selecting a processing target, moving a cursor, etc. The DVD-RW drive 514 controls reading and writing of various data from a DVD-RW 513, which is an example of a removable recording medium. Note that the removable recording medium is not limited to a DVD-RW, and may be a DVD-R or a Blu-ray Disc, etc. The media I / F 516 controls reading and writing (storing) of data from a recording medium 515, such as a flash memory.
[0032] Each of the above programs may be recorded as an installable or executable file on a computer-readable recording medium and distributed. Examples of the recording medium include a CD-R (Compact Disc Recordable), a DVD (Digital Versatile Disk), a Blu-ray Disc, an SD card, and a USB memory. The recording medium may also be provided domestically or internationally as a program product. For example, the display device 10 realizes the display control method according to the present invention by executing the program according to the present invention.
[0033] Overview Next, the relationship between the shared area shared among display devices 10A1, 10B, and 10C and the display screens displayed on each of display devices 10A1, 10B, and 10C will be described with reference to Fig. 6. Fig. 6 is a schematic diagram illustrating the relationship between the shared area shared by multiple display devices and the display screens displayed on the display devices.
[0034] In FIG. 6, display devices 10A1, 10B, and 10C share objects drawn on their respective display units as a shared area to hold events such as remote conferences. The shared area is a handwriting input area that can be shared by multiple users and allows 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 mutually transmitting and receiving handwriting input data for displaying objects drawn on display devices 10A1, 10B, and 10C.
[0035] The shared area is an expandable area with no limitations on the area available for handwriting input. The shared area includes, for example, a so-called infinite canvas or finite canvas. That is, the shared area is larger than the area that can be displayed on the display screen of the display device 10. Therefore, as shown in FIG. 6, the display devices 10A1, 10B, and 10C each display at least a portion of the shared area on their display screens. By displaying only a portion of the shared area rather than the entire shared area, the display devices 10A1, 10B, and 10C can facilitate handwriting input by the user and facilitate understanding of the contents of the handwritten object. Furthermore, the display devices 10A1, 10B, and 10C can display different areas of the shared area, allowing the user to view a desired area during an event.
[0036] When multiple users collaborate using a shared area, writing in the same area at the same time can lead to overlapping annotations. If annotations unintentionally overlap, it becomes necessary to move or erase one of the annotations. However, if both annotations can be manipulated, this operation becomes cumbersome, reducing the efficiency of collaborative work. To prevent unintentional editing in such collaborative work among multiple users, users are restricted from using a large area for writing, or it is difficult for users to write using other users' annotations. Furthermore, users are unable to individually set editing permissions for handwritten input data entered on the handwriting input screen, and the process for setting editing restrictions is complicated, resulting in issues with user operability.
[0037] Therefore, the screen sharing system 1 can set permissions such as editing permissions and viewing permissions for other users for handwritten input data (written content) entered by a user, and allows only authorized users to perform editing operations or viewing. The screen sharing system 1 restricts unauthorized users from editing or viewing the entered handwritten input data. This allows the screen sharing system 1 to individually set user permissions for the entered handwritten input data. Furthermore, the screen sharing system 1 prevents inadvertent editing, while allowing a wide range of users to use the handwritten input screen without worrying about the operations of other users.
[0038] Furthermore, in the screen sharing system 1, data may be input using an input means such as a keyboard instead of or in addition to handwritten input data. FIG. 7 illustrates 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 (handwriting input area) as shown in FIG. 6. At this time, a predetermined text editor area 1111 is displayed on the display screen 100A of the display device 10A1. Note that this text editor may 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 FIG. 7 is displayed at an arbitrary position on the display screen 100A. Specifically, the CPU 201 illustrated in FIG. 3 may control the GPU 212 and the display controller 213 to read a virtual keyboard template previously stored in a predetermined area of the ROM 202 or the SSD 204, and display the virtual keyboard 1121 in an arbitrary area of the display 280.
[0039] Subsequently, when the user of display device 10A1 keys in a desired word, character string, number, sentence, etc. via virtual keyboard 1121, the desired word, character string, number, sentence, etc. may be entered onto a cursor in text editor area 1111 in synchronization with the timing of the input. Alternatively, a configuration may be adopted in which, when a predetermined selection is accepted by operating setting button 150 displayed on display screen 100A, activation of predetermined text editor area 1111 and display of virtual keyboard 1121 are performed in parallel. Data entry using an input means such as a keyboard described above is not limited to site A where display device 10A1 is used, and may be realized, for example, at another site C shown in FIG. 1.
[0040] 6 are connected by wire or wirelessly, a keyboard on display device 10B may function as an input means for text editor area 1111, instead of virtual keyboard 1121 shown in FIG. 7. Specifically, each key on the keyboard provided on display device 10B may be linked (synchronized) with each key on virtual keyboard 1121 displayed on display device 10A1, so that a desired word, character string, number, sentence, etc. input on display device 10B may be input onto a cursor in text editor area 1111 displayed on display device 10A1. By providing a UI (User Interface) such as the one described above, a user may be allowed to set a predetermined editing authority.
[0041] ●Function configuration Next, the functional configuration of the screen sharing system according to the first embodiment will be described with reference to Fig. 8 to Fig. 13. Fig. 7 is a diagram showing an example of the functional configuration of the screen sharing system. Fig. 8 shows devices or terminals shown in Fig. 1 that are related to the processing or operation described below.
[0042] ○Functional configuration of the display device○ First, the functional configuration of display devices 10A1, 10B, and 10C will be described using FIG. 8. Because display devices 10A1, 10B, and 10C have similar functions, the functions of display device 10 will be described here. Display device 10 has a transmitting / receiving unit 11, a receiving unit 12, a display control unit 13, a determining unit 14, a shared area generating unit 15, a screen data generating unit 16, a setting unit 17, an editing restriction unit 18, a non-sharing notifying unit 19, a viewing request notifying unit 21, an editing authority request notifying unit 22, a recommendation notifying unit 23, a selecting unit 24, a detecting unit 25, an external device communication unit 26, and a storing / reading unit 29. Each of these units is a function or means realized by any of the components shown in FIG. 3 or FIG. 4 operating in accordance with an instruction from CPU 201 in accordance with a program loaded from SSD 204 onto RAM 203, or an instruction from CPU 301 in accordance with a program loaded from HD 304 onto RAM 303. The display device 10 also has a storage unit 1000 constructed by the ROM 202, SSD 204, or USB memory 230 shown in FIG. 3, or the ROM 302, HD 304, or recording medium 321 shown in FIG.
[0043] The transmission / reception unit 11 is mainly realized 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 to and from other devices or terminals via the communication network 5.
[0044] The accepting unit 12 is realized mainly by the processing of the CPU 201 on the contact sensor 214 and the electronic pen controller 216, or the processing of the CPU 301 on the pointing device 312 or the touch panel 309, and accepts various inputs from the user.
[0045] The display control unit 13 is mainly realized by the processing of the CPU 201 on the display controller 213 or the processing of the CPU 301, and displays drawn images on the display 280 or the display 306, or 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), thereby displaying various screens drawn by the API (Application Programming Interface) provided by the OS on the display 280 or the display 306.
[0046] The determination unit 14 is mainly realized by the processing of the CPU 201 or the CPU 301, and performs various determinations. The shared area generation unit 15 is mainly realized by the processing of the CPU 201 or the CPU 301, and generates a shared area that can be shared with other display devices 10 and displayed.
[0047] The screen data generation unit 16 is mainly realized by the processing of the CPU 201 or the CPU 301 and generates screen data constituting the shared area. The screen data generation unit 16 generates handwritten input data and an image of an object based on the handwritten input accepted by the accepting unit 12. The screen data generation unit 16 also generates an image of an object based on the handwritten input data received by the transmitting / receiving unit 11. The screen data generation unit 16 performs, for example, a process of converting an object obtained by a user's handwritten input on a display into coordinate data. For example, when a display device 10 at a given 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 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 indicating the execution history of executed events.
[0048] The setting unit 17 is mainly realized by the processing of the CPU 201 or the CPU 301, and sets various permissions of other users who use other display devices 10 for handwritten input data input by a user who uses the display device 10. For example, the setting unit 17 sets editing permissions of other users for handwritten input data input by a user who uses the display device 10. Furthermore, the setting unit 17 sets viewing permissions of other users for handwritten input data input by a user who uses the display device 10. Furthermore, the setting unit 17 sets editing permissions of users who use the display device 10 for handwritten input data input by other users who use other display devices 10.
[0049] Editing restriction unit 18 is mainly realized 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 authority, based on the authority information set by setting unit 17. Furthermore, for example, if the editing restriction unit 18 does not have editing authority for the handwritten input data entered by other users, it displays an editing restriction notice indicating that the other users do not have editing authority on the display screen. Here, editing refers to selecting, inputting, adding, changing, erasing, enlarging, reducing, moving, or the like, an image, text, or handwritten input data displayed on the display screen of display device 10, in accordance with an input operation accepted by accepting unit 12.
[0050] The non-sharing notification unit 19 is mainly realized by processing of the CPU 201 on the display controller 213 or processing of the CPU 301, and displays a non-sharing notification on the display screen indicating that 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 realized by processing of the CPU 201 on the display controller 213 or processing of the CPU 301, and displays a viewing request notification on the display screen indicating that a viewing request for handwritten input data entered by a user using the display device 10 has been sent from another display device 10.
[0052] The editing authority request notification unit 22 is mainly realized by processing of the CPU 201 on the display controller 213 or processing of the CPU 301, and displays an editing authority request notification on the display screen indicating that a request for editing authority for handwritten input data entered by a user using the display device 10 has been sent from another display device.
[0053] The recommendation notification unit 23 is mainly realized by processing of the CPU 201 on the display controller 213 or processing of the CPU 301, and when handwritten input data entered by a user using the display device 10 overlaps with second handwritten input data entered by another user using another display device 10, an authority change recommendation notification recommending a change in editing authority is displayed on the display screen.
[0054] The selection unit 24 is mainly realized by the processing of the CPU 201 or the CPU 301, and selects handwritten input data to be edited for each user who inputs the handwritten input data.
[0055] The detection unit 25 is mainly realized by the processing of the CPU 201 or the CPU 301, and detects the writing pressure applied to the display screen that serves as the handwriting input screen.
[0056] The external device communication unit 26 is realized by processing of the CPU 201 on the external device connection I / F 206 or processing of the CPU 301 on the external device connection I / F 307, and accepts input of various data or information from external devices connected to the display device 10.
[0057] The storage / readout unit 29 is mainly realized by the processing of the CPU 201 or CPU 301 , and stores various data (or information) in the storage unit 1000 and reads out various data (or information) from the storage unit 1000 .
[0058] ○Functional configuration of communication management device○ Next, the functional configuration of the communication management device 50A will be described with reference to Fig. 7. The communication management device 50A has a transmission / reception 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 / readout unit 59. Each of these units is a function or means realized when any of the components shown in Fig. 5 operates in response to an instruction from the CPU 501 in accordance with a program for the communication management device that has been loaded from the HD 504 onto the RAM 503. The communication management device 50A also has a storage unit 5000 constructed using the ROM 502, HD 504, or recording medium 515 shown in Fig. 5.
[0059] The transmitting / receiving unit 51 is mainly realized by the processing of the CPU 501 for the network I / F 509, and transmits and receives various data or information to and from other devices or terminals via the communication network 5.
[0060] The authentication unit 52 is realized by the processing of the CPU 501, and performs authentication processing for users who participate in an event using the display device .
[0061] Event information generating unit 53 is mainly realized by the processing of CPU 501, and generates event information relating to events executed by the user.
[0062] The shared area generating unit 54 is realized mainly by the processing of the CPU 501, and generates a shared area that can be shared among a plurality of display devices 10 and displayed.
[0063] The event information management unit 55 is mainly realized by the processing of the CPU 501 , and manages the event information generated by the event information generation unit 53 .
[0064] The authority information management unit 56 is mainly realized by the processing of the CPU 501, and manages authority information indicating various authorities of other users with respect to handwritten input data input by a predetermined user.
[0065] The storage / readout unit 59 is mainly realized by the processing of the CPU 501 , and stores various data (or information) in the storage unit 5000 and reads out various data (or information) from the storage unit 5000 .
[0066] User information management table Fig. 9 is a conceptual diagram showing an example of a user information management table. The user information management table manages user information for identifying users participating in an event. A user information management DB 5001 configured by the user information management table shown in Fig. 9 is constructed in the storage unit 5000. This user information management table manages user information associated with a user ID, user name, and password for identifying a user, as well as an email address, which is an example of destination information indicating the user's destination.
[0067] Event information management table Fig. 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 carried out by users. An event information management DB 5002 configured using the event information management table shown in Fig. 10 is constructed in the storage unit 5000. This event information management table manages event information that associates an event ID and event name that identify the event, the date and time the event is held, participating users who will participate in the event, and the storage locations of various event files generated by the event.
[0068] Among these, the event start date and time indicates, for example, the date and time the event file was last updated. The event start date and time may be the date and time the event was first held, or may store the start date and time and end date and time of the event, respectively. The participating users indicate the usernames of the users who participated in the event. The file storage location indicates information about the storage destination where various event files are stored. The file storage location may be an internal data path of the communication management device 50A, or an external URL (Uniform Resource Locator) or URI (Uniform Resource Identifier) of the communication management device 50A. The event files stored in the file storage location include, for example, the metadata file 500, the handwritten input data file 550, and shared area data for the event generated by the shared area generation unit 54, etc.
[0069] Metadata file FIG. 11 is a diagram showing an example of a metadata file. The metadata file 500 shown in FIG. 11 is an event file generated when an event is executed. The metadata file 500 shows, as metadata, a display screen operation history for each user, such as moving, enlarging, or reducing the display area. The metadata file 500 shown in FIG. 11 includes the event name (Name), the start time (Start) and end time (End) of the event, and an operation history (Operation Log) for each user. The operation history includes, as the display area (ViewArea) for each user, area information indicating the coordinate position (X, Y) and size (Width, Height) of the display area, as well as display history data indicating the display time (Time).
[0070] The example shown in FIG. 11 indicates that an event named "Theme A Regular Event 1" was held from 1:00 PM to 3:00 PM on January 15, 2021. The example also indicates that participant "userA" first displayed an area in the shared area with a width of 100 pixels and a height of 80 pixels, with the upper left point at (X,Y)=(10,310), for 100 seconds, and then moved to the area at (X,Y)=(100,210). The area last displayed by "userA" was the area at (X,Y)=(150,130). The area last displayed by "userB" was the area at (X,Y)=(105,1200), and the area last displayed by "userC" was the area at (X,Y)=(130,1300). The metadata file 500 stores such operation history for each user. Note that, although the metadata file 500 shown in FIG. 10 is an example in a data format of JSON (JavaScript Object Notation), the data format of the metadata file 500 is not limited to this.
[0071] Handwritten input data file FIG. 12 is a diagram illustrating an example of a handwriting input data file. The handwriting input data file 550 illustrated in FIG. 12 is an event file generated during an executed event. The handwriting input data file 550 indicates, as object data, the operation history of handwritten objects, such as strokes or stamps. The handwriting input data file 550 illustrated in FIG. 12 includes the background color (BackgroundColor) of the shared area and object data (Objects) indicating the input history of handwritten objects. The object data includes the object type (Type), detailed data (Data) indicating the content of the object, the user name (User) who input the object, and the input date and time (Data). The object type is, for example, a stroke (Stroke) or a stamp (Stamp). Furthermore, if the object type is a stroke, the detailed data information includes data on the stroke's coordinate position locus (Point), line thickness (Thin), and line color (Color). Furthermore, if the object type is a stamp, the detailed data information includes, for example, the stamp's coordinate position (Point), size (Size), and image file (Image) data.
[0072] The example shown in FIG. 12 represents a shared area with a white background color, where "userA" input a 5-pixel-thick black stroke from (X,Y)=(10,10) to (X,Y)=(30,30) at 2021 / 01 / 15 13:32. It also represents a subsequent input by "userB" of a 20-pixel x 20-pixel image file "Circle.jpg" at 2021 / 01 / 15 13:40, with (X,Y)=(100,200) at the top left. The handwriting input data file 550 stores such object data for each input object. While the handwriting input data file 550 shown in FIG. 12 is an example of a JSON-formatted data file, the data format of the handwriting input data file 550 is not limited to this. In addition, the object format is not limited to strokes or stamps, but may include text in which the strokes have been processed using an OCR (Optical Character Reader) to represent symbols such as letters or numbers, system-generated characters such as dates or times, predetermined shapes such as triangles, stars, or circles, or lines such as arrows, line segments, or Bezier curves.
[0073] The metadata file 500 and the handwriting input data file 550 may be configured to be stored in the storage unit 1000 of the display device 10 participating in the event, along with the communication management device 50A. In this case, the display device 10 stores history data including metadata indicating the operation history of the user using the display device 10 and handwriting input data in the storage unit 1000. In addition, in the case of a display device 10 having a server function, the storage unit 1000 may be configured to store metadata including the operation history of all users participating in the event and handwriting input data.
[0074] ○Authorization information management table FIG. 13 is a conceptual diagram showing an example of an authority information management table. The authority information management table manages authority information indicating various authorities of other users for handwritten input data entered by a specific user. An authority information management DB 5003 configured by the authority information management table shown in FIG. 13 is constructed in the storage unit 5000. This authority information management table manages, for each event ID that identifies an event, authority information that associates a user ID and user name that identify the user who entered the handwritten input data, as well as various authorities for the handwritten input data, such as editing authority and viewing authority. The authority information managed in the authority information management DB 5003 is shared as common authority information by each display device 10 used by users participating in the event, and is stored in the storage unit 1000 of the display device 10 during the event.
[0075] Fig. 13 shows a setting state in which, for example, no user has editing authority (null) for handwritten input data entered by "userA," and only "userB" has viewing authority. Fig. 13 also shows a setting state in which, for example, only "userC" has editing authority and viewing authority for handwritten input data entered by "userB." Fig. 12 also shows a setting state in which, for example, no user has editing authority and viewing authority for handwritten input data entered by "userC."
[0076] Processing or operation of the embodiment ○Processing at the start of an event○ Next, the processing or operation of the screen sharing system according to the first embodiment will be described with reference to Figs. 14 to 40. In the following description, processing will be described using the display device 10A1 used by user A and the display device 10B used by user B, but similar processing is also performed on the display device 10C used by user C shown in Fig. 1. First, the display screen displayed on the display device 10 at the start of an event will be described with reference to Figs. 14 and 15. Fig. 14 is a sequence diagram showing an example of screen display processing at the start of an event.
[0077] First, user A operates a predetermined input means of display device 10A1, causing reception unit 12A of display device 10A1 to receive input of a user ID and password (step S11). Next, transmission / reception unit 11A transmits login request information to communication management device 50A (step S12). This login request information includes the user ID and password received in step S11. As a result, transmission / reception unit 51 of communication management device 50A receives the login request information transmitted by display device 10A1.
[0078] Next, authentication unit 52 of communication management device 50A performs user authentication using the user ID and password received in step S12 (step S13). Specifically, storage / readout unit 59 searches user information management DB 5001 (see FIG. 9) for a pair of user ID and password corresponding to the pair of user ID and password received in step S12. If a corresponding pair is found, authentication unit 52 determines that requesting user A is a valid user. If a corresponding pair is not found, authentication unit 52 determines that requesting user A is an invalid (illegitimate) user. If the requesting user A is invalid, transmitting / receiving unit 51 notifies display device 10A1 that the requesting user A is invalid; however, here we will continue to explain the case where the requesting user A is valid.
[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 is information indicating an event ID that identifies the event, the event name, the start time of the event, and the storage location of an event file generated for the event. The event information management unit 55 stores the generated event information in the event information management DB 5002 (see FIG. 10) via the storage / readout unit 59.
[0080] Furthermore, the authority information management unit 56 generates authority information indicating the editing authority and viewing authority for each user for the handwritten input data entered during the event (step S16). For example, the authority information is set so that, at the start of the event, all users have the editing authority and viewing authority for the handwritten input data of other users. The authority information management unit 56 stores the generated authority information in the authority information management DB 5003 (see FIG. 13) via the storage / readout unit 59.
[0081] Next, the transmitter / receiver 51 transmits the shared area data generated in step S14, the event information generated in step S15, and the authority information generated in step S16 to the display device 10A1 (step S17). As a result, the transmitter / receiver 11A of the display device 10A1 receives the shared area data, event information, and authority information transmitted by the communication management device 50A.
[0082] Then, the display control unit 13A of the display device 10A1 causes the display unit (for example, the display 280 or the display 306) to display the shared area 700 configured using the shared area data received in step S17 (step S18). FIG. 15 is a diagram showing an example of a shared area. The shared area 700 shown in FIG. 15 is a handwriting input screen that is shared and displayed with other display devices 10 during an event. The shared area 700 is in a state in which multiple objects have been input by users participating in the event inputting handwriting onto the display screen. Because 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 a display area on the display screen of the display device 10. Users participating in the event can display a desired area of the shared area 700 during the event to input and view objects by handwriting.
[0083] Furthermore, similar to the processing by display device 10A1, user B operates a predetermined input means of display device 10B, causing reception unit 12B of display device 10B to receive input of user information including a user ID and password (step S19). Next, transmission / reception unit 11B transmits login request information to communication management device 50A (step S20). This login request information includes the user ID and password received in step S19. As a result, transmission / reception unit 51 of communication management device 50A receives the login request information transmitted by 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 processing in step S13 (step S21). Next, when the authentication unit 52 has completed authentication of user B, the event information management unit 55 reads the event information generated in step S15 from the event information management DB 5002 via the storage / readout unit 59 (step S22). Furthermore, the authority information management unit 56 reads the authority information generated in step S16 from the authority information management DB 5003 via the storage / readout unit 59 (step S23).
[0085] Next, the transmitter / receiver 51 transmits the shared area data generated in step S14, the event information read in step S22, and the authority information read in step S23 to the display device 10B (step S24). As a result, the transmitter / receiver 11B of the display device 10B receives the shared area data, event information, and authority information transmitted by the communication management device 50A. Then, the display control unit 13B of the display device 10B causes the display unit to display the shared area 700 configured by the received shared area data (step S25), similar to the processing of the display device 10A1 in step S17.
[0086] In this way, the screen sharing system 1 allows the shared area 700 that constitutes the handwriting input screen to be shared and displayed among a plurality of display devices 10 participating in the event.
[0087] ○Permission setting process○ Next, a process for setting editing rights or viewing rights of other users for handwritten input data input by a user will be described with reference to Fig. 16 to Fig. 19. Fig. 16 is a sequence diagram showing an example of a process for setting rights for other users.
[0088] First, the reception unit 12A of the display device 10A1 receives the selection of the setting button 150 displayed on the display screen 100A displayed on the display unit (step S51). FIG. 17(A) is a diagram showing an example of the display screen. The display screen 100A shown in FIG. 17(A) is a screen displayed on the display unit of the display device 10A1, and displays at least a part of the shared area 700 shown in FIG. 15. The display screen 100A also includes the setting button 150 that is pressed when setting authority. The reception unit 12A receives the selection of the setting button 150 by, for example, an input operation by the user A on the display screen 100A.
[0089] Next, when the display control unit 13A receives the selection of the setting button 150 in step S51, the display control unit 13A displays an authority setting screen 400 on the display screen 100A (step S52). FIG. 17B is a diagram showing an example of the authority setting screen. The display screen 100A shown in FIG. 17B displays an authority setting screen 400 that allows other users to set editing authority or viewing authority for handwritten input data entered by user A. The authority setting screen 400 includes an edit authority setting button 410 for setting editing authority for other users for handwritten input data entered by user A, and a user information input area 415 for inputting users who are not restricted from editing the handwritten input data entered by user A. The authority setting screen 400 also includes a view authority setting button 430 for setting view authority for other users for handwritten input data entered by user A, and a user information input area 435 for inputting users who are not restricted from viewing the handwritten input data entered by user A.
[0090] In the example of FIG. 17(B), users other than user B are restricted from editing the handwritten input data entered by user A. Also, in the example of FIG. 17(B), no restrictions are placed on viewing the handwritten input data entered by user A, and all users are able to view the handwritten input data entered by user A. Users for whom editing or viewing is not restricted can edit or view user A's handwritten input data (writings). On the other hand, users for whom editing or viewing is restricted cannot edit or view user A's handwritten input data (writings). User A can set the authority for his or her own writings by performing an input operation on authority setting screen 400.
[0091] 18, a user or user group selected by user A from other users or user group candidates composed of multiple users searched from the list of event participants is set in user information input area 415 of authority setting screen 400. When a user group is set, all users belonging to that user group are targeted. Note that a user or user group may be set in user information input area 415 by searching through direct input into user information input area 415. The same applies to user information input area 435. Also, although FIGS. 17(B) and 18 have described examples in which users who are not restricted are input in user information input area 415 or user information input area 435 when editing or viewing is restricted, a configuration in which restricted users are input when editing or viewing is permitted may also be used.
[0092] Next, when user A performs a predetermined input operation on the authority setting screen 400, the setting unit 17A sets the authority of other users for the handwritten input data entered by user A (step S53). The authority setting changed by the setting unit 17A is stored in the storage unit 1000A as authority information for the event being executed. Then, the setting unit 17A generates setting change data related to the authority setting changed in step S53 (step S54). The setting change data is generated, for example, in a json data format, and is generated in the format of {"authority":[{"userA":[{"edit":[null],"view":["userB","userC"]}]}]}. Specifically, the setting unit 17A specifies the user who will change the setting with ""userA"", and specifies the users who will be restricted from viewing and editing with ""edit"" and ""view"", respectively.
[0093] Then, the transmitter / receiver 11A transmits the setting change data generated in step S54 to the communications management device 50A (step S55). This setting change data includes an event ID that identifies the event being executed and authority information that indicates the authority set in step S53. As a result, the transmitter / receiver 51 of the communications management device 50A receives the setting change data transmitted by the display device 10A1.
[0094] Next, the authority information management unit 56 of the communications management device 50A searches the authority information management DB 5003 (see FIG. 13) using the event ID included in the setting change data received in step S55 as a search key, and updates the authority information associated with the same event ID as the received event ID to the received authority information (step S56). Furthermore, the transmission / reception unit 51 transmits (transfers) the setting change data received in step S55 to the display device 10B (step S57). As a result, the transmission / reception unit 11B of the display device 10B receives the setting change data transmitted by the display device 10A1.
[0095] The setting unit 17B of the display device 10B changes the authority setting based on the authority information included in the setting change data received in step S57 (step S58). The authority setting changed by the setting unit 17B is stored in the storage unit 1000B as authority information for the event being executed.
[0096] In this way, 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 setting change data, allowing permission settings for handwritten input data at an event to be shared among users participating in the event. Furthermore, 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 setting. As described 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. In this way, a configuration in which another device such as the communication management device 50A acts as an intermediary between the display devices may be used.
[0097] Furthermore, display device 10A1 can prevent other users from viewing or editing the writing or editing process by setting the viewing and editing rights of other users for the handwritten input data entered by user A. User A can enable other users to view and edit the writing by, for example, removing the restriction when the work is completed, thereby flexibly switching the content of the handwritten input data shared with other users.
[0098] Here, another example of the permission setting screen 400a will be described with reference to FIG. 19. FIG. 19 illustrates another example of the permission setting screen. The permission setting screen 400a shown in FIG. 19 is a screen on which permission for handwritten input data entered by user A can be set for each user. The permission setting screen 400a includes an editing permission setting area 410a for setting editing permission for other users for handwritten input data entered by user A, and a viewing permission setting area 430a for setting viewing permission for other users for handwritten input data entered by user A. The editing permission setting area 410a also includes a batch setting button 420 for setting editing permission for all users collectively, and individual setting buttons 421 and 422 for setting editing permission for each user. The viewing permission setting area 430a also includes a batch setting button 440 for setting viewing permission for all users collectively, and individual setting buttons 441 and 442 for setting viewing permission for each user. 19, all users are restricted from editing the handwritten input data of user A, and only user B is restricted from viewing the handwritten input data of user A. Note that, similar to the authority setting screen 400, the authority 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 FIG. 17(A).
[0099] If there is a main user, such as an administrator or owner of the event, among multiple users participating in the event, the permission setting screen 400, 400a may be configured to be accessible only to the main user, allowing the main user to set various permissions. In this case, for example, in an event such as a class in which a teacher (the main user) and multiple students (other users) are participating, the teacher can restrict the students' viewing and editing. In other words, when editing and viewing are restricted, the students' writings are not shared with other students and can only be viewed by the teacher. In this way, the teacher (the main user) can, for example, remove the viewing restrictions to allow students to share and view their writings, while maintaining the editing restrictions to prevent other students from inadvertently editing.
[0100] ○ Display of handwritten input data ○ Next, a process for displaying handwritten input data input by other users on a display screen in accordance with the viewing authority of each user will be described with reference to Fig. 20 to Fig. 27. Fig. 20 is a flowchart showing an example of a process for displaying handwritten input data input by other users. Fig. 20 illustrates a process for receiving handwritten input data input to the display device 10A1 used by user A on the display device 10C used by user C. However, the combination of display devices 10 that transmit and receive handwritten input data is not limited to this, and similar processes are performed for other combinations of display devices 10 used by users participating in an event.
[0101] First, transmitter / receiver 11C of display device 10C receives the handwritten input data transmitted by display device 10A1 (step S71). This handwritten input data is handwritten input data input by user A. As shown in Fig. 21(A), display screen 100A of display device 10A1 displays the handwritten input data input by user A.
[0102] Next, the determination unit 14C determines whether or not the user A who input the received handwritten input data has a viewing authority for the handwritten input data received in step S71 (step S72). Specifically, the determination unit 14C refers to the authority information set by the setting unit 17C and determines whether or not the user A has a viewing authority for the received handwritten input data. If the determination unit 14C determines that the user A has a viewing authority for the received handwritten input data (YES in step S72), the process proceeds 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 the user A does not have the permission to view the received handwritten input data (NO in step S72), the determination unit 14C shifts the process to step S74. Then, the display control unit 13C restricts the viewing of the received handwritten input data by not displaying it on the display screen 100C (step S74). In addition, the display control unit 13C displays a viewing restriction notice on the display screen 100C indicating that viewing of the handwritten input data entered by the user A is restricted (step S75).
[0104] 21(B) shows display screen 100B of display device 10B as an example of a case where user A has permission to view the handwritten input data entered. Display screen 100B shown in FIG. 21(B) displays the same handwritten input data as display screen 100A shown in FIG. 21(A) because user B has permission to view the handwritten input data entered by user A. Display screen 100B also displays user display image 170, which identifies the user who entered the displayed handwritten input data, together with the handwritten input data.
[0105] 21(C) shows a 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 C. Since user C does not have permission to view the handwritten input data entered by user A, the handwritten input data shown on display screen 100A in FIG. 21(A) is not displayed on display screen 100C shown in FIG. 21(C). This restricts user C's viewing of the handwritten input data entered by user A.
[0106] In this way, when the display device 10 receives handwritten input data that has been input on another display device 10, it checks whether the user has permission to view the received handwritten input data, and displays the handwritten input data on the display screen only if the user has permission to view the data. This allows the screen sharing system 1 to prevent users who do not have permission to view the content written by the user. Furthermore, if the display device 10 does not have permission to view the received handwritten input data, it displays a viewing restriction notice, which will be described below, on the display screen.
[0107] Here, various notifications that are displayed on the display screen when access restrictions are imposed on certain handwritten input data will be described with reference to Fig. 22 to Fig. 24. Fig. 22(A) is a diagram showing an example of a non-sharing notification, and Fig. 22(B) is a diagram showing an example of an access restriction notification.
[0108] Display screen 100A shown in Fig. 22(A) is a display screen displayed on display device 10A1 as an example in which the viewing of input handwritten input data by other users (other display devices) is restricted. Display screen 100A shown in Fig. 22(A) includes non-sharing notification 350 indicating that the handwritten input data input by user A is not shared with other users. Non-sharing notification unit 19A of display device 10A1 displays non-sharing notification 350 on display screen 100A when any of the other users participating in the event does not have viewing authority for the input handwritten input data.
[0109] Display screen 100C shown in Fig. 22(B) is a display screen displayed on display device 10C as an example of a case where viewing of handwritten input data entered by user A is restricted. Display screen 100C shown in Fig. 22(B) includes a viewing restriction notice 450 indicating that viewing of the handwritten input data entered by user A is restricted. This viewing restriction notice 450 is displayed on display screen 100C of display device 10C, for example, in the processing of step S75.
[0110] If the writing contents of other users are not shared because the user does not have the viewing authority, the user who inputted the writing (e.g., user A) will not know whether the writing contents are being shared, and the restricted user (e.g., user C) will not know what work the other users are doing. Therefore, the screen sharing system 1 displays a notice on the display screen (e.g., display screen 100A) of the user who has restricted viewing that the handwritten input data (writing contents) is not being shared with other users, and displays a notice on the display screen (e.g., display screen 100C) of the user whose viewing is restricted that another user is entering (writing) handwritten input data. In this way, the 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] 23 and 24 show another example of a non-sharing notification displayed on the display screen 100A. The non-sharing notification 360 displayed on the display screen 100A shown in FIG. 23 includes an authority edit button 365 that is pressed when editing the authority of other users for user A's handwritten input data. The non-sharing notification unit 19A of the display device 10A1 displays the non-sharing notification 360 on the display screen 100A when any of the other users participating in the event does not have viewing authority for the entered handwritten input data. When user A presses the authority edit button 365, the display control unit 13A of the display device 10A1 displays, for example, an authority setting screen 400 shown in FIG. 18, etc. This allows the display device 10A1 to allow user A to change the authority of other users.
[0112] The non-sharing notification 370 displayed on the display screen 100A shown in FIG. 24 includes a viewing permission button 375 that is pressed to permit viewing by other users who have been restricted from viewing the data. The non-sharing notification unit 19A of the display device 10A1 displays the non-sharing notification 370 on the display screen 100A when any of the other users participating in the event does not have viewing permission for the input handwritten input data. When user A presses the viewing permission button 375, the setting unit 17A of the display device 10A1 changes the viewing permission for the other users who have been restricted from viewing user A's handwritten input data so that they are permitted to view the data. Compared to the non-sharing notification 360 shown in FIG. 23, the non-sharing notification 370 allows the viewing permission to be changed directly from the non-sharing notification 370 without performing permission setting processing using the permission setting screen 400 or the like, thereby simplifying the processing by user A.
[0113] ○ Viewing request processing Next, a process for requesting viewing of handwritten input data whose viewing is restricted will be described with reference to Fig. 25 and Fig. 26. Fig. 25 is a sequence diagram showing an example of a process for requesting viewing of another user. Fig. 25 describes an example in which a display device 10C used by user C, whose viewing of user A's handwritten input data is restricted, makes a request for viewing to display device 10A1 used by user A. However, the combination of display devices 10 that transmit and receive a request for viewing is not limited to this, and similar processing is performed for other combinations of display devices 10 used by users participating in an event.
[0114] The display control unit 13C of the display device 10C displays a viewing restriction notice 480 on the display screen 100C (step S91). Fig. 26(A) is a diagram showing an example of the viewing restriction notice 480. The viewing restriction notice 480 shown in Fig. 26(A) includes a viewing request button 485 that is pressed to request viewing of the handwritten input data that is restricted from viewing.
[0115] Next, the reception unit 12C receives selection of the view request button 485 included in the view restriction notification 480 in response to an input operation by user C (step S92). The transmission / reception unit 11C transmits, to the communication management device 50A, view request information indicating a request to view the restricted handwritten input data of user A (step S93). This view request information includes the user ID of the user to whom the view request is made. In this case, the transmission / reception unit 11C transmits the view request information including the user ID of user A. As a result, the transmission / reception unit 51 of the communication management device 50A receives the view request information transmitted by the display device 10C. Then, the transmission / reception unit 51 of the communication management device 50A transmits (transfers) the view request information transmitted by the display device 10C to the display device 10A1 used by user A, who is the destination of the view request (step S94). As a result, the transmission / reception unit 11A of the display device 10A1 receives the view request information transmitted by the requesting display device 10C.
[0116] Then, when the view request information is received in step S94, view request notifier 21A of display device 10A1 displays, on display screen 100A, view request notification 380 indicating that a view request has been made by user C (step S95).
[0117] Next, the accepting unit 12A of the display device 10A1 accepts various button operations (step S96). FIG. 26(B) is a diagram showing an example of a view request notification 380. The view request notification 380 shown in FIG. 26(B) includes an individual view permission button 381, which is pressed to permit the requesting user C to view the data, an individual view rejection button 382, and a collective view permission button 383, which is pressed to permit all users to view the data. When user A presses the individual view permission button 381 or the collective view permission button 383, the setting unit 17A of the display device 10A1 changes the viewing authority so that the user corresponding to the selected button is permitted to view the handwritten input data of user A. Note that the display device 10A1 may be configured to display an authority setting screen 400, 400a when user A presses the individual view permission button 381 or the collective view 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 the viewing of user A's handwritten input data for the user corresponding to the selected button, and maintains the viewing authority status. In this case, the reason or condition for user A to press the individual viewing rejection button 382 may be, for example, that the viewing request for another user (e.g., user C) who has made the viewing request be rejected at user A's own discretion, taking into account the content of the handwritten input. Furthermore, the viewing request for another user who has made the viewing request may be rejected at user A's own discretion, taking into account the attributes (e.g., department, work, position, etc.) of the other user who has sent the viewing request, the content of the handwritten strokes, etc. Furthermore, the rejection of the viewing request may be determined by the determination unit 14A of the display device 10A1, instead of or in addition to being based on user A's judgment, based on the attributes (e.g., department, work, position, etc.) of the other user who has sent the viewing request, the content of the handwritten strokes, etc. Depending on the result of the determination, the editing authority unit 18A may reject the viewing request from the other user who made the viewing request. Based on the individual viewing rejection information generated by pressing the individual viewing rejection button 382 based on such a determination criterion, the setting unit 17A of the display device 10A1 rejects the viewing of the handwritten input data of user A for the user corresponding to the selected button, and maintains the state of the viewing authority. Note that when the individual viewing rejection button 382 is pressed, transition to the authority setting screen 400, 400a does not necessarily occur.
[0119] Returning to FIG. 25, the transmitter / receiver 11A of the display device 10A1 transmits viewing response information to the communication management device 50A as a response to the viewing request information received in step S94 (step S97). As a result, the transmitter / receiver 51 of the communication management device 50A receives the viewing response information transmitted by the display device 10A1. The transmitter / receiver 51 then transmits the viewing response information received in step S97 to the display device 10C (step S98). As a result, the transmitter / receiver 11C of the display device 10C receives the viewing 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 viewing request (step S99). As a result, the display device 10C can notify the user C of the result of the viewing request.
[0120] Fig. 27(A) is a diagram showing an example of a viewing permission notification. Viewing permission notification 481 shown in Fig. 27(A) includes a confirmation button 486 to be pressed when confirming the notification that viewing by requester user C has been permitted. Fig. 27(B) is a diagram showing an example of a viewing rejection notification. Viewing rejection notification 482 shown in Fig. 27(B) includes a confirmation button 486 to be pressed when confirming the notification that viewing by requester user C has been rejected.
[0121] Editing handwritten input data Next, a process for editing handwritten input data input by other users on the display screen in accordance with the viewing authority of each user will be described with reference to Fig. 28 to Fig. 32. Fig. 28 is a flowchart showing an example of a process for editing handwritten input data input by other users. Fig. 28 illustrates a process for editing handwritten input data input by user A on display device 10A1 used by user A, but the combination of display devices 10 is not limited to this, and similar processes are performed for other combinations of display devices 10 used by users participating in an event.
[0122] First, the accepting unit 12B of the display device 10B accepts an editing operation for the handwritten input data displayed on the display screen 100B by a predetermined input operation on the display screen 100B by the user B (step S101).
[0123] Next, the determination unit 14B determines whether or not the user has editing authority for the handwritten input data that is the target of the editing operation accepted 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 the user has editing authority for user A who inputs the handwritten input data to be edited. When the determination unit 14B determines that the user has editing authority for the handwritten input data to be edited (YES in step S102), the determination unit 14B shifts the process to step S103. Then, the display control unit 13B executes the editing operation for the handwritten input data and displays the edited handwritten input data on the display screen 100B (step S103).
[0124] On the other hand, if determination unit 14B determines that user A does not have the editing authority for the handwritten input data to be edited (NO in step S102), the process proceeds to step S104. Then, edit restriction unit 18B restricts editing of the handwritten input data to be edited (step S104). Furthermore, edit restriction unit 18B displays an edit restriction notice on display screen 100B indicating that editing of the handwritten input data entered by user A is restricted (step S105).
[0125] In this way, when display device 10 receives an editing operation for the displayed handwritten input data, it checks whether or not the user has editing authority for the target handwritten input data, and executes the editing operation only if the user has editing authority. In this way, screen sharing system 1 restricts editing of handwritten input data (written content) by users who do not have editing authority, thereby preventing inadvertent editing of handwritten input data for which the user does not have editing authority. Furthermore, when display device 10 does not have editing authority for the received handwritten input data, it displays an editing restriction notice, which will be described below, on the display screen.
[0126] FIG. 29 illustrates an example of an editing restriction notification. Display screen 100B illustrated in FIG. 29 is a display screen displayed on display device 10B as an example in which editing of handwritten input data entered by user A is restricted. Display screen 100B illustrated in FIG. 29 includes user display images 170a and 170b for identifying the user who entered the handwritten input data and an editing tool 190 used to edit the handwritten input data. Editing tool 190 is, for example, an erasure tool used to erase the handwritten input data. Display screen 100B illustrated in FIG. 29 also includes an editing restriction notification 650 indicating that editing of the handwritten input data entered by user A is restricted. In the example of FIG. 29, editing restriction notification 650 is displayed on display screen 100C of display device 10B when user B attempts to erase the handwritten input data entered by user A using editing tool 190. By displaying editing restriction notification 650 when user B does not have editing authority, display device 10B can allow user B to understand the reason for the inability to edit.
[0127] Editing permission request processing Next, a process for requesting editing authority for handwritten input data for which editing is restricted will be described with reference to Fig. 30 to Fig. 32. Fig. 30 is a sequence diagram showing an example of a process for requesting editing authority from another user. Fig. 30 describes an example in which a request for editing authority is made from display device 10B used by user B, who is restricted from editing handwritten input data of user A, to display device 10A1 used by user A. However, the combination of display devices 10 that transmit and receive the editing authority request is not limited to this, and similar processing is performed for other combinations of display devices 10 used by users participating in an event.
[0128] The editing restriction unit 18B of the display device 10B displays an editing restriction notice 660 on the display screen 100B (step S111). Fig. 31(A) is a diagram showing an example of the editing restriction notice 660. The editing restriction notice 660 shown in Fig. 31(A) includes an editing authority request button 665 that is pressed to request editing authority for handwritten input data that is restricted from being edited.
[0129] Next, the reception unit 12B receives selection of the edit authority request button 665 included in the edit restriction notification 660 in response to an input operation by user B (step S112). The transmission / reception unit 11B transmits, to the communication management device 50A, editing authority request information indicating a request for editing authority for the restricted handwritten input data of user A (step S113). This editing authority request information includes the user ID of the user to whom the editing authority request is made. In this case, the transmission / reception unit 11B transmits the editing authority request information including the user ID of user A. As a result, the transmission / reception unit 51 of the communication management device 50A receives the editing authority request information transmitted by the display device 10B. Then, the transmission / reception unit 51 of the communication management device 50A transmits (transfers) the editing authority request information transmitted by the display device 10B to the display device 10A1 used by user A, who is the destination of the viewing request (step S114). As a result, the transmission / reception unit 11A of the display device 10A1 receives the editing authority request information transmitted by the requesting display device 10B.
[0130] Then, when the editing authority request information is received in step S114, the editing authority request notification unit 22A of the display device 10A1 displays an editing authority request notification 560 on the display screen 100A indicating that an editing authority request has been made by user B (step S115).
[0131] Next, the accepting unit 12A of the display device 10A1 accepts various button operations (step S116). FIG. 31(B) is a diagram showing an example of an editing authority request notification 560. The editing authority request notification 560 shown in FIG. 31(B) includes an individual editing permission button 561, which is pressed to permit editing by the requesting user B, an individual editing rejection button 562, and a collective editing permission button 563, which is pressed to permit editing for all users. When user A presses the individual editing permission button 561 or the collective 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 permitted to edit the handwritten input data of user A. Note that the display device 10A1 may be configured to display the permission setting screen 400, 400a when user A presses the individual editing permission button 561 or the collective editing permission button 563.
[0132] On the other hand, when user A presses the individual editing 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 and maintains the status of the editing authority. In this case, the reason or condition for user A to press the individual editing rejection button 562 may be, for example, that the editing authority request for another user (e.g., user B) who requested editing authority be rejected at user A's own discretion, taking into account the content of the handwritten input. Furthermore, the editing authority request for another user who requested editing authority may be rejected at user A's own discretion, taking into account the attributes (e.g., department, job responsibilities, position, etc.) of the other user who sent the editing authority request, the content of the handwritten strokes, etc. Furthermore, the rejection of the above editing authority request may be determined by the determination unit 14A of the display device 10A1, instead of or in addition to being based on user A's judgment, based on the attributes (e.g., department, job responsibilities, position, etc.) of the other user who sent the editing authority request, the content of the handwritten strokes, etc. Depending on the result of the determination, the editing authority unit 18A may reject the editing authority request for the other user who made the editing authority request. Based on the individual editing rejection information generated by pressing the individual editing rejection button 562 based on such a determination criterion, the setting unit 17A of the display device 10A1 rejects the editing of the handwritten input data of user A for the user corresponding to the selected button, and maintains the state of editing authority. Note that when the individual viewing rejection button 382 is pressed, transition to the authority setting screen 400, 400a does not necessarily occur.
[0133] Returning to FIG. 30, the transmitter / receiver 11A of the display device 10A1 transmits editing authority response information to the communication management device 50A as a response to the editing authority request information received in step S114 (step S117). As a result, the transmitter / receiver 51 of the communication management device 50A receives the editing authority response information transmitted by the display device 10A1. The transmitter / receiver 51 then transmits the editing authority response information received in step S117 to the display device 10B (step S118). As a result, the transmitter / receiver 11B of the display device 10B receives the editing authority 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 editing authority request (step S119). As a result, the display device 10B can notify user B of the result of the editing authority request.
[0134] Fig. 32(A) is a diagram showing an example of an editing authority permission notification. Editing authority permission notification 661 shown in Fig. 32(A) includes a confirmation button 668 that is pressed to confirm the notification that editing authority has been granted to user B, the requester. Fig. 32(B) is a diagram showing an example of an editing authority denial notification. Editing authority denial notification 662 shown in Fig. 32(B) includes a confirmation button 668 that is pressed to confirm the notification that viewing by user B, the requester, has been denied.
[0135] ○Restrict editing of other users' handwritten input data○ Next, a process for setting editing authority for handwritten input data input by another user will be described with reference to Fig. 33 to Fig. 37. Fig. 33 is a flowchart showing an example of editing process for handwritten input data input by another user. Fig. 33 describes a process for setting editing authority for handwritten input data input by another user (e.g., user B) on display device 10A1 used by user A, but similar processes are also performed on other display devices 10 used by users participating in the event.
[0136] First, accepting unit 12A of display device 10A1 accepts an editing operation for handwritten input data displayed on display screen 100A by user A's predetermined input operation on display screen 100A (step S151).
[0137] Next, determination unit 14A determines whether or not editing of the handwritten input data of the user who input the handwritten input data to be edited, which is the target of the editing operation accepted in step S151, is restricted (step S152). When determination unit 14A determines that editing of the handwritten input data of the user who input the handwritten input data to be edited is restricted (YES in step S152), the process proceeds to step S153. Then, display device 10A1 displays a predetermined notice on display screen 100A (step S153). On the other hand, when determination unit 14A determines that editing of the handwritten input data of the user who input the handwritten input data to be edited is not restricted (NO in step S152), the process proceeds to step S154. Then, display control unit 13A executes the editing operation on the handwritten input data, and displays the edited handwritten input data on display screen 100A (step S154).
[0138] Here, the predetermined notification displayed on the display screen 100A in step S153 will be described in detail with reference to FIGS. 34 to 36. FIG. 34 is a diagram showing an example of an editing restriction notification 830 displayed on the display device 10A1 in step S153. The display screen 100A shown in FIG. 34 is a display screen displayed on the display device 10A1 as an example of a case where user A does not have editing authority over the handwritten input data of user B, which is the target of an editing operation performed by user A. The display screen 100A shown in FIG. 34 includes user display images 170a and 170b that identify the users who input the handwritten input data, and displays the handwritten input data input by users A and B. On the display screen 100A shown in FIG. 34, when user A performs an editing operation to erase the handwritten input data input by user B using the editing tool 190, the editing restriction unit 18A displays an editing restriction notification 830 on the display screen 100A, indicating that editing of the handwritten input data input by user B is restricted. This edit restriction notification 830 includes an authority edit button 835 that is pressed when user B's authority for the handwritten input data is to be edited.
[0139] When user A presses the authority edit button 835, the display control unit 13A of the display device 10A1 displays, for example, an authority setting screen 800 shown in FIG. 35. This causes the display device 10A1 to allow user A to change the authority for handwritten input data entered by another user. Note that the display device 10A1 may be configured to release the direct editing restriction when user A presses the authority edit button 835. In this case, the setting unit 17A changes the editing authority for the user who input the corresponding handwritten input data so that user A is permitted to edit.
[0140] As a result, by displaying the edit restriction notification 830 when the user does not have the editing authority, the display device 10A1 can allow the user A to understand, for example, the above-described user attributes (for example, department, work in charge, position, etc.) and the contents of handwritten strokes, etc., as reasons why the user A cannot edit. At the same time, the editing authority for handwritten input data entered by other users can be changed.
[0141] Fig. 35 is a diagram showing an example of an authority setting screen. In addition to the contents of the authority setting screen 400 shown in Fig. 17, the authority setting screen 800 shown in Fig. 35 includes an edit authority setting button 810 for setting edit authority for handwritten input data (writing content) of other users, and a user information input area 815 for inputting users for whom editing by user A is not restricted. In the example of Fig. 35, user A's editing of handwritten input data entered by users other than user C is restricted. The setting unit 17A changes user A's editing authority for writings of other users through an input operation by user A on the authority 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 of other users for one's own writings but also one's own editing permission for other users' writings. This allows the screen sharing system 1 to prevent inadvertent editing of other users' writings. Note that the permission setting screen 800 may be a screen that allows each user to set their own editing permission for other users' handwritten input data, similar to the permission setting screen 400a shown in FIG. 19. Furthermore, as described above, 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 FIG. 17(A).
[0143] Fig. 36 is a diagram showing an example of authority change recommendation notice 850 displayed in step S153. Display screen 100A shown in Fig. 36 is a display screen displayed on display device 10A1 when an editing operation performed by user A overlaps handwritten input data of another user. When overlapping between the editing operation of user A and handwritten input data of user B is detected, recommendation notification unit 23A displays authority change recommendation notice 850, which recommends that user A change his or her authority, on display screen 100A.
[0144] A method for detecting overlap between an editing operation by user A and handwritten input data by user B is, for example, to define a path (trajectory) between the sequence of points (coordinate positions) that make up the object each time a coordinate position (Point) of an object included in the handwritten input data file is added, and detect an overlap of handwritten input data when an intersection of the defined paths is detected. Also, if the object format is a stamp rather than a stroke, an overlap of handwritten input data is detected by detecting whether a sequence of points has been added within the area of the object specified by the coordinate position (Point) and size (Size) of the stamp.
[0145] This permission change recommendation notice 850 includes an edit restriction button 855 that is pressed to restrict user A from editing the input of another user who input the handwritten input data in which overlapping was detected. When user A presses the edit restriction button 855, the setting unit 17A changes the editing authority so that user A's editing of the other user who input the handwritten input data in which overlapping was detected is restricted. Note that display device 10A1 may be configured to display permission setting screen 800 when user A presses edit restriction button 855. In this way, by displaying permission change recommendation notice 850 when overlapping with handwritten input data of another user is detected, display device 10A1 can allow user A to input (write) a new object without affecting the writing of the other user.
[0146] Furthermore, when it is desired to distinguish between writings made by different users as shown in FIG. 36, a configuration may be adopted in which a writing layer capable of handwriting input is distinguished for each user and the writing layers are superimposed to construct the display screen 100A, as shown in FIG. 37. The example of FIG. 37 shows the display screen 100A in which the writing layer of user A containing writings made by user A and the writing layers of other users containing writings made by other users are superimposed and displayed. In this case, the display device 10A1 applies the authority information for each user set by the setting unit 17A to each writing layer of each user. The editing restriction unit 18 restricts users who do not have editing authority from editing the writing layer of a user whose editing is restricted.
[0147] In this way, 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 the handwritten input data entered by other users, thereby preventing inadvertent editing of the writings of other users.
[0148] ○Examples of editing operations○ Next, application examples of editing operations on handwritten input data will be described with reference to Fig. 38 to Fig. 40. First, an example in which an editing target can be selected using an editing tool will be described with reference to Fig. 38 and Fig. 39. Fig. 38 and Fig. 39 are diagrams showing examples of editing operation selection screens.
[0149] Display screen 100 shown in FIG. 38 includes an editing operation selection screen 900 for selecting handwritten input data to be erased. Editing operation selection screen 900 is displayed when a user selects editing tool 190a displayed on display screen 100. Editing tool 190a is, for example, a selection tool used to select handwritten input data to be erased. Editing operation selection screen 900 includes a selection area 901 selected when erasing all input handwritten input data, a selection area 903 selected when erasing only handwritten input data entered by the user, and a selection area 905 selected when erasing only handwritten input data entered by other users. When a user selects one of selection areas 901, 903, or 905, selection unit 24 of display device 10 switches, for example, from a writing mode to a writing content erasure mode and selects handwritten input data to be erased based on the selected conditions. For example, when selection area 901 is selected, all handwritten input data can be selected to be erased, when selection area 903 is selected, only the handwritten input data that the user has input can be selected to be erased, and when selection area 905 is selected, only the handwritten input data that other users have input can be selected to be erased.
[0150] Display screen 100 shown in FIG. 39 includes an editing operation selection screen 910 for selecting handwritten input data to be selected all at once. Editing operation selection screen 910 is displayed when a user selects editing tool 195 displayed on display screen 100. Editing tool 195 is, for example, a selection tool used to select handwritten input data to be edited. Editing operation selection screen 910 includes selection area 911, which is selected when selecting all input handwritten input data, selection area 913, which is selected when selecting only handwritten input data entered by the user, and selection area 915, which is selected when selecting only handwritten input data entered by other users. When a user selects one of selection areas 911, 913, or 915, selection unit 24 of display device 10 switches, for example, from a writing mode to a writing content selection mode and selects the handwritten input data to be selected based on the selected conditions. For example, when selection area 911 is selected, all handwritten input data can be selected as selection targets, when selection area 913 is selected, only handwritten input data that the user has input can be selected as selection targets, and when selection area 915 is selected, only handwritten input data that other users have input can be selected as selection targets.
[0151] In this way, when performing editing operations such as erasing or selecting handwritten input data entered on the display screen 100, the display device 10 can use the desired editing tool 190a, 195 to switch the handwritten input data to be edited for each user who entered the handwritten input data.
[0152] Next, a process of switching editing operations in accordance with the pen pressure input to the display screen 100 will be described with reference to Fig. 40. Fig. 40 is a diagram for explaining an example of switching editing operations based on pen pressure. When a user attempts to erase handwritten input data input to the display screen 100, if the pen pressure on the display screen 100 is weak, only the user's handwritten input data is erased, and if the pen pressure on the display screen 100 is strong, all handwritten input data including handwritten input data of other users is erased.
[0153] FIG. 40(A) illustrates an editing operation performed when the display screen 100 is touched with a weak pen pressure. The detection unit 25 of the display device 10 detects the pen pressure input by the user on the display screen 100. As shown in the left diagram of FIG. 40(A), when the pen pressure detected by the detection unit 25 is weak, the display screen 100 displays a small editing area 180a. Then, when the user performs an operation using the editing tool 190, only the user's own handwritten input data is erased. On the other hand, FIG. 40(B) illustrates an editing operation performed when the display screen 100 is touched with a strong pen pressure. As shown in the left diagram of FIG. 40(B), when the pen pressure detected by the detection unit 25 is strong, the display screen 100 displays a large editing area 180b. Then, when the user performs an operation using the editing tool 190, all handwritten input data, including that of other users, is erased. The size (for example, the length of the radius) of the above-mentioned editing areas 180a and 180b may be changed in proportion to the pen pressure.
[0154] When the detected writing pressure is weak, the display device 10 displays a small erasure circle, such as in the editing area 180a, and erases only the user's own handwritten input data. On the other hand, when the detected writing pressure is strong, the display device 10 displays a large erasure circle, such as in the editing area 180b, and erases all handwritten input data. Here, the writing pressure is detected, for example, using a device capable of writing pressure input, and the writing pressure is acquired as a numerical input of "0 to 1." The detection unit 25 processes the input as weak writing pressure when it first acquires the input, and switches to strong writing pressure when the writing pressure exceeds "0.6." The detection unit 25 switches to weak writing pressure when the writing pressure falls below "0.4." When detecting the writing pressure, the display device 10 may set a writing pressure detection threshold (e.g., "0.6," "0.4," etc.) for each user who performs handwritten input. This is because the writing pressure used when handwriting varies from user to user. In this way, by setting a threshold for detecting pen pressure for each user, it becomes possible for each user to edit handwritten input data according to their intended pen pressure, thereby making it possible to avoid accidental erasure of handwritten input data or situations where handwritten input data cannot be erased even when an attempt is made to do so.
[0155] This allows the display device 10 to switch the handwritten input data to be edited in accordance with the writing pressure input to the display screen 100, which is a handwriting input screen. The editing operation is not limited to erasing the handwritten input data, but may be other editing operations such as selecting handwritten input data. The display device 10 may also be configured to switch the handwritten input data to be edited in accordance with other operation operations such as the contact time on the display screen 100, in addition to the writing 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 for handwritten input data entered by a user, allowing only users with editing permissions to perform editing operations. The screen sharing system 1 can also set viewing permissions for other users for handwritten input data entered by a user, allowing only users with viewing permissions to view the handwritten input data. This allows the screen sharing system 1 to set permissions for handwritten input data entered by each user, preventing inadvertent editing and allowing a wide range of users to use the handwritten input screen without worrying about operations by other users.
[0157] Furthermore, the screen sharing system 1 allows users to set permissions for handwritten input data by displaying permission setting screens 400, 400a, and 800, which allow permission setting for each user, on the display device 10. This allows the screen sharing system 1 to improve the operability of permission setting for users.
[0158] In the above embodiment, the process of restricting viewing and editing of handwritten input data on the display device 10 has been described, but the process of restricting viewing and editing of handwritten input data may be configured to 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, a communication management device 50B determines whether to permit a viewing request and an editing authority request made by a user. The overall configuration of the screen sharing system according to the second embodiment is similar to that of the screen sharing system according to the first embodiment, and therefore a description of each device constituting the system will be omitted. Similarly, the hardware configuration is similar to that of the devices or terminals constituting the screen sharing system according to the first embodiment, and therefore a description of the hardware resources of each device or terminal will be omitted.
[0160] ●Function configuration Next, the functional configuration of a screen sharing system according to the second embodiment will be described. FIG. 41 is a diagram illustrating an example of the functional configuration of a screen sharing system according to the second embodiment. Note that FIG. 41 illustrates a state in which the following functions of the functional configuration illustrated in FIG. 8 have been swapped between the display device 10A2 and the communication management device 50B. That is, the determination unit 14A, setting unit 17A, and editing restriction unit 18A of the display device 10A1 have been swapped with the determination unit 57, setting unit 58, and editing restriction unit 60 of 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 determination unit 57, setting unit 58, and editing restriction unit 60, and therefore detailed description thereof will be omitted.
[0161] The determination unit 57 is mainly realized by the processing of the CPU 501, and performs various determinations in the communication management device 50B. The setting unit 58 is mainly realized by the processing of the CPU 501, and sets various permissions for other users using other display devices 10 with respect to handwritten input data input by a user using the display device 10. The setting unit 58, for example, sets the viewing permissions of other users with respect to handwritten input data input by a user using the display device 10. The setting unit 58 also sets the editing permissions of other users with respect to handwritten input data input by a user using the display device 10. The setting unit 58 also sets the editing permissions of users using the display device 10 with respect to handwritten input data input by other users using other display devices 10, for example.
[0162] The editing restriction unit 60 is mainly realized by the processing of the CPU 501, and restricts editing of handwritten input data entered by other users who do not have editing authority, based on the authority information set by the setting unit 17 of the display device 10. Furthermore, for example, when the editing restriction unit 60 does not have editing authority for the handwritten input data entered by other users, the editing restriction unit 60 edits an editing restriction notice to be displayed on the display screen of the display device 10, indicating that the other users do not have editing authority. Here, editing refers to controlling operations such as selection, input, addition, change, deletion, enlargement, reduction, and movement of images, text, or handwritten input data displayed on the display screen of the display device 10, in accordance with input operations accepted by the accepting unit 12 of the display device 10.
[0163] The screen sharing system 1 may have both the functional configuration of the display device 10A1 (display device 10) shown in the first embodiment (see FIG. 8) and the functional configuration of the communication management device 50B shown in the second embodiment (see FIG. 41). That is, the determination unit, setting unit, and editing restriction unit in the screen sharing system 1 may be configured so that the determination unit 14A and the determination unit 57, the setting unit 17A and the setting unit 58, and the editing restriction unit 18A and the editing restriction unit 60 are respectively provided with and executed by each of them. Furthermore, in addition to the determination unit, setting unit, and editing restriction unit described above, a functional configuration may also be configured so that other functions are provided with and executed by each of them 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 with reference to Fig. 42 to Fig. 45. Note that the processing at the start of an event and the authority setting processing described in the first embodiment are the same, and therefore the description of each processing will be omitted.
[0165] ○ Display request for handwritten input data ○ First, a process for displaying handwritten input data input by other users on a display screen on another display device according to the viewing authority of each user will be described with reference to Fig. 42. Fig. 42 is a flowchart showing an example of a viewing restriction process for handwritten input data input by other users according to the second embodiment. Fig. 42 describes a process for receiving handwritten input data input to display device 10A2 used by user A on display device 10C used by user C, but the combination of display devices 10 that transmit and receive handwritten input data is not limited to this, and similar processes are performed for other combinations of display devices 10 used by users participating in an event.
[0166] First, the transmitter / receiver 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 handwritten input data input by the user A. As shown in FIG. 20(A) of the first embodiment, the handwritten input data input by the user A is displayed on the display screen 100A of the display device 10A2.
[0167] Next, the determination unit 57 determines whether or not the user A who inputted the received handwritten input data has a viewing authority for the handwritten input data received in step S211 (step S212). Specifically, the determination unit 57 refers to the authority information set by the setting unit 58, and determines whether or not the user A has a viewing authority for the received handwritten input data. If the determination unit 57 determines that the user A has a viewing authority for the received handwritten input data (YES in step S212), the process proceeds to step S213. Then, the transmission / reception unit 51 transmits display permission information indicating a display permission for the handwritten input data to the display device 10C 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 the user does not have permission to view the received handwritten input data (NO in step S212), the process proceeds to step S214. Then, the editing restriction unit 60 restricts viewing of the handwritten input data (step S214). Then, the editing restriction unit 60 transmits, to the display device 10C, via the transmitting / receiving unit 51, viewing restriction display request information indicating a request to display a viewing restriction notice indicating that viewing of the handwritten input data entered by user A is restricted (step S215). Note that the examples of the screens displayed on the display device 10 can be implemented in the same manner as the contents shown in FIGS. 21 to 24 of the first embodiment, and therefore examples and descriptions thereof will be omitted.
[0169] In this way, when the communication management device 50B receives the displayed handwritten input data, it determines whether or not the user has permission to view the handwritten input data, and transmits display permission information for the handwritten input data to the display device 10 only if the user has permission to view the data. In this way, the screen sharing system 1 restricts the user from viewing the handwritten input data (written content) without permission, thereby preventing the user from inadvertently viewing the handwritten input data without permission. Furthermore, if the user does not have permission to view the received handwritten input data, the display device 10 displays a viewing restriction notice on the display screen. In this way, in the second embodiment, the communication management device 50B determines whether or not the user has permission to view the data and controls whether or not to allow execution, thereby reducing the processing load on the display device 10.
[0170] ○ Viewing request processing Next, a process for requesting viewing of handwritten input data whose viewing is restricted will be described with reference to Fig. 43. Fig. 43 is a sequence diagram showing an example of a process for requesting viewing of another user according to the second embodiment. Fig. 43 describes an example in which a display device 10C used by user C, whose viewing of user A's handwritten input data is restricted, issues a request for viewing to display device 10A2 used by user A. However, the combination of display devices 10 that transmit and receive a request for viewing is not limited to this, and similar processing is performed for other combinations of display devices 10 used by users participating in an event.
[0171] First, the display control unit 13C of the display device 10C displays the access restriction notice 480 on the display screen 100C (step S221). The access restriction notice 480 is as shown in FIG.
[0172] Next, the reception unit 12C receives selection of the view request button 485 included in the view restriction notification 480 in response to an input operation by user C (step S222). The transmission / reception unit 11C transmits, to the communication management device 50B, view request information indicating a request to view the restricted handwritten input data of user A (step S223). This view request information includes the user ID of the user to whom the view request is being sent. In this case, the transmission / reception unit 11C transmits the view request information including the user ID of user A. As a result, the transmission / reception unit 51 of the communication management device 50B receives the view request information transmitted by the display device 10C.
[0173] Next, the determination unit 55 of the communication management device 50B makes a determination on the view request information received in step S223 (step S224). Specifically, the determination unit 55 determines whether the received view request information is viewable by the user of the display device 10C, taking into consideration the attributes (e.g., department, work, position, etc.) of the user who uses the display device 10C that sent the view request, the contents of the handwritten strokes displayed on the display device 10A2, etc.
[0174] Next, the transmitter / receiver 51 of the communication management device 50B transmits (transfers) the determination result information for the viewing request transmitted by the display device 10C to the display device 10A2 used by the user A who is the destination of the viewing request (step S225). As a result, the transmitter / receiver 11A of the display device 10A2 receives the determination result information for the viewing request transmitted by the requesting display device 10C.
[0175] Then, when the determination result information for the view request is received in step S225, view request notifier 21A of display device 10A2 displays view request notification 380 indicating that a view request has been made by user C on display screen 100A (step S226). Then, receiver 12A of display device 10A2 receives various button operations (step S227).
[0176] The transmitter / receiver 11A of the display device 10A2 transmits, to the communication management device 50B, determination response information for the viewing request as a response to the determination result information for the viewing request received in step S225 (step S228). As a result, the transmitter / receiver 51 of the communication management device 50B receives the determination response information for the viewing request transmitted by the display device 10A2. Then, the transmitter / receiver 51 transmits, to the display device 10C, viewing response information corresponding to the determination response information for the viewing request received in step S228 (step S229). As a result, the transmitter / receiver 11C of the display device 10C receives the viewing response information transmitted by the communication management device 50B. Next, the display control unit 13C of the display device 10C displays the result of the viewing request (step S230). As a result, the display device 10C can notify the user C of the result of the viewing request.
[0177] ○ Request to edit handwritten input data ○ Next, a process for editing handwritten input data input by other users on the display screen in accordance with the viewing authority of each user will be described with reference to Fig. 44. Fig. 44 is a flowchart showing an example of an edit restriction process for handwritten input data input by other users according to the second embodiment. Fig. 44 describes a process in which handwritten input data input to the display device 10A2 used by user A is edited on the display device 10B used by user B. However, the combination of display devices 10 is not limited to this, and similar processes are performed for other combinations of display devices 10 used by users participating in an event.
[0178] First, the transmitter / receiver 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 handwritten input data input by the user A. As shown in FIG. 20(A) of the first embodiment, the handwritten input data input by the user A is displayed on the display screen 100A of the display device 10A2.
[0179] Next, the determination unit 57 determines whether or not the user has editing authority for 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 the user has editing authority for user A who input the received handwritten input data. If the determination unit 57 determines that the user has editing authority for the received handwritten input data (YES in step S232), the process proceeds to step S233. Then, the transmission / reception unit 51 transmits execution permission information indicating permission to execute an editing operation to the display device 10C so as to permit execution of an editing operation on the received handwritten input data (step S233).
[0180] On the other hand, if the determination unit 57 determines that the user A does not have the editing authority for the handwritten input data to be edited (NO in step S232), the process proceeds to step S234. Then, the edit restriction unit 60 restricts the editing of the handwritten input data to be edited (step S234). Then, the edit restriction unit 60 transmits, to the display device 10C via the transmission / reception unit 51, edit restriction display request information indicating a display request for an edit restriction notice indicating that editing of the handwritten input data entered by the 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 authority for the target handwritten input data, and transmits execution permission information for the editing operation to the display device 10 only if the user has editing authority. In this way, the screen sharing system 1 restricts editing of handwritten input data (written content) by users who do not have editing authority, thereby preventing inadvertent editing of handwritten input data for which the user does not have editing authority. Furthermore, if the display device 10 does not have editing authority for the received handwritten input data, it displays an editing restriction notification on the display screen. In this way, in the second embodiment, the communication management device 50B determines whether or not the user has editing authority and controls whether or not to allow execution, which makes it possible to reduce the processing load on the display device 10.
[0182] Editing permission request processing Next, a process for requesting editing authority for handwritten input data for which editing is restricted will be described with reference to Fig. 45. Fig. 45 is a sequence diagram showing an example of a process for requesting editing authority from another user according to the second embodiment. Fig. 45 describes an example in which a request for editing authority is made from display device 10B used by user B, who is restricted from editing handwritten input data of user A, to display device 10A2 used by user A. However, the combination of display devices 10 that transmit and receive an editing authority request is not limited to this, and similar processing is performed for other combinations of display devices 10 used by users participating in an event.
[0183] First, the display control unit 13B of the display device 10B displays the edit operation execution permission or edit restriction notification 660 on the display screen 100B (step S241). The edit restriction notification 660 is as shown in FIG.
[0184] Next, the reception unit 12B receives selection of the edit authority request button 665 included in the edit restriction notification 660 in response to an input operation by user B (step S242). The transmission / reception unit 11B transmits, to the communication management device 50B, editing authority request information indicating a request for editing authority for the restricted handwritten input data of user A (step S243). This editing authority request information includes the user ID of the user to whom the editing authority request is made. In this case, the transmission / reception unit 11B transmits the editing authority request information including the user ID of user A. As a result, the transmission / reception unit 51 of the communication management device 50B receives the editing authority request information transmitted by the display device 10B.
[0185] Next, the determination unit 55 of the communication management device 50B makes a determination on the editing authority request information received in step S243 (step S244). Specifically, the determination unit 55 determines whether or not the editing authority is granted to the user using the display device 10B in response to the received editing authority request information, taking into consideration the attributes (e.g., department, work assignment, job title, etc.) of the user using the display device 10B who sent the editing authority request, the contents of the handwritten strokes displayed on the display device 10A2, etc.
[0186] Next, the transmitter / receiver 51 of the communication management device 50B transmits (transfers) the determination result information for the editing authority request transmitted by the display device 10B to the display device 10A2 used by user A, who is the destination of the viewing request (step S245). As a result, the transmitter / receiver 11A of the display device 10A2 receives the determination result information for the editing authority request transmitted by the requesting display device 10B.
[0187] Then, when the determination result information for the editing authority request is received in step S245, editing authority request notifying unit 22A of display device 10A2 displays editing authority request notification 560 indicating that an editing authority request has been made by user B on display screen 100A (step S246). Then, accepting unit 12A of display device 10A2 accepts various button operations (step S247).
[0188] The transmitter / receiver 11A of the display device 10A2 transmits, to the communication management device 50B, determination response information for the editing authority request as a response to the determination result information for the editing authority request received in step S245 (step S248). As a result, the transmitter / receiver 51 of the communication management device 50B receives the determination response information for the editing authority request transmitted by the display device 10A2. Then, the transmitter / receiver 51 transmits, to the display device 10B, the editing authority response information for the editing authority request received in step S248 (step S249). As a result, the transmitter / receiver 11B of the display device 10B receives the editing authority response information transmitted by the communication management device 50B. Next, the display control unit 13B of the display device 10B displays the result of the editing authority request (step S250). As a result, the display device 10B can notify user B of the result of the editing authority request.
[0189] The allocation of functions between the display device 10 and the communication management device 50B in the screen sharing system 1 shown in the second embodiment is not limited to the above example.
[0190] Main effects of the second embodiment As described above, according to this embodiment, the screen sharing system 1 is configured such that the various determination functions for viewing requests and editing authority requests from other display devices 10 (10B or 10C), which were previously provided to the display device 10, are provided to the communication management device 50B. This eliminates the need for various determination processes in the display device 10, allowing the display device 10 to focus mainly on screen display and data communication processes. This system configuration reduces the processing load on the display device 10, making it possible to provide a comfortable usage environment for users of the display device 10, for example.
[0191] Modified examples of the embodiment Next, a modified example of the screen sharing system according to the embodiment will be described with reference to Figures 46 to 50. The same configurations and functions as those of the above embodiment will be assigned the same reference numerals, and the description thereof will be omitted. The screen sharing system 1 according to the modified example is an example of a system in which a shared area displayed in common among a plurality of display devices 10 is composed of a plurality of pages.
[0192] FIG. 46 is a schematic diagram illustrating an example of the display state of a shared area on a display device according to a modified example of the embodiment. In FIG. 46, display devices 10A, 10B, and 10C share a shared area divided into multiple pages to hold an event such as a remote conference. 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, each of the display devices 10A, 10B, and 10C can display a different page, allowing a user to view a desired page during an event. Each page constituting the shared area may be an area of the same size as the display screen of the display device 10, or, as in the above-described embodiment, the page itself may be an expandable area with no limit on the area available for handwriting input.
[0193] FIG. 47 is a diagram for schematically illustrating an example of display screen information according to a modified example of the embodiment. FIG. 47 shows an example of the state of the display screen displayed on the display device 10. In the example of FIG. 47, the display screen has a hierarchical structure of "events," "pages (pages 1 to 3)," and "objects (objects 1 to 5)." "Objects" correspond to handwritten input data and are managed by "pages." A "page" refers to one page of images displayed on the display screen. An "event" refers to information about an event being executed by the display device 10. For example, object 1 includes an object ID (id=sr001) that identifies object 1, information (parent=pag01) that specifies page 1 on which object 1 exists, and a global ID (GID) of object 1, "g001." For example, when an operation such as moving is performed on the image represented by object 1, the object ID (id=sr001) remains the same, but the GID of object 1, "g001," is updated.
[0194] The display device 10 can switch pages, and a "page" corresponds to each page of the display device 10. For example, page 1 includes a page ID (id=pag01) that identifies page 1, information (parent=G001) for specifying an "event" being executed on the display device 10, and the gid of page 1, "g01." An "event" corresponds to an event being executed on the display device 10, and is managed by an event ID (id=G001) that identifies the event and the gid of the event, "g1." The gids shown in each hierarchy are assigned by the communication management device 5 when screen data is shared with other display devices 10. The hierarchical structure of the display screen information shown in FIG. 39 is shared among multiple display devices 10 when screen data is shared.
[0195] Fig. 48 is a diagram showing an example of a metadata file according to a modified example of the embodiment. The metadata file 500a shown in Fig. 48 is stored in the storage unit 5000 of the communication management device 50, similar to the metadata file 500 shown in Fig. 11. Unlike the metadata file 500 shown in Fig. 11, the metadata file 500a includes, as area information shown in the display area (ViewArea) for each user, page number (Page) information as well as the coordinate position (X, Y) and size (Width, Height) of the display area.
[0196] Fig. 49 is a diagram showing an example of a handwritten input data file according to a modified example of the embodiment. The handwritten input data file 550a shown in Fig. 49 is stored in the storage unit 5000 of the communication management device 50, similar to the handwritten input data file 550 shown in Fig. 12. Unlike the handwritten input data file 550 shown in Fig. 12, the handwritten input data file 550a includes information on the page number (Page) on which the object was input as detailed data information (Data) shown in the object data (Objects).
[0197] Fig. 50 is a conceptual diagram showing an example of a screen information management table according to a modified example of the embodiment. A screen information management DB configured by a screen information management table such as that shown in Fig. 50 is constructed in the storage unit 5000 of the communication management device 50. This screen information management table stores and manages various data related to display screens shared between 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 Fig. 47) described as display screen information on the display device 10.
[0198] The data shown in the screen information management table includes an ID for identifying each piece of data, a sequence number indicating the order in which each piece of data occurred, information (body) indicating the content of the data, and information (parent) for specifying the parent data. The screen information management table includes, for example, an event ID for identifying the event being executed, and information (children) indicating the page generated by the event. In addition, for example, in the case of page data, the screen information management table includes a page ID for identifying the page (page data), and information (parent) for specifying the parent event.
[0199] For example, in the case of object data, 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) for specifying the parent page (page data). In this case, the information (body) indicating the content of the object data includes information such as the color of the input object, the width indicating the thickness of the line of the input object, the vertices (x, y) of the input object, and the name of the user who input the object. The color of the object is expressed in RGBA (Red Green Blue Alpha) data format, with each element represented by a number from 0 to 255. The width indicating the thickness of the line of the object is expressed in pixels. Furthermore, the vertices of the object are represented by X and Y coordinates, and connecting each vertex with a Bézier curve results in a line segment indicating a stroke.
[0200] In this way, the screen sharing system 1 according to the modified example can execute an event using a plurality of display devices 10 even when the shared area is made up of a plurality of 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 handwritten 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 second user's editing authority for first handwritten input data entered by the first user, and the second display device restricts editing of the first handwritten input data based on the editing authority set on the first display device. This allows the screen sharing system 1 to individually set users' editing authority for handwritten input data.
[0202] In addition, in a screen sharing system according to an embodiment of the present invention, a first display device (e.g., display device 10A) used by a first user (e.g., user A) sets a viewing authority for a second user (e.g., user B or user C) for 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 authority set on the first display device. This allows the screen sharing system 1 to individually set users' viewing authority for handwritten input data.
[0203] Furthermore, in a screen sharing system according to an 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 authority for second handwritten input data entered by a second user (e.g., user B or user C), and if the first user does not have editing authority for the second handwritten input data based on the set editing authority, restricts editing of the second handwritten input data. This allows the screen sharing system 1 to set editing authority for handwritten input data entered by other users in addition to the other users' authority for handwritten input data entered by the first user, thereby preventing inadvertent editing of content written by other users.
[0204] ●Additional Information● Each function of the above-described embodiments can be realized by one or more processing circuits. Here, the term "processing circuit" in the present embodiment includes a processor programmed to perform each function by software, such as a processor implemented by an electronic circuit, as well as devices designed to perform each function described above, such as an application specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), a system on a chip (SOC), a graphics processing unit (GPU), and a conventional circuit module.
[0205] Furthermore, the various tables in the above-described embodiments may be generated by the learning effects of machine learning, and tables may not be used by classifying data for each associated item using machine learning. Here, machine learning refers to a technology that allows a computer to acquire human-like learning capabilities, in which the computer autonomously generates algorithms necessary for judgments such as data classification from previously acquired learning data and applies these algorithms to new data to make predictions. The learning method for machine learning may be any of supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, and deep learning, or may be a combination of these learning methods. Any learning method for machine learning is acceptable.
[0206] So far, we have described a screen sharing system, a screen sharing method, a display device, a display control method, and a program according to one embodiment of the present invention, but the present invention is not limited to the above-described embodiment, and other embodiments can be added, modified, or deleted within the scope that can be conceived by a person skilled in the art, and any aspect is within the scope of the present invention as long as it achieves the functions and effects of the present invention. [Explanation of symbols]
[0207] 1. Screen sharing system 5. Communication Network 10 Display device 10A1 Display device (an example of the 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 Transmitter / receiver unit (an example of authority information transmitting means) 11B Transmitting / receiving unit (an example of an editing authority request transmitting means, an example of a viewing request transmitting means, an example of a receiving means) 11C Transmitting / receiving unit (an example of an editing authority request transmitting means, an example of a viewing request transmitting means, an example of a receiving means) 13A Display control unit (an example of a second display control means) 13B display control unit (an example of a display control means) 13C Display control unit (an example of a display control means) 17A Setting unit (an example of a setting means) 18A Editing restriction unit (an example of a second editing restriction means) 18B Editing restriction unit (an example of an editing restriction means) 18C Editing restriction unit (an example of an editing restriction means) 19A Non-sharing notification section (an example of non-sharing notification means) 21A View request notification unit (an example of a view request notification means) 22A Editing authority request notification unit (an example of an editing authority request notification means) 23A Recommended notification section (an example of a recommended notification method) 25 Selection unit (an example of a selection means) 26 Detection unit (an example of detection means) 50A communication management device 50B Communication management device 100(100A,100B,100C) display screen 350,360,370 Unshared notifications 380 View Request Notification 400, 400a, 800 permission setting screen (example of setting screen) 450,480 Viewing restriction notice 560 Edit permission request notification 650,660,830 Editing Restriction Notice 700 Shared Area 850 Permission Change Recommendation Notice [Prior art documents] [Patent documents]
[0208] [Patent Document 1] Japanese Patent Application Laid-Open No. 2009-93274 [Patent Document 2] Japanese Patent Publication No. 2020-156085
Claims
1. A screen sharing system in which a first display device used by a first user and a plurality of second display devices used by a plurality of second users can communicate with each other via a communication network, and a handwriting input screen, which is a handwriting input area that can be shared by the first user and the plurality of second users and in which handwriting input can be performed, is shared between the first display device and the plurality of second display devices, The first display device is a first display control means for causing the first display device to display a first handwriting input screen, which is the handwriting input screen; a setting unit for setting editing authority of the plurality of second users for first handwriting input data input by the first user on the first handwriting input screen; The second display device is a second display control means for causing the second display device to display a second handwriting input screen, which is the handwriting input screen, on which the first handwriting input data input by the first user to the first handwriting input screen is displayed; and an editing restriction means for restricting editing of the first handwritten input data displayed on the second handwritten input screen based on the editing authority set on the first display device, the editing restriction means causing a second user among the plurality of second users who does not have editing authority for the first handwritten input data to display an editing restriction notice indicating that the second user does not have editing authority on the second display device used by the second user, and accepting a request for editing authority for the first handwritten input data in response to an input made in response to the displayed editing restriction notice; an editing authority request sending means for sending an editing authority request for the first handwritten input data to the first display device; A screen sharing system comprising:
2. 2. The screen sharing system according to claim 1, The first display device further comprises: an authority information transmitting means for transmitting authority information indicating the set editing authority; A screen sharing system in which the editing restriction means restricts editing of the first handwritten input data displayed on the second handwritten input screen based on the authority information transmitted by the first display device.
3. the first display control means displays, on the first display device, a setting screen for accepting setting of the editing authority for each of the plurality of second users with respect to the first handwritten input data; 3. The screen sharing system according to claim 1, wherein the setting unit sets the editing authority in response to an input made to the displayed setting screen.
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 by a second user among the plurality of second users who does not have editing authority over the first handwritten input data.
5. 5. A screen sharing system according to claim 1, The first display device further includes: a screen sharing system comprising an editing authority request notification means for causing the first display device to display an editing authority request notification indicating that the second display device has transmitted the editing authority request;
6. 6. The screen sharing system according to claim 5, wherein the setting means changes the editing authority of the second users in response to an input made in response to the displayed editing authority request notice.
7. 7. A screen sharing system according to claim 1, the setting means sets viewing authorities of the second users for the first handwritten input data input by the first user; The second display control means A screen sharing system that displays the first handwritten input data on the second handwritten input screen based on the viewing authority set on the first display device.
8. The screen sharing system of claim 7, wherein the second display control means causes a second user among the plurality of second users who has viewing authority to the first handwritten input data to display the first handwritten input data on the second handwritten input screen shared by that second user.
9. A screen sharing system in which a first display device used by a first user and a plurality of second display devices used by a plurality of second users can communicate with each other via a communication network, and a handwriting input screen, which is a handwriting input area that can be shared by the first user and the plurality of second users and in which handwriting input can be made, is shared between the first display device and the plurality of second display devices, The first display device is a first display control means for causing the first display device to display a first handwriting input screen, which is the handwriting input screen; a setting unit for setting editing authority of the plurality of second users for first handwriting input data input by the first user on the first handwriting input screen; The second display device is a second display control means for causing the second display device to display a second handwriting input screen, which is the handwriting input screen, on which the first handwriting input data input by the first user to the first handwriting input screen is displayed; and an editing restriction means for restricting editing of the first handwriting input data displayed on the second handwriting input screen based on the editing authority set on the first display device; Equipped with the setting means sets viewing authorities of the second users for the first handwritten input data input by the first user; The second display control means displaying the first handwriting input data on the second handwriting input screen based on the viewing authority set in the first display device; displaying, on the second display device used by a second user who does not have a viewing authority for the first handwriting input data among the plurality of second users, a viewing restriction notice indicating that viewing of the first handwriting input data is restricted; accepting a request to view the first handwritten input data in response to an input made in response to the displayed access restriction notice; The second display device further includes: A screen sharing system comprising a view request sending means for sending a view request for the first handwritten input data to the first display device.
10. 10. The screen sharing system according to claim 9, The first display device further includes: A screen sharing system comprising a view request notification means for causing the first display device to display a view request notification indicating that the second display device has transmitted the view request.
11. 11. The screen sharing system according to claim 10, wherein the setting means changes the viewing authority of the second users in response to an input made in response to the displayed viewing request notification.
12. 12. A screen sharing system according to any one of claims 7 to 11, The first display device further includes: A screen sharing system that includes a non-sharing notification means that, if there is a second user among the multiple second users who does not have the viewing authority for the first handwritten input data, displays a non-sharing notification on the first display device indicating that the first handwritten input data is not shared with that second user.
13. A screen sharing system in which a first display device used by a first user and a plurality of second display devices used by a plurality of second users can communicate with each other via a communication network, and a handwriting input screen, which is a handwriting input area that can be shared by the first user and the plurality of second users and in which handwriting input can be made, is shared between the first display device and the plurality of second display devices, The first display device is a first display control means for causing the first display device to display a first handwriting input screen, which is the handwriting input screen; a setting means for setting editing authorities of the plurality of second users for first handwritten input data input by the first user on the first handwritten input screen, and for setting editing authorities of the first users for second handwritten input data input by the plurality of second users on a second handwritten input screen; a second editing restriction means for restricting editing of the second handwriting input data displayed on the first handwriting input screen when the first user does not have editing authority for the second handwriting input data based on the set editing authority; The second display device is a second display control means for causing the second display device to display a second handwriting input screen, which is the handwriting input screen, on which the first handwriting input data input by the first user to the first handwriting input screen is displayed; and an editing restriction means for restricting editing of the first handwriting input data displayed on the second handwriting input screen based on the editing authority set on the first display device; Equipped with the first display control means displays a first layer including the writings of the first user and a second layer including the writings of each of the plurality of second users in a superimposed manner; The second editing restriction means includes: If the first user does not have editing authority for the writings of each of the plurality of second users, restricting editing of the second layer including the writings; If the first user does not have editing authority for the second handwriting input data, displaying a second editing restriction notice indicating that the editing is restricted on the first display device used by the first user; A screen sharing system in which the setting means changes the editing authority for the second handwritten input data displayed on the first handwritten input screen in accordance with input in response to the displayed second editing restriction notification.
14. 14. The screen sharing system according to claim 13, The first display device further includes: A screen sharing system that includes a recommendation notification means that, when the first handwritten input data and the second handwritten input data displayed on the first handwritten input screen overlap, displays on the first display device a permission change recommendation notification recommending a change in editing permissions.
15. The screen sharing system of claim 14, wherein the setting means changes the editing authority for the second handwritten input data displayed on the first handwritten input screen in accordance with input in response to the displayed permission change recommendation notification.
16. 16. A screen sharing system according to any one of claims 1 to 15, The first display device further includes: a screen sharing system including a selection unit for selecting handwritten input data to be edited, the handwritten input data being displayed on the first handwritten input screen, for each user who has input the handwritten input data;
17. 17. A screen sharing system according to any one of claims 1 to 16, The first display device further includes: a detection means for detecting a writing pressure applied to the first handwriting input screen, A screen sharing system that switches handwritten input data to be edited depending on the detected pen pressure.
18. A screen sharing method executed by a screen sharing system in which a first display device used by a first user and a plurality of second display devices used by a plurality of second users can communicate with each other via a communication network, and a handwriting input screen, which is a handwriting input area that can be shared by the first user and the plurality of second users and in which handwriting input can be made, is shared between the first display device and the plurality of second display devices, The first display device is a first display step of displaying a first handwriting input screen, which is the handwriting input screen, on the first display device; a setting step of setting editing authorities of the plurality of second users for first handwriting input data input by the first user on the first handwriting input screen; The second display device is a second display step of displaying, on the second display device, a second handwriting input screen that is the handwriting input screen, and on which the first handwriting input data input by the first user to the first handwriting input screen is displayed; an editing restriction step of restricting editing of the first handwritten input data displayed on the second handwritten input screen based on the editing authority set on the first display device, the editing restriction step including displaying an editing restriction notice, indicating that a second user does not have editing authority for the first handwritten input data, on the second display device used by the second user among the plurality of second users, and accepting a request for editing authority for the first handwritten input data in response to an input in response to the displayed editing restriction notice; an editing authority request sending step of sending an editing authority request for the first handwritten input data to the first display device; How to share your screen.
19. A screen sharing method executed by a screen sharing system in which a first display device used by a first user and a plurality of second display devices used by a plurality of second users can communicate with each other via a communication network, and a handwriting input screen, which is a handwriting input area that can be shared by the first user and the plurality of second users and in which handwriting input can be made, is shared between the first display device and the plurality of second display devices, The first display device is a first display step of displaying a first handwriting input screen, which is the handwriting input screen, on the first display device; a setting step of setting editing authorities of the plurality of second users for first handwriting input data input by the first user on the first handwriting input screen; The second display device is a second display step of displaying, on the second display device, a second handwriting input screen that is the handwriting input screen, and on which the first handwriting input data input by the first user to the first handwriting input screen is displayed; an editing restriction step of restricting editing of the first handwriting input data displayed on the second handwriting input screen based on the editing authority set on the first display device; Run the setting step sets viewing authorities of the plurality of second users for first handwritten input data input by the first user; The second display step includes: displaying the first handwriting input data on the second handwriting input screen based on the viewing authority set in the first display device; displaying, on the second display device used by a second user who does not have a viewing authority for the first handwriting input data among the plurality of second users, a viewing restriction notice indicating that viewing of the first handwriting input data is restricted; accepting a request to view the first handwritten input data in response to an input made in response to the displayed access restriction notice; The second display device further includes: A screen sharing system that executes a view request sending step of sending a view request for the first handwritten input data to the first display device.
20. A screen sharing method executed by a screen sharing system in which a first display device used by a first user and a plurality of second display devices used by a plurality of second users can communicate with each other via a communication network, and a handwriting input screen, which is a handwriting input area that can be shared by the first user and the plurality of second users and in which handwriting input can be made, is shared between the first display device and the plurality of second display devices, The first display device is a first display step of displaying a first handwriting input screen, which is the handwriting input screen, on the first display device; a setting step of setting editing authorities of the plurality of second users for first handwritten input data input by the first user on the first handwritten input screen, and setting editing authorities of the first users for second handwritten input data input by the plurality of second users on a second handwritten input screen; executing an edit restriction step of restricting editing of the second handwriting input data displayed on the first handwriting input screen when the first user does not have an edit authority for the second handwriting input data based on the set edit authority; The second display device is a second display step of displaying, on the second display device, a second handwriting input screen that is the handwriting input screen, and on which the first handwriting input data input by the first user to the first handwriting input screen is displayed; an editing restriction step of restricting editing of the first handwriting input data displayed on the second handwriting input screen based on the editing authority set on the first display device; Run the first display step includes displaying a first layer including the writings of the first user and a second layer including the writings of each of the plurality of second users in a superimposed manner; The editing restriction step includes: If the first user does not have editing authority for the writings of each of the plurality of second users, restricting editing of the second layer including the writings; If the first user does not have editing authority for the second handwriting input data, displaying a second editing restriction notice indicating that the editing is restricted on the first display device used by the first user; A screen sharing method in which the setting step changes the editing authority for the second handwriting input data displayed on the first handwriting input screen in accordance with input in response to the displayed second editing restriction notification.
21. A display device that shares a handwriting input screen, which is a handwriting input area that can be shared with another display device used by another user and allows handwriting input, with the other user, a receiving means for receiving authority information indicating an editing authority for the handwriting input data input by the other user on the handwriting input screen; a display control means for causing the display device to display the handwriting input screen on which the handwriting input data input by the other user is displayed; an editing restriction means for restricting editing of the handwritten input data displayed on the handwritten input screen displayed on the display device based on the received authority information, the editing restriction means causing an editing restriction notice to be displayed on the other display device used by a user who does not have editing authority for the handwritten input data, the editing restriction notice indicating that the user does not have editing authority, and accepting a request for editing authority for the handwritten input data in response to an input in response to the displayed editing restriction notice; an editing authority request sending means for sending an editing authority request for the handwritten input data to the other display device; A display device comprising:
22. A display control method executed by a display device that shares a handwriting input screen, which is a handwriting input area that can be shared with another display device used by another user and that can input handwriting, comprising: a receiving step of receiving authority information indicating an editing authority for the handwriting input data input by the other user on the handwriting input screen; a display control step of displaying, on the display device, the handwriting input screen on which the handwriting input data input by the other user is displayed; an editing restriction step of restricting editing of the handwritten input data displayed on the handwritten input screen displayed on the display device based on the received authority information, the editing restriction step including displaying an editing restriction notice indicating that a user who does not have editing authority for the handwritten input data among the other users on the other display device used by the other users does not have editing authority for the handwritten input data, and accepting a request for editing authority for the handwritten input data in response to an input in response to the displayed editing restriction notice; an editing authority request sending step of sending an editing authority request for the handwritten input data to the other display device; A display control method that performs the following.
23. a display device that shares a handwriting input screen, which is a handwriting input area that can be shared with another display device used by another user, with the other user; a receiving step of receiving authority information indicating an editing authority for the handwriting input data input by the other user on the handwriting input screen; a display control step of displaying the handwriting input screen on the display device, on which the handwriting input data has been input; an editing restriction step of restricting editing of the handwritten input data displayed on the handwritten input screen displayed on the display device based on the received authority information, the editing restriction step including displaying an editing restriction notice indicating that a user who does not have editing authority for the handwritten input data among the other users on the other display device used by the other users does not have editing authority for the handwritten input data, and accepting a request for editing authority for the handwritten input data in response to an input in response to the displayed editing restriction notice; an editing authority request sending step of sending an editing authority request for the handwritten input data to the other display device; A program that executes the following.
Citation Information
Patent Citations
Picture editing device
JP1992279980A
Information processor and entry information management method
JP2005011321A
Object editing method, data sharing system and electronic remote conference system
JP2009093274A
Information processing program, information processing apparatus, information processing system, and information processing method
JP2014007723A
Information processing device, right management system, right management method, and program
JP2019160138A