System, shared terminal, information processing device, user terminal, information processing method and program

Abstract

To provide a text data transmission / reception system capable of supporting a user participating in an event in operating a shared terminal 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 connectable to each of the plurality of user terminals and the shared terminal via a network, which solves the above problem by having a transmission and reception means for transmitting and receiving text data between the plurality of user terminals, a judgment means for determining whether the text data transmitted and received between the plurality of user terminals includes a request for control of the shared terminal, and a control means for controlling the shared terminal when the text data includes a request for control of the shared terminal.

Description

[Technical Field]

[0001] The present invention , Shi The present invention relates to a system, a shared terminal, an information processing device, a user terminal, an information processing method, and a program. [Background technology]

[0002] Conventionally, remote conference systems have been known in which an interactive whiteboard is connected to a computer or the like via a network. Some conventional remote conference systems also have a function for managing audio data during a conference, captured images from an electronic whiteboard, various data received from terminal devices (text data such as chat data), and the like as a conference log (see, for example, Patent Document 1). Summary of the Invention [Problem to be solved by the invention]

[0003] In recent years, tools (an example of a collaboration tool) that support collaborative work in groups or teams by providing functions such as communication and information sharing to multiple users working in groups or teams have come into use. Collaboration tools allow multiple users who have formed a group or team for collaborative work to hold online conferences by using communication functions such as chat and voice calling. In online conferences using communication functions, multiple users who have formed a group or team to work together can record data sent and received using the chat function during the online conference, as well as audio and video recording data recorded using the audio and video recording function, as a conference log.

[0004] However, when used in an online conference, which is one example of an event, there was a problem in that in order to display a specified file on a shared terminal such as an electronic whiteboard that is being used by participants in the online conference, or to share or capture the screen displayed on the shared terminal, a user participating in the same online conference as the shared terminal had to directly operate the shared terminal from the conference room where the shared terminal is installed.

[0005] The embodiment of the present invention can support users participating in an event in operating shared terminals participating in the same event. Rusi The purpose is to provide a stem. [Means for solving the problem]

[0006] In order to achieve the above-mentioned object, claim 1 of the present application provides a system for transmitting and receiving voice data, which includes a plurality of user terminals, a plurality of shared terminals, and an information processing device connectable to each of the plurality of user terminals and the plurality of shared terminals via a network, and which includes: a voice analysis processing means for performing voice analysis on voice data uttered by a user input from one of the plurality of user terminals; a determination means for determining whether or not a request for control of a shared terminal is included based on the voice analysis result analyzed by the voice analysis processing means; and a control means for controlling a shared terminal specified by the voice analysis result among the plurality of shared terminals based on the request for control when the determination means determines that a request for control of a shared terminal is included. the control means controls the shared terminal if the user who spoke the voice data is participating in the same event, and does not control the shared terminal if the user is not participating in the event. It is characterized by: [Effects of the Invention]

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

[0008] [Figure 1] 1 is a configuration diagram of an example of an information processing system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram illustrating a hardware configuration of an example of a shared terminal according to the present embodiment. [Figure 3] FIG. 2 is a diagram illustrating an example of a hardware configuration of a computer according to the present embodiment. [Figure 4] FIG. 2 is a diagram illustrating a software configuration of a shared terminal. [Figure 5] FIG. 2 is a diagram illustrating a software configuration of a user terminal. [Figure 6] 1 is a functional configuration diagram of an example of an information processing system according to an embodiment of the present invention. [Figure 7] FIG. 10 is a conceptual diagram illustrating a user authentication management table. [Figure 8] FIG. 10 is a conceptual diagram illustrating an access management table. [Figure 9] FIG. 10 is a conceptual diagram illustrating a schedule management table. [Figure 10] FIG. 10 is a conceptual diagram illustrating an execution event management table. [Figure 11] FIG. 10 is a conceptual diagram illustrating a content management table. [Figure 12] FIG. 10 is a conceptual diagram illustrating a user authentication management table. [Figure 13] FIG. 10 is a conceptual diagram illustrating a user management table. [Figure 14] FIG. 10 is a conceptual diagram illustrating a union management table. [Figure 15] FIG. 10 is a conceptual diagram illustrating a union reservation management table. [Figure 16] FIG. 10 is a conceptual diagram illustrating an event management table. [Figure 17] FIG. 10 is a conceptual diagram illustrating a server authentication management table. [Figure 18] FIG. 10 is a conceptual diagram illustrating a project member management table. [Figure 19] FIG. 10 is a conceptual diagram illustrating an execution event history management table. [Figure 20] FIG. 10 is a conceptual diagram illustrating an execution event management table. [Figure 21] FIG. 10 is a conceptual diagram illustrating a related information management table. [Figure 22]FIG. 10 is a sequence diagram showing a schedule registration process. [Figure 23] FIG. 10 is a diagram showing a sign-in screen. [Figure 24] 10 is an example of an initial screen of a user terminal. [Figure 25] FIG. 10 is a diagram showing a schedule screen. [Figure 26] FIG. 10 is a diagram showing a schedule input screen. [Figure 27] FIG. 10 is a diagram showing candidates proposed on a schedule input screen. [Figure 28] FIG. 10 is a diagram showing a schedule input screen. [Figure 29] FIG. 10 is a diagram showing a schedule input screen. [Figure 30] FIG. 10 is a sequence diagram illustrating a process for starting an event. [Figure 31] FIG. 10 is a sequence diagram illustrating a process for starting an event. [Figure 32] FIG. 10 is a diagram showing a reservation list screen for a union. [Figure 33] FIG. 10 is a diagram showing a project list screen. [Figure 34] FIG. 10 is a diagram showing a detailed information screen for an event. [Figure 35] FIG. 10 is a diagram showing the relationship between the message content of the chat function and the operation content (function) of the shared terminal that can be controlled by the message content. [Figure 36] FIG. 10 is a diagram showing an example of a message content posted using a chat function. [Figure 37] FIG. 10 is a diagram showing an example of a display screen of an attached file. [Figure 38] FIG. 10 is a diagram showing an example of a message content posted using a chat function. [Figure 39] FIG. 10 is a diagram showing a screen image of a shared terminal. [Figure 40] 10A and 10B are diagrams illustrating an example of a display screen and a camera image of a shared terminal. [Figure 41] FIG. 10 is a diagram showing an example of a message content posted using a chat function. [Figure 42] FIG. 10 is a sequence diagram showing a process in which a user requests control of a shared terminal using a chat function. [Figure 43] FIG. 10 is a sequence diagram showing a process in which a user requests control of a shared terminal using a chat function. [Figure 44] FIG. 10 is a diagram showing an example of a message content posted using a chat function. [Figure 45] FIG. 10 is a sequence diagram showing a process in which a user requests control of a shared terminal using a chat function. [Figure 46] FIG. 10 is a sequence diagram showing a process in which a user requests control of a shared terminal using a chat function. [Figure 47] FIG. 10 is a sequence diagram showing a process in which a user requests control of a shared terminal by voice. [Figure 48] FIG. 10 is a diagram showing a screen image of a shared terminal. [Figure 49] FIG. 10 is a diagram showing an example of a message content posted using a chat function. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In this embodiment, a group or team of users gathered for a joint work is called a project, and users belonging to the project are called project members. In this embodiment, the term "file" refers to an "electronic file."

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

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

[0012] The collaboration system 10 is a system that supports multiple people working together on a single project. One example of the collaboration system 10 is a system used in a place where people gather to exchange opinions and discuss a specific purpose (including when they are physically together or when they are physically separated but their user terminals are connected via a communication network 50). The system uses PCs, mobile devices, electronic whiteboards, projectors, conference tools, and the like to conduct voice calls, video calls, chats, screen sharing (projection), information sharing, agenda discussions, document creation and compilation, schedule setting, action item determination, and the like. The collaboration system 10 has the same meaning as a collaborative work support system. A collaborative work support system is a system that supports multiple people working together on a single project. For example, it provides communication functions, information sharing functions, and the like. The collaboration system 10 provides collaboration tools that support project members working together on a single project. A collaboration tool is a means, function, or tool for supporting multiple people working together on a single project. For example, collaboration tools include communication functions, schedule management functions, information sharing functions, action item management functions, and the like. Collaborative work refers to multiple people working together on a single project.

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

[0014] The schedule management server 12 provides schedule management functions to project members. The voice-to-text conversion server 13 converts voice 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] The online storage server 20 also provides users with an online storage service. The online storage service is a service that rents out disk drives (storage) on the cloud that can be used via the Internet to users. By using the online storage service, project members can share files.

[0016] The user terminal 40 is an information processing terminal that is operated by a user, including a member of the project. The user can use the collaboration system 10, the online storage server 20, and the shared terminal 42 from the user terminal 40.

[0017] In addition, the user terminal 40 may be any device with communication capabilities, such as a PJ (Projector), an IWB (Interactive White Board: an electronic whiteboard with a function of a whiteboard that allows mutual communication; an electronic whiteboard), an output device such as digital signage, a HUD (Head Up Display) device, industrial machinery, an imaging device, a sound collection device, medical equipment, a network home appliance, an automobile (Connected Car), a notebook PC (Personal Computer), a mobile phone, a smartphone, a tablet terminal, a game console, a PDA (Personal Digital Assistant), a digital camera, a wearable PC or a desktop PC.

