System, information processing device, information processing method, and program

Abstract

To provide a text data transmission and reception system that can assist users participating in an event with operations on shared terminals also participating in the same event. [Solution] A text data transmission and reception system having a plurality of user terminals, a shared terminal, and an information processing device that can be connected to each of the plurality of user terminals and the shared terminal via a network, wherein the system includes a transmission and reception means for transmitting and receiving text data between the plurality of user terminals, a determination means for determining whether or not the text data transmitted and received between the plurality of user terminals includes a request for control to the shared terminal, and a control means for controlling the shared terminal when the text data includes a request for control to the shared terminal, thereby solving the above problem.

Description

Technical Field

[0001] The present invention relates to a text data transmission / reception system, a shared terminal, an information processing apparatus, a user terminal, an information processing method, and a program.

Background Art

[0002] Conventionally, a remote conference system in which an interactive whiteboard and a computer or the like are connected via a network is known. Some conventional remote conference systems have a function of managing, as a conference log, voice data during a conference, a captured image of an electronic blackboard, various types of data received from terminal devices (text data such as chat) (see, for example, Patent Document 1).

Summary of the Invention

Problems to be Solved by the Invention

[0003] In recent years, tools (an example of a collaboration tool) that support collaborative work in a group or the like have been used by providing functions such as a communication function and an information sharing function to a plurality of users who work in groups or teams. In a collaboration tool, a plurality of users who form a group or a team for collaborative work can hold an online meeting by using a communication function such as a chat function or a voice call function. In an online meeting using a communication function, a plurality of users who form a group or a team and perform collaborative work can leave, as a meeting log, data transmitted and received by the chat function during the online meeting, recording / recording data recorded / recorded by the recording / recording function, and the like.

[0004] However, when used in an online meeting, for example, there was a problem: in order to display a specific file on a shared terminal, such as an electronic whiteboard, or to share or capture the screen displayed on the shared terminal, a user participating in the same online meeting as the shared terminal had to directly operate the shared terminal from the conference room where the shared terminal was located.

[0005] The embodiment of the present invention aims to provide a text data transmission and reception system that can support users participating in an event in operating on shared terminals participating in the same event. [Means for solving the problem]

[0006] To achieve the above-mentioned objectives, claim 1 of the present application provides a text data transmission and reception system having a plurality of user terminals, a shared terminal, and an information processing device that can be connected to each of the plurality of user terminals and the shared terminal via a network, characterized in that it comprises: transmission and reception means for transmitting and receiving text data between the plurality of user terminals; determination means for determining whether or not the text data transmitted and received between the plurality of user terminals includes a request for control to the shared terminal; and control means for controlling the shared terminal when the text data includes a request for control to the shared terminal. [Effects of the Invention]

[0007] According to an embodiment of the present invention, it is possible to support users participating in an event in operating on shared terminals that are also participating in the same event. [Brief explanation of the drawing]

[0008] [Figure 1] This is a diagram illustrating an example of an information processing system according to this embodiment. [Figure 2] This is a hardware configuration diagram of an example of a shared terminal according to this embodiment. [Figure 3]This is a hardware configuration diagram of an example of a computer according to this embodiment. [Figure 4] This diagram shows the software configuration of the shared terminal. [Figure 5] This diagram shows the software configuration of the user terminal. [Figure 6] This is a functional configuration diagram of an example of an information processing system according to this embodiment. [Figure 7] This is a conceptual diagram showing the user authentication management table. [Figure 8] This is a conceptual diagram showing the access management table. [Figure 9] This is a conceptual diagram showing a schedule management table. [Figure 10] This is a conceptual diagram showing the execution event management table. [Figure 11] This is a conceptual diagram showing a content management table. [Figure 12] This is a conceptual diagram showing the user authentication management table. [Figure 13] This is a conceptual diagram showing the user management table. [Figure 14] This is a conceptual diagram showing the community management table. [Figure 15] This is a conceptual diagram showing the common area reservation management table. [Figure 16] This is a conceptual diagram showing the event management table. [Figure 17] This is a conceptual diagram showing the server authentication management table. [Figure 18] This is a conceptual diagram showing a project member management table. [Figure 19] This is a conceptual diagram showing the execution event history management table. [Figure 20] This is a conceptual diagram showing the execution event management table. [Figure 21] This is a conceptual diagram showing a related information management table. [Figure 22] This is a sequence diagram showing the schedule registration process. [Figure 23] This is a diagram showing the sign-in screen. [Figure 24] This is an example of the initial screen of the user terminal. [Figure 25] This is a diagram showing the schedule screen. [Figure 26] This is a diagram showing the schedule input screen. [Figure 27] This is a diagram showing the candidates proposed on the schedule input screen. [Figure 28] This is a diagram showing the schedule input screen. [Figure 29] This is a diagram showing the schedule input screen. [Figure 30] This is a sequence diagram showing the start process of the event. [Figure 31] This is a sequence diagram showing the start process of the event. [Figure 32] This is a diagram showing the reservation list screen of the union. [Figure 33] This is a diagram showing the project list screen. [Figure 34] This is a diagram showing the detailed information screen of the event. [Figure 35] [[ID=3 | 4]] [Figure 36] This is a diagram showing an example of the display screen of the attached file. [Figure 38] This is a diagram showing an example of the message content posted by the chat function. [Figure 39] This is a diagram showing the screen image of the shared terminal. [Figure 40] This is a diagram showing an example of the display screen and camera image of the shared terminal. [Figure 41] This is a diagram showing an example of the message content posted by the chat function. [Figure 42] This is a sequence diagram showing the process in which the user requests control of the shared terminal using the chat function. [Figure 43] ​​This is a sequence diagram illustrating the process by which a user requests control of a shared terminal using the chat function. [Figure 44] This figure shows an example of a message posted using the chat function. [Figure 45] This is a sequence diagram illustrating the process by which a user requests control of a shared terminal using the chat function. [Figure 46] This is a sequence diagram illustrating the process by which a user requests control of a shared terminal using the chat function. [Figure 47] This is a sequence diagram illustrating the process by which a user requests control of a shared terminal via voice. [Figure 48] This is a diagram showing the screen image of a shared terminal. [Figure 49] This figure shows an example of a message posted using the chat function. [Modes for carrying out the invention]

[0009] Embodiments of the present invention will be described below with reference to the drawings. In these embodiments, a group or team of users assembled for collaborative work will be referred to as a project, and users belonging to that project will be referred to as project members. In these embodiments, "file" refers to an "electronic file."

[0010] [First Embodiment] <System Configuration> Figure 1 is a diagram showing an example of an information processing system according to this embodiment. In the information processing system 1 of Figure 1, a collaboration system 10, an online storage server 20, a user terminal 40, and a shared terminal 42 are connected to each other via a communication network 50.

[0011] The communication network 50 is constructed using the Internet, mobile communication networks, LANs (Local Area Networks), etc. The communication network 50 may include not only wired communication but also wireless communication networks such as 3G (3rd Generation), WiMAX (Worldwide Interoperability for Microwave Access), or LTE (Long Term Evolution).

[0012] Collaboration System 10 is a system that supports multiple people working together on a single task. An example of Collaboration System 10 is a system used in a setting where people gather to exchange opinions and discuss a specific objective (including cases where they are physically in the same location, or where they are physically separated but their user terminals are connected via a communication network 50). It utilizes PCs, mobile devices, electronic whiteboards, projectors, and meeting tools to facilitate voice calls, video calls, chat, screen sharing (projection), information sharing, agenda discussion, document creation and compilation, schedule setting, action item determination, etc. Collaboration System 10 is synonymous with collaborative work support system. A collaborative work support system is a system that supports multiple people working together on a single task. For example, it provides communication functions and information sharing functions. Collaboration System 10 provides collaboration tools to support collaborative work among project members. Collaboration tools are means, functions, and tools for supporting multiple people working together on a single task. Examples of collaboration tools include communication functions, schedule management functions, information sharing functions, and action item management functions. Collaborative work means multiple people working together on a single task.

[0013] Note that the collaboration tools provided by the collaboration system 10 do not necessarily have to be identical. For this reason, the server configurations of the two collaboration systems 10 are different in Figure 1. The shared support server 11 of the collaboration system 10 provides project members with, for example, communication functions and information sharing functions.

[0014] The schedule management server 12 provides schedule management functions to project members. The speech-to-text conversion server 13 converts speech data from project members into text data. The file management server 14 stores files uploaded, recorded, or filmed by project members during online meetings, etc. By using the file management server 14, project members can share files.

[0015] Furthermore, the online storage server 20 provides users with online storage services. Online storage services are services that, for example, rent out cloud-based disk drives (storage) that can be accessed via the internet to users. By using online storage services, project members can share files.

[0016] User terminal 40 is an information processing terminal operated by users, including project members. Users can access the collaboration system 10, the online storage server 20, and the shared terminal 42 from user terminal 40.

[0017] The user terminal 40 may be any device equipped with communication capabilities, such as a PJ (Projector), IWB (Interactive White Board), digital signage output device, HUD (Head Up Display) device, industrial machinery, imaging device, sound collection device, medical equipment, networked home appliance, automobile (Connected Car), notebook PC (Personal Computer), mobile phone, smartphone, tablet device, game console, PDA (Personal Digital Assistant), digital camera, wearable PC, or desktop PC.

[0018] The shared terminal 42 is an information processing terminal that is shared by multiple people, such as an electronic whiteboard installed in a conference room. The shared terminal 42 may be any device equipped with communication capabilities, such as a PJ (Projector), IWB (Interactive White Board: an electronic whiteboard with the ability to communicate with each other), output devices such as digital signage, HUD (Head Up Display) devices, industrial machinery, imaging devices, sound collection devices, medical equipment, networked home appliances, automobiles (Connected Car), notebook PCs (Personal Computers), mobile phones, smartphones, tablet devices, game consoles, PDAs (Personal Digital Assistants), digital cameras, wearable PCs, or desktop PCs. For example, a shared terminal 42 installed in a conference room can be shared by multiple people by requiring the reservation of the terminal itself or the conference room in order to use it.

[0019] Furthermore, the shared support server 11, the schedule management server 12, the speech-to-text conversion server 13, and the file management server 14 can be implemented by, for example, one or more information processing devices. Alternatively, the collaboration system 10 may consist of one or more computers that integrate all or part of the functions of the shared support server 11, the schedule management server 12, the speech-to-text conversion server 13, and the file management server 14.

[0020] Furthermore, the shared support server 11, the schedule management server 12, the speech-to-text conversion server 13, and the file management server 14 may each be configured to distribute their respective functions across multiple computers.

[0021] Furthermore, the shared support server 11, schedule management server 12, speech-to-text conversion server 13, and file management server 14 may be configured to be implemented on computers in a cloud environment or on computers in an on-premises environment. Thus, the information processing system 1 in Figure 1 is just one example.