[0018] The shared terminal 42 is an information processing terminal shared by multiple people, such as an electronic whiteboard installed in a conference room or the like. The shared terminal 42 may be any device with a communication function, such as a PJ (Projector), an IWB (Interactive Whiteboard: a whiteboard with an electronic whiteboard function that allows mutual communication), an output device such as digital signage, a HUD (Head Up Display) device, industrial machinery, an imaging device, a sound collection device, medical equipment, a network appliance, an automobile (Connected Car), a laptop PC (Personal Computer), a mobile phone, a smartphone, a tablet terminal, a game console, a PDA (Personal Digital Assistant), a digital camera, a wearable PC, or a desktop PC. For example, the shared terminal 42 installed in a conference room or the like can be shared by multiple people by requiring a reservation of the terminal itself or the conference room for use.

[0019] The sharing support server 11, schedule management server 12, voice-to-text conversion server 13, and file management server 14 are realized by, for example, one or more information processing devices. The collaboration system 10 may be one or more computers that integrate all or part of the functions of the sharing support server 11, schedule management server 12, voice-to-text conversion server 13, and file management server 14.

[0020] Furthermore, each of the sharing support server 11, schedule management server 12, voice-to-text conversion server 13, and file management server 14 may be configured to have its functions distributed among a plurality of computers.

[0021] Furthermore, the sharing support server 11, the schedule management server 12, the speech-to-text conversion server 13, and the file management server 14 may be configured to be realized by a computer in a cloud environment or a computer in an on-premise environment. Thus, the information processing system 1 in FIG. 1 is an example.

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

[0023] The collaboration system 10, the sharing support server 11, the schedule management server 12, the speech-to-text conversion server 13, the file management server 14, and the online storage server 20 may be, for example, output devices such as a projector, an IWB, or a digital signage, a head-up display (HUD) device, an industrial machine, an imaging device, a sound collection device, a medical device, a network appliance, an automobile, a notebook PC, a mobile phone, a smartphone, a tablet terminal, a game console, a PDA, a digital camera, a wearable PC, or a desktop PC.

[0024] The collaboration information provided by the collaboration system 10 to project members using the collaboration tool includes both synchronous collaboration information and asynchronous collaboration information. Synchronous collaboration information is information exchanged in real time during a forum (e.g., an online conference) where people gather to exchange opinions and discuss matters related to a specific purpose. Synchronous collaboration information includes, for example, voice calls, video calls, and screens shared on PCs, mobile devices, electronic whiteboards, etc. (including text and diagrams entered from PCs, mobile devices, etc., and handwritten content entered on the screen of an electronic whiteboard, etc.).

[0025] Asynchronous collaboration information is information that is entered and shared over a network. It also includes information that can be shared or referenced by participants before and after a meeting where people gather to exchange opinions and discuss a specific purpose. Examples of asynchronous collaboration information include chat, messages, content, schedules, action items, and audio / video recordings.

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

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

[0028] Of these, CPU 201 controls the overall operation of shared terminal 42. ROM 202 stores programs used to drive CPU 201, such as CPU 201 and an IPL (Initial Program Loader). RAM 203 is used as a work area for CPU 201. SSD 204 stores various data, such as programs for shared terminal 42. Network I / F 205 controls communication with communication network 50. External device connection I / F 206 controls communication with USB (Universal Serial Bus) memory 2600, PC 2700, 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 of the short-range communication circuit 219, and a power switch 222.

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

[0031] The contact sensor 214 detects contact of the electronic pen 2500, the user's hand H, or the like on the display 220. The sensor controller 215 controls the processing of the contact sensor 214. The contact sensor 214 inputs and detects coordinates using an infrared blocking method. This coordinate input and coordinate detection method involves two light receiving and emitting devices installed at both ends of the upper side of the display 220 emitting multiple infrared rays parallel to the display 220, and receiving light that is reflected by a reflecting member installed around the periphery of the display 220 and returns along the same optical path as the light emitted by the light receiving element.

[0032] The contact sensor 214 outputs the ID of the infrared light radiated by the two light receiving and emitting devices that has been blocked by the object to the sensor controller 215, and the sensor controller 215 identifies the coordinate position that is the contact position of the object. The electronic pen controller 216 communicates with the electronic pen 2500 to determine whether the pen tip or the pen tail has touched the display 220.

[0033] Near field communication circuit 219 is a communication circuit such as NFC (Near Field Communication), Bluetooth (registered trademark), etc. Power switch 222 is a switch for switching the power of shared terminal 42 ON / OFF.

[0034] Furthermore, shared terminal 42 includes bus line 210. Bus line 210 is an address bus, a data bus, etc. for electrically connecting the components such as CPU 201 shown in FIG.

[0035] The contact sensor 214 is not limited to an infrared blocking type, and various detection means may be used, such as a capacitive touch panel that identifies the contact position by detecting a change in capacitance, a resistive film touch panel that identifies the contact position by a change in voltage between two opposing resistive films, or an electromagnetic induction touch panel that identifies the contact position by detecting electromagnetic induction caused by a contacting object coming into contact with the display unit. Also, the electronic pen controller 216 may determine whether or not a part of the electronic pen 2500 that is held by the user or other parts of the electronic pen has been touched, in addition to the pen tip and pen butt.

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

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

[0038] Of these, the CPU 501 controls the overall operation of the computer 500 in accordance with a program. The ROM 502 stores programs used to drive the CPU 501, such as the IPL. The RAM 503 is used as a work area for the CPU 501. The HD 504 stores various data such as programs. The HDD controller 505 controls the reading and writing of various data from and to the HD 504 in accordance with the control of the CPU 501.

[0039] The display 506 displays various types of information such as a cursor, menus, windows, characters, or images. The external device connection I / F 508 is an interface for connecting various types of external devices. In this case, the external devices are, for example, USB (Universal Serial Bus) memories, printers, etc. The network I / F 509 is an interface for data communication using the network 16. The data bus 510 is an address bus, data bus, etc. for electrically connecting each component such as the CPU 501.

[0040] The keyboard 511 is a type of input means having multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 512 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, etc. The DVD-RW drive 514 controls reading and writing of various data from a DVD-RW 513, which is an example of a removable recording medium. Note that this is not limited to a DVD-RW, and may be a DVD-R, etc. The media I / F 516 controls reading and writing (storing) of data from a recording medium 515, such as a flash memory.

[0041] Each of the above programs may be recorded on a computer-readable recording medium as an installable or executable file and distributed. Examples of recording media include CD-Rs (Compact Disc Recordables), DVDs (Digital Versatile Disks), Blu-ray Discs, SD cards, etc. The recording media may be provided domestically or internationally as a program product.

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

[0043] Additionally, an application is a general term for software used to perform specific processes. On the other hand, an operating system (hereinafter referred to as OS) is software that controls a computer and allows applications to use computer resources. The OS performs basic management and control of a computer, such as input / output control, management of hardware such as memory and hard disks, and process management. Applications run using the functions provided by the OS.

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

[0045] Launcher 102 is a launcher application that runs on OS 101. Launcher 102, for example, manages the start and end of events being executed on shared terminal 42, or manages external applications such as schedule viewer 103a, file viewer 103b, browser app 103c, and collaboration app 103d that are used during an event. An event is, for example, a meeting, gathering, get-together, consultation, arrangement, conference, seminar, webinar (online seminar), academic study group, policy presentation, or other event where people gather in person or via communication network 50 to share opinions, make presentations, or consult with each other for a specific purpose.

[0046] The schedule viewer 103a, the file viewer 103b, the browser application 103c, and the collaboration application 103d are external applications (hereinafter, referred to as external applications 103 when no particular distinction is required) that run on the Launcher 102. The external applications 103 are executed independently of the Launcher 102, and execute services or functions provided on the OS 101. Note that while FIG. 4 shows an example in which four external applications 103, namely the schedule viewer 103a, the file viewer 103b, the browser application 103c, and the collaboration application 103d, are installed on the shared terminal 42, the number of external applications 103 is not limited to this. Furthermore, the schedule viewer 103a, the file viewer 103b, the browser application 103c, and the collaboration application 103d may be downloaded and installed from, for example, a server provided in the collaboration system 10 or a server provided in the cloud or on-premise.

[0047] Next, the software installed in the user terminal 40 will be described with reference to Fig. 5. Fig. 5 is a diagram showing the software configuration of the user terminal. As shown in Fig. 5, an OS 5501, a collaboration application 5502a, and a browser 5502b run on a working area 5500 of RAM 503. The OS 5501 is basic software that provides the basic functions of the user terminal 40 and manages the entire user terminal 40.

[0048] The collaboration application 5502a and the browser 5502b are external applications (hereinafter, referred to as external applications 5502 when there is no need to particularly distinguish between them) that run on the OS 5501. The external applications 5502 execute services or functions provided on the OS 5501. Note that, while FIG. 5 shows an example in which two external applications 5502, the collaboration application 5502a and the browser 5502b, are installed on the user terminal 40, this is not limiting. 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 downloadable and installable from, for example, a server provided in the collaboration system 10 or a server provided in the cloud or on-premise.

[0049] <Functional configuration> The information processing system 1 according to this embodiment is realized by, for example, a functional configuration as shown in Fig. 6. Fig. 6 is a functional configuration diagram of an example of the information processing system according to this embodiment. In the functional configuration of Fig. 6, configurations that are not necessary for explaining this embodiment are omitted as appropriate.

[0050] <<Functional configuration of shared terminals>> As shown in Fig. 6, the shared terminal 42 in the case of an electronic whiteboard includes a transmitting / receiving unit 21, a receiving unit 22, an image / sound processing unit 23, a display control unit 24, a determining unit 25, a recognizing unit 26, an acquiring / providing unit 28, a storing / reading processing unit 29, a function control unit 31, and a save request unit 32. Each of these units is a function or a means for performing the function, which is realized when any of the components shown in Fig. 2 operates in response to an instruction from the CPU 201 in accordance with a program loaded from the SSD 204 onto the RAM 203. The shared terminal 42 also has a memory unit 2000 constructed by the RAM 203, the SSD 204, or the USB memory 2600 shown in Fig. 2.

[0051] (Functional configuration of shared terminal) Next, we will explain each component of shared terminal 42. Transmitting / receiving unit 21 is realized by commands from CPU 201 shown in Fig. 2, as well as network I / F 205 and external device connection I / F 206, and transmits and receives various data (or information) to and from other terminals, devices, or systems via communication network 50. Transmitting / receiving unit 21 is an example of a transmitting means and a receiving means.

[0052] The reception unit 22 is realized mainly by instructions from the CPU 201 shown in Fig. 2, the contact sensor 214, and the electronic pen controller 216, and receives various inputs from the user. The reception unit 22 is an example of a reception means.

[0053] 2 and the capture device 211, and stores image data displayed on the display 220. Also, the image and sound processing unit 23 is realized by the instruction from the CPU 201 and the GPU 212 shown in Fig. 2, and performs image processing for displaying an image on the display 220. Furthermore, the image and sound processing unit 23 performs image processing on image data obtained by the camera 2400 capturing an image of a subject.

[0054] Furthermore, after the user's voice is converted into an audio signal by the microphone 2200, the image / sound processing unit 23 performs audio processing on the audio data related to this audio signal. Furthermore, 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 audio. Furthermore, the image / sound processing unit 23 performs processing to convert drawing image data obtained by the user drawing on the display 220 with the electronic pen 2500 or the hand H into coordinate data.

[0055] The display control unit 24 is realized by commands from the CPU 201 shown in Fig. 2 and the display controller 213 shown in Fig. 2, and displays drawn images on the display 220, and accesses the sharing support server 11 and the schedule management server 12 using a Web browser to display various screen data. Specifically, the display control unit 24 starts and executes the launcher 102 and external application 103 that run on the OS 101 shown in Fig. 4, thereby displaying various screens drawn by an 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] Determination unit 25 is implemented by instructions from CPU 201 shown in Fig. 2 and performs various determinations. For example, determination unit 25 determines whether a user who sent a message using the chat function is participating in the same online conference as shared terminal 42.

[0057] The recognition unit 26 is realized by an instruction from the CPU 201 shown in Fig. 2, and recognizes a designated area enclosed on the display 220. The acquisition / provision unit 28 is executed by an instruction from the CPU 201 shown in Fig. 2, as well as by the short-range communication circuit 219 and the antenna 219a, and acquires and provides data via short-range communication with a dedicated terminal such as an IC card or a smartphone.

[0058] The function control unit 31 receives control requests from users based on user operations and controls functions. The function control unit 31 also receives control requests from users based on messages from the chat function, as described below, and controls functions. For example, when a screen capture request is received from a user participating in the same online conference, the function control unit 31 controls the capture function to capture the display screen. For example, when a message with a file attached is received from a user participating in the same online conference, the function control unit 31 displays the attached file.

[0059] After the online conference ends, the save request unit 32 requests the sharing support server 11 to save the shared data used during the online conference. The shared data referred to here is information used during an event such as an online conference, such as files, image data of a shared screen, video data, audio data, stroke data, pointer data, chat data, etc. The save request unit 32 may request the sharing support server 11 to save the shared data used during the online conference while the online conference is being held (from the start to the end of the conference, while the conference is being held). If the number or volume of shared data is large, starting the save during the online conference allows the shared data to be saved completely when or immediately after the online conference ends.

[0060] 2 and SSD 204, and performs processes such as storing various data in storage unit 2000 and reading out various data stored in storage unit 2000. Furthermore, image data and sound data received during communication with other shared terminals 42, user terminals 40, etc. are overwritten and stored in storage unit 2000 each time they are received. Of these, images are displayed on display 220 using image data before being overwritten, and sound is output from speaker 2300 using sound data before being overwritten.

[0061] <User terminal functional configuration> The user terminal 40 has a transmitting / receiving unit 51, a receiving unit 52, a display control unit 54, a generating unit 56, a sound control unit 58, and a storage / readout processing unit 59. Each of these units is a function or a means for performing a function that is realized when any of the components shown in Fig. 3 operates in response to an instruction from the CPU 501 in accordance with a program loaded 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 Fig. 3.

[0062] (Functional configuration of user terminal) Next, we will explain each component of the user terminal 40. The transmitting / receiving unit 51 is realized by commands from the CPU 501 and the network I / F 509 shown in Fig. 3, and transmits and receives various data (or information) to and from 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 realized mainly by instructions from the CPU 501 shown in Fig. 3, as well as the keyboard 511 and the pointing device 512, and receives various inputs from the user. The reception unit 52 is an example of a reception means.

[0064] The display control unit 54 is realized by instructions from the CPU 501 shown in Fig. 3, and displays images on the display 506, and accesses the sharing 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 sharing support server 11 or the schedule management server 12 by, for example, starting and executing the collaboration application 5502a or the browser 5502b that runs on the OS 5501 shown in Fig. 5.

[0065] Then, the display control unit 54 downloads a WebAPP (WebApplication) that includes at least HTML (HyperText Markup Language) and also includes CSS (Cascading Style Sheets) or JAVA SCRIPT (registered trademark), and causes various image data generated by the WebAPP to be displayed on the display 506. The display control unit 54 causes image data generated by "HTML5" that includes data in, for example, XML (Extensible Markup Language), JSON (JavaScript Object Notation), or SOAP (Simple Object Access Protocol) format to be displayed on the display 506. The display control unit 54 is an example of a display control means.

[0066] The generation unit 56 is realized by commands from the CPU 501 shown in FIG. 3, and has a 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 the content data, and generates image data related to the text data, which is the content data, in order to display the rendered data. Rendering is a process of interpreting data written in a language for describing web pages (HTML, CSS, XML, etc.) and calculating the layout of characters, image data, etc., to be actually displayed on the screen.

[0067] The sound control unit 58 is realized by an instruction from the CPU 501 shown in Fig. 3, and has a function of outputting a sound signal from a speaker. The sound control unit 58 sets sound data to be output from the speaker, and reproduces the sound data by outputting a sound signal related to the set sound data from the speaker.

[0068] The storage / readout processing unit 59 is executed by instructions from the CPU 501 shown in FIG. 3 and the HDD controller 505, etc., 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 sharing support server 11 has a transmitting / receiving unit 61, an authenticating unit 62, a creating unit 63, a generating unit 64, a determining unit 65, a distributing unit 66, a control requesting unit 67, and a storing / reading processing unit 69. Each of these units is a function or a means for performing a function that is realized when any of the components shown in Fig. 2 operates in response to an instruction from the CPU 501 in accordance with the sharing support program loaded from the HD 504 onto the RAM 503. The sharing support server 11 also has a storage unit 6000 constructed by the HD 504 etc. shown in Fig. 2.

[0070] (User authentication management table) Fig. 7 is a conceptual diagram showing a user authentication management table. A user authentication management DB 6001 configured with a user authentication management table such as that shown in Fig. 7 is constructed in the storage unit 6000. In this user authentication management table, 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 are associated and managed. The organization ID also includes a domain name representing a group or organization for managing multiple computers on the communication network 50.

[0071] (Access control table) Fig. 8 is a conceptual diagram showing an access management table. An access management DB 6002 configured with an access management table such as that shown in Fig. 8 is constructed in the storage unit 6000. In this access management table, an organization ID, an access ID required for authentication when accessing the schedule management server 12, and an access password are associated and managed. The access ID and access password are required for the sharing support server 11 to use the services (functions) provided by the schedule management server 12 via a WebAPI or the like using the HTTP (Hypertext Transfer Protocol) or HTTPS (Hypertext Transfer Protocol Secure) protocol.

[0072] The schedule management server 12 manages a plurality of schedulers, and different organizations may use different schedulers, so management using the access management table of FIG. 8 is necessary.

[0073] (Schedule management table) Fig. 9 is a conceptual diagram showing a schedule management table. A schedule management DB 6003 configured with a schedule management table such as that shown in Fig. 9 is constructed in the storage unit 6000. In this schedule management table, for each scheduled event ID and executed event ID, the organization ID, the user ID of the person who made the reservation, whether or not the person who made the reservation will participate, the name of the person who made the reservation, the scheduled start time, the scheduled end time, the event name, the user IDs of other participants, whether or not the other participants will participate, the names of the other participants, and file data are associated and managed.

[0074] Among these, the scheduled event ID is identification information for identifying a reserved event. The scheduled event ID is an example of scheduled event identification information for identifying an event scheduled to be executed. The executed event ID is identification information for identifying an event that has actually been executed or is currently being executed among the reserved events.