[0022] Furthermore, the collaboration system 10, shared support server 11, schedule management server 12, speech-to-text conversion server 13, file management server 14, and online storage server 20 are not limited to PCs, as long as they are devices equipped with communication capabilities.

[0023] The collaboration system 10, shared support server 11, schedule management server 12, voice-to-text conversion server 13, file management server 14, and online storage server 20 may be, for example, output devices such as projectors, interoperable whiteboards, and digital signage, HUD devices, industrial machinery, imaging devices, sound collection devices, medical equipment, networked home appliances, automobiles, notebook PCs, mobile phones, smartphones, tablet devices, game consoles, PDAs, digital cameras, wearable PCs, or desktop PCs.

[0024] The collaboration information that the collaboration system 10 provides to project members through the collaboration tool includes both synchronous and asynchronous collaboration information. Synchronous collaboration information is information exchanged in real time during a gathering where people come together to exchange opinions and discuss a specific purpose (for example, an online meeting). Synchronous collaboration information includes, for example, voice calls, video calls, and screens shared on PCs, mobile devices, and electronic whiteboards (including text and diagrams entered from PCs and mobile devices, and handwritten entries on screens such as electronic whiteboards).

[0025] Furthermore, asynchronous collaboration information is information that is entered and shared over a network. Asynchronous collaboration information also includes information that can be shared and referenced by participants before and after a gathering where people come together to exchange opinions and discuss a specific purpose (e.g., a meeting). Examples of asynchronous collaboration information include chats, messages, content, scheduling, action items, and audio / video recordings.

[0026] These terms are also included in Gartner's meeting solutions report ("Magic Quadrant Meeting Solutions," published September 2019).

[0027] <Hardware Configuration> If the shared terminal 42 in Figure 1 is an electronic whiteboard, it can be implemented with a hardware configuration such as that shown in Figure 2. Figure 2 is a hardware configuration diagram of an example of a shared terminal according to this embodiment. As shown in Figure 2, the shared terminal 42 is equipped with a CPU (Central Processing Unit) 201, ROM (Read Only Memory) 202, RAM (Random Access Memory) 203, SSD (Solid State Drive) 204, network I / F 205, and external device connection I / F (Interface) 206.

[0028] Of these, CPU201 controls the operation of the entire shared terminal 42. ROM202 stores programs used to drive CPU201, such as CPU201 and IPL (Initial Program Loader). RAM203 is used as the work area for CPU201. SSD204 stores various data, such as programs for the shared terminal 42. Network I / F205 controls communication with the communication network 50. External device connection I / F206 controls communication with USB (Universal Serial Bus) memory 2600, PC2700, and external devices (microphone 2200, speaker 2300, camera 2400).

[0029] The shared terminal 42 also includes a capture device 211, a GPU 212, a display controller 213, a contact sensor 214, a sensor controller 215, an electronic pen controller 216, a short-range communication circuit 219, an antenna 219a for the short-range communication circuit 219, and a power switch 222.

[0030] Of these, the capture device 211 acquires image data displayed on the display 220, which is an example of a display unit (display means), via the display controller 213, and stores it in RAM 203 or the like. The GPU (Graphics Processing Unit) 212 is a semiconductor chip that specializes in graphics. The display controller 213 controls and manages the screen display in order to output the output image from the capture device 211 or GPU 212 to the display 220 or the like.

[0031] The contact sensor 214 detects when an electronic pen 2500 or the user's hand H comes into contact with the display 220. The sensor controller 215 controls the processing of the contact sensor 214. The contact sensor 214 performs coordinate input and coordinate detection using an infrared blocking method. This method of coordinate input and detection involves two light-emitting and receiving devices installed at both ends of the upper side of the display 220 emitting multiple infrared rays parallel to the display 220, which are reflected by reflective members provided around the display 220, and the light receiving element receives the light that returns along the same optical path as the light emitted.

[0032] The contact sensor 214 outputs the infrared ID emitted by the two light-receiving devices, which are blocked by the object, to the sensor controller 215, which then identifies the coordinate position of the object's contact. The electronic pen controller 216 communicates with the electronic pen 2500 to determine whether the pen tip or the pen's end has touched the display 220.

[0033] 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 turning the power of the shared terminal 42 ON / OFF.

[0034] Furthermore, the shared terminal 42 is equipped with a bus line 210. The bus line 210 is an address bus, data bus, etc., for electrically connecting the various components such as the CPU 201 shown in Figure 2.

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

[0036] The collaboration system 10, shared support server 11, schedule management server 12, speech-to-text conversion server 13, file management server 14, and online storage server 20 in Figure 1 are implemented by a computer 500 with the hardware configuration shown in Figure 2, for example. Furthermore, if the user terminal 40 in Figure 1 is a PC, it is implemented by a computer 500 with the hardware configuration shown in Figure 3, for example. Figure 3 is a hardware configuration diagram of an example computer according to this embodiment.

[0037] As shown in Figure 3, the computer 500 includes a CPU (Central Processing Unit) 501, ROM (Read Only Memory) 502, RAM (Random Access Memory) 503, HD 504, HDD (Hard Disk Drive) controller 505, display 506, external device connection I / F (Interface) 508, network I / F 509, data bus 510, keyboard 511, pointing device 512, DVD-RW (Digital Versatile Disk Rewritable) drive 514, and media I / F 516.

[0038] Of these components, the CPU 501 controls the operation of the entire computer 500 according to the program. The ROM 502 stores programs used to drive the CPU 501, such as the IPL. The RAM 503 is used as the work area for the CPU 501. The HD 504 stores various data, such as programs. The HDD controller 505 controls the reading or writing of various data to the HD 504 according to the control of the CPU 501.

[0039] The display 506 displays various information such as cursors, menus, windows, characters, or images. The external device connection interface 508 is an interface for connecting various external devices. In this case, external devices include, for example, USB (Universal Serial Bus) memory and printers. The network interface 509 is an interface for data communication using the network 16. The data bus 510 is an address bus and data bus for electrically connecting various components such as the CPU 501.

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

[0041] Furthermore, each of the above programs may be distributed as an installable or executable file recorded on a computer-readable storage medium. Examples of storage media include CD-R (Compact Disc Recordable), DVD (Digital Versatile Disk), Blu-ray disc, and SD card. The storage media may also be provided domestically or internationally as a program product.

[0042] <Software Configuration> Next, Figure 4 will be used to explain the computer software installed on the shared terminal 42. Here, computer software (hereinafter referred to as "software") refers to programs related to the operation of a computer, and other information used for processing by a computer that is equivalent to a program. A program is a set of instructions for a computer that are combined to obtain a specific result. Something equivalent to a program is something that cannot be called a program because it is not a direct instruction to the computer, but has properties similar to a program in that it defines the processing of the computer. For example, a data structure (the logical structure of data, expressed by the interrelationships between data elements) falls under the category of something equivalent to a program.

[0043] Furthermore, an application is a general term for software used to perform specific processing tasks. On the other hand, an operating system (hereinafter referred to as OS) is software that controls the computer and makes computer resources available to applications and other users. The OS performs basic computer management and control, such as input / output control, management of hardware such as memory and hard disks, and process management. Applications operate by utilizing the functions provided by the OS.

[0044] Figure 4 shows the software configuration of the shared terminal 42. As shown in Figure 4, the OS 101, Launcher 102, schedule viewer 103a, file viewer 103b, browser application 103c, and collaboration application 103d run on the workspace 15 of RAM 203. The OS 101 is the basic software that provides the basic functions of the shared terminal 42 and manages the entire shared terminal 42.

[0045] Launcher102 is a launcher application that runs on OS101. Launcher102 manages, for example, the start and end of events executed on shared terminal 42, or external applications such as schedule viewer 103a, file viewer 103b, browser application 103c, and collaboration application 103d that are used while events are running. An event is a place where people gather in person or via a communication network 50 to express opinions, make presentations, or discuss for a specific purpose, such as meetings, gatherings, meetings, consultations, conferences, seminars, webinars (online seminars), academic research meetings, policy presentations, etc.

[0046] The schedule viewer 103a, file viewer 103b, browser application 103c, and collaboration application 103d are external applications (hereinafter referred to as external applications 103 unless otherwise specified) that run on the Launcher 102. The external applications 103 are processed independently of the Launcher 102 and execute services or functions provided on the OS 101. Figure 4 shows an example in which four external applications 103—the schedule viewer 103a, file viewer 103b, browser application 103c, and collaboration application 103d—are installed on the shared terminal 42, but the number of external applications 103 is not limited to this. Furthermore, the schedule viewer 103a, file viewer 103b, browser application 103c, and collaboration application 103d may be made downloadable and installable from a server located in, for example, the collaboration system 10, or from a server located in the cloud or on-premises.

[0047] Next, we will explain the software installed on the user terminal 40 using Figure 5. Figure 5 is a diagram showing the software configuration of the user terminal. As shown in Figure 5, the OS 5501, the collaboration application 5502a, and the browser 5502b operate on the workspace 5500 of the RAM 503. The OS 5501 is the basic software that provides the basic functions of the user terminal 40 and manages the user terminal 40 as a whole.

[0048] The collaboration application 5502a and the browser 5502b are external applications (hereinafter referred to as external applications 5502 unless otherwise specified) that run on the OS 5501. The external applications 5502 execute services or functions provided on the OS 5501. Figure 5 shows an example where two external applications 5502, the collaboration application 5502a and the browser 5502b, are installed on the user terminal 40, but this is not limited to this example. The number of external applications 5502 installed on the user terminal 40 may be other than two. Furthermore, the collaboration application 5502a and the browser 5502b may be made available for download and installation from a server located in, for example, the collaboration system 10, or from a server located in the cloud or on-premises.

[0049] <Functional Configuration> The information processing system 1 according to this embodiment is realized by a functional configuration such as that shown in Figure 6. Figure 6 is a functional configuration diagram of an example of the information processing system according to this embodiment. In the functional configuration of Figure 6, components that are not necessary for the explanation of this embodiment have been appropriately omitted.

[0050] 《Functional Configuration of Shared Terminals》 As shown in Figure 6, the shared terminal 42 in the case of an electronic whiteboard has a transmitting / receiving unit 21, a receiving unit 22, an image / sound processing unit 23, a display control unit 24, a judgment unit 25, a recognition unit 26, an acquisition / provision unit 28, a storage / reading processing unit 29, a function control unit 31, and a storage request unit 32. Each of these units is a function or means of functioning, realized by any of the components shown in Figure 2 operating according to instructions from the CPU 201 following a program deployed from the SSD 204 onto the RAM 203. The shared terminal 42 also has a storage unit 2000 constructed from the RAM 203, SSD 204, or USB memory 2600 shown in Figure 2.