[0075] The execution event ID is an example of execution event identification information for identifying an event that has been executed or is being executed. The reservation name is the name of the person who reserved a union such as a conference room. A union is an object, service, space (room), place, or information that is used jointly by multiple people or organizations. A conference room is an example of a union shared by multiple users. If the union is a conference room, the name would be the organizer's name, for example. The scheduled start time indicates the scheduled start time of use of the union. The scheduled end time indicates the scheduled end time of use of the union. The event name indicates the name of the event that the reservationr plans to execute.

[0076] The user IDs of other participants are identification information for identifying 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 also include unions. In other words, in this case, the users include not only the person who made the reservation and the other participants, but also the shared terminal 42, which is an example of a union. 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 specified 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) Fig. 10 is a conceptual diagram showing an execution event management table. An execution event management DB 6004 configured by an execution event management table such as that shown in Fig. 10 is constructed in the storage unit 6000. In this execution event management table, an execution event ID is associated with each project ID and managed.

[0078] The project ID is identification information for identifying a project (an example of project identification information). A project indicates a group, team, or group of users formed to achieve a specific goal, plan, or project.

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

[0080] (Content Management Table) Fig. 11 is a conceptual diagram showing a content management table. A content management DB 6005 configured with a content management table such as that shown in Fig. 11 is constructed in the storage unit 6000. In this content management table, a content processing ID, a type of content processing, content details, and 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 an event such as an online conference for a project (such as the content of the event or materials used in the event). Types of content processing include audio recording, video recording, file sharing, screen sharing, snapshots, speech-to-text conversion, action item generation, chat, document upload, handwriting operation, and pointing device operation. The content processing ID is identification information used to identify the content processing generated at each event.

[0082] A snapshot is a process of acquiring image data of a display screen at a certain point in time during an event that is being executed. Note that a snapshot is also called, for example, a capture or image recognition.

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

[0084] When the content processing type is "chat," the content includes the user ID of the participant who posted the message, and if a mention is specified, the user ID of the mention and the message content. A message is information exchanged between users participating in an event. Examples include text entered by each user, comments entered by voice, data converted from voice-entered utterances into text, files exchanged by each user during the event, and mentions included in text entered by each user or comments entered by voice. A message with a specified mention is a message notifying multiple participants and specifies which of the multiple participants should read the message. Note that the message content includes not only the text data of the posted message, but also posted image data and meeting log data files.

[0085] An action item occurs during an event such as a meeting in a project, and indicates the action that must be taken by those involved in the event. When the type of content processing is "action item occurrence," the content includes the user ID of the person who executes the action item, the deadline for completing the action item, and a URL indicating the location where text data representing the content of the action item is saved.

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

[0087] (Functional configuration of the shared support server) Next, a detailed description will be given of each functional configuration of the sharing support server 11. In the following, when describing each functional configuration of the sharing support server 11, the relationship between each component shown in Fig. 3 and the main components for realizing each functional configuration of the sharing support server 11 will also be described.

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

[0089] The authentication unit 62 is realized 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 the shared terminal 42 is information that has been pre-registered in the user authentication management DB 6001.

[0090] The creation unit 63 is realized by commands from the CPU 501 shown in FIG. 3, and creates image data for various screens, such as image data for a reservation list screen based on the reservation information and plan information sent from the schedule management server 12.

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

[0092] <<Schedule management server functional configuration>> The schedule management server 12 has a transmission / reception unit 81, an authentication unit 82, a generation unit 83, a management unit 84, and a storage / readout processing unit 89. Each of these units is a function or a means for performing a function that is realized when any of the components shown in Fig. 2 operates in response to an instruction from the CPU 501 in accordance with a schedule management program loaded 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 Fig. 2.

[0093] (User authentication management table) Fig. 12 is a conceptual diagram showing a user authentication management table. A user authentication management DB 8001 configured with a user authentication management table such as that shown in Fig. 12 is constructed in the storage unit 8000. In this user authentication management table, a user ID for identifying a user is associated with an organization ID for identifying the organization to which the user belongs, and a password, and these are managed.

[0094] (User management table) Fig. 13 is a conceptual diagram showing a user management table. A user management DB 8002 configured by a user management table such as that shown in Fig. 13 is constructed in the storage unit 8000. In this user management table, a user ID and the name of the user indicated by the user ID (user name) are associated and managed for each organization ID.

[0095] (Union management table) Fig. 14 is a conceptual diagram showing a union management table. A union management DB 8003 configured by a union management table such as that shown in Fig. 14 is constructed in the storage unit 8000. In this union management table, a union ID for identifying a union and a name of the union (union name) are associated and managed for each organization ID.

[0096] (Union reservation management table) Fig. 15 is a conceptual diagram showing a union reservation management table. A union reservation management DB 8004 configured with a union reservation management table such as that shown in Fig. 15 is constructed in the storage unit 8000. This union reservation management table manages reservation information in which each piece of information is associated with other information. The reservation information includes, for each organization ID, a union ID, a union name, the user ID of the shared terminal, the user ID of the person who made the reservation, the scheduled start date and time of use, the scheduled end date and time of use, and the event name.

[0097] The "user ID of the shared terminal" is the user ID of the shared terminal 42 installed in the conference room, which is an example of a union. The scheduled start date and time of use indicates the scheduled start date and time of use of the union. The scheduled end date and time of use indicates the scheduled end date and time of use of the union. Each date and time indicates the year, month, day, hour, minute, second, and time zone. Due to space limitations, each date and time in Figure 15 is expressed down to the year, month, day, hour, and minute.

[0098] (Event management table) Fig. 16 is a conceptual diagram showing an event management table. An event management DB 8005 configured with an event management table such as that shown in Fig. 16 is constructed in the storage unit 8000. This event management table manages schedule information in which each piece of information is associated with each other. The schedule information manages the following for each scheduled event ID in association with each other: 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 executed. The scheduled event end date and time indicates the scheduled end date and time if the event is to be executed. Each date and time indicates the year, month, day, hour, minute, second, and time zone. Due to space limitations, each date and time in Figure 16 is expressed to the year, month, day, hour, and minute. In addition, the event management table in Figure 16 manages file data of materials used in events shown in the schedule information, associated with the scheduled event ID.

[0100] (Server authentication management table) 17 is a conceptual diagram showing a server authentication management table. A server authentication management DB 8006 configured by the server authentication management table shown in FIG. 17 is constructed in the storage unit 8000. In this server authentication management table, access IDs and access passwords are associated and managed. The access IDs and access passwords are the same concept as the access IDs and access passwords managed in the access management DB 6002 of the sharing support server 11.

[0101] (Project member management table) Fig. 18 is a conceptual diagram showing a project member management table. A project member management DB 8007 configured with a project member management table such as that shown in Fig. 18 is constructed in the storage unit 8000. 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) Fig. 19 is a conceptual diagram showing an execution event history management table. An execution event history management DB 8008 configured with an execution event history management table such as that shown in Fig. 19 is constructed in the storage unit 8000. In this execution event history management table, a content processing ID, a type of content processing, content details, and start and end dates and times of content processing are associated and managed for each project ID and execution event ID.

[0103] The execution event history management DB 8008 manages some of the same data as the content management DB 6005. The same data includes the execution event ID, content processing ID, type of content processing, start date and time, and end date and time of content processing. The only difference between the contents is the notation of the content data storage destination (http: / / or c: / / ), and the storage destination is the same.

[0104] (Execution event management table) Fig. 20 is a conceptual diagram showing an execution event management table. An execution event management DB 8009 configured with an execution event management table such as that shown in Fig. 20 is constructed in the storage unit 8000. In this execution event management table, an execution event ID is associated with an event name, and the start and end dates and times of the event. This execution event management DB 8009 manages information related to events that have actually been executed, out of the schedule information managed in the event management DB 8005.

[0105] (Related information management table) Fig. 21 is a conceptual diagram showing a related information management table. A related information management DB 8010 configured with a related information management table such as that shown in Fig. 21 is constructed in the storage unit 8000. In this related information management table, related information in which each piece of information (data) is associated with each project ID and execution event ID is managed. The related information is managed in association with the time period in which the content occurred, audio / video data, audio text data, and screen data.

[0106] The content occurrence time zone indicates the elapsed time from the start date and time of the event at the time when the content occurred in the executed event. The content occurrence time zone is generated by the generation unit 83 based on the start date and time of the event stored in the event management DB 8005 and the start date and time and end date and time of the content processing stored in the executed event history management DB 8008. The content occurrence time zone 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 chronological order in which content processing occurred in the audio / text data and screen data, respectively.

[0108] (Schedule management server functional configuration) Next, a detailed description will be given of each functional configuration of schedule management server 12. In the following, when describing each functional configuration of schedule management server 12, the relationship between each component shown in Fig. 3 and the main components for realizing each functional configuration of schedule management server 12 will also be described.

[0109] The transmitting / receiving unit 81 of the schedule management server 12 shown in Fig. 6 is realized by commands from the CPU 501 shown in Fig. 3 and the network I / F 509 shown in Fig. 3. The transmitting / receiving unit 81 transmits and receives various data (or information) to and from the user terminal 40, the shared terminal 42, other servers, other systems, etc. via the communication network 50.

[0110] 3, the authentication unit 82 performs authentication by determining whether the information (user ID, organization ID, and password) sent from the user terminal 40 or the 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 sharing support server 11 is information that has been pre-registered in the server authentication management DB 8006.

[0111] The generation unit 83 is realized by an instruction from the CPU 501 shown in Fig. 3, and has a function of generating related information to be registered in the related information management DB 8010. The management unit 84 is realized by an instruction from the CPU 501 shown in Fig. 3, and manages events such as online conferences.

[0112] The storage / readout processing unit 89 is realized by instructions from the CPU 501 shown in FIG. 3 and the HDD controller 505 shown in FIG. 3, and performs processing such as storing various data in the memory unit 8000 and reading out various data stored in the memory unit 8000.

[0113] <<Functional configuration of online storage server>> The online storage server 20 has a transmission / reception unit 91 and a storage / readout processing unit 99. Each of these units is a function or a means for performing a function that is realized when any of the components shown in Fig. 3 operates in response to an instruction from the CPU 501 in accordance with a program loaded from the HD 504 onto the RAM 503. The online storage server 20 in Fig. 6 also has a memory unit 9000 constructed by the HD 504 shown in Fig. 3.

[0114] (Online storage server functional configuration) Next, we will explain in detail each functional configuration of the online storage server 20. In explaining each functional configuration of the online storage server 20, we will also explain the relationship between each component shown in Fig. 3 and the main components that realize each functional configuration of the online storage server 20.

[0115] The transmitting / receiving unit 91 of the online storage server 20 shown in Fig. 6 is realized by commands from the CPU 501 shown in Fig. 3 and the network I / F 509 shown in Fig. 2. The transmitting / receiving unit 91 transmits and receives various data (or information) to and from the user terminal 40, the shared terminal 42, other servers, other systems, etc. via the communication network 50.

[0116] The storage / readout processing unit 99 is realized by instructions from the CPU 501 shown in FIG. 3 and the HDD controller 505 shown in FIG. 3, and performs processing such as storing various data in the memory unit 9000 and reading out various data stored in the memory unit 9000.

[0117] The above IDs are examples of identification information. Organization IDs include company names, business names, department names, and local area names. User IDs include employee numbers, driver's license numbers, and My Numbers under Japan's social security and tax numbering system.

[0118] 6 is an example, and the functions (each processing unit and memory unit) of the sharing support server 11, schedule management server 12, online storage server 20, user terminal 40, and shared terminal 42 may be executed by any of the sharing support server 11, schedule management server 12, online storage server 20, user terminal 40, and shared terminal 42. For example, the determination unit 65 of the sharing support server 11 may be included 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》 Here, we will explain the process by which reserver A (Rikotaro) registers his / her own schedule in schedule management server 12 from user terminal 40. Fig. 22 is a sequence diagram showing the schedule registration process. Fig. 23 is a diagram showing a sign-in screen. Fig. 24 is an example of the initial screen of the user terminal. Fig. 25 is a diagram showing a schedule screen. Fig. 26 is a diagram showing a schedule input screen.

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

[0122] This sign-in screen 530 includes an input field 531 for inputting the user's user ID and organization ID, an input field 532 for inputting a password, a sign-in button 538 that is pressed to sign in, and a cancel button 539 that is pressed to cancel sign-in. Here, the user ID and organization ID are the email address of subscriber A. The username portion of the email address indicates the user ID, and the domain name portion indicates the organization ID. Note that input field 531 may be an input field for separately inputting the user ID and organization ID instead of the email address.

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

[0124] Then, the transmitting / receiving unit 51 of the user terminal 40 transmits sign-in request information indicating a sign-in request to the schedule management server 12 (step S13). The sign-in request information includes the information (user ID, organization ID, and password) accepted in step S12. 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 user A using the user ID, organization ID, and password (step S14). Specifically, the storage / readout processing unit 89 searches the user authentication management DB 8001 (see FIG. 12) for a set of user ID, organization ID, and password that corresponds to the set of user ID, organization ID, and password received in step S13.

[0126] If a corresponding pair is found, the authentication unit 82 determines that the requesting subscriber A is a valid user. If a corresponding pair is not found, the authentication unit 82 determines that the subscriber A is an invalid (illegitimate) user. If the subscriber A is not valid, the transmitting / receiving unit 81 notifies the user terminal 40 that the subscriber A is not valid. Here, the explanation will continue for the valid case. Next, the transmitting / receiving unit 81 transmits 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 authentication result indicating authenticity is received in step S15, the generation unit 56 of the user terminal 40 generates an initial screen 540 as shown in Fig. 24 (step S16). Then, the display control unit 54 of the user terminal 40 displays the initial screen 540 as shown in Fig. 24 on the display 506 (step S17).

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

[0129] Here, when the user presses the "Schedule registration" button 541, the acceptance unit 52 accepts the schedule registration (step S18). Then, the transmission / reception unit 51 transmits schedule registration request information to the schedule management server 12 (step S19). As a result, the transmission / reception unit 81 of the schedule management server 12 receives the schedule registration request information.

[0130] Next, the storage / readout processing unit 89 of the schedule management server 12 searches the event management DB 8005 (see FIG. 16) managed by the scheduler using the user ID of the reservation user A received in step S13 as a search key, thereby reading out the corresponding schedule information. The storage / readout processing unit 89 of the schedule management server 12 also searches the user management DB 8002 (see FIG. 13) using the organization ID received in step S13 as a search key, thereby reading out all corresponding user IDs and all user names (step S20). The transmission / reception unit 81 then transmits schedule input screen information to the user terminal 40 (step S21). The transmission / reception unit 51 of the user terminal 40 receives the schedule input screen information.

[0131] This schedule input screen information includes the schedule information of reserver A, all user IDs, and all user names read out in step S20. All user names also include the name (user name) of reserver A who entered the information for signing in in step S12.

[0132] Next, in the user terminal 40, the generation unit 56 generates a schedule screen 545 and a 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 as shown in Fig. 25 and the schedule input screen 550 as shown in Fig. 25 on the display 506 (step S23).

[0133] This schedule screen 545 includes a schedule information display field 546 that displays schedule information set for reservation person A, and a "Create a meeting" button 547 that is pressed when creating a meeting schedule. By pressing the "Create a meeting" button 547 on the schedule screen 545, reservation person A can transition from the schedule screen 545 to a 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 union ID or union name of the location to be used (such as a conference room), an input field 553 for entering the scheduled start date and time and scheduled end date and time 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 participants other than the person who made the reservation, an input field 558 for entering the shared terminal 42 to be used in the event, a "Schedule setting" button 559 that is pressed when registering a schedule, and a "Close" button 560 that is pressed when canceling content that is being entered or has been entered.

[0135] Note that input field 558 for inputting the shared terminal 42 to be used at the event may be configured to suggest candidates 561 as shown in Fig. 27 by inputting part of the name (user name) of the shared terminal 42. When input is made into input field 558 or the shared terminal 42 to be used at the event is selected from candidates 561, it is set as the device to be used at the event, as shown in device display field 562 on schedule input screen 550 in Fig. 28.

[0136] In addition, the setting of the equipment to be used at the event may be performed by inputting the location of the event, such as a conference room, in input field 552, as shown in schedule input screen 550 in FIG. 29, so that the shared terminal 42 installed in the location of the event, such as a conference room, is set as the equipment to be used at the event.

[0137] Next, reserver A inputs the necessary information into schedule input screen 550 and presses "Schedule setting" button 559. This causes reception unit 52 to receive the input of schedule information (step S24). Then, transmission / reception unit 51 transmits the schedule information to schedule management server 12 (step S25).

[0138] This schedule information includes the event name, union ID (or union name), scheduled start date and time, scheduled end date and time, user ID of each participant, user ID of the shared terminal 42 to be used, and memos. Although omitted from schedule input screen 550 in Fig. 25, when selection of file data of materials to be used in the event is accepted from reservation user A, that file data is included in the schedule information.

[0139] The transmission / reception unit 81 of the schedule management server 12 receives the 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 FIG. 14) using the received union ID as a search key to read out the corresponding union name (or union ID) (step S26).

[0140] Next, the storage / readout processing unit 89 stores the reservation information for the union name (or union ID) read out in step S26 in the union reservation management DB 8004 (see FIG. 15) (step S27). The storage / readout processing unit 89 adds one record's worth 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 configured based on the schedule information received in step S25 and the union name (or union ID) read out in step S26. In the example of the union reservation management table in FIG. 15, the item "shared terminal user ID" represents the shared terminal 42 set as the device to be used in the event. The scheduled start date and time of use in the union reservation management DB 8004 corresponds to the scheduled start date and time in the schedule information. The scheduled end date and time of use in the union reservation management DB 8004 corresponds to the scheduled end date and time in the schedule information.

[0141] Furthermore, the storage / readout processing unit 89 stores the schedule information in the event management DB 8005 (see FIG. 16) (step S28). The storage / readout 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 plan information is configured based on the schedule information received in step S25. The example of the event management table in FIG. 16 shows an example in which the shared terminal 42 with user ID "u0000" is set as the device to be used in the event. 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. 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. In this way, reserver A can register the schedule of an event such as an online conference in which the shared terminal 42 has been selected as the device to be used.