[0051] (Functional configuration of each shared terminal) Next, the components of the shared terminal 42 will be described. The transmitting / receiving unit 21 is implemented by instructions from the CPU 201 shown in Figure 2, as well as the network interface 205 and the external device connection interface 206, and transmits and receives various data (or information) with other terminals, devices, or systems via the communication network 50. The transmitting / receiving unit 21 is an example of a transmitting means and a receiving means.

[0052] The reception unit 22 is mainly implemented by commands from the CPU 201 shown in Figure 2, as well as the contact sensor 214 and the electronic pen controller 216, and accepts various inputs from the user. The reception unit 22 is an example of a reception means.

[0053] The image and sound processing unit 23 is implemented by instructions from the CPU 201 and the capture device 211 shown in Figure 2, and stores the image data displayed on the display 220. The image and sound processing unit 23 is also implemented by instructions from the CPU 201 and the GPU 212 shown in Figure 2, and performs image processing to display the image on the display 220. Furthermore, the image and sound processing unit 23 performs image processing on the image data obtained by the camera 2400 when it captures the subject.

[0054] Furthermore, the image / sound processing unit 23 performs audio processing on the audio data related to the audio signal after the user's voice is converted into an audio signal by the microphone 2200. In addition, the image / sound processing unit 23 outputs the audio signal related to the audio data to the speaker 2300, causing the speaker 2300 to output sound. The image / sound processing unit 23 also performs processing to convert the drawn image data obtained by the user drawing on the display 220 with the electronic pen 2500 or their hand H into coordinate data.

[0055] The display control unit 24 is implemented by instructions from the CPU 201 shown in Figure 2 and the display controller 213 shown in Figure 2. It displays images on the display 220 and accesses the shared support server 11 and the schedule management server 12 using a web browser to display various screen data. Specifically, the display control unit 24 launches and executes the Launcher 102 and external application 103, which run on the OS 101 shown in Figure 4, to display various screens drawn by the API (Application Programming Interface) provided by the OS 101 on the display 220. The display control unit 24 is an example of a display control means.

[0056] The determination unit 25 is implemented by instructions from the CPU 201 shown in Figure 2 and performs various decisions. For example, the determination unit 25 determines whether the user who sent the chat message is participating in the same online meeting as the shared terminal 42.

[0057] The recognition unit 26 is implemented by instructions from the CPU 201 shown in Figure 2 and recognizes a designated area enclosed on the display 220. The acquisition and provision unit 28 is executed by instructions from the CPU 201 shown in Figure 2, as well as the short-range communication circuit 219 and antenna 219a, and acquires and provides data via short-range communication with dedicated terminals such as IC cards and smartphones.

[0058] The function control unit 31 receives control requests from the user based on user operations and controls the functions. Furthermore, the function control unit 31 receives control requests from the user based on chat function messages, as described below, and controls the functions. For example, if a user participating in the same online meeting requests a screen capture, the function control unit 31 controls the capture function to capture the displayed screen. Also, if a user participating in the same online meeting sends a message with an attached file, the function control unit 31 displays the attached file.

[0059] The save request unit 32 requests the shared support server 11 to save the shared data used during the online meeting after the online meeting has ended. Shared data here refers to information used during events such as online meetings, including files, shared screen image data, video recording data, audio recording data, stroke data, pointer data, chat data, etc. The save request unit 32 may also request the shared support server 11 to save the shared data used during the online meeting while the online meeting is in progress (from the start to the end of the meeting; while the meeting is being conducted). If the amount or size of the shared data is large, starting the saving process during the online meeting will allow the saving of the shared data to be completed when the online meeting ends or immediately after it ends.

[0060] The memory / read processing unit 29 is executed by instructions from the CPU 201 and the SSD 204 shown in Figure 2, and performs processing such as storing various data in the memory unit 2000 and reading various data stored in the memory unit 2000. Furthermore, image data and sound data received when communicating with other shared terminals 42 and user terminals 40 are overwritten in the memory unit 2000 each time they are received. Of these, the image data before overwriting is used to display an image on the display 220, and the sound data before overwriting is used to output sound from the speaker 2300.

[0061] <User terminal functional configuration> The user terminal 40 includes a transmitting / receiving unit 51, a receiving unit 52, a display control unit 54, a generation unit 56, a sound control unit 58, and a storage / reading processing unit 59. Each of these units is a function or means of functioning, realized by any of the components shown in Figure 3 operating according to instructions from the CPU 501 following a program deployed from the HD 504 onto the RAM 503. The user terminal 40 also has a storage unit 5000 constructed by the HD 504 shown in Figure 3.

[0062] (Functional configuration of each user terminal) Next, the components of the user terminal 40 will be described. The transmitting / receiving unit 51 is implemented by instructions from the CPU 501 and the network I / F 509 shown in Figure 3, and transmits and receives various data (or information) with other terminals, devices, or systems via the communication network 50. The transmitting / receiving unit 51 is an example of a transmitting means and a receiving means.

[0063] The reception unit 52 is mainly implemented by instructions from the CPU 501 shown in Figure 3, as well as the keyboard 511 and pointing device 512, and accepts various inputs from the user. The reception unit 52 is an example of a reception means.

[0064] The display control unit 54 is implemented by instructions from the CPU 501 shown in Figure 3, and displays images on the display 506, or accesses the shared support server 11 or the schedule management server 12 using the browser 5502b to display images of various screen data. Specifically, the display control unit 54 accesses the shared support server 11 or the schedule management server 12 by, for example, launching and executing the collaboration application 5502a or the browser 5502b that runs on the OS 5501 shown in Figure 5.

[0065] The display control unit 54 then downloads a WebApp (Web Application) that includes, for example, HTML (HyperText Markup Language), CSS (Cascading Style Sheets), or Java Script (registered trademark), and displays various image data generated by that WebApp on the display 506. The display control unit 54 also displays image data generated by "HTML5" that includes data in formats such as XML (Extensible Markup Language), JSON (JavaScript Object Notation), or SOAP (Simple Object Access Protocol) on the display 506. The display control unit 54 is an example of a display control means.

[0066] The generation unit 56 is implemented by instructions from the CPU 501 shown in Figure 3 and has the function of generating various image data to be displayed on the display 506. The generation unit 56 generates various image data using content data received by the transmission / reception unit 51. For example, the generation unit 56 renders text data, which is content data, and generates image data related to the text data, which is content data, in order to display the rendered data. Rendering is the process of interpreting data written in a language for describing web pages (HTML, CSS, or XML, etc.) and calculating the arrangement of characters, image data, etc. that will actually be displayed on the screen.

[0067] The sound control unit 58, implemented by instructions from the CPU 501 shown in Figure 3, has the function of outputting sound signals from the speaker. The sound control unit 58 sets the sound data to be output from the speaker and plays the sound data by outputting the sound signal related to the set sound data from the speaker.

[0068] The memory and read processing unit 59 is executed by instructions from the CPU 501 shown in Figure 3, as well as the HDD controller 505, and performs processing such as storing various data in the memory unit 5000 and reading various data from the memory unit 5000.

[0069] 《Functional Configuration of the Shared Support Server》 The shared support server 11 includes a transmission / reception unit 61, an authentication unit 62, a creation unit 63, a generation unit 64, a determination unit 65, a distribution unit 66, a control request unit 67, and a storage / reading processing unit 69. Each of these units is a function or means of functioning, realized by any of the components shown in Figure 2 operating according to instructions from the CPU 501 following a shared support program deployed from the HD 504 onto the RAM 503. The shared support server 11 also has a storage unit 6000 constructed from the HD 504 and other components shown in Figure 2.

[0070] (User authentication management table) Figure 7 is a conceptual diagram showing the user authentication management table. The storage unit 6000 has a user authentication management DB 6001 constructed, which consists of the user authentication management table shown in Figure 7. This user authentication management table manages and associates a user ID for identifying a user, a user name, an organization ID for identifying the organization to which the user belongs, and a password. The organization ID also includes a domain name that represents a group or organization for managing multiple computers on the communication network 50.

[0071] (Access management table) Figure 8 is a conceptual diagram showing the access management table. The storage unit 6000 has an access management DB 6002 constructed, which consists of the access management table shown in Figure 8. This access management table associates and manages the organization ID, the access ID required for authentication when accessing the schedule management server 12, and the access password. The access ID and access password are necessary for the shared support server 11 to use the services (functions) provided by the schedule management server 12 via Web API, etc., using the HTTP (Hypertext Transfer Protocol) or HTTPS (Hypertext Transfer Protocol Secure) protocol.

[0072] The schedule management server 12 manages multiple schedulers, and different organizations may use different schedulers; therefore, management using the access management table shown in Figure 8 is necessary.

[0073] (Schedule management table) Figure 9 is a conceptual diagram showing the schedule management table. The storage unit 6000 has a schedule management DB 6003 built on it, which consists of the schedule management table shown in Figure 9. In this schedule management table, for each scheduled event ID and execution event ID, the following information is associated and managed: organization ID, user ID of the person who made the reservation, whether or not this person is participating, name of the person who made the reservation, scheduled start time, scheduled end time, event name, user IDs of other participants, whether or not these other participants are participating, names of other participants, and file data.

[0074] Of these, the Scheduled Event ID is identification information used to identify a reserved event. The Scheduled Event ID is an example of scheduled event identification information used to identify an event scheduled to run. The Runnable Event ID is identification information used to identify a reserved event that has actually been run or is currently being run.

[0075] The Execution Event ID is an example of execution event identification information used to identify an event that has been executed or is currently being executed. The Reservation Name is the name of the person who reserved a shared space such as a meeting room. A shared space is an object, service, space (room), place, or information used jointly by multiple people or groups. A meeting room is an example of a shared space used by multiple users. If the shared space is a meeting room, the name is, for example, the name of the organizer. The Scheduled Start Time indicates the scheduled start time for using the shared space. The Scheduled End Time indicates the scheduled end time for using the shared space. The Event Name indicates the name of the event that the reservation holder plans to execute.

[0076] The user IDs of other participants are identification information used to identify participants other than the person who made the reservation. The names of other participants are the names of participants other than the person who made the reservation, and include shared entities. In other words, in this case, users include the person who made the reservation and other participants, as well as a shared terminal 42, which is an example of a shared entity. The file data is file data such as materials to be used in the event corresponding to the scheduled event ID, registered by the user. The file data is data in a predetermined file format created using various applications. The file format of the file data is, for example, a file for presentation software, a file for spreadsheet software, etc.

[0077] (Execution event management table) Figure 10 is a conceptual diagram showing the execution event management table. The memory unit 6000 has an execution event management DB 6004 constructed, which consists of the execution event management table shown in Figure 10. In this execution event management table, execution event IDs are associated and managed for each project ID.

[0078] A project ID is an identifier used to identify a project (an example of project identifier information). A project represents a group, team, or collective of users formed to achieve a specific goal, plan, or initiative.

[0079] Users who are members of the same project can share shared data, such as meeting minutes, associated with the project ID as an event history. Shared data refers to information used during events such as online meetings, including files, shared screen image data, video recordings, audio recordings, stroke data, pointer data, and chat data. A project ID is assigned to each project. The project ID may also be referred to as a group ID or team ID.

[0080] (Content management table) Figure 11 is a conceptual diagram showing the content management table. The storage unit 6000 has a content management DB 6005 constructed, which is composed of the content management table shown in Figure 11. In this content management table, the content processing ID, content processing type, content content, and the start and end dates and times of the content processing are associated and managed for each execution event ID.

[0081] Content refers to shared data generated during events such as online meetings within a project (the details of the event itself, or materials used in that event). Types of content processing include audio recording, video recording, file sharing, screen sharing, snapshots, speech-to-text conversion, action item generation, chat, document uploads, handwriting input, and pointing device operation. The content processing ID is an identifier used to identify the content processing that occurred during each event.

[0082] A snapshot is the process of capturing the display screen as image data at a specific point in time during an ongoing event. Snapshots are also sometimes referred to as image capture or image recognition.

[0083] If the content processing type is "recording," the content includes a URL indicating the location where the recorded audio data is saved. If the content processing type is "snapshot," the content includes a URL indicating the location where the image data of the screen captured by the snapshot (capture) is saved. Capturing means saving the image (still image, moving image) displayed on display 220 or 506 as image data. If the content processing type is "speech-to-text conversion," the content includes a URL indicating the location where the text data of the received audio data is saved. Text data refers to the character information exchanged between users participating in the event. Examples include text entered by each user participating in the event, data converted from voice-inputted statements to text, character data contained in files exchanged by each user within the event, mentions contained in manually entered text or voice-inputted comments, etc.

[0084] When the content processing type is "chat," the content includes the user ID of the participant who posted the message, the user ID of the recipient (if mentioned), and the message content. A message is information exchanged between users participating in an event. Examples include text entered by each user, voice-input comments, data converted from voice-input statements to text, files exchanged by each user within the event, and mentions included in manually entered text or voice-input comments. A message with a mention is a message that notifies multiple participants, specifically identifying the person among those participants that the message should be read. The message content includes not only the text data of the posted message, but also files such as posted image data and meeting log data.

[0085] An action item is generated during an event such as a meeting within a project, and indicates the actions that those involved in the event should take. If the content processing type is "Action Item Occurrence," the content includes the user ID of the person performing the action item, the deadline for completing the action item, and a URL indicating the location where the text data representing the action item's content is stored.

[0086] If the content type is "recording," the content includes a URL indicating the location where the recorded video data is saved. If the content type is "file sharing," the content includes a URL indicating the location where the file data shared by participants in an online meeting or other event is saved. If the content type is "screen sharing," the content includes a URL indicating the location where the image data or video data of the screen shared by participants in an online meeting or other event is saved.

[0087] (Functional configuration of the shared support server) Next, we will explain in detail the functional configurations of the shared support server 11. In addition, when explaining the functional configurations of the shared support server 11, we will also explain the relationship between each component shown in Figure 3 and the main components necessary to realize each functional configuration of the shared support server 11.

[0088] The transmitting / receiving unit 61 of the shared support server 11 shown in Figure 6 is implemented by instructions from the CPU 501 shown in Figure 3 and the network I / F 509 shown in Figure 3. The transmitting / receiving unit 61 transmits and receives various data (or information) with user terminals 40, shared terminals 42, other servers, or other systems via the communication network 50. The transmitting / receiving unit 61 is an example of a transmitting or receiving means.

[0089] The authentication unit 62 is implemented by instructions from the CPU 501 shown in Figure 3, and performs authentication by determining whether the information (user ID, organization ID, and password) sent from the user terminal 40 or shared terminal 42 is information that has been pre-registered in the user authentication management DB 6001.

[0090] The creation unit 63 is implemented by instructions from the CPU 501 shown in Figure 3, and creates image data for various screens, including image data for the reservation list screen based on reservation information and schedule information sent from the schedule management server 12.

[0091] The generation unit 64 is implemented by instructions from the CPU 501 shown in Figure 3 and generates an execution event ID, a content processing ID, and a URL for saving. The determination unit 65 is implemented by instructions from the CPU 501 shown in Figure 3 and performs various decisions. These decisions will be described later. The distribution unit 66 is implemented by instructions from the CPU 501 shown in Figure 3 and provides a chat function to participants in online meetings, etc. The control request unit 67 is implemented by instructions from the CPU 501 shown in Figure 3 and, based on the operation requested by the chat message, makes a control request to the shared terminal 42, as described later. The memory and read processing unit 69 is implemented by instructions from the CPU 501 shown in Figure 3 and the HDD controller 505 shown in Figure 3, and performs processing such as storing various data in the memory unit 6000 and reading various data stored in the memory unit 6000.

[0092] 《Functional Configuration of the Schedule Management Server》 The schedule management server 12 includes a transmit / receive unit 81, an authentication unit 82, a generation unit 83, a management unit 84, and a storage / reading processing unit 89. Each of these units is a function or means of functioning, realized by any of the components shown in Figure 2 operating according to instructions from the CPU 501 following a schedule management program deployed from the HD 504 onto the RAM 503. The schedule management server 12 also has a storage unit 8000 constructed by the HD 504 shown in Figure 2.

[0093] (User authentication management table) Figure 12 is a conceptual diagram showing the user authentication management table. The storage unit 8000 has a user authentication management DB 8001 constructed, which consists of the user authentication management table shown in Figure 12. In this user authentication management table, a user ID for identifying a user, an organization ID for identifying the organization to which the user belongs, and a password are associated and managed.

[0094] (User management table) Figure 13 is a conceptual diagram showing the user management table. The storage unit 8000 has a user management DB 8002 constructed, which consists of the user management table shown in Figure 13. In this user management table, the user ID and the name of the user (user name) indicated by the user ID are associated and managed for each organization ID.

[0095] (Common area management table) Figure 14 is a conceptual diagram showing the union management table. The storage unit 8000 has a union management DB 8003 constructed, which consists of the union management table shown in Figure 14. In this union management table, a union ID and the name of the union (union name) are associated and managed for each organization ID to identify the union.

[0096] (Shared Reservation Management Table) Figure 15 is a conceptual diagram showing the shared reservation management table. The storage unit 8000 has a shared reservation management DB 8004 constructed, which consists of the shared reservation management table shown in Figure 15. This shared reservation management table manages reservation information in which each piece of information is associated with another. The reservation information includes, for each organization ID, the shared ID, the shared name, the user ID of the shared terminal, the user ID of the person making the reservation, the scheduled start date and time of use, the scheduled end date and time of use, and the event name.

[0097] Note that the "User ID of the shared terminal" is the user ID of shared terminal 42, which is installed in a conference room, an example of a shared facility. The scheduled start date and time of use indicates the scheduled start date and time of use for the shared facility. The scheduled end date and time of use indicates the scheduled end date and time of use for the shared facility. Each date and time shows the year, month, day, hour, minute, second, and time zone. Due to space limitations, each date and time in Figure 15 is shown only up to the year, month, day, hour, and minute.

[0098] (Event management table) Figure 16 is a conceptual diagram showing the event management table. The memory unit 8000 has an event management DB 8005 constructed, which consists of the event management table shown in Figure 16. This event management table manages scheduled information in a way that each piece of information is associated with others. For each scheduled event ID, the scheduled information is managed with associated organization ID, user ID, user name, scheduled event start date and time, scheduled event end date and time, event name, memo, and file data.

[0099] Of these, the scheduled event start date and time indicates the scheduled start date and time if the event is to be held. The scheduled event end date and time indicates the scheduled end date and time if the event is to be held. Each date and time shows the year, month, day, hour, minute, second, and time zone. Due to space limitations, each date and time in Figure 16 is shown up to the year, month, day, hour, and minute. In addition, the event management table in Figure 16 manages file data of materials used in the event indicated in the scheduled information, associated with the scheduled event ID.

[0100] (Server Authentication Management Table) Figure 17 is a conceptual diagram showing the server authentication management table. The storage unit 8000 has a server authentication management DB 8006 constructed, which is composed of the server authentication management table shown in Figure 17. In this server authentication management table, access IDs and access passwords are associated and managed. The concepts of access IDs and access passwords are the same as those of access IDs and access passwords managed in the access management DB 6002 of the shared support server 11.

[0101] (Project Member Management Table) Figure 18 is a conceptual diagram showing the project member management table. The memory unit 8000 has a project member management DB 8007 constructed, which consists of the project member management table shown in Figure 18. In this project member management table, the project ID, project name, and user ID of each project member are associated and managed for each organization ID.

[0102] (Execution event history management table) Figure 19 is a conceptual diagram showing the execution event history management table. The memory unit 8000 has an execution event history management DB 8008 constructed, which consists of the execution event history management table shown in Figure 19. In this execution event history management table, the content processing ID, content processing type, content content, and the start and end dates and times of the content processing are associated and managed for each project ID and execution event ID.

[0103] The execution event history management DB8008 manages some of the same data as the content management DB6005. The same data includes the execution event ID, content processing ID, content processing type, content processing start date and time, and content processing end date and time. The content itself is the same, except that the notation for the content data storage location (http: / / or c: / / ) is different.

[0104] (Execution event management table) Figure 20 is a conceptual diagram showing the execution event management table. The memory unit 8000 has an execution event management DB 8009 constructed, which is composed of the execution event management table shown in Figure 20. In this execution event management table, the event name, the start date and time of the event, and the end date and time are associated with and managed for each execution event ID. This execution event management DB 8009 manages information about events that have actually been executed from the scheduled information managed in the event management DB 8005.

[0105] (Related Information Management Table) Figure 21 is a conceptual diagram showing the related information management table. The memory unit 8000 has a related information management DB 8010 constructed, which is composed of the related information management table shown in Figure 21. In this related information management table, related information is managed in which each piece of information (data) is associated with each project ID and execution event ID. The related information is managed in association with the time period in which the content occurred, the audio / video recording data, the audio-text data, and the screen data.

[0106] The content generation time period indicates the elapsed time from the event's start date and time to the point in time when the content was generated in the executed event. The content generation time period is generated by the generation unit 83 based on the event's start date and time stored in the event management DB 8005, and the content processing start and end dates and times stored in the executed event history management DB 8008. The content generation time period is an example of time information.

[0107] Audio / video data includes a content processing ID and content type. Audio-text data and screen data include a content processing ID, content type, and sequence number. The sequence number indicates the order in which content processing occurred for each of the audio-text and screen data.

[0108] (Functional configuration of the schedule management server) Next, we will explain in detail the functional configurations of the schedule management server 12. In addition, when explaining the functional configurations of the schedule management server 12, we will also explain the relationship between each component shown in Figure 3 and the main components necessary to realize each functional configuration of the schedule management server 12.