[0143] Event Start Processing Here, a process will be described in which a reservation person A (Rikotaro) uses a shared terminal 42 to hold an online conference with the user terminals 40 of other participants in a reserved conference room X. Figures 30 and 31 are sequence diagrams showing the start process of an event.

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

[0145] Next, when user A inputs his / her email address and password on the sign-in screen, the reception unit 22 receives the sign-in request (step S33). The transmission / reception unit 21 transmits sign-in request information indicating the sign-in request to the sharing 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 sharing support server 11 receives the sign-in request information.

[0146] Next, the authentication unit 62 of the sharing support server 11 authenticates the user A using the user ID, organization ID, and password of the user A received in step S34 (step S35). Specifically, the storage / readout processing unit 69 uses the user ID, organization ID, and password of the user A received in step S34 as search keys to search the user authentication management DB 6001 (see FIG. 7) for a set of user ID, organization ID, and password that corresponds to the set of user ID, organization ID, and password of the user A received in step S34.

[0147] If a corresponding pair exists, authentication unit 62 determines that requesting subscriber A is a valid user. If a corresponding pair does not exist, authentication unit 62 determines that requesting subscriber A is an invalid (illegitimate) user. If not valid, transmitting / receiving unit 61 notifies shared terminal 42 that the requesting subscriber A is not valid. Here, the explanation continues for the valid case.

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

[0149] Next, the transmitting / receiving unit 61 transmits reservation request information indicating a request for reservation information of the union and schedule request information indicating a request for schedule information of the user 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 reserving user 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 sharing support server 11 using the access ID and access password (step S38).

[0150] Specifically, the storage / read processing unit 89 searches the server authentication management DB 8006 (see FIG. 17) for a set of an access ID and an access password that corresponds to the set of the access ID and the access password received in step S37.

[0151] If there is a corresponding pair, the authentication unit 82 determines that the requesting sharing support server 11 is a valid accessor. If there is no corresponding pair, the authentication unit 82 determines that the requesting sharing support server 11 is an invalid (illegitimate) accessor. If it is not valid, the transmitting / receiving unit 81 notifies the sharing support server 11 that it is not valid. Here, the explanation will continue for the valid case.

[0152] The storage / readout processing unit 89 of the schedule management server 12 searches the union reservation management DB 8004 (see FIG. 15) managed by the scheduler using the union ID received in step S37 as a search key, and reads out the corresponding reservation information (step S39). In this case, the storage / readout processing unit 89 reads out the reservation information whose scheduled start date and time of use is today.

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

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

[0155] Next, the storage / read processing unit 89 searches the project member management DB 8007 (see Figure 18) using the user ID of the subscriber A received in step S37 as a search key, and reads out the project IDs and project names of all projects that include the user ID of the subscriber 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 sharing support server 11 (step S42). As a result, the transmitting / receiving unit 61 of the sharing support server 11 receives the reservation information, schedule information, all project IDs, and all project names.

[0157] Next, the creation unit 63 of the sharing support server 11 creates a reservation list based on the reservation information and schedule information received in step S42 (step S43). Then, the transmitting / receiving unit 61 transmits reservation list information indicating the contents of the reservation list, as well as all project IDs and all project names, to the shared terminal 42 (step S44). The transmitting / receiving 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 a reservation list screen 230 as shown in FIG. 32 on the display 220 (step S45). FIG. 32 is a diagram showing a reservation list screen for a union. This reservation list screen 230 includes a display area 231 that displays the union name (here, the location name) and a display area 232 that displays today's date and time. Furthermore, the reservation list screen 230 displays event information 235-237 and the like related to today's events that use this union (here, conference room X). Event information refers to the information and data related to the events described above. Each event information includes, for each event, the scheduled start and end times of use of this union, the event name, and the name of the person who reserved this union (reservation name). The event information includes, but is not limited to, start buttons 235s-237s that a user presses to specify an event to start, as well as participants and actual start and end times of use.

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

[0160] 33 is a diagram showing a project list screen. The project list screen 240 includes project icons 241 to 246 that represent the respective projects. The project list screen 240 also includes an "OK" button 248 that is pressed to confirm the selected project icon, and a "CANCEL" button 249 that is pressed to cancel the selection of the project icon.

[0161] Next, in FIG. 33, when reserver A presses the project icon 241 with the electronic pen 2500 or the like, the acceptance 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 sharing support server 11 a scheduled event ID indicating the scheduled event selected in step S51 and a project ID indicating the project selected in step S53 (step S54). The processing in step S54 is a transmission request processing for the execution event identification information. As a result, the transmitting / receiving unit 61 of the sharing support server 11 receives the selected scheduled event ID and the selected project ID.

[0163] Next, in the sharing support server 11, the generation unit 64 generates a unique execution event ID (step S55). Then, the storage / readout processing unit 69 associates and manages the execution event ID generated in step S55, the reserved event ID received in step S54, the user ID and organization ID of the reserver, and the event information (step S56).

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

[0165] Next, the storage / read 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, in the sharing support server 11, the transmitting / receiving unit 61 transmits file data transmission request information indicating a transmission request for the file data registered in the schedule management server 12 to 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 reserver A received in step S34, and the access ID and access password read in step S36. As a result, the transmitting / receiving unit 81 of the schedule management server 12 receives the file data transmission request information.

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

[0168] Next, the storage / read processing unit 69 of the sharing 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 executed 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 to which reserver 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 the file data. Note that the transmitting / receiving unit 21 may also transmit an attendance request to the event to the user terminals 40 of the other participants using an invitation email or the like. This event attendance request includes various information for participating in (attending) the event started by reserver A.

[0170] As a result, other participants can use the request to attend the event to notify the sharing support server 11 from the user terminal 40 of their participation in the event, and participate in the event such as an online conference started by the reservation user A.

[0171] Next, in shared terminal 42, storage / read processing unit 29 stores the execution event ID and file data in storage unit 2000 (step S63). Here, the file data transmitted from sharing support server 11 is stored in a specific storage area of ​​storage unit 2000. As a result, shared terminal 42 accesses the specific storage area while the event is being executed, and display control unit 24 causes display 220 to display the file data stored in the specific storage area.

[0172] Here, the specific storage area is a temporary storage destination for data provided for each event being executed, and is a storage area specified by an arbitrary path (character string) indicating the location within storage unit 2000. The specific storage area is not limited to being provided inside shared terminal 42, but may be provided in an external storage device connected to shared terminal 42, or in a local server or the like that exists in an on-premise environment and is capable of communicating with shared terminal 42.

[0173] Next, the display control unit 24 displays a detailed information screen 250 of the selected event on the display 220, as shown in Fig. 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 planned time of the event (planned start time and planned end time), and a display area 253 for the names of people who have made reservations. Furthermore, the detailed information screen 250 of the event displays a display area 256 for displaying the contents of notes, a display area 257 for displaying the names of people who will be attending, and a display area 258 for displaying identification information (e.g., a file name) for identifying file data stored in a specific storage area of ​​the storage unit 2000.

[0174] The name of the person who made the reservation and the names of other selected participants are displayed in display area 257. In addition, display area 258 displays the file names of file data stored in a specific storage area of ​​storage unit 2000, i.e., file data downloaded from sharing support server 11, as well as the file names of file data currently being downloaded from sharing support server 11. Furthermore, the bottom right of event detailed information screen 250 includes a "Close" button 259 that can be pressed to close this detailed information screen 250.

[0175] Next, for example, other participants who have received a request to attend the event notify the sharing support server 11 from their own user terminals 40 of their participation in the event, and participate in the event such as an online conference started by reserver A (step S66). As a result, the transmitting / receiving unit 61 of the sharing support server 11 receives the user IDs of the other participants who have participated in the event such as an online conference started by reserver A. Next, the sharing support server 11 stores and manages whether or not the participants will participate in the participation / non-participation field that has not been entered in the schedule management DB 6003 (step S67).

[0176] As a result, the reservation user A and the other participants can start an event (here, an online conference) using the union (here, conference room X) and the shared terminal 42. The display control unit 24 causes the display 220 to display an event execution screen.

[0177] <<Processing during the event>> Next, we will explain the processing during an online conference, which is an example of an event, after it has started. First, in the started online conference, the reservation user 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, and the like provided by the collaboration system 10.

[0178] During the online conference, the reservation person A and other participants can use the chat function to send a message with a mention of the shared terminal 42 from the user terminal 40 to the shared terminal 42, thereby controlling the functions of the shared terminal 42 as described below.

[0179] Figure 35 is a diagram that associates the message content of the chat function with the operation content (functions) of the shared terminal that can be controlled by the 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 of Fig. 35, if the message content includes an attached file "test.ppt" with a mention, such as "@XX Conference Room Electronic Whiteboard" in Fig. 36, it indicates that the operation is to display the "test.ppt" file in Fig. 36 on the shared terminal 42, as shown in the screen image diagram of Fig. 37. Fig. 36 is a diagram showing an example of the message content posted using the chat function. Fig. 37 is a diagram showing an example of a display screen for an attached file.

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

[0182] In the example of Fig. 35, if the message content includes a mention such as "@XX conference room electronic whiteboard" and the text "view screen," it indicates that the operation is to share the display screen of the shared terminal 42, such as the screen image diagram in Fig. 40(a), with members participating in the same online conference. Fig. 40 is a diagram showing an example of the display screen and camera image of the shared terminal.