[0109] The transmit / receive unit 81 of the schedule management server 12 shown in Figure 6 is implemented by instructions from the CPU 501 shown in Figure 3 and the network I / F 509 shown in Figure 3. The transmit / receive unit 81 transmits and receives various data (or information) with user terminals 40, shared terminals 42, other servers, or other systems via the communication network 50.

[0110] The authentication unit 82 is implemented by instructions from the CPU 501 shown in Figure 3, and performs authentication by determining whether the information (user ID, organization ID, and password) sent from the user terminal 40 or shared terminal 42 is information that has been pre-registered in the user authentication management DB 8001. The authentication unit 82 also performs authentication by determining whether the information (access ID and access password) sent from the shared support server 11 is information that has been pre-registered in the server authentication management DB 8006.

[0111] The generation unit 83 is implemented by instructions from the CPU 501 shown in Figure 3 and has the function of generating related information to be registered in the related information management DB 8010. The management unit 84 is implemented by instructions from the CPU 501 shown in Figure 3 and manages events such as online meetings.

[0112] The memory and read processing unit 89 is implemented by instructions from the CPU 501 shown in Figure 3 and the HDD controller 505 shown in Figure 3, and performs processing such as storing various data in the memory unit 8000 and reading various data stored in the memory unit 8000.

[0113] 《Online Storage Server Functional Configuration》 The online storage server 20 has a transmitting / receiving unit 91 and a storage / reading processing unit 99. Each of these units is a function or means of functioning, which is realized by any of the components shown in Figure 3 operating according to instructions from the CPU 501 in accordance with a program deployed from the HD 504 onto the RAM 503. Furthermore, the online storage server 20 in Figure 6 has a storage unit 9000 constructed by the HD 504 shown in Figure 3.

[0114] (Functional configuration of each online storage server) Next, we will describe in detail the functional configurations of the online storage server 20. In addition, when describing the functional configurations of the online storage server 20, we will also explain the relationship between each component shown in Figure 3 and the main components necessary to realize each functional configuration of the online storage server 20.

[0115] The transmitting / receiving unit 91 of the online storage server 20 shown in Figure 6 is implemented by instructions from the CPU 501 shown in Figure 3 and the network interface 509 shown in Figure 2. The transmitting / receiving unit 91 transmits and receives various data (or information) with user terminals 40, shared terminals 42, other servers, or other systems via the communication network 50.

[0116] The memory and read processing unit 99 is implemented by instructions from the CPU 501 shown in Figure 3 and the HDD controller 505 shown in Figure 3, and performs processing such as storing various data in the memory unit 9000 and reading various data stored in the memory unit 9000.

[0117] Please note that the above IDs are examples of identification information. Organization IDs include company name, business name, department name, and regional name. User IDs include employee number, driver's license number, and My Number (social security and tax number) under Japan's social security and tax number system.

[0118] The functional configuration shown in Figure 6 is just one example, and the functions (each processing unit and storage unit) of the shared support server 11, schedule management server 12, online storage server 20, user terminal 40, and shared terminal 42 may be executed by any of them. For example, the determination unit 65 of the shared support server 11 may be located in either the user terminal 40 or the shared terminal 42.

[0119] <Processing or operation of the embodiment> The processing or operation of each embodiment will be described below.

[0120] 《Schedule Registration Process》 This section describes the process by which user A (Riko Taro) registers his own schedule from user terminal 40 to the schedule management server 12. Figure 22 is a sequence diagram showing the schedule registration process. Figure 23 is a diagram showing the sign-in screen. Figure 24 is an example of the initial screen of the user terminal. Figure 25 is a diagram showing the schedule screen. Figure 26 is a diagram showing the schedule input screen.

[0121] First, when user A operates the keyboard 511 or the like on user terminal 40, the display control unit 54 of user terminal 40 displays a sign-in screen 530 on the display 506 for signing in, as shown in Figure 23 (step S11).

[0122] This sign-in screen 530 includes input fields 531 for entering the user's user ID and organization ID, an input field 532 for entering a password, a sign-in button 538 to be pressed when signing in, and a cancel button 539 to be pressed when canceling the sign-in. Here, the user ID and organization ID are the email address of reservation holder A. The username part of the email address represents the user ID, and the domain name part represents the organization ID. Note that input field 531 may be an input field for entering the user ID and organization ID separately, rather than an email address.

[0123] Next, when user A enters their user ID and organization ID in input field 531, enters their password in input field 532, and presses the sign-in button 538, the reception unit 52 accepts the sign-in request (step S12).

[0124] Then, the transmitting / receiving unit 51 of the user terminal 40 sends sign-in request information to the schedule management server 12, indicating a request to sign in (step S13). The sign-in request information includes the information received in step S12 (user ID, organization ID, and password). As a result, the transmitting / receiving unit 81 of the schedule management server 12 receives the sign-in request information.

[0125] Next, the authentication unit 82 of the schedule management server 12 authenticates the reservation holder A using the user ID, organization ID, and password (step S14). Specifically, the storage and retrieval processing unit 89 searches the user authentication management DB 8001 (see Figure 12) for a user ID, organization ID, and password pair that corresponds to the user ID, organization ID, and password pair received in step S13.

[0126] If a matching pair exists, the authentication unit 82 determines that the requesting user A is a legitimate user. If no matching pair exists, the authentication unit 82 determines that user A is an illegitimate (unauthorized) user. If the user is not authorized, the transmitting / receiving unit 81 notifies the user terminal 40 that the user is not authorized. Here, we will continue the explanation for the case where the user is authorized. Next, the transmitting / receiving unit 81 sends the authentication result to the user terminal 40 (step S15). As a result, the transmitting / receiving unit 51 of the user terminal 40 receives the authentication result.

[0127] Next, if the user terminal 40's generation unit 56 receives an authentication result indicating that it is legitimate in step S15, it generates an initial screen 540 as shown in Figure 24 (step S16). Then, the user terminal 40's display control unit 54 displays the initial screen 540 as shown in Figure 24 on the display 506 (step S17).

[0128] This initial screen 540 includes a "Schedule Registration" button 541, which is pressed when registering a schedule, and a "View Execution Event History" button 543, which is pressed when viewing the execution event history.

[0129] When the user presses the "Register Schedule" button 541, the reception unit 52 accepts the schedule registration (step S18). Then, the transmitting / receiving unit 51 sends the schedule registration request information to the schedule management server 12 (step S19). As a result, the transmitting / receiving unit 81 of the schedule management server 12 receives the schedule registration request information.

[0130] Next, the storage and retrieval processing unit 89 of the schedule management server 12 uses the user ID of the reservation holder A received in step S13 as a search key to search the event management DB 8005 (see Figure 16) managed by the scheduler and retrieve the corresponding schedule information. The storage and retrieval processing unit 89 of the schedule management server 12 also uses the organization ID received in step S13 as a search key to search the user management DB 8002 (see Figure 13) and retrieve all corresponding user IDs and all user names (step S20). Then, the transmitting and receiving unit 81 transmits the schedule input screen information to the user terminal 40 (step S21). The transmitting and receiving unit 51 of the user terminal 40 receives the schedule input screen information.

[0131] This schedule input screen information includes the reservation information of reservation holder A read in step S20, all user IDs, and all user names. All user names also include the name (user name) of reservation holder A that was entered for sign-in in step S12.

[0132] Next, in the user terminal 40, the generation unit 56 generates the schedule screen 545 and the schedule input screen 550 using the schedule input screen information received in step S21 (step S22). Then, the display control unit 54 of the user terminal 40 displays the schedule screen 545 and the schedule input screen 550, as shown in Figure 25, on the display 506 (step S23).

[0133] This schedule screen 545 includes a schedule information display area 546 that displays the schedule information set for reservation user A, and a "Create Meeting" button 547 that is pressed when creating a meeting schedule. By pressing the "Create Meeting" button 547 on the schedule screen 545, reservation user A can transition from the schedule screen 545 to the schedule input screen 550.

[0134] This schedule input screen 550 includes an input field 551 for entering the event name, an input field 552 for entering the shared ID or shared name of the location to be used (such as a meeting room), an input field 553 for entering the scheduled start and end dates and times of the event, an input field 555 for entering notes, a display area 556 for displaying the name of the person who made the reservation, an input field 557 for entering the names of other participants besides the person who made the reservation, an input field 558 for entering the shared terminal 42 to be used for the event, a "Schedule Settings" button 559 to be pressed when registering a schedule, and a "Close" button 560 to be pressed when canceling the content being entered or that has been entered.

[0135] Furthermore, the input field 558 for entering the shared terminal 42 to be used in the event may be configured to suggest candidates 561, as shown in Figure 27, by entering part of the name (user name) of the shared terminal 42. When a terminal is entered in the input field 558, or when a shared terminal 42 to be used in the event is selected from the candidates 561, it is set as a device to be used in the event, as shown in the device display field 562 of the schedule input screen 550 in Figure 28.

[0136] Alternatively, the settings for the equipment to be used at the event can be configured, for example, by entering the location to be used, such as a conference room, in the input field 552, as shown in the schedule input screen 550 in Figure 29. This will configure the shared terminal 42 installed in that location as the equipment to be used at the event.

[0137] Next, the reservation holder A enters the necessary information on the schedule input screen 550 and presses the "Schedule Settings" button 559. The reception unit 52 then accepts the schedule information (step S24). The transmission / reception unit 51 then sends the schedule information to the schedule management server 12 (step S25).

[0138] This schedule information includes the event name, shared ID (or shared name), scheduled start date and time, scheduled end date and time, each participant's user ID, the user ID of the shared terminal 42 to be used, and a memo. Although omitted in the schedule input screen 550 in Figure 25, if the reservation holder A has selected file data for materials to be used in the event, that file data will be included in the schedule information.

[0139] The transmit / receive unit 81 of the schedule management server 12 receives schedule information. Next, when the schedule management server 12 receives the union ID (or union name) in step S25, it searches the union management DB 8003 (see Figure 14) using the received union ID as a search key and reads the corresponding union name (or union ID) (step S26).

[0140] Next, the storage / reading processing unit 89 stores the reservation information for the union name (or union ID) read in step S26 in the union reservation management DB 8004 (see Figure 15) (step S27). The storage / reading processing unit 89 adds one record of reservation information to the union reservation management table of the union reservation management DB 8004, which is managed by a pre-registered scheduler. The reservation information is composed of the schedule information received in step S25 and the union name (or union ID) read in step S26. In the example of the union reservation management table in Figure 15, the item "User ID of shared terminal" represents the shared terminal 42 that has been set as the device to be used in the event. The scheduled start date and time in the union reservation management DB 8004 corresponds to the scheduled start date and time in the schedule information. Also, the scheduled end date and time in the union reservation management DB 8004 corresponds to the scheduled end date and time in the schedule information.

[0141] Furthermore, the storage and retrieval processing unit 89 stores the schedule information in the event management DB 8005 (see Figure 16) (step S28). The storage and retrieval processing unit 89 adds one record of schedule information to the event management table of the event management DB 8005, which is managed by a pre-registered scheduler.

[0142] The schedule information is constructed based on the schedule information received in step S25. In the example event management table in Figure 16, a shared terminal 42 with user ID "u0000" is set as the device to be used for the event. Note that the scheduled start date and time of the event in the event management DB 8005 corresponds to the scheduled start date and time in the schedule information. Also, the scheduled end date and time of the event in the event management DB 8005 corresponds to the scheduled end date and time in the schedule information. Thus, user A can register the schedule for an online meeting or other event in which they have selected the shared terminal 42 as the device to be used.

[0143] Event Start Processing This section describes the process of conducting an online meeting with other participants' user terminals 40 using a shared terminal 42 in conference room X, which was reserved by participant A (Rikotaro). Figures 30 and 31 are sequence diagrams showing the event start process.

[0144] First, when user A presses the power switch of the shared terminal 42, the reception unit 22 of the shared terminal 42 receives a power-on request from user A (step S31). The display control unit 24 of the shared terminal 42 displays a sign-in screen on the display 220 for signing in (step S32).

[0145] Next, when user A enters their email address and password on the sign-in screen, the reception unit 22 accepts the sign-in request (step S33). The transmission / reception unit 21 sends sign-in request information to the shared support server 11 (step S34). The sign-in request information includes the information received in step S33 (user ID, organization ID, and password). As a result, the transmission / reception unit 61 of the shared support server 11 receives the sign-in request information.

[0146] Next, the authentication unit 62 of the shared support server 11 authenticates user A using the user ID, organization ID, and password of user A received in step S34 (step S35). Specifically, the storage and retrieval processing unit 69 uses the user ID, organization ID, and password of user A received in step S34 as a search key to search the user authentication management DB 6001 (see Figure 7) for a user ID, organization ID, and password pair corresponding to the user ID, organization ID, and password pair of user A received in step S34.

[0147] If a matching pair exists, the authentication unit 62 determines that the requesting user A is a legitimate user. If no matching pair exists, the authentication unit 62 determines that the requesting user A is an illegitimate (unauthorized) user. If the user is not authorized, the transmission / reception unit 61 notifies the shared terminal 42 that the user is not authorized. The explanation continues here regarding the case where the user is authorized.

[0148] Next, the storage and read processing unit 69 of the shared support server 11 searches the access management DB 6002 (see Figure 8) using the organization ID of the reservation holder A received in step S34 as the search key, and reads the corresponding access ID and access password (step S36).

[0149] Next, the transmitting / receiving unit 61 transmits reservation request information indicating a request for shared reservation information and schedule request information indicating a request for user schedule information to the schedule management server 12 (step S37). The reservation request information and schedule request information include the user ID, organization ID, and password of the reservation holder A received in step S34, as well as the access ID and access password read in step S36. The transmitting / receiving unit 81 of the schedule management server 12 receives the reservation request information and schedule request information. Next, the authentication unit 82 of the schedule management server 12 authenticates the shared support server 11 using the access ID and access password (step S38).

[0150] Specifically, the storage and retrieval processing unit 89 searches the server authentication management DB 8006 (see Figure 17) for the access ID and access password pair corresponding to the access ID and access password pair received in step S37.

[0151] If a matching pair exists, the authentication unit 82 determines that the requesting shared support server 11 is a legitimate accessor. If no matching pair exists, the authentication unit 82 determines that the requesting shared support server 11 is an unauthorized (illegitimate) accessor. If the access is not legitimate, the transmission / reception unit 81 notifies the shared support server 11 that the access is not legitimate. The explanation continues here for cases where the access is legitimate.

[0152] The storage and retrieval processing unit 89 of the schedule management server 12 uses the shared ID received in step S37 as a search key to search the shared reservation management DB 8004 (see Figure 15) managed by the scheduler, and retrieves the corresponding reservation information (step S39). In this case, the storage and retrieval processing unit 89 retrieves the reservation information for which the scheduled start date and time is today.

[0153] Furthermore, the memory / reading processing unit 89 uses the user ID of reservation holder A received in step S37 as a search key to search the event management DB 8005 (see Figure 16) managed by the scheduler, and reads the corresponding schedule information (step S40).

[0154] In this case, the memory / reading processing unit 89 reads out the scheduled event information for which the scheduled start date and time is today. If the schedule management server 12 is in a different country or region from the shared terminal 42, it adjusts the time zone to match the country or region where the shared terminal 42 is located, based on the time zone information.

[0155] Next, the storage and retrieval processing unit 89 uses the user ID of reservation holder A received in step S37 as a search key to search the project member management DB 8007 (see Figure 18) and retrieves the project IDs and project names of all projects that include the user ID of reservation holder A (step S41).

[0156] Next, the transmitting / receiving unit 81 transmits the reservation information read in step S39, the schedule information read in step S40, and all project IDs and all project names read in step S41 to the shared support server 11 (step S42). As a result, the transmitting / receiving unit 61 of the shared support server 11 receives the reservation information, schedule information, all project IDs, and all project names.

[0157] Next, the creation unit 63 of the shared support server 11 creates a reservation list based on the reservation information and schedule information received in step S42 (step S43). Then, the transmission / reception unit 61 transmits reservation list information, which shows the contents of the reservation list, as well as all project IDs and all project names, to the shared terminal 42 (step S44). The transmission / reception unit 21 of the shared terminal 42 receives the reservation list information, as well as all project IDs and all project names.

[0158] Next, in the shared terminal 42, the display control unit 24 displays the reservation list screen 230 shown in Figure 32 on the display 220 (step S45). Figure 32 is a diagram showing the reservation list screen of a shared space. This reservation list screen 230 includes a display area 231 that displays the name of the shared space (in this case, the location name), and a display area 232 that displays the date and time of today. Furthermore, the reservation list screen 230 displays event information 235~237 etc. related to events using this shared space (in this case, conference room X) today. Event information refers to the information and data related to the aforementioned events. Each event information includes, for each event, the scheduled start and end times for using this shared space, the event name, and the name of the person who reserved this shared space (reservation name). Event information includes, but is not limited to, start buttons 235s~237s etc. that are pressed when a user identifies an event to start, and may also include participants and the actual start and end times of use.

[0159] Next, in Figure 28, when user A presses the start button 235s with the electronic pen 2500 or the like, the reception unit 22 accepts the selection of the event indicated in the event information 235 (step S51). Then, the display control unit 24 displays the project list screen 240 on the display 220, as shown in Figure 33, based on the project ID and project name received in step S44 (step S52).

[0160] Figure 33 shows the project list screen. The project list screen 240 includes project icons 241 to 246, each representing a project. The project list screen 240 also includes an "OK" button 248, which is pressed to confirm the selected project icon, and a "CANCEL" button 249, which is pressed to cancel the selection of a project icon.

[0161] Next, in Figure 33, when user A presses the project icon 241 with the electronic pen 2500 or the like, the reception unit 22 accepts the selection of the project indicated by the project icon 241 (step S53).

[0162] Next, the transmitting / receiving unit 21 of the shared terminal 42 transmits to the shared support server 11 the scheduled event ID indicating the scheduled event selected in step S51, and the project ID indicating the project selected in step S53 (step S54). The processing in step S54 is a request processing for transmission of execution event identification information. As a result, the transmitting / receiving unit 61 of the shared support server 11 receives the selected scheduled event ID and the selected project ID.

[0163] Next, in the shared support server 11, the generation unit 64 generates a unique execution event ID (step S55). Then, the storage / reading processing unit 69 manages the execution event ID generated in step S55, the reservation event ID received in step S54, the user ID and organization ID of the person making the reservation, and the event information in association (step S56).

[0164] The user ID and organization ID of the person making the reservation, as well as the event information, are based on the reservation and schedule information received in step S42. At this point, there is no input in the participation status column of the reservation management table (see Figure 9).

[0165] Next, the storage and retrieval processing unit 69 stores and manages the project ID received in step S54 and the execution event ID generated in step S55 in association with each other (step S57).

[0166] Next, the shared support server 11's transmission / reception unit 61 sends file data transmission request information to the schedule management server 12, indicating a request to send file data registered with the schedule management server 12 (step S58). The file data transmission request information includes the scheduled event ID received in step S54, the user ID and organization ID of reservation holder A received in step S34, and the access ID and access password read in step S36. As a result, the transmission / reception unit 81 of the schedule management server 12 receives the file data transmission request information.

[0167] Next, the storage and read processing unit 89 of the schedule management server 12 searches the event management DB 8005 (see Figure 16) using the scheduled event ID received in step S58 as a search key, and reads the file data associated with the scheduled event ID (step S59). Then, the transmitting and receiving unit 81 sends the file data read in step S59 to the shared support server 11 (step S60). As a result, the transmitting and receiving unit 61 of the shared support server 11 receives the file data.

[0168] Next, the storage and reading processing unit 69 of the shared support server 11 stores and manages the file data received in step S60 in the schedule management DB 6003 (see Figure 9) in association with the scheduled event ID received in step S54 and the execution event ID generated in step S55 (step S61).

[0169] The transmitting / receiving unit 61 transmits the execution event ID generated in step S55 and the file data received in step S60 to the shared terminal 42 where reservation holder A is signed in (step S62). As a result, the transmitting / receiving unit 21 of the shared terminal 42 receives the execution event ID and file data. The transmitting / receiving unit 21 may also send invitations to other participants' user terminals 40 to attend the event using email or other means. These invitations to attend the event include various information necessary for participating in (attending) the event started by reservation holder A.

[0170] This allows other participants to use the event attendance request to notify the shared support server 11 from their user terminal 40 of their participation in the event, and to join the online meeting or other event started by participant A.

[0171] Next, in the shared terminal 42, the storage and reading processing unit 29 stores the execution event ID and file data in the storage unit 2000 (step S63). Here, the file data transmitted from the shared support server 11 is stored in a specific storage area of ​​the storage unit 2000. As a result, when the shared terminal 42 is executing an event, it accesses the specific storage area, causing the display control unit 24 to display the file data stored in the specific storage area on the display 220.

[0172] Here, the specific storage area is a temporary storage location for data provided for each event in progress, and is identified by an arbitrary path (string) indicating its location within the storage unit 2000. The specific storage area is not limited to being located inside the shared terminal 42, but may also be located in an external storage device connected to the shared terminal 42, or in a local server or the like that exists in an on-premises environment and can communicate with the shared terminal 42.