[0183] Also, in the example of Figure 35, if the message content includes a mention such as "@XX 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, such as the screen image shown in Figure 40(b), among members participating in the same online conference.

[0184] In addition to using the chat function, switching between the display image in FIG. 40(a) and the camera image in FIG. 40(b) may also be possible using button 580 at the bottom left of the screen of shared terminal 42 in FIG.

[0185] Furthermore, in the example of Figure 35, if the message content includes text indicating the end of the conference, such as "The test has ended" in Figure 41, it indicates that the operation is to post the conference log data file "ConferenceLog.zip," as in the message in the lower part of Figure 41.

[0186] The process in which participants in an online conference such as that shown in FIG. 35 use the chat function to control the functions of the shared terminal 42 can be realized by the processing procedures shown in the sequence diagrams of FIGS. 42 and 43, for example.

[0187] Figures 42 and 43 are sequence diagrams showing the process in which a user requests control of a shared terminal using the chat function. The sequence diagram of Figure 42 shows an example in which a request to control the functions of shared terminal 42 using the chat function is accepted from a user (person A) who is participating in the same online conference as shared terminal 42. The sequence diagram of Figure 43 shows an example in which a request to control the functions of shared terminal 42 using the chat function is accepted from a user (person B) who is not participating in the same online conference as shared terminal 42.

[0188] In FIG. 42, the user terminal 40 posts a chat message by sending a chat message to the collaboration system 10 in which the shared terminal 42 is specified as a mention by the user (Mr. A) and a file is attached (step S100).

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

[0190] Here, the determination unit 25 of the shared terminal 42 inquires of the collaboration system 10 whether the user (person A) who posted the message received in step S102 is participating in the same online conference as the shared terminal 42 (step S104). As an example, the identification information of the user (person A) who posted the message from the shared terminal 42 is sent to the collaboration system 10. The collaboration system 10 has the schedule management table shown in FIG. 9 in the storage unit 6000 of the sharing support server 11. The schedule management table includes the name of the person who made the reservation for the online conference, the user ID of the person who made the reservation, the names of the other participants, and the user IDs of the other participants. The collaboration system 10 determines whether the received user identification information is included in the identification information of the person who made the reservation or the other participants in the schedule management table. If included, it is determined that the users are participating in the same online conference. Since FIG. 42 shows an example in which the users are participating in the same online conference, the collaboration system 10 sends the shared terminal 42 a response of "Yes" indicating that the users are participating in the same online conference (step S106).

[0191] Since the user who posted the message (Mr. A) was participating in the same online conference as the shared terminal 42, the function control unit 31 of the shared terminal 42 performs control to display (project) the attachment of the message received in step S102 (step S108).

[0192] According to the sequence diagram of FIG. 42, a user can operate a shared terminal 42 from a user terminal 40 by sending a chat message to the shared terminal 42 participating in the same online conference.

[0193] In FIG. 43, the user terminal 40 posts a chat message by sending a chat message to the collaboration system 10 in which the shared terminal 42 is specified as a mention by the user (person B) and in which a file is attached (step S110).

[0194] The collaboration system 10 transmits the posted message with the mention to the shared terminal 42 (step S112). The shared terminal 42 determines that the mention in the received message specifies its own device and that the message has a file attached, and therefore determines that the message is a request to display (project) the attached file.

[0195] Here, the determination unit 25 of the shared terminal 42 inquires of the collaboration system 10 whether the user (person B) who posted the message received in step S112 is participating in the same online conference as the shared terminal 42 (step S114). Since Fig. 43 shows an example in which the users are not participating in the same online conference, the collaboration system 10 returns to the shared terminal 42 the information "No" indicating that the users are not participating in the same online conference (step S116).

[0196] The function control unit 31 of the shared terminal 42 does not display (project) the attachment 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 the shared terminal 42.

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

[0198] The collaboration system 10 sends the posted message with the mention to the user terminal 40 operated by the user (person B) (step S120). The user (person B) can confirm from the message content in Fig. 44 that the file attached to the message posted in step S110 was not displayed (projected) on the shared terminal 42 because he or she is not participating in the same online conference as the shared terminal 42.

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

[0200] In the sequence diagrams shown in FIGS. 42 and 43, the shared terminal 42 determines from the received message content that the request is to display (project) an attached file, but the determination may also be made by the collaboration system 10, as in the sequence diagrams shown in FIGS. 45 and 46, for example.

[0201] Figures 45 and 46 are sequence diagrams showing the process in which a user requests control of a shared terminal using the chat function. The sequence diagram of Figure 45 shows an example in which a request to control a function of shared terminal 42 using the chat function is accepted from a user (person A) who is participating in the same online conference as shared terminal 42. The sequence diagram of Figure 46 shows an example in which a request to control a function of shared terminal 42 using the chat function is accepted from a user (person B) who is not participating in the same online conference as shared terminal 42.

[0202] In FIG. 45, the user terminal 40 posts a chat message by sending a chat message to the collaboration system 10 in which the shared terminal 42 is specified as a mention by the user (person A) and a file is attached (step S140).

[0203] The determination 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 the message is a request to display (project) the attached file. Note that the determination unit 65 can determine the type of operation request by using a combination table that associates the message content with the operation content (function) of the shared terminal 42 that can be controlled by the message content, for example, as shown in Fig. 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 conference as the shared terminal 42 (step S142). Since Fig. 45 shows an example in which the users are participating in the same online conference, it is determined that they are participating in the same online conference.

[0205] Because the user who posted the message (Mr. A) was participating in the same online conference as the shared terminal 42, the control request unit 67 of the collaboration system 10 requests control from the shared terminal 42 to display (project) the attachment of the message received in step S140 (step S144).

[0206] In accordance with the control request of step S144, function control unit 31 of shared terminal 42 performs control to display (project) the file attached to the message of step S140 (step S146).

[0207] According to the sequence diagram of FIG. 42, a user can operate a shared terminal 42 from a user terminal 40 by sending a chat message to the shared terminal 42 participating in the same online conference.

[0208] In FIG. 46, the user terminal 40 posts a chat message by sending a chat message to the collaboration system 10 in which the shared terminal 42 is specified as a mention by the user (person B) and in which a file is attached (step S160).

[0209] The determination 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, 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 conference as the shared terminal 42 (step S162). Since Fig. 46 shows an example in which the users are not participating in the same online conference, it is determined that they are not participating in the same online conference.

[0211] Because the user (person B) who posted the message is not participating in the same online conference as the shared terminal 42, the collaboration system 10 transmits a message with a mention, for example, as shown in Fig. 44, to the user terminal 40 operated by the user (person B) (step S164). The user (person B) can confirm from the message content in Fig. 44 that the file attached to the message posted in step S160 was not displayed (projected) on the shared terminal 42 because he is not participating in the same online conference as the shared terminal 42.

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

[0213] [Other embodiments] In the above embodiment, a case where messages displayed on the chat screen are used has been described, but messages sent internally to the system (not displayed on the chat screen) may also be used. Also, this can be realized by using a message sending function separate from the chat function.

[0214] Furthermore, although the above embodiment has shown an example of text chat, it is also possible to operate shared terminal 42 by voice, for example. Fig. 47 is a sequence diagram showing the process in which a user requests control of a shared terminal by voice. The sequence diagram of Fig. 47 shows an example in which a request to control the functions of shared terminal 42 using the chat function is received from a user (person A) who is participating in the same online conference as shared terminal 42.

[0215] 47, a user (person A) operating user terminal 40 vocally utters, "Capture the screen of the electronic whiteboard in XX conference room" (step S180). User terminal 40 operated by user (person A) performs a voice analysis process on the utterance and converts the voice data into text data (step S182).

[0216] The user terminal 40 posts a chat message by sending the text data converted from the voice data by the voice analysis process of step S182 to the collaboration system 10, in which the shared terminal 42 is designated as a mention and in which a file is attached (step S184). The collaboration system 10 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 Fig. 42, and therefore description thereof will be omitted. Note that although the user terminal 40 performs the voice analysis processing of the utterance in Fig. 47, this may also be performed on the collaboration system 10 side. Also, for example, by using a voice chat function, a voice message may be posted, and the voice analysis processing may be performed on the collaboration system 10 or the shared terminal 42, which determines the type of operation request from the message content.

[0218] In addition, after the online conference mentioned above has ended, the conference log data posted as a file, such as the message in the lower part of Figure 41, may include, for example, a screen capture containing the content written at the time the online conference ended, or audio / video recording data from the microphone 2200, camera 2400, or audio / video recordings.

[0219] It is conceivable that after a typical online conference ends, the shared terminal 42 will be powered off or all of the posted content will be deleted. In this way, there is no problem if the operation of powering off or deleting the posted content is performed after the online conference ends, but if the operation of powering off or deleting the posted content is performed during the online conference, the conference log data will not be able to be posted correctly.

[0220] Therefore, for example, when the shared terminal 42 receives an operation to turn off the power or delete written content (delete all, delete page, etc.) from a user during an online conference, the shared terminal 42 may display a UI such as that shown in Fig. 48 to confirm with the user whether or not to post the conference log to the chat. By using a UI such as that shown in Fig. 48, even when the shared terminal 42 receives an operation to turn off the power or delete written content from a user during an online conference, the shared terminal 42 can successfully post a conference log data file as shown in Fig. 49.