[0173] Next, the display control unit 24 displays the detailed information screen 250 of the selected event on the display 220, as shown in Figure 34 (step S64). This detailed information screen 250 of the event includes a display area 251 for the event name, a display area 252 for the scheduled event duration (scheduled start time and scheduled end time), and a display area 253 for the name of the person who made the reservation. Furthermore, the detailed information screen 250 of the event also displays a display area 256 for displaying the contents of a memo, a display area 257 for displaying the names of the participants, and a display area 258 for displaying identification information (e.g., file name) to identify file data stored in a specific storage area of ​​the storage unit 2000.

[0174] Display area 257 displays the name of the person who made the reservation and the names of other selected participants. Display area 258 displays the file names of file data stored in a specific storage area of ​​the storage unit 2000, i.e., file data downloaded from the shared support server 11, as well as the file names of file data currently being downloaded from the shared support server 11. Furthermore, the lower right side of the event details screen 250 includes a "close" button 259 which is pressed to close this details screen 250.

[0175] Next, for example, other participants who have received an invitation to attend an event send a notification of their participation to the shared support server 11 from their user terminal 40 and join the event, such as an online meeting, started by reservation holder A (step S66). As a result, the sending / receiving unit 61 of the shared support server 11 receives the user IDs of the other participants who have joined the event, such as an online meeting, started by reservation holder A. Next, the shared support server 11 stores and manages whether or not participants are participating in the participation status column, which was not previously entered in the schedule management DB 6003 (step S67).

[0176] As a result, the reservation holder A and the other participants can start an event (in this case, an online meeting) using the shared space (in this case, conference room X) and the shared terminal 42. The display control unit 24 displays the event execution screen on the display 220.

[0177] ≪Processing during the event≫ Next, we will explain the process that takes place during an online meeting, which is an example of an event. First, in the online meeting that has started, participant A, who is a member of the collaborative project, and other participants can use the file sharing function, screen sharing function, voice call function, video call function, chat function, etc. provided by the collaboration system 10.

[0178] During the online meeting, participant A and other participants can use the chat function to send a message from user terminal 40 to shared terminal 42 that mentions shared terminal 42, thereby controlling the functions of shared terminal 42 as described below.

[0179] Figure 35 is a diagram illustrating the relationship between the message content of a chat function and the operations (functions) of a shared terminal that can be controlled by that message content. The message content in Figure 35 is the content of a message posted using the chat function, and may be text or an attached file.

[0180] For example, in the example in Figure 35, if the message content includes a file "test.ppt" with a mention, such as "@○○ Conference Room Electronic Whiteboard" in Figure 36, then the operation is to display the "test.ppt" file in Figure 36 on the shared terminal 42, as shown in the screen image in Figure 37. Figure 36 is a diagram showing an example of message content posted using the chat function. Figure 37 is a diagram showing an example of the attached file display screen.

[0181] Furthermore, the example in Figure 35 indicates that if the message content includes a mention, such as "@○○ Conference Room Electronic Whiteboard" in Figure 38, and also contains the text "screen capture," the operation involves capturing a screen containing written content, such as the screen image in Figure 39, and posting that screen capture file as shown in the message content at the bottom of Figure 38.

[0182] Furthermore, in the example in Figure 35, if the message content includes a mention such as "@○○ Conference Room Electronic Whiteboard" and the text "View Screen," it indicates that the operation involves screen sharing of the display screen of the shared terminal 42, such as the screen image diagram in Figure 40(a), among members participating in the same online meeting. Figure 40 shows an example of the display screen and camera image of the shared terminal.

[0183] Furthermore, in the example in Figure 35, if the message content includes a mention such as "@○○ Conference Room Electronic Whiteboard" and the text "View Camera Footage," it indicates that the operation involves screen sharing of the camera image of the shared terminal 42, as shown in the screen image diagram in Figure 40(b), among members participating in the same online meeting.

[0184] In addition to using the chat function, the display image in Figure 40(a) and the camera image in Figure 40(b) can also be switched using the button 580 in the lower left corner of the screen of the shared terminal 42 in Figure 40.

[0185] Furthermore, in the example in Figure 35, if the message content includes text indicating the end of the meeting, such as "Test finished" in Figure 41, it indicates that the operation is to post the meeting log data file "meetinglog.zip", as shown in the lower part of Figure 41.

[0186] The process by which participants in an online meeting control the functions of the shared terminal 42 using the chat function, as shown in Figure 35, can be realized, for example, by the processing steps shown in the sequence diagrams in Figures 42 and 43.

[0187] Figures 42 and 43 are sequence diagrams illustrating the process by which a user requests control of a shared terminal using the chat function. The sequence diagram in Figure 42 shows an example where a user (Person A) participating in the same online meeting as shared terminal 42 requests control of the shared terminal 42's functions using the chat function. The sequence diagram in Figure 43 shows an example where a user (Person B) not participating in the same online meeting as shared terminal 42 requests control of the shared terminal 42's functions using the chat function.

[0188] In Figure 42, user terminal 40 posts a chat message to the collaboration system 10 by sending a chat message from user (Person A) that mentions shared terminal 42 and has a file attached (step S100).

[0189] The collaboration system 10 sends the posted message with a mention to the shared terminal 42 (step S102). The shared terminal 42 determines that the message it received is a request to display (project) the attached file because the mention specifies its own machine and the message has a file attachment.

[0190] Here, the determination unit 25 of the shared terminal 42 queries the collaboration system 10 to determine whether the user (Person A) who posted the message received in step S102 is participating in the same online meeting as its own device (shared terminal 42) (step S104). As an example, the identification information of the user (Person A) who posted the message is sent from the shared terminal 42 to the collaboration system 10. The collaboration system 10 has a schedule management table, as shown in Figure 9, in the storage unit 6000 of the shared support server 11. The schedule management table contains the name of the person who made the reservation for the online meeting, the user ID of the person who made the reservation, the names of other participants, and the user IDs of the other participants. The collaboration system 10 determines whether the received user's identification information is included in the identification information of the person who made the reservation or other participants in the schedule management table. If it is included, it determines that they are participating in the same online meeting. Since Figure 42 is an example of participating in the same online meeting, the collaboration system 10 returns "Yes" to the shared terminal 42, indicating that they are participating in the same online meeting (step S106).

[0191] The function control unit 31 of the shared terminal 42 controls the system to display (project) the attached files of the message received in step S102 (step S108) because the user who posted the message (Person A) was participating in the same online conference as the shared terminal 42.

[0192] According to the sequence diagram in Figure 42, a user can operate the shared terminal 42 from their user terminal 40 by sending a chat message to the shared terminal 42, which is participating in the same online meeting.

[0193] In Figure 43, user terminal 40 posts a chat message (step S110) by sending a chat message to the collaboration system 10 in which user (Person B) mentions shared terminal 42 and has a file attached.

[0194] The collaboration system 10 sends the posted message with a mention to the shared terminal 42 (step S112). The shared terminal 42 determines that the message it received is a request to display (project) the attached file because the mention specifies its own machine and the message has a file attachment.

[0195] Here, the determination unit 25 of the shared terminal 42 queries the collaboration system 10 to find out whether the user (Person B) who posted the message received in step S112 is participating in the same online meeting as its own device (shared terminal 42) (step S114). Figure 43 shows an example where the users are not participating in the same online meeting, so the collaboration system 10 returns "No" to the shared terminal 42, indicating that they are not participating in the same online meeting (step S116).

[0196] The function control unit 31 of the shared terminal 42 does not display (project) the attachments of the message received in step S112 because the user who posted the message (Person B) is not participating in the same online conference as its own device (shared terminal 42).

[0197] Furthermore, the determination unit 25 posts a message, for example, as shown in Figure 44, specifying the user (Mr. B) as a mention (step S118). Figure 44 is a diagram showing an example of a message posted using the chat function. In the example in Figure 44, the message includes a mention, such as "@Mr. B", and contains the text, "You cannot operate this because you are not participating in the same meeting as the electronic whiteboard in the XX conference room."

[0198] The collaboration system 10 sends the posted message with the mention to the user terminal 40 operated by user (Person B) (step S120). User (Person B) can confirm from the message content in Figure 44 that he is not participating in the same online meeting as the shared terminal 42, and therefore the file attached to the message posted in step S110 was not displayed (projected) on the shared terminal 42.

[0199] According to the sequence diagram in Figure 43, it is possible to reject operations on the shared terminal 42 using the chat function from users who are not participating in the same online meeting.

[0200] In the sequence diagrams shown in Figures 42 and 43, the shared terminal 42 determined from the message content it received that it was a request to display (project) an attachment. However, the collaboration system 10 may also make this determination, for example, as shown in the sequence diagrams in Figures 45 and 46.

[0201] Figures 45 and 46 are sequence diagrams illustrating the process by which a user requests control of a shared terminal using the chat function. The sequence diagram in Figure 45 shows an example where a user (Person A) participating in the same online meeting as shared terminal 42 requests control of the shared terminal 42's functions using the chat function. The sequence diagram in Figure 46 shows an example where a user (Person B) not participating in the same online meeting as shared terminal 42 requests control of the shared terminal 42's functions using the chat function.

[0202] In Figure 45, user terminal 40 posts a chat message by sending a chat message to the collaboration system 10 in which user (Person A) mentions shared terminal 42 and has a file attached (step S140).

[0203] The decision unit 65 of the collaboration system 10 determines that the posted message with a mention is a request to display (project) an attached file because the mention specifies the shared terminal 42 and the message has a file attachment. The decision unit 65 can determine the type of operation request using a combination table that associates message content with the operation content (function) of the shared terminal 42 that can be controlled by that message content, for example, as shown in Figure 35.

[0204] Here, the determination unit 65 checks whether the user (Person A) who posted the message received in step S140 is participating in the same online meeting as the shared terminal 42 (step S142). Figure 45 is an example of participating in the same online meeting, so it is determined that they are participating in the same online meeting.

[0205] The control request unit 67 of the collaboration system 10 requests control from the shared terminal 42 to display (project) the attached file of the message received in step S140, because the user who posted the message (Person A) was participating in the same online meeting as the shared terminal 42 (step S144).

[0206] The function control unit 31 of the shared terminal 42 controls the display (projection) of the message attachments in step S140 in accordance with the control request in step S144 (step S146).

[0207] According to the sequence diagram in Figure 42, a user can operate the shared terminal 42 from their user terminal 40 by sending a chat message to the shared terminal 42, which is participating in the same online meeting.

[0208] In Figure 46, user terminal 40 posts a chat message by sending a chat message to the collaboration system 10 in which user (Person B) has mentioned shared terminal 42 and attached a file (step S160).

[0209] The decision unit 65 of the collaboration system 10 determines that the posted message with a mention specifies the shared terminal 42 and has a file attached, and therefore determines that it is a request to display (project) the attached file.

[0210] Here, the determination unit 65 checks whether the user (Person B) who posted the message received in step S160 is participating in the same online meeting as the shared terminal 42 (step S162). Figure 46 is an example where they are not participating in the same online meeting, so it is determined that they are not participating in the same online meeting.

[0211] The collaboration system 10 sends a message with a mention, such as the one shown in Figure 44, to the user terminal 40 operated by user (B) because user (B) is not participating in the same online meeting as shared terminal 42 (step S164). User (B) can confirm from the message content in Figure 44 that the file attached to the message posted in step S160 was not displayed (projected) on shared terminal 42 because he / she is not participating in the same online meeting as shared terminal 42.

[0212] According to the sequence diagram in Figure 46, it is possible to reject operations on the shared terminal 42 using the chat function from users who are not participating in the same online meeting.

[0213] [Other embodiments] In the above embodiment, we described the use of messages displayed on the chat screen, but it is also possible to use messages sent internally by the system (not displayed on the chat screen). Furthermore, this can also be achieved using a message sending function separate from the chat function.

[0214] Furthermore, although the above embodiment shows an example of text chat, it is also possible to operate the shared terminal 42 by voice, for example. Figure 47 is a sequence diagram showing the process of a user requesting control of the shared terminal by voice. The sequence diagram in Figure 47 shows an example in which a user (Person A) participating in the same online meeting as the shared terminal 42 requests control of the functions of the shared terminal 42 using the chat function.

[0215] In Figure 47, the user (Person A) operating the user terminal 40 speaks aloud, "Capture the screen of the electronic whiteboard in the XX conference room" (Step S180). The user terminal 40 operated by User A performs voice analysis processing of the spoken words and converts the voice data into text data (Step S182).

[0216] The user terminal 40 posts a chat message to the collaboration system 10 by using the text data converted from the audio data through the audio analysis process in step S182, in which the shared terminal 42 is specified as a mention and a file is attached (step S184). The collaboration system 10 then sends the posted message with the mention to the shared terminal 42 (step S186).

[0217] The processing from step S186 onwards is the same as the processing from step S102 onwards in Figure 42, so the explanation is omitted. Note that in Figure 47, the user terminal 40 performs the voice analysis processing of the spoken words, but this may be done on the collaboration system 10 side. Alternatively, for example, by using the voice chat function, voice messages may be posted, and the collaboration system 10 or shared terminal 42 may perform the voice analysis processing to determine the type of operation request from the message content.

[0218] Furthermore, after the aforementioned online meeting ends, the meeting log data posted as a file, such as the message in the lower part of Figure 41, includes, for example, a screenshot of the screen containing the content written at the end of the online meeting, and audio / video recordings of the microphone 2200, camera 2400, and other recorded audio / video data.

[0219] It should be noted that after a typical online meeting ends, the shared terminal 42 may be powered off or all its contents deleted. While this is not a problem if the power is turned off or the contents deleted after the online meeting ends, if this operation is performed during the online meeting, it will become impossible to post the meeting log data correctly.

[0220] Therefore, if the shared terminal 42 receives an operation from a user to turn off the power or delete the contents (such as deleting all or deleting a page) during an online meeting, it may display a UI like the one in Figure 48 to confirm with the user whether or not to post the meeting log to the chat. By using a UI like the one in Figure 48, the shared terminal 42 can successfully post the meeting log data file, as shown in Figure 49, even if it receives an operation from a user to turn off the power or delete the contents during an online meeting.

[0221] The present invention is not limited to the embodiments specifically disclosed above, and various modifications and changes are possible without departing from the scope of the claims. For example, it is possible to combine the first embodiment with other embodiments. It goes without saying that the information processing system 1 described in this embodiment is just one example, and there are various system configurations depending on the application and purpose.

[0222] Each of the functions of the embodiments described above can be realized by one or more processing circuits. Hereinafter, "processing circuit" as used herein includes processors programmed to execute each function by software, such as processors implemented by electronic circuits, as well as devices such as ASICs (Application Specific Integrated Circuits), DSPs (digital signal processors), FPGAs (field programmable gate arrays), and conventional circuit modules designed to execute each of the functions described above.

[0223] The apparatus described in the examples represents only one of several computing environments for carrying out the embodiments disclosed herein.

[0224] In one embodiment, the shared support server 11 and the schedule management server 12 include multiple computing devices, such as a server cluster. The multiple computing devices are configured to communicate with each other via any type of communication link, including a communication network 50 and shared memory, and perform the processing disclosed herein.

[0225] Furthermore, the shared support server 11, schedule management server 12, speech-to-text conversion server 13, file management server 14, user terminal 40, and shared terminal 42 can be configured to share the disclosed processing steps in various combinations. For example, a process performed by a given unit may be performed by other units. Similarly, the functions of a given unit may be performed by other units. In addition, the elements of the shared support server 11, schedule management server 12, speech-to-text conversion server 13, and file management server 14 may be combined into a single device or divided among multiple devices.

[0226] Note that the collaboration system 10 is an example of a collaborative work support system. The management unit 84 is an example of a management means. Chat function messages and voice messages are examples of spoken data. The distribution unit 66 is an example of a distribution means. The function control unit 31 is an example of a function control means. The save request unit 32 is an example of a save request means. The schedule input screen 550 is an example of a settings screen. The judgment unit 25 is an example of a judgment means. The control request unit 67 is an example of a control request means. The information processing system 1 is an example of a text data transmission and reception system. The collaboration system 10 is an example of an information processing device. The transmission and reception unit 51 is an example of a transmission and reception means. The function control unit 31 is an example of a control means. The storage unit 6000 is an example of a storage means. The camera 2400 is an example of a shooting means. [Explanation of symbols]

[0227] 1. Information Processing System 10 Collaboration Systems 11. Shared support server 12. Schedule Management Server 13. Speech-to-text conversion server 14. File Management Server 20 Online Storage Servers 25 Judgment Department 31 Functional Control Unit 32 Save request section 40 User terminals 42 Shared terminals 50 Communication Networks 66 Distribution Department 67 Control Request Unit 84 Management Department [Prior art documents] [Patent Documents]

[0228] [Patent Document 1] Japanese Patent Publication No. 2018-32096

Claims

1. A text data transmission and reception system comprising multiple user terminals, a shared terminal, and an information processing device that can connect to each of the multiple user terminals and the shared terminal via a network, A transmission and reception means for sending and receiving text data between the aforementioned multiple user terminals, A determination means for determining whether or not the text data transmitted and received between the plurality of user terminals includes a request for control to the shared terminal, A control means for controlling the shared terminal when the text data includes a request to control the shared terminal, A text data transmission and reception system having the following features.

2. The control means controls the shared terminal if the user who sent the text data from one of the multiple user terminals participates in an event related to the text data transmitted and received between the multiple user terminals, and does not control the shared terminal if the user does not participate in the event. The text data transmission and reception system according to claim 1.

3. The determination means determines whether the identification information of the user who sent the text data from one of the user terminals is included in the identification information of the participants taking part in the event. The control means controls the shared terminal when it is determined that the user's identification information is included in the identification information of participants participating in the event. If it is determined that the user's identification information is not included in the identification information of participants taking part in the event, the shared terminal will not be controlled. The text data transmission and reception system according to claim 2.

4. The system further includes a storage means for storing shared data, including text data used in the aforementioned event. The text data transmission and reception system according to claim 2 or 3.

5. The storage means saves the shared data during or after an event relating to text data transmitted and received between the plurality of user terminals. The text data transmission and reception system according to claim 4.

6. The system further includes a management means for managing event information, which includes information about users who send and receive text data between the plurality of user terminals, and information about the shared terminal. A text data transmission and reception system according to any one of claims 1 to 5.

7. The control of the aforementioned shared terminal is as follows: Control for acquiring the screen displayed on the display unit of the shared terminal, control for displaying the screen captured by the shooting means of the shared terminal on the display units of the multiple user terminals, and Includes at least one of the following: control to save shared data used in events related to text data sent and received between the aforementioned multiple user terminals. A text data transmission and reception system according to any one of claims 1 to 6.

8. A shared terminal that can be connected via a network to multiple user terminals and information processing devices, Receiving means for receiving text data transmitted and received between the aforementioned plurality of user terminals, A determination means for determining whether the received text data includes a request for control to the shared terminal, A control means for controlling the shared terminal when the text data includes a request to control the shared terminal, A shared terminal having the following features.

9. An information processing device that can connect to multiple user terminals and shared terminals via a network, Receiving means for receiving text data transmitted and received between the aforementioned plurality of user terminals, A determination means for determining whether the received text data includes a request for control to the shared terminal, A control request means for making a control request to the shared terminal when the text data includes a control request to the shared terminal, An information processing device having

10. A user terminal that can connect to a shared terminal, an information processing device, and other user terminals via a network, A receiving means for receiving input of text data to be sent to the aforementioned other user terminal, A determination means for determining whether the received text data includes a request for control to the shared terminal, If the text data includes a request to control the shared terminal, a control request means for making a request to control the shared terminal is provided. A user terminal.

11. An information processing method performed by multiple user terminals and a shared terminal that can be connected to an information processing device via a network, A receiving step of receiving text data transmitted and received between the aforementioned multiple user terminals, A determination step of determining whether the received text data includes a request for control to the shared terminal, If the text data includes a request to control the shared terminal, a control step is performed to control the shared terminal. An information processing method having

12. An information processing method performed by an information processing device that can connect to multiple user terminals and shared terminals via a network, A receiving step of receiving text data transmitted and received between the aforementioned multiple user terminals, A determination step of determining whether the received text data includes a request for control to the shared terminal, If the text data includes a request for control to the shared terminal, a control request step is made to make a request for control to the shared terminal. An information processing method having

13. An information processing method performed by a user terminal that can connect to a shared terminal, an information processing device, and other user terminals via a network, A reception step that accepts input of text data to be sent to the aforementioned other user terminal, A determination step of determining whether the received text data includes a request for control to the shared terminal, If the text data includes a request to control the shared terminal, a control request step is made to request control of the shared terminal. An information processing method having

14. A shared terminal that can connect to multiple user terminals and information processing devices via a network, Receiving means for receiving text data transmitted and received between the aforementioned plurality of user terminals, A determination means for determining whether the received text data includes a request for control to the shared terminal. If the text data includes a request to control the shared terminal, a control means for controlling the shared terminal, A program designed to function as such.

15. An information processing device that can connect to multiple user terminals and shared terminals via a network, Receiving means for receiving text data transmitted and received between the aforementioned plurality of user terminals, A determination means for determining whether the received text data includes a request for control to the shared terminal. If the text data includes a request for control to the shared terminal, a control request means for making a request for control to the shared terminal, A program designed to function as such.

16. A shared terminal, an information processing device, and a user terminal that can connect to other user terminals via a network, A receiving means for receiving input of text data to be sent to the aforementioned other user terminal, A determination means for determining whether the received text data includes a request for control to the shared terminal. If the text data includes a request to control the shared terminal, a control request means for making a request to control the shared terminal, A program designed to function as such.

Images