[0221] The present invention is not limited to the specifically disclosed embodiments described above, and various modifications and changes are possible without departing from the scope of the claims. For example, a configuration in which the first embodiment is combined with other embodiments is also possible. Note that the information processing system 1 described in this embodiment is merely an example, and it goes without saying that there are various system configuration examples depending on the application and purpose.

[0222] Each function of the above-described embodiments can be realized by one or more processing circuits. Here, the term "processing circuit" in this specification includes a processor programmed to perform each function by software, such as a processor implemented by an electronic circuit, as well as devices such as an ASIC (Application Specific Integrated Circuit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), or a conventional circuit module designed to perform each function described above.

[0223] The devices described in the example are merely representative of one of several computing environments for implementing the embodiments disclosed herein.

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

[0225] Furthermore, the sharing 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 processing steps disclosed above in various combinations. For example, a process performed by a specific unit can be performed by another unit. Similarly, the function of a specific unit can be performed by another unit. Furthermore, the sharing support server 11, schedule management server 12, speech-to-text conversion server 13, and file management server 14 may be integrated into a single device or separated into multiple devices.

[0226] 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 utterance 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 setting 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 sending and receiving system. The collaboration system 10 is an example of an information processing device. The sending and receiving unit 51 is an example of a sending and receiving means. The function control unit 31 is an example of a control means. The memory unit 6000 is an example of a saving means. The camera 2400 is an example of an imaging means. [Explanation of symbols]

[0227] 1. Information Processing Systems 10 Collaboration System 11 Shared Support Server 12 Schedule Management Server 13 Speech-to-text server 14 File Management Server 20 Online Storage Server 25 Judgment Department 31 Function control section 32 Save request part 40 User terminals 42 Shared Terminals 50 Communication Network 66 Distribution Department 67 Control request section 84 Management Department [Prior art documents] [Patent documents]

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

Claims

1. A system for transmitting and receiving voice data, comprising: a plurality of user terminals; a plurality of shared terminals; and an information processing device connectable to each of the plurality of user terminals and the plurality of shared terminals via a network, a voice analysis processing means for performing voice analysis on voice data uttered by a user input from one of the plurality of user terminals; a determination means for determining whether or not a request for control of a shared terminal is included based on the voice analysis result analyzed by the voice analysis processing means; a control means for controlling a shared terminal designated by the voice analysis result among the plurality of shared terminals based on the control request when the determination means determines that the voice analysis result includes a request for control of the shared terminal; and and the control means controls the shared terminal if the user who uttered the voice data is participating in the same event, and does not control the shared terminal if the user is not participating in the event. system.

2. the determining means determines whether or not identification information of the user who uttered the voice data is included in identification information of participants attending the event; the control means controls the shared terminal when it is determined that the identification information of the user is included in the identification information of a participant attending the event; not controlling the shared terminal when it is determined that the identification information of the user is not included in the identification information of participants attending the event; The system of claim 1 .

3. the determining means determines whether or not identification information of the user who uttered the voice data is included in a database managed by the information processing device; the control means controls the shared terminal when it is determined that the user's identification information is included in the database; If it is determined that the user's identification information is not included in the database, the shared terminal is not controlled. The system of claim 1 .

4. and a storage means for storing shared data including text data used in the event.

3. The system according to claim 1 or 2.

5. the storage means stores the shared data during an event related to text data transmitted and received among the plurality of user terminals or after the event has ended. The system of claim 4.

6. and a management unit for managing event information including information on users participating in the event and information on the shared terminals.

3. The system according to claim 1 or 2.

7. The control of the shared terminal includes: Control of acquiring a screen displayed on a display unit of the shared terminal, control of displaying a screen captured by an image capturing means of the shared terminal on the display units of the plurality of user terminals, and and a control for saving shared data used in the event.

3. The system according to claim 1 or 2.

8. A shared terminal that can be connected to a plurality of user terminals and information processing devices via a network, a voice analysis processing means for analyzing voice data uttered by a user; a determination means for determining whether or not a request for control of the shared terminal is included based on the voice analysis result analyzed by the voice analysis processing means; a control means for controlling a shared terminal designated by the voice analysis result based on the control request when the determination means determines that the voice analysis result includes a request for control of the shared terminal; and and the control means controls the shared terminal if the user who uttered the voice data is participating in the same event, and does not control the shared terminal if the user is not participating in the event. Shared terminal.

9. An information processing device connectable to a plurality of user terminals and a plurality of shared terminals via a network, a voice analysis processing means for analyzing voice data uttered by a user; a determination means for determining whether or not a request for control of the shared terminal is included based on the voice analysis result analyzed by the voice analysis processing means; a control request means for, when the determination means determines that the voice analysis result includes a request for control of a shared terminal, making a request for control of a shared terminal specified by the voice analysis result among the plurality of shared terminals based on the control request; and the control request means requests control from the shared terminal if the user who has uttered the voice data is participating in the same event, and does not request control from the shared terminal if the user is not participating in the event; Information processing device.

10. A user terminal that can be connected to a plurality of shared terminals, information processing devices, and other user terminals via a network, a voice analysis processing means for analyzing voice data uttered by a user; a determination means for determining whether or not a request for control of the shared terminal is included based on the voice analysis result analyzed by the voice analysis processing means; a control request means for, when the determination means determines that the voice analysis result includes a request for control of a shared terminal, making a request for control of a shared terminal specified by the voice analysis result among the plurality of shared terminals based on the control request; and the control request means requests control from the shared terminal if the user who has uttered the voice data is participating in the same event, and does not request control from the shared terminal if the user is not participating in the event; User terminal.

11. An information processing method executed by a shared terminal connectable to a plurality of user terminals and information processing devices via a network, comprising: a voice analysis processing step of analyzing voice data uttered by a user; a determination step of determining whether or not the voice includes a request for control of the shared terminal based on the voice analysis result analyzed by the voice analysis processing step; a control step of controlling the shared terminal designated by the voice analysis result based on the control request when it is determined in the determination step that the voice analysis result includes a control request for the shared terminal; and the control step controls the shared terminal if the user who uttered the voice data is participating in the same event, and does not control the shared terminal if the user is not participating in the event. Information processing methods.

12. An information processing method executed by an information processing device connectable to a plurality of user terminals and a plurality of shared terminals via a network, comprising: a voice analysis processing step of analyzing voice data uttered by a user; a determination step of determining whether or not the voice includes a request for control of the shared terminal based on the voice analysis result analyzed by the voice analysis processing step; a control request step of requesting control of a shared terminal designated by the voice analysis result among the plurality of shared terminals based on the control request when it is determined in the determination step that the voice analysis result includes a request for control of the shared terminal; and the control request step requests the shared terminal to control the user who has uttered the voice data if the user is participating in the same event, and does not request the shared terminal to control the user if the user is not participating in the event; Information processing methods.

13. An information processing method executed by a user terminal connectable to a plurality of shared terminals, an information processing device, and other user terminals via a network, comprising: a voice analysis processing step of analyzing voice data uttered by a user; a determination step of determining whether or not the voice includes a request for control of the shared terminal based on the voice analysis result analyzed by the voice analysis processing step; a control request step of requesting control of a shared terminal designated by the voice analysis result among the plurality of shared terminals based on the control request when it is determined in the determination step that the voice analysis result includes a request for control of the shared terminal; and the control request step requests the shared terminal to control the user who has uttered the voice data if the user is participating in the same event, and does not request the shared terminal to control the user if the user is not participating in the event; Information processing methods.

14. A shared terminal that can be connected to a plurality of user terminals and information processing devices via a network, a voice analysis processing means for analyzing voice data uttered by a user; a determination means for determining whether or not the voice includes a request for control of the shared terminal based on the voice analysis result obtained by the voice analysis processing means; a control means for controlling the shared terminal designated by the voice analysis result based on the control request when the determination means determines that the voice analysis result includes a request for control of the shared terminal; It functions as the control means controls the shared terminal if the user who uttered the voice data is participating in the same event, and does not control the shared terminal if the user is not participating in the event. program.

15. An information processing device that can be connected to a plurality of user terminals and a plurality of shared terminals via a network, a voice analysis processing means for analyzing voice data uttered by a user; a determination means for determining whether or not the voice includes a request for control of the shared terminal based on the voice analysis result obtained by the voice analysis processing means; a control request means for, when the determination means determines that the voice analysis result includes a request for control of a shared terminal, making a request for control of a shared terminal specified by the voice analysis result among the plurality of shared terminals based on the control request; It functions as the control request means requests control from the shared terminal if the user who has uttered the voice data is participating in the same event, and does not request control from the shared terminal if the user is not participating in the event; program.

16. A user terminal that can be connected to a plurality of shared terminals, information processing devices, and other user terminals via a network, a voice analysis processing means for analyzing voice data uttered by a user; a determination means for determining whether or not the voice includes a request for control of the shared terminal based on the voice analysis result obtained by the voice analysis processing means; a control request means for, when the determination means determines that the voice analysis result includes a request for control of a shared terminal, making a request for control of a shared terminal specified by the voice analysis result among the plurality of shared terminals based on the control request; It functions as the control request means requests control from the shared terminal if the user who has uttered the voice data is participating in the same event, and does not request control from the shared terminal if the user is not participating in the event; program.

Images