JP2019192226A - Communication terminal, sharing system, communication method, and program - Google Patents

Abstract

To suppress a labor for causing a management system to store file data used for an event in association with content generated by the event.SOLUTION: A communication terminal which communicates with a management system which manages content generated by an executed event comprises: first transmission means for transmitting a transmission request of execution event identification information for identifying the executed event to the management system; first reception means for receiving the execution event identification information from the management system on the basis of the transmitted transmission request; event end reception means for receiving the end of the executed event; and second transmission means for, when the end of the event is received by the event end reception means, transmitting the received execution event identification information and file data used for the executed event to the management system.SELECTED DRAWING: Figure 38

Description

  The present disclosure relates to a communication terminal, a shared system, a communication method, and a program.

  2. Description of the Related Art In recent years, electronic blackboards that allow a background image to be displayed on a large display and a user to draw stroke images such as letters, numbers, and figures on the background image have been used in meetings, etc. in companies, educational institutions, and government agencies. (See Patent Document 1).

  Further, in an event such as a meeting, work for creating contents such as minutes is generated. Then, in order to share the content generated in the event among the participants of the event, the management system transmits each content generated in the event to a management system such as a server from a communication terminal such as an electronic blackboard, so that the management system Is remembered.

  However, in the conventional method, the management system can store the content that is the data to be stored for each event in response to the occurrence of the event, but stores the file data that was used for the event that is not the storage target for each event. I couldn't. Therefore, in order to store the file data used in the event in association with the content generated by the event in the management system, there is a problem that a separate process is required and takes time and effort.

  In order to solve the above-described problem, the invention according to claim 1 is a communication terminal that communicates with a management system that manages content generated by an event being executed, and for executing the event to be executed. First transmission means for transmitting a transmission request for event identification information to the management system, and first reception means for receiving execution event identification information from the management system based on the transmitted transmission request. An event end accepting unit for accepting the end of the event, and when the end is accepted by the event end accepting unit, the received execution event identification information and the file data used in the executed event are transmitted to the management system. And a transmission means.

  According to the present invention, there is no need for a separate process for storing the file data used in the event in association with the content generated by the event and storing it in the management system.

It is a schematic diagram of a shared system concerning this embodiment. It is a hardware block diagram of an electronic blackboard. It is a hardware block diagram of a video conference terminal. It is a hardware block diagram of a car navigation apparatus. It is a hardware block diagram of PC and a server. It is a software block diagram of an electronic blackboard. It is a software block diagram of PC. It is a functional block diagram of a shared system. (A) is a conceptual diagram of a user authentication management table, (B) is a conceptual diagram of an access management table, and (C) is a conceptual diagram of a schedule management table. (A) is a conceptual diagram of an execution event management table, (B) is a conceptual diagram of a content management table. (A) is a conceptual diagram of a user authentication management table, (B) is a conceptual diagram of a user management table, and (C) is a conceptual diagram of a union management table. (A) is a conceptual diagram of a union reservation management table, and (B) is a conceptual diagram of an event management table. (A) is a conceptual diagram of a union reservation management table, and (B) is a conceptual diagram of a project member management table. (A) Conceptual diagram of execution event history management table, (B) Conceptual diagram of execution event management table. It is a conceptual diagram of a related information management table. It is the sequence diagram which showed the registration process of the project. It is the figure which showed the sign-in screen. It is an example of the initial screen of PC. It is an example of a project registration screen. It is the sequence figure which showed the registration process of the schedule. It is the figure which showed the schedule input screen. It is the sequence diagram which showed the start process of an event. It is the figure which showed the sign-in screen displayed on an electronic blackboard. It is the figure which showed the union reservation list screen. It is the sequence diagram which showed the start process of an event. It is the figure which showed the project list screen. It is the figure which showed the detailed information screen of an event. It is the image figure which showed the state in which a user uses an electronic blackboard. It is the sequence figure which showed the registration processing of execution event history. It is the flowchart which showed the audio | voice text conversion process. It is the sequence figure which showed the registration processing of execution event history. It is a follow chart which showed the registration process of action item. It is an example of a screen which recognizes an action item. It is an example of a screen which shows the candidate list | wrist which performs an action item. It is an example of a screen which shows the calendar for selecting the expiration date of an action item. It is the sequence figure which showed the end process of the event. It is the sequence figure which showed the end process of the event. It is the figure which showed the event end screen on the electronic blackboard. It is the figure which showed the upload screen of file data on an electronic blackboard. It is the figure which showed the upload completion screen of file data on an electronic blackboard. It is the sequence figure which showed the browsing process of execution event history. It is the sequence figure which showed the browsing process of execution event history. It is the figure which showed the project list screen on PC. It is the figure which showed the execution event list screen on PC. It is the figure which showed the execution event log | history screen on PC. It is the figure which showed the execution event log | history screen on PC. It is the figure which showed the action item screen on PC.

  Hereinafter, the shared system 1 according to the present embodiment will be described in detail with reference to the drawings. In the present embodiment, “file” indicates “electronic file”.

<< Outline of system configuration >>
First, an outline of the configuration of the shared system 1 will be described. FIG. 1 is a schematic diagram of a shared system according to the present embodiment.

  As shown in FIG. 1, the shared system 1 of this embodiment includes an electronic blackboard 2, a video conference terminal 3, a car navigation device 4, a PC (Personal Computer) 5, a shared support server 6, and a schedule management. The server 8 and the voice text conversion server 9 are constructed.

  In addition, the electronic blackboard 2, the video conference terminal 3, the car navigation device 4, the PC 5, the shared support server 6, the schedule management server 8, and the voice text conversion server 9 can communicate via the communication network 10. The communication network 10 is constructed by the Internet, a mobile communication network, a LAN (Local Area Network) or the like. The communication network 10 may include not only wired communication but also a network based on wireless communication such as 3G (3rd Generation), WiMAX (Worldwide Interoperability for Microwave Access), or LTE (Long Term Evolution).

  The electronic blackboard 2 is used in the conference room X. The video conference terminal 3 is used in the conference room Y. In addition, unions are subject to reservation by each user. The car navigation device 4 is used in the vehicle α. The vehicle α in this case is a vehicle that is a target of car sharing. Vehicles include cars, motorcycles, bicycles, wheelchairs and the like.

  “Union” indicates an object, service, space (room), place, or information that is shared by a plurality of people or organizations. The conference room X, the conference room Y, and the vehicle α are an example of a common body shared by a plurality of users. An example of information assigned to a union is an account. For example, in a specific service provided on the Web, the number of accounts used is limited to one.

  The electronic blackboard 2, the video conference terminal 3, and the car navigation device 4 are examples of communication terminals. The “communication terminal” is, for example, a terminal that can be used by a user sign-in (see S32 described later). Note that the communication terminals used in the vehicle α include not only the car navigation device 4 but also a smartphone or a smart watch installed with a car navigation application.

  The PC 5 is an information processing apparatus, and is an example of a registration apparatus that registers a reservation for use of each union and an event scheduled for execution by each user with respect to the schedule management server 8. The event is, for example, a meeting, a meeting, a gathering, a meeting, a consultation, a meeting, a driving, a ride or a movement.

  The sharing support server 6 is a computer, and provides support when sharing a union remotely with respect to each communication terminal.

  The schedule management server 8 is a computer, and manages reservations for each union and schedules for each user.

  The voice text conversion server 9 is a computer, and converts sound (voice) data received from an external computer (for example, the shared support server 6) into text data.

  Here, the sharing support server 6, the schedule management server 8, and the voice text conversion server 9 are referred to as a management system. The management system may be, for example, a server that bears all or some of the functions of the sharing support server 6, the schedule management server 8, and the voice text conversion server 9.

<< Hardware configuration >>
Subsequently, a hardware configuration of an apparatus or a terminal that constructs the shared system 1 will be described with reference to FIGS. 2 to 5.

<Hardware configuration of electronic blackboard>
FIG. 2 is a hardware configuration diagram of the electronic blackboard. As shown in FIG. 2, the electronic blackboard 2 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 / O. F205 and an external device connection I / F (Interface) 206 are provided.

  Among these, the CPU 201 controls the overall operation of the electronic blackboard 2. The ROM 202 stores programs used for driving the CPU 201 such as the CPU 201 and IPL (Initial Program Loader). The RAM 203 is used as a work area for the CPU 201. The SSD 204 stores various data such as an electronic blackboard program. The network I / F 205 controls communication with the communication network 10. The external device connection I / F 206 controls communication with a USB (Universal Serial Bus) memory 2600, a PC 2700, and external devices (a microphone 2200, a speaker 2300, and a camera 2400).

  The electronic blackboard 2 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. I have.

  Among these, the capture device 211 acquires image data displayed on the display 220 which is an example of a display unit (display unit) via the display controller 213 and stores the acquired image data in the 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 the GPU 212 to the display 220 or the like. The contact sensor 214 detects that the electronic pen 2500, the user's hand H, or the like has touched the display 220. The sensor controller 215 controls processing of the contact sensor 214. The contact sensor 214 performs input of coordinates and detection of coordinates by an infrared ray blocking method. In this coordinate input and coordinate detection method, two light emitting and receiving devices installed at both upper ends of the display 220 radiate a plurality of infrared rays in parallel with the display 220, and are provided around the display 220. This is a method of receiving light that is reflected by the reflecting member and returns on the same optical path as the light path emitted by the light receiving element. The contact sensor 214 outputs infrared IDs emitted from the two light receiving and emitting devices blocked by the object to the sensor controller 215, and the sensor controller 215 specifies 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 or not there is a pen tip touch or a pen butt touch on the display 220. The short-range communication circuit 219 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The power switch 222 is a switch for switching on / off the power of the electronic blackboard 2.

  Further, the electronic blackboard 2 includes a bus line 210. The bus line 210 is an address bus, a data bus, or the like for electrically connecting components such as the CPU 201 shown in FIG.

  The contact sensor 214 is not limited to the infrared blocking method, and a capacitive touch panel that specifies a contact position by detecting a change in capacitance, and a contact position is specified by a voltage change between two opposing resistance films. Various detection means such as a resistive film type touch panel that detects the electromagnetic induction generated when the contact object touches the display unit and identifies the contact position may be used. In addition, the electronic pen controller 216 may determine whether there is a touch on a part gripped by the user of the electronic pen 2500 and other electronic pen parts as well as the pen tip and pen butt of the electronic pen 2500.

<Hardware configuration of video conference terminal>
FIG. 3 is a diagram illustrating a hardware configuration of the video conference terminal. As shown in FIG. 3, the video conference terminal 3 includes a CPU 301, a ROM 302, a RAM 303, a flash memory 304, an SSD 305, a media I / F 307, an operation button 308, a power switch 309, a bus line 310, a network I / F 311, CMOS (Complementary Metal Oxide Semiconductor) sensor 312, image sensor I / F 313, microphone 314, speaker 315, sound input / output I / F 316, display I / F 317, external device connection I / F 318, short-range communication circuit 319 and short-range communication An antenna 319a of the circuit 319 is provided. Among these, the CPU 301 controls the operation of the entire video conference terminal 3. The ROM 302 stores a program used for driving the CPU 301 such as IPL. The RAM 303 is used as a work area for the CPU 301. The flash memory 304 stores various data such as a communication program, image data, and sound data. The SSD 305 controls reading or writing of various data with respect to the flash memory 304 according to the control of the CPU 301. An HDD may be used instead of the SSD. A media I / F 307 controls reading or writing (storage) of data with respect to a recording medium 306 such as a flash memory. The operation button 308 is a button that is operated when the destination of the video conference terminal 3 is selected. The power switch 309 is a switch for switching on / off the power of the video conference terminal 3.

  The network I / F 311 is an interface for performing data communication using the communication network 10 such as the Internet. The CMOS sensor 312 is a kind of built-in imaging unit that captures an image of a subject under the control of the CPU 301 and obtains image data. The image sensor I / F 313 is a circuit that controls driving of the CMOS sensor 312. The microphone 314 is a kind of built-in sound collecting means for inputting sound. The sound input / output I / F 316 is a circuit that processes input / output of a sound signal between the microphone 314 and the speaker 315 under the control of the CPU 301. The display I / F 317 is a circuit that transmits image data to the external display 320 under the control of the CPU 301. The external device connection I / F 318 is an interface for connecting various external devices. The short-range communication circuit 319 is a communication circuit such as NFC or Bluetooth.

  The bus line 310 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 301 shown in FIG.

  The display 320 is a type of display unit (display unit) configured by a liquid crystal or organic EL that displays an image of a subject, an operation icon, and the like. The display 320 is connected to the display I / F 317 by a cable 320c. The cable 320c may be an analog RGB (VGA) signal cable, a component video cable, DisplayPort, HDMI (registered trademark) (High-Definition Multimedia Interface) (registered trademark). ) Or DVI (Digital Video Interactive) signal cable.

  Instead of the CMOS sensor 312, an image sensor such as a CCD (Charge Coupled Device) sensor may be used. External devices such as an external camera, an external microphone, and an external speaker can be connected to the external device connection I / F 318 by a USB cable or the like. When an external camera is connected, the external camera is driven in preference to the built-in CMOS sensor 312 according to the control of the CPU 301. Similarly, when an external microphone is connected or when an external speaker is connected, each of the external microphone and the internal speaker 315 is given priority over the internal microphone 314 or the internal speaker 315 according to the control of the CPU 301. An external speaker is driven.

  The recording medium 306 is detachable from the video conference terminal 3. Further, as long as it is a nonvolatile memory that reads or writes data according to the control of the CPU 301, not only the flash memory 304 but also an EEPROM or the like may be used.

<Hardware configuration of car navigation system>
FIG. 4 is a hardware configuration diagram of the car navigation apparatus. As shown in FIG. 4, the car navigation device 4 includes a CPU 401, a ROM 402, a RAM 403, an EEPROM 404, a power switch 405, an acceleration / direction sensor 406, a media I / F 408, and a GPS receiver 409.

  Among these, the CPU 401 controls the operation of the entire car navigation device 4. The ROM 402 stores a program used for driving the CPU 401 such as IPL. The RAM 403 is used as a work area for the CPU 401. The EEPROM 404 reads or writes various data such as a program for the car navigation device 4 under the control of the CPU 401. The power switch 405 is a switch for switching on / off the power of the car navigation device 4. The acceleration / direction sensor 406 is various sensors such as an electronic magnetic compass, a gyrocompass, and an acceleration sensor that detect geomagnetism. A media I / F 408 controls reading or writing (storage) of data with respect to a recording medium 407 such as a flash memory. The GPS receiver 409 receives GPS signals from GPS satellites.

  The car navigation device 4 includes a long-distance communication circuit 411, an antenna 411a of the long-distance communication circuit 411, a CMOS sensor 412, an image sensor I / F 413, a microphone 414, a speaker 415, a sound input / output I / F 416, a display 417, and a display. An I / F 418, an external device connection I / F 419, a short-range communication circuit 420, and a short-range communication circuit 420 antenna 420 a are provided.

  Among these, the long-distance communication circuit 411 receives traffic information, road construction information, traffic accident information, etc. provided from the infrastructure outside the vehicle, and conversely transmits the vehicle position, emergency lifesaving signal, etc. to the outside. It is a circuit for doing. The external infrastructure is, for example, a road information guidance system such as a VICS (registered trademark) (Vehicle Information and Communication System) system. The CMOS sensor 412 is a kind of built-in imaging unit that captures an image of a subject under the control of the CPU 401 and obtains image data. The image sensor I / F 413 is a circuit that controls driving of the CMOS sensor 412. The microphone 414 is a kind of built-in sound collecting means for inputting sound. The sound input / output I / F 416 is a circuit that processes input / output of a sound signal between the microphone 414 and the speaker 415 under the control of the CPU 401. The display 417 is a type of display unit (display unit) such as a liquid crystal display or an organic EL display that displays an image of a subject, various icons, and the like, and has a touch panel function. The touch panel is a kind of input means for the user to operate the car navigation device 4. The display I / F 418 is a circuit that displays an image on the display 417. The external device connection I / F 419 is an interface for connecting various external devices. The short-range communication circuit 420 is a communication circuit such as NFC or Bluetooth. In addition, the car navigation device 4 includes a bus line 410. The bus line 410 is an address bus, a data bus, or the like for electrically connecting the components such as the CPU 401 shown in FIG.

<Hardware configuration of PC and server>
FIG. 5 is a hardware configuration diagram of the PC and the server. The PC 5 is constructed by a computer, and as shown in FIG. 5, a CPU 501, ROM 502, RAM 503, HD 504, HDD (Hard Disk Drive) controller 505, recording medium 506, media I / F 507, display 508, network An I / F 509, a keyboard 511, a mouse 512, a CD-RW drive 514, a speaker 515, and a bus line 510 are provided.

  Among these, the CPU 501 controls the operation of the entire PC 5. The ROM 502 stores a program used for driving the CPU 501 such as IPL. The RAM 503 is used as a work area for the CPU 501. The HD 504 stores various data such as programs. An HDD (Hard Disk Drive) controller 505 controls reading or writing of various data with respect to the HD 504 according to the control of the CPU 501. A media I / F 507 controls reading or writing (storage) of data with respect to a recording medium 506 such as a flash memory. The display 508 displays various types of information such as a cursor, menu, window, character, or image. A network I / F 509 is an interface for performing data communication using the communication network 10. The keyboard 511 is a kind of input means having a plurality of keys for inputting characters, numerical values, various instructions, and the like. The mouse 512 is a kind of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, and the like. The CD-RW drive 514 controls reading or writing of various data with respect to a CD-RW (Compact Disc-ReWritable) 513 as an example of a removable recording medium. The speaker 515 outputs a sound signal according to the control of the CPU 501.

  The PC 5 includes a bus line 510. The bus line 510 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 501 shown in FIG.

  The shared support server 6 is constructed by a computer, and as shown in FIG. 5, a CPU 601, ROM 602, RAM 603, HD 604, HDD controller 605, recording medium 606, media I / F 607, display 608, network An I / F 609, a keyboard 611, a mouse 612, a CD-RW drive 614, and a bus line 610 are provided. These are the CPU 501, ROM 502, RAM 503, HD 504, HDD controller 505, recording medium 506, media I / F 507, display 508, network I / F 509, keyboard 511, mouse 512, CD-RW drive 514, and bus line, respectively. Since it is the same structure as 510, description is abbreviate | omitted.

  Further, the schedule management server 8 is constructed by a computer, and as shown in FIG. 5, a CPU 801, ROM 802, RAM 803, HD 804, HDD controller 805, recording medium 806, media I / F 807, display 808, network An I / F 809, a keyboard 811, a mouse 812, a CD-RW drive 814, and a bus line 810 are provided. These are the CPU 501, ROM 502, RAM 503, HD 504, HDD controller 505, recording medium 506, media I / F 507, display 508, network I / F 509, keyboard 511, mouse 512, CD-RW drive 514, and bus line, respectively. Since it is the same structure as 510, description is abbreviate | omitted.

  The voice text conversion server 9 is constructed by a computer, and as shown in FIG. 5, a CPU 901, ROM 902, RAM 903, HD 904, HDD controller 905, recording medium 906, media I / F 907, display 908, A network I / F 909, a keyboard 911, a mouse 912, a CD-RW drive 914, and a bus line 910 are provided. These are the CPU 501, ROM 502, RAM 503, HD 504, HDD controller 505, recording medium 506, media I / F 507, display 508, network I / F 509, keyboard 511, mouse 512, CD-RW drive 514, and bus line, respectively. Since it is the same structure as 510, description is abbreviate | omitted.

  Each of the above-mentioned programs may be recorded in a computer-readable recording medium and distributed as a file in an installable or executable format. Examples of the recording medium include a CD-R (Compact Disc Recordable), a DVD (Digital Versatile Disk), a Blu-ray disc, and an SD card. The recording medium can be provided domestically or abroad as a program product.

  Furthermore, the shared support server 6 may be constructed by a single computer, or may be constructed by a plurality of computers arbitrarily assigned by dividing each unit (function, means, or storage unit). The same applies to the schedule management server 8 and the speech text conversion server 9.

<< Software configuration of electronic blackboard >>
Next, computer software installed on the electronic blackboard 2 will be described with reference to FIG. Here, the computer software (hereinafter referred to as software) is a program related to the operation of the computer and other information used for processing by the computer, and corresponds to the program. A program is a command to a computer and is combined so that one result can be obtained. In addition, the term “similar to a program” refers to a program that has a property similar to a program in that it defines a computer process, although it cannot be called a program because it is not a direct command to a computer. For example, a data structure (a logical structure of data represented by a mutual relationship between data elements) corresponds to a program.

  An application is a generic name for software used for performing a specific process among software classifications. On the other hand, an operating system (hereinafter referred to as OS) is software for controlling a computer and making applications and the like available to computer resources. The OS performs basic management and control of computers such as input / output control, management of hardware such as a memory and a hard disk, and management of processes. The application operates using a function provided by the OS.

  FIG. 6 is a diagram illustrating a software configuration of the electronic blackboard. As shown in FIG. 6, the OS 101, Launcher 102, schedule viewer 103 a, file viewer 103 b, and browser application 103 c operate on the work area 15 of the RAM 203. The OS 101 is basic software that provides basic functions of the electronic blackboard 2 and manages the entire electronic blackboard 2.

  The Launcher 102 is a launcher application that operates on the OS 101. For example, the launcher 102 manages the start and end of an event such as a meeting executed on the electronic blackboard 2, or manages external applications such as the schedule viewer 103a, the file viewer 103b, and the browser application 103c used during the execution of the event.

  The schedule viewer 103a, the file viewer 103b, and the browser application 103c are external applications that operate on the Launcher 102 (hereinafter, referred to as the external application 103 when there is no need to distinguish between them). The external application 103 executes processing independently of the Launcher 102 and executes a service or function provided on the OS 101. FIG. 6 shows an example in which three external applications of the schedule viewer 103a, the file viewer 103b, and the browser application 103c are installed on the electronic blackboard 2, but the number of external applications is not limited to this.

<< PC software configuration >>
Next, computer software installed in the PC 5 will be described with reference to FIG. FIG. 7 is a diagram showing a software configuration of the PC. As shown in FIG. 7, the OS 5501, the minutes application 5502 a, and the browser 5502 b operate on the work area 5500 of the RAM 503. The OS 5501 is basic software that provides basic functions of the PC 5 and manages the entire PC 5.

  The minutes application 5502a and the browser 5502b are applications for generating and displaying an execution event history screen, which is a minutes of events executed by the electronic blackboard 2, using various data transmitted from the schedule management server 8. is there. FIG. 7 shows an example in which two external applications, the minutes application 5502a and the browser 5502b, are installed in the PC 5, but the number of external applications is not limited to this.

<< Functional configuration of shared system >>
Subsequently, the functional configuration of the present embodiment will be described with reference to FIGS. FIG. 8 is a functional block diagram of the shared system. In FIG. 8, among the terminals, devices, and servers shown in FIG. 1, those related to the processing or operation described later are shown.

<Functional configuration of electronic blackboard>
As shown in FIG. 8, the electronic blackboard 2 includes a transmission / reception unit 21, a reception unit 22, an image / sound processing unit 23, a display control unit 24, a determination unit 25, a recognition unit 26, an acquisition / providing unit 28, a storage A read processing unit 29 is included. Each of these units is a function realized by any one of the constituent elements shown in FIG. 2 or a functioning means that is operated by an instruction from the CPU 201 according to a program developed on the RAM 203 from the SSD 204. is there. The electronic blackboard 2 includes a storage unit 2000 constructed by the RAM 203, the SSD 204, or the USB memory 2600 shown in FIG.

(Each blackboard functional configuration)
Next, each component of the electronic blackboard 2 will be described. The transmission / reception unit 21 is realized by a command from the CPU 201 illustrated in FIG. 2, a network I / F 205 and an external device connection I / F 206, and other terminals, devices, or systems and various data ( Or information).

  The accepting unit 22 is mainly realized by a command from the CPU 201 shown in FIG. 2, and the contact sensor 214 and the electronic pen controller 216, and accepts various inputs by the user.

  The image / sound processing unit 23 stores the image data displayed on the display 220, which is realized by the command from the CPU 201 shown in FIG. 2 and the capture device 211. The image / sound processing unit 23 is realized by a command from the CPU 201 shown in FIG. 2 and the GPU 212, and performs image processing for displaying an image on the display 220. Further, the image / sound processing unit 23 performs image processing on image data obtained by the camera 2400 imaging the subject. The image / sound processing unit 23 performs sound processing on sound data related to the sound signal after the user's sound is converted into a sound signal by the microphone 2200. Further, the image / sound processing unit 23 outputs a sound signal related to the sound data to the speaker 2300 and causes the speaker 2300 to output sound. In addition, the image / sound processing unit 23 performs processing for converting drawing image data obtained by drawing on the display 220 by the user with the electronic pen 2500 or the hand H into coordinate data. For example, when the electronic blackboard (2a) of an arbitrary base transmits coordinate data to the electronic blackboard (2b) of another base, the electronic blackboard (2b) is connected to the other electronic blackboard (2b) side based on the coordinate data. A drawing having the same content is displayed on the display 220.

  The display control unit 24 is realized by the instruction from the CPU 201 shown in FIG. 2 and the display controller 213 shown in FIG. 2, and displays a drawing image on the display 220 or supports sharing using a Web browser. The server 6 is accessed to display various screen data. Specifically, the display control unit 24 starts and executes the launcher 102 that operates on the OS 101 and the external application 103 illustrated in FIG. 6, and thereby performs various renderings that are rendered by an API (Application Programming Interface) provided by the OS 101. The screen is displayed on the display 220.

  The determination unit 25 is realized by a command from the CPU 201 illustrated in FIG. 2 and performs various determinations.

  The recognition unit 26 is realized by a command from the CPU 201 shown in FIG. 2 and recognizes a designated area 262 surrounded on the display 220 as shown in FIG. 31 described later.

  The acquisition / providing unit 28 is executed by the instruction from the CPU 201 shown in FIG. 2 and the short-range communication circuit 219 and the antenna 219a, and by short-range communication with a dedicated terminal such as an IC card or a smartphone, Acquire and provide data.

  The storage / reading processing unit 29 is executed by the instruction from the CPU 201 and the SSD 204 shown in FIG. 2, and stores various data in the storage unit 2000 and reads out various data stored in the storage unit 2000. I do. Furthermore, the storage unit 2000 overwrites and stores image data and sound data received when communicating with other electronic blackboards and video conference terminals. Among these, an image is displayed on the display 220 by the image data before being overwritten, and sound is output from the speaker 2300 by the sound data before being overwritten.

  Note that the video conference terminal 3 and the car navigation device 4 have the same functions as those of the electronic blackboard 2, and thus the description thereof is omitted here.

<Functional configuration of PC>
The PC 5 includes a transmission / reception unit 51, a reception unit 52, a display control unit 54, a generation unit 56, a sound control unit 58, and a storage / read processing unit 59. Each of these units is a function or a means that functions when any one of the components shown in FIG. 5 is operated by an instruction from the CPU 501 according to a program expanded from the HD 504 to the RAM 503. . Further, the PC 5 has a storage unit 5000 constructed by the HD 504 shown in FIG.

(Functional configuration of PC)
Next, each component of the PC 5 will be described. The transmission / reception unit 51 is realized by a command from the CPU 501 and the network I / F 509 illustrated in FIG. 5, and transmits / receives various data (or information) to / from other terminals, devices, or systems via the communication network 10.

  The accepting unit 52 is mainly realized by a command from the CPU 501 shown in FIG. 5 and a keyboard 511 and a mouse 512, and accepts various inputs by the user.

  The display control unit 54 is realized by a command from the CPU 501 shown in FIG. 5, and displays an image on the display 508 or accesses the shared support server 6 using a Web browser to display various screen data. To do. Specifically, for example, the display control unit 54 accesses the shared support server 6 or the schedule management server 8 by starting and executing the minutes application 5502a or the browser 5502b operating on the OS 5501 shown in FIG. . The display control unit 54, for example, downloads WebAPP (WebApplication) including at least HTML (HyperText Markup Language), including CSS (Cascading Style Sheets) or JAVA SCRIPT (registered trademark), and generated by the WebAPP. Various image data are displayed on the display 508. For example, the display control unit 54 causes the display 508 to display image data generated by HTML 5 including data such as XML (Extensible Markup Language), JSON (JavaScript Object Notation), or SOAP (Simple Object Access Protocol).

  The generation unit 56 is realized by a command from the CPU 501 shown in FIG. 5 and has a function of generating various image data to be displayed on the display 508. The generation unit 56 generates various image data using the content data received by the transmission / reception unit 51. For example, the generation unit 56 renders text data that is content data, and generates image data related to the text data that is content image data in order to display the rendered data. Rendering is processing for interpreting data described in a Web page description language (HTML, CSS, XML, etc.) and calculating the arrangement of characters, image data, etc. that are actually displayed on the screen.

  The sound control unit 58 is realized by a command from the CPU 501 shown in FIG. 5 and has a function of outputting a sound signal from the speaker 515. The sound control unit 58 sets sound data to be output from the speaker 515, and reproduces the sound data by outputting a sound signal related to the set sound data from the speaker 515.

  The storage / read processing unit 59 is executed by the instruction from the CPU 501 shown in FIG. 5 and the HDD controller 505 and the like, and stores various data in the storage unit 5000 and reads various data from the storage unit 5000. Process.

<Functional configuration of shared support server>
The sharing support server 6 includes a transmission / reception unit 61, an authentication unit 62, a creation unit 63, a generation unit 64, a determination unit 65, and a storage / read processing unit 69. Each of these units functions or functions realized by any of the constituent elements shown in FIG. 5 operating according to instructions from the CPU 601 according to the sharing support program expanded from the HD 604 to the RAM 603. Means. The shared support server 6 includes a storage unit 6000 constructed by the HD 604 and the like shown in FIG.

(User authentication management table)
FIG. 9A is a conceptual diagram showing a user authentication management table. In the storage unit 6000, a user authentication management DB 6001 configured by a user authentication management table as shown in FIG. 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 managed in association with each other. The organization ID includes a domain name representing a group or organization for managing a plurality of computers on the communication network.

(Access management table)
FIG. 9B is a conceptual diagram showing an access management table. In the storage unit 6000, an access management DB 6002 configured by an access management table as shown in FIG. 9B is constructed. In this access management table, an organization ID, an access ID necessary for authentication when accessing the schedule management server 8, and an access password are managed in association with each other. This access ID and access password are received by the schedule management server 8 via the Web API (Application Programming Interface) or the like using the HTTP (Hypertext Transfer Protocol) or HTTPS (Hypertext Transfer Protocol Secure) protocol. Necessary for using the provided services (functions). The schedule management server 8 manages a plurality of schedulers, and if the organization is different, the scheduler to be used may be different. Therefore, the schedule management server 8 needs to be managed by an access management table.

(Schedule management table)
FIG. 9C is a conceptual diagram showing a schedule management table. In the storage unit 6000, a schedule management DB 6003 configured by a schedule management table as shown in FIG. In this schedule management table, for each scheduled event ID and execution event ID, organization ID, reservation user ID, presence / absence of participation of this reservation person, reservation person name, scheduled start time, scheduled end time, event name, etc. The participant user ID, the presence / absence of participation of other participants, other participant names, and file data are managed in association with each other.

  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 execution event ID is identification information for identifying an actually executed event among the reserved events. The execution event ID is an example of execution event identification information for identifying the event being executed. The name of the reservation person is the name of the person who reserved the union. For example, if the union is a conference room, the name of the organizer is used. If the union is a vehicle, the name of the driver is used. The scheduled start time indicates the scheduled use start time of the union. The scheduled end time indicates the scheduled use end time of the union. The event name indicates the name of the event scheduled by the reservation person. The user IDs of the other participants are identification information for identifying participants other than the reservation person. Other participant names are names of participants other than the reservation person, and also include unions. In other words, the users in this case include reservations and other participants as well as unions. The file data is file data of a material file used in an event corresponding to the scheduled event ID registered by the user A using a schedule input screen 550 (see FIG. 21) described later. The file data is data in a predetermined file format created using various applications. The file format of the file data is, for example, a power point file or an Excel file.

(Execution event management table)
FIG. 10A is a conceptual diagram showing an execution event management table. In the storage unit 6000, an execution event management DB 6004 configured by an execution event management table as shown in FIG. In this execution event management table, an execution event ID is associated with each project ID and managed. The project ID is identification information (an example of project identification information) for identifying a project. A project indicates a group, team, or group composed of a plurality of members to achieve a specific goal, plan, plan, or the like. Members belonging to the same project can share an execution event history such as minutes of events associated with the project ID. As shown in FIG. 26, which will be described later, the project ID is assigned to each project such as a policy for the next fiscal year and customer development. The project ID is registered by a project registration process shown in FIG. The project ID may be referred to as a group ID or a team ID.

(Content management table)
FIG. 10B is a conceptual diagram showing a content management table. In the storage unit 6000, a content management DB 6005 configured by a content management table as shown in FIG. In this content management table, for each execution event ID, the content processing ID, the type of content processing, the content content, and the start date / time and end date / time of the content processing are associated and managed. Here, the content is the content of an execution event that has occurred at an event such as a meeting in a certain project, or materials used in the event. Types of content processing include recording, snapshot, voice text reception, generation of action items, and material delivery. The content processing ID is identification information for identifying the processing of the content that has occurred in each event.

  Here, the content includes history information indicating the execution contents of the event and action items generated by the executed event. The history information is data such as recorded data, snapshots, audio texts, or materials. A snapshot is a process of acquiring a display screen at a certain time point of an event being executed as image data. The snapshot is also referred to as capture or image recognition, for example.

  When the type of content processing is “recording”, the content includes a URL indicating a storage destination of the recorded sound data. Further, when the type of content processing is “snapshot”, the content content includes a URL indicating the storage destination of the image data of the screen acquired by the snapshot (capture). Capturing means saving an image (still image or moving image) displayed on the display 200 as image data. Further, when the type of content processing is “speech text reception”, the content content includes a URL indicating a storage destination of text data of the received speech text.

  Here, the action item is generated at an event such as a meeting in a certain project, and indicates the content of an action that should be handled by a person related to the event. When the type of content processing is “action item occurrence”, the content content includes the user ID of the person executing the action item, the due date for completing the action item, and the URL indicating the storage location of the image data indicating the action item including.

(Each functional configuration of the shared support server)
Next, each functional configuration of the shared support server 6 will be described in detail. In the following description, in describing each functional configuration of the shared support server 6, among the components illustrated in FIG. 5, the main components for realizing each functional configuration of the shared support server 6 are described. Explain the relationship.

  The transmission / reception unit 61 of the shared support server 6 shown in FIG. 8 is realized by a command from the CPU 601 shown in FIG. 5 and the network I / F 609 shown in FIG. Various types of data (or information) are exchanged with other terminals, devices or systems.

  The authentication unit 62 is realized by a command from the CPU 601 shown in FIG. 5, and information (user ID, organization ID, and password) sent from the communication terminal is registered in the user authentication management DB 6001 in advance. Authentication is performed by determining whether the information is present.

  The creation unit 63 is realized by a command from the CPU 601 shown in FIG. 5, and based on reservation information and schedule information sent from the schedule management server 8, as shown in FIG. A reservation list screen 230 is created.

  The generation unit 64 is realized by a command from the CPU 601 illustrated in FIG. 5, and generates an execution event ID, a content processing ID, and a storage destination URL.

  The determination unit 65 is realized by a command from the CPU 601 shown in FIG. 5 and makes various determinations. This determination will be described later.

  The storage / reading processing unit 69 is realized by an instruction from the CPU 601 shown in FIG. 5 and the HDD controller 605 shown in FIG. 5, and stores various data in the storage unit 6000 or in the storage unit 6000. A process of reading various stored data is performed.

<Functional configuration of the schedule management server>
The schedule management server 8 includes a transmission / reception unit 81, an authentication unit 82, a generation unit 83, and a storage / read processing unit 89. Each of these units functions or functions realized by any one of the constituent elements shown in FIG. 5 operating according to a command from the CPU 801 according to the schedule management program expanded from the HD 804 to the RAM 803. Means. Further, the schedule management server 8 includes a storage unit 8000 constructed by the HD 804 shown in FIG.

(User authentication management table)
FIG. 11A is a conceptual diagram showing a user authentication management table. In the storage unit 8000, a user authentication management DB 8001 configured by a user authentication management table as shown in FIG. In this user authentication management table, a user ID for identifying a user is managed in association with an organization ID and a password for identifying the organization to which the user belongs.

(User management table)
FIG. 11B is a conceptual diagram showing a user management table. In the storage unit 8000, a user management DB 8002 configured by a user management table as shown in FIG. In this user management table, for each organization ID, a user ID and a user name (user name) indicated by the user ID are associated and managed.

(Union management table)
FIG. 11C is a conceptual diagram showing a union management table. In the storage unit 8000, a union management DB 8003 configured by a union management table as shown in FIG. In this union management table, a union ID for identifying a union and a union name (union name) are managed in association with each organization ID.

(Union reservation management table)
FIG. 12A is a conceptual diagram showing a union reservation management table. In the storage unit 8000, a union reservation management DB 8004 configured by a union reservation management table as shown in FIG. In this union reservation management table, reservation information in a state where each information is associated is managed. The reservation information includes, for each organization ID, a union ID, a union name, a user ID of the reservation person, a scheduled use start date and time, a scheduled use end date and event name. Among these, the scheduled use start date / time indicates the scheduled use start date / time of the union. The scheduled use end date / time indicates the scheduled use end date / time of the union. Each date and time indicates year, month, date, hour, minute, second, and time zone, but in FIG. 12A, the year, month, day, hour, and minute are shown due to space limitations.

(Event management table)
FIG. 12B is a conceptual diagram showing an event management table. In the storage unit 8000, an event management DB 8005 configured by an event management table as shown in FIG. In this event management table, schedule information in a state where each information is associated is managed. In the schedule information, for each organization ID, a user ID, a user name, an event start scheduled date and time, an event end scheduled date and time, and an event name are associated and managed. Among these, the scheduled event start date and time indicates the scheduled start date and time when the event is executed. The scheduled event end date and time indicates the scheduled end date and time when the event is executed. Each date and time indicates year, month, date, hour, minute, second, and time zone, but in FIG. 12B, the year, month, day, hour, and minute are shown due to space limitations. In the event management table, the file data of the material file used in the event indicated in the schedule information is managed in association with the scheduled event ID.

(Server authentication management table)
FIG. 13A is a conceptual diagram showing a server authentication management table. In the storage unit 8000, a server authentication management DB 8006 configured by a server authentication management table as shown in FIG. In this server authentication management table, an access ID and an access password are managed in association with each other. The access ID and access password have the same concept as the access ID and access password managed by the access management DB 6002 of the sharing support server 6.

(Project member management table)
FIG. 13B is a conceptual diagram showing a project member management table. In the storage unit 8000, a project member management DB 8007 configured by a project member management table as shown in FIG. In this project member management table, a project ID, a project name, and a user ID of each project member are managed in association with each organization ID. Further, the project member management table is registered by the user by a project registration process shown in FIG.

(Execution event history management table)
FIG. 14A is a conceptual diagram showing an execution event history management table. In the storage unit 8000, an execution event history management DB 8008 configured by an execution event history management table as shown in FIG. In this execution event history management table, the content processing ID, the type of content processing, the content content, and the start date / time and end date / time of content processing are managed in association with each other for each project ID and execution event ID. This execution event history management DB 8008 manages the same data as the content management DB 6005. The same data includes an execution event ID, content processing ID, content processing type, content processing start date and time, and end date and time. The contents are stored in the same storage location except for the content data storage destination notation method (http: // or c: //).

(Execution event management table)
FIG. 14B is a conceptual diagram showing an execution event management table. In the storage unit 8000, an execution event management DB 8009 configured by an execution event management table as shown in FIG. In this execution event management table, for each execution event ID, an event name, an event start date and time, and an end date and time are associated and managed. The execution event management DB 8009 manages information related to an actually executed event among schedule information managed in the event management DB 8005.

(Related information management table)
FIG. 15 is a conceptual diagram showing a related information management table. In the storage unit 8000, a related information management DB 8010 configured by a related information management table as shown in FIG. In this related information management table, related information in a state where each piece of information (data) is associated is managed for each project ID and execution event ID. The related information is managed in association with the content generation time zone, sound data, voice text data, and screen data. The content occurrence time zone indicates an elapsed time from the start date and time of the event when the content is generated in the executed event. The content generation time zone is an example of time information. The sound data includes a content processing ID and a content type. The audio text data and the screen data include a content processing ID, a content type, and a sequence number. Sequence No. indicates the order in which the content processing occurred for each of the audio text data and the screen data.

(Each functional configuration of the schedule management server)
Next, each functional configuration of the schedule management server 8 will be described in detail. In the following description, in describing each functional configuration of the schedule management server 8, among the components illustrated in FIG. 5, the main components for realizing the functional configurations of the schedule management server 8 are described. Explain the relationship.

  The transmission / reception unit 81 of the schedule management server 8 shown in FIG. 6 is realized by a command from the CPU 801 shown in FIG. 5 and the network I / F 809 shown in FIG. Various types of data (or information) are transmitted to and received from other terminals, devices, or systems.

  The authentication unit 82 is realized by a command from the CPU 801 shown in FIG. 5, and information (user ID, organization ID, and password) sent from the union is registered in the user authentication management DB 8001 in advance. Authentication is performed by determining whether the information is present. The authentication unit 82 performs authentication by determining whether the information (access ID and access password) sent from the sharing support server 6 is information registered in advance in the server authentication management DB 8006.

  The generation unit 83 is a function that is realized by a command from the CPU 801 illustrated in FIG. 5 and generates related information registered in the related information management DB 8010.

  The storage / reading processing unit 89 is realized by the instruction from the CPU 801 shown in FIG. 5 and the HDD controller 805 shown in FIG. 5, and stores various data in the storage unit 8000 or the storage unit 8000. A process of reading various stored data is performed.

<Functional configuration of the voice-to-text conversion server>
The voice text conversion server 9 includes a transmission / reception unit 91, a conversion unit 93, and a storage / reading processing unit 99. Each of these units is a function or means that functions when any of the components shown in FIG. 5 is operated by an instruction from the CPU 901 according to a program expanded from the HD 904 to the RAM 903. . The voice text conversion server 9 has a storage unit 9000 constructed by the HD 904 shown in FIG.

(Functional configuration of the voice-to-text conversion server)
Next, each functional configuration of the voice text conversion server 9 will be described in detail. In the following description, in describing each functional configuration of the voice text conversion server 9, main components for realizing the functional configurations of the voice text conversion server 9 among the components shown in FIG. The relationship is also explained.

  6 is realized by a command from the CPU 901 shown in FIG. 5 and the network I / F 909 shown in FIG. Various data (or information) is transmitted / received to / from other terminals, devices, or systems.

  The conversion unit 93 is realized by a command from the CPU 901 shown in FIG. 5, and converts sound data received by the transmission / reception unit 91 via the communication network 10 into text data.

  The storage / reading processing unit 99 is realized by an instruction from the CPU 901 shown in FIG. 5 and the HDD controller 905 shown in FIG. 5, and stores various data in the storage unit 9000 or in the storage unit 9000. A process of reading various stored data is performed.

  Each ID is an example of identification information. The organization ID includes a company name, business office name, department name, area name, and the like. The user ID includes an employee number, a driver's license number, and my number in the Japanese social security / tax number system.

<< Processing or Operation of Embodiment >>
Hereinafter, processing or operation of each embodiment will be described.

<Project registration process>
First, a process of registering a project from the PC 5 to the schedule management server 8 by the user A (Taro Riko) will be described with reference to FIGS. FIG. 16 is a sequence diagram showing a project registration process. FIG. 17 is a diagram showing a sign-in screen. FIG. 18 is an example of the initial screen of the PC. FIG. 19 is a diagram showing a project registration screen.

  First, when the user A operates the keyboard 511 and the like of the PC 5, the display control unit 54 of the PC 5 displays a sign-in screen 530 for signing in on the display 508 as shown in FIG. It is displayed (step S201). The sign-in screen 530 includes an input field 531 for inputting the user ID and organization ID of the user, an input field 532 for inputting a password, a sign-in button 538 that is pressed when signing in, and canceling sign-in. A cancel button 539 that is pressed in the case of performing is included. Here, the user ID and the organization ID are the email address of the user A. The user name portion of the e-mail address is a user ID, and the domain name portion is an organization ID. Note that the input field 551 may be an input field for separately inputting the user ID and the organization ID instead of the e-mail address.

  Next, when the user A inputs his / her user ID and organization ID in the input field 531, inputs his / her password in the input field 532, and presses the sign-in button 538, the reception unit 52 performs sign-in. Is received (step S202). Then, the transmission / reception unit 51 of the PC 5 transmits sign-in request information indicating a sign-in request to the schedule management server 8 (step S203). The sign-in request information includes the information (user ID, organization ID, and password) received in step S202. Thereby, the transmission / reception unit 81 of the schedule management server 8 receives the sign-in request information.

  Next, the authentication unit 82 of the schedule management server 8 authenticates the user A using the user ID, organization ID, and password (step S204). Specifically, the storage / reading processing unit 89 uses the user ID corresponding to the combination of the user ID, organization ID, and password received in step S203 in the user authentication management DB 8001 (see FIG. 11A). Search for a set of organization ID and password. If there is a corresponding pair, the authentication unit 82 determines that the requesting user A is a valid user. If there is no corresponding pair, the authentication unit 82 determines that the user A is an unauthorized (invalid) user. If it is not valid, the transmission / reception unit 81 notifies the PC 5 that it is not valid. Here, the description of the case where it is valid will be continued.

  Next, the transmission / reception unit 81 transmits the authentication result to the PC 5 (step S205). Thereby, the transmission / reception unit 51 of the PC 5 receives the authentication result.

  Next, when the authentication result is received in step 205, the generating unit 56 of the PC 5 generates an initial screen 540 as shown in FIG. 18 (step S206). Then, the display control unit 54 of the PC 5 displays an initial screen 540 as shown in FIG. 18 on the display 508 (step S207). The initial screen 540 includes a “schedule registration” button 541 for registering a schedule, a “project registration” button 542 for registering projects and project members, and an “action item browsing” button 542 for browsing action items. It is included. Here, when the user presses the “project registration” button 542, the receiving unit 52 receives the project registration (step S208). Then, the transmission / reception unit 51 transmits the project registration request information to the schedule management server 8 (step S209). Thereby, the transmission / reception unit 81 of the schedule management server 8 receives the project registration request information.

  Next, the storage / reading processing unit 89 of the schedule management server 8 searches the user management DB 8002 (see FIG. 11B) using the organization ID received in step S203 as a search key, and thereby performs all the corresponding operations. The user ID and all user names are read out (step S210). Then, the transmission / reception unit 81 transmits the project registration screen information to the PC 5 (step S211). This project registration screen information includes all user IDs and all user names read in step S210. All user names include the name (name) of the reservation person who is the user A who has made the input for sign-in in step S202. Thereby, the transmission / reception unit 51 of the PC 5 receives the project registration screen information.

  Next, when the project registration screen information is received in step 211, the generation unit 56 of the PC 5 generates a project registration screen 520 as shown in FIG. 19 (step S212). In the PC 5, the display control unit 24 displays a project registration screen 520 as shown in FIG. 19 on the display 508 (step S213). The project registration screen 520 includes an input field 521 for inputting a project name, a selection menu 523 for selecting a manager name of the project, a display area 525 for displaying the manager name, and other than the manager A selection menu 527 for selecting the user name of the member, an “OK” button 528 to be pressed when registering a project, and a “CANCEL” button 529 for canceling the input or the input content. include. A mouse pointer p2 is also displayed. As the administrator name, a user different from the user who has made an input for signing in to the PC 5 in step S202 may be selected.

  Next, the user A inputs the project name in the input field 521, and selects the name of the user (user name) to be registered with the project member from the selection menu 523 and the selection menu 527 using the pointer p2. When the “OK” button 528 is pressed, the accepting unit 52 accepts input of project information (step S214). And the transmission / reception part 51 transmits project information with respect to the schedule management server 8 (step S215). This project information includes a project name, a manager user ID, and a user ID of each member. In the project registration screen 520, the user name is selected from the selection menus 523 and 527, but since the user ID is also received in step S210, the user ID corresponding to the user name is transmitted. Thereby, the transmission / reception unit 81 of the schedule management server 8 receives the project information.

  Next, the storage / read processing unit 89 of the schedule management server 8 stores the project information received in step S213 in the project member management DB 8007 (see FIG. 13B) (step S216). In this case, the storage / read processing unit 89 adds project information for one record to the project member management table of the project member management DB 8007.

  As described above, when the receiving unit 52 of the PC 5 receives an input to the project registration screen 520 displayed on the display 508 by the display control unit 54, the user A assigns the project and members belonging to the project to the schedule management server 8. Can be newly registered. In addition, when the reception unit 52 of the PC 5 receives an input to the project registration screen 520 displayed on the display 508 by the display control unit 54, the user A registers in the project that has already been registered in the schedule management server 8. Members can also be changed.

<Schedule registration process>
Here, a process in which the reservation person A (Taro Riko) registers his / her schedule from the PC 5 to the schedule management server 8 will be described with reference to FIGS. FIG. 20 is a sequence diagram showing a schedule registration process. FIG. 21 is a diagram showing a schedule input screen. Note that the processing in steps S11 to S16 shown in FIG. 20 is the same as the processing in steps S201 to S206 shown in FIG.

  In step S <b> 17, when the authentication result is received by the transmission / reception unit 51, the display control unit 54 of the PC 5 displays an initial screen 540 as shown in FIG. 18 on the display 508. Here, when the user presses the “schedule registration” button 541, the reception unit 52 receives the schedule registration (step S18). Then, the transmitting / receiving unit 51 transmits a schedule registration request to the schedule management server 8 (step S19). Thereby, the transmission / reception unit 81 of the schedule management server 8 receives the schedule registration request.

  Next, the storage / reading processing unit 89 of the schedule management server 8 searches the user management DB 8002 (see FIG. 11B) using the organization ID received in step S13 as a search key, and thereby performs all the corresponding operations. The user ID and all user names are read out (step S20). And the transmission / reception part 81 transmits schedule input screen information with respect to PC5 (step S21). This schedule input screen information includes all user IDs and all user names read in step S19. All user names include the name (name) of the reservation person who is the user A who has made the input for sign-in in step S12. Thereby, the transmission / reception unit 51 of the PC 5 receives the schedule input screen information.

  Next, in PC5, the production | generation part 56 produces | generates the schedule input screen 550 using the schedule input screen information received by step S21. (Step S22). Then, the display control unit 24 of the PC 5 causes the display control unit 24 of the PC 5 to display the schedule input screen 550 as shown in FIG. 21 on the display 508 (step S23).

  In this schedule input screen 550, an input field 551 for inputting an event name, an input field 552 for inputting a union ID or a union name, and an event execution (union use) scheduled start date and time are input. Input field 553 for inputting, an input field 554 for inputting the scheduled date and time of event execution (use of union), an input field 555 for inputting a note such as an agenda, and a display area for displaying the name of the reservation person 556, a selection menu 557 for selecting a participant name of a participant other than the reservation person, an “OK” button 558 to be pressed when registering a reservation, and canceling the content being input or input A “CANCEL” button 559 for uploading the file data of the material file used for the event to the shared support server 6 Which includes loading "button 545. The name of the reservation person is the name of the user who made an input for signing in to the PC 5 in step S12. A mouse pointer p1 is also displayed.

  In the input field 552, an e-mail address may be input. When a union name is selected on the selection menu 557, the union is also added as another participant.

  Next, the user A inputs predetermined items in the input fields 551 to 555, selects the name (user name) of the user who wants to participate in the event from the selection menu 557 using the mouse pointer p1, When the “OK” button 558 is pressed, the accepting unit 52 accepts input of schedule information (step S24).

  And the transmission / reception part 51 transmits schedule information with respect to the schedule management server 8 (step S25). This schedule information includes event name, union ID (or union name), scheduled start date and time, scheduled end date and time, user ID of each participant, memo and file data. In the schedule input screen 550, when the union ID is input to the input field 552, the union ID is transmitted, and when the union name is input to the input field 552, the union name is transmitted. Is sent. In the schedule input screen 550, the user name is selected from the selection menu 557, but since the user ID is also received in step S21, the user ID corresponding to the user name is transmitted. Thereby, the transmission / reception unit 81 of the schedule management server 8 receives the schedule information.

  Next, the schedule management server 8 searches the union management DB 8003 (see FIG. 13C) using the union ID (or union name) received in step S25 as a search key, thereby corresponding union. A name (or union ID) is read (step S26).

  Next, the storage / reading processing unit 89 stores the reservation information in the union reservation management DB 8004 (see FIG. 12A) (step S27). In this case, the storage / read processing unit 89 adds reservation information for one record to the union reservation management table of the union reservation management DB 8004 managed by the scheduler registered in advance. 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. Note that the scheduled use start date and time in the union reservation management DB 8004 corresponds to the scheduled start date and time in the schedule information. The scheduled use end date / time in the union reservation management DB 8004 corresponds to the scheduled end date / time in the schedule information.

  Further, the storage / read processing unit 89 stores the schedule information in the event management DB 8005 (see FIG. 12B) (step S28). In this case, the storage / read processing unit 89 adds schedule information for one record to the event management table of the event management DB 8005 managed by a scheduler registered in advance. The schedule information is configured based on the schedule information received in step S25. Note that the scheduled event start date and time in the event management DB 8005 corresponds to the scheduled start date and time in the schedule information. The scheduled event end date / time in the event management DB 8005 corresponds to the scheduled end date / time in the schedule information.

  As described above, the user A can register his / her schedule in the schedule management server 8.

<Event start processing>
Here, with reference to FIG. 22 to FIG. 28, a process of having a meeting with other participants using the electronic blackboard 2 in the conference room X reserved by the reservation person A (Taro Riko) will be described. 22 and 25 are sequence diagrams showing event start processing. FIG. 23 is a diagram showing a sign-in screen displayed on the electronic blackboard. FIG. 24 is a diagram showing a union reservation list screen. FIG. 26 is a diagram showing a project list screen. FIG. 27 shows a detailed event information screen. FIG. 28 is an image diagram showing a state in which the user uses the electronic blackboard.

  First, when the user A presses the power switch 222 of the electronic blackboard 2, the receiving unit 22 of the electronic blackboard 2 receives power ON from the user (step S31). The launcher 102 shown in FIG. 6 is activated by accepting the power ON by the accepting unit 22. Then, as shown in FIG. 23, the display control unit 24 of the electronic blackboard 2 displays a sign-in screen 110 for signing in on the display 220 (step S32). In this sign-in screen 110, the user A signs in by inputting his / her e-mail address and password, and a selection icon 111 that is pressed when the user A signs in using his / her IC card. A selection icon 113 that is pressed when performing power supply and a power supply icon 115 that is pressed when powering off without performing sign-in are included.

  Next, the user A presses the selection icon 111 to perform communication with the short-range communication circuit 219 such as an IC card reader, or the user A presses the selection icon 113 and the user A By receiving the user's own e-mail address and password, the accepting unit 22 accepts a sign-in request (step S33). Then, the transmitting / receiving unit 21 transmits sign-in request information indicating a sign-in request to the sharing support server 6 (step S34). This sign-in request information includes the time zone information of the country or region where the electronic blackboard 2 is installed, the user ID and organization ID of the communication terminal (here, the electronic blackboard 2), and the password. Thereby, the transmission / reception unit 61 of the shared support server 6 receives the sign-in request information.

  Next, the authentication unit 62 of the shared support server 6 authenticates the user A using the user ID, organization ID, and password (step S35). Specifically, the storage / reading processing unit 69 uses the user ID, organization ID, and password received in step S35 as search keys to receive the above-mentioned data in the user authentication management DB 6001 (see FIG. 9A). A set of user ID, organization ID and password corresponding to the set of user ID, organization ID and password is searched. If there is a corresponding pair, the authentication unit 62 determines that the requesting user A is a valid user. If there is no corresponding pair, the authentication unit 62 determines that the requesting user A is an unauthorized (invalid) user. If it is not valid, the transmission / reception unit 61 notifies the electronic blackboard 2 that it is not valid. Here, the case where it is valid will be described.

  Next, the storage / reading processing unit 69 of the shared support server 6 searches the access management DB 6002 (see FIG. 9B) using the organization ID received in step S34 as a search key, so that the corresponding access ID and The access password is read (step S36).

  Next, the transmission / reception unit 61 transmits reservation request information indicating a request for union reservation information and schedule request information indicating a request for user schedule information to the schedule management server 8 (step S37). The reservation request information and the schedule request information include the time zone information, the communication terminal user ID and organization ID received in step S34, and the access ID and password read in step S36. Thereby, the transmission / reception unit 81 of the schedule management server 8 receives the reservation request information and the schedule request information.

  Next, the authentication unit 82 of the schedule management server 8 authenticates the sharing support server 6 using the access ID and the access password (step S38). Specifically, the storage / read processing unit 89 uses the access ID and access password pair corresponding to the access ID and access password pair received in step S37 in the server authentication management DB 8006 (see FIG. 13A). Search for. If there is a corresponding pair, the authentication unit 82 determines that the sharing support server 6 that is the request source is a valid accessor. If there is no corresponding pair, the authentication unit 82 determines that the sharing support server 6 as the request source is an unauthorized (invalid) accessor. If it is not valid, the transmission / reception unit 81 notifies the sharing support server 6 that it is not valid. Here, the description of the case where it is valid will be continued.

  The storage / read processing unit 89 of the schedule management server 8 uses the user ID of the communication terminal received in step S37 as a search key, and the union reservation management DB 8004 (FIG. The corresponding reservation information is read by searching (see A)) (step S39). In this case, the storage / reading processing unit 89 reads the reservation information whose scheduled use start date is today.

  Further, the storage / reading processing unit 89 searches for the specified event management DB 8005 (see FIG. 12B) using the communication terminal user ID received in step S37 as a search key, thereby responding. The schedule information to be read is read (step S40). In this case, the storage / reading processing unit 89 reads schedule information whose event start scheduled date and time is today. When the schedule management server 8 is in a country or region other than the communication terminal such as the electronic blackboard 2, the time zone is combined with the country or region where the communication terminal is installed based on the time zone information. It is adjusted.

  Next, the storage / read processing unit 89 uses the communication terminal by searching the project member management DB 8007 (see FIG. 13B) using the communication terminal user ID received in step S37 as a search key. The project IDs and project names of all projects including the manager ID are read (step S41).

  Next, the transmission / reception unit 81 sends the reservation information read in step S39, the schedule information read in step S40, and all project IDs and all projects read in step S41 to the shared support server 6. The name is transmitted (step S42). Thereby, the transmission / reception unit 61 of the shared support server 6 receives the reservation information, schedule information, all project IDs, and all project names.

  Next, the creation unit 63 of the shared support server 6 creates a reservation list based on the reservation information and schedule information received in step S42 (step S43). Then, the transmission / reception unit 61 transmits reservation list information indicating the contents of the reservation list, all project IDs, and all project names to the electronic blackboard 2 (step S44). Thereby, the transmission / reception unit 21 of the electronic blackboard 2 receives the reservation list information, all project IDs, and all project names.

  Next, in the electronic blackboard 2, the display control unit 24 displays a reservation list screen 230 as shown in FIG. 24 on the display 220 (step S45). The reservation list screen 230 includes a display area 231 for displaying a union name (here, a place name), and a display area 232 for displaying the date and time of today. Furthermore, on the reservation list screen 230, event information 235, 236, 237 and the like indicating events that use today's union (here, the conference room X) are displayed. Each event information includes, for each event, the scheduled use start time and scheduled use end time of the union, the event name, and the name of the reservation person (reservation person name) who reserved the union. The event information includes start buttons 235s, 236s, 237s, and the like that are pressed when the user specifies an event to be started.

  Next, in FIG. 23, when the user A presses the start button 235s with the electronic pen 2500 or the like, for example, the reception unit 22 receives the selection of the event indicated by the event information 235 (step S51). Then, the display control unit 24 displays the project list screen 240 as shown in FIG. 24 on the display 220 based on the project ID and project name received in step S42 (step S52). The project list screen 240 includes project icons 241 to 246 indicating the respective projects. In addition, the project list screen 240 includes an “OK” button 248 to be pressed when confirming the selected project icon, and a “CANCEL” button 249 to cancel the selection of the project icon.

  Next, in FIG. 24, when the user A presses the project icon 241 with the electronic pen 2500 or the like, for example, the accepting unit 22 accepts the selection of the project indicated by the project icon 241 (step S53).

  Next, the transmitting / receiving unit 21 of the electronic blackboard 2 transmits to the shared support server 6 the scheduled event ID indicating the scheduled event selected in step S51 and the project ID indicating the project selected in step S53. (Step S54). The process of step S54 is an execution event identification information transmission request process. Thereby, the transmission / reception unit 61 of the shared support server 6 receives the selected scheduled event ID and the selected project ID.

  Next, in the shared support server 6, the generation unit 64 generates a unique execution event ID (step S55). Then, the storage / reading processing unit 69 manages the execution event ID generated in step S55, the reservation event ID received in step S54, the user ID and organization ID of the reservation person, and event information in association with each other (step). S56). The user ID and organization ID of the reservation person and the event information are ID and information based on the reservation information and schedule information received in step S42. At this time, there is no entry in the participation presence / absence column in the reservation management table (see FIG. 7C).

  Next, the storage / reading processing unit 69 manages the project ID received in step S54 in association with the execution event ID generated in step S55 (step S57).

  Next, in the sharing support server 6, the transmission / reception unit 61 transmits file data transmission request information indicating a file data transmission request registered in the schedule management server 8 to the schedule management server 8 (step S58). The file data transmission request information includes the event ID received in step S54, the user ID and organization ID of the communication terminal received in step S34, and the access ID and access password read in step S36. Yes. Thereby, the transmission / reception unit 81 of the schedule management server 8 receives the file data transmission request information.

  Next, the storage / read processing unit 89 of the schedule management server 8 searches the event management DB 8005 (see FIG. 12B) using the event ID received in step S58 as a search key, thereby associating with the event ID. Read the file data (step S59). Then, the transmission / reception unit 81 transmits the file data read in step S59 to the sharing support server 6 (step S60). Thereby, the transmission / reception unit 61 of the shared support server 6 receives the file data.

  Next, the storage / reading processing unit 69 of the shared support server 6 associates the file data received in step S54 with the scheduled event ID received in step S60 and the execution event ID generated in step S55. It is stored and managed in the schedule management DB 6003 (step S61).

  Then, the transmission / reception unit 61 transmits the execution event ID generated in step S55 and the file data received in step S60 to the electronic blackboard 2 (step S62). Thereby, the transmission / reception unit 21 of the electronic blackboard 2 receives the execution event ID and the file data.

  Next, in the electronic blackboard 2, the storage / reading processing unit 29 stores the execution event ID and file data in the storage unit 2000 (step S63). Here, the file data transmitted from the shared support server 6 is stored in a specific storage area of the storage unit 2000. Therefore, the electronic blackboard 2 causes the display 220 to display the file data stored in the specific storage area on the display 220 by accessing the specific storage area during the execution of the event. Here, the specific storage area is a temporary storage destination of data provided for each event being executed, and is a storage area specified by an arbitrary path (character string) indicating the location in the storage unit 2000 It is. The specific storage area is not limited to the configuration provided in the electronic blackboard 2, but may be an external storage device connected to the electronic blackboard 2 or a local server that exists in the on-premises environment and can communicate with the electronic blackboard 2. The structure provided may be sufficient.

  Next, the display control unit 24 causes the detailed information screen 250 for the selected event to be displayed on the display 220 as shown in FIG. 27 (step S64). The event detailed information screen 250 includes an event name display area 251, an event execution scheduled time (scheduled start time and scheduled end time) display area 252, and a reservation person name display area 253. Further, the event detail information screen 250 includes a display area 256 for displaying the contents of the memo, a display area 257 for displaying the names of prospective participants, and files stored in a specific storage area of the storage unit 2000. A display area 258 for displaying identification information (for example, a file name) for identifying data is displayed. In the display area 257, the name of the reservation person shown in FIG. 21 and the names of other selected participants are displayed, and the names of the prospective participants are for checking who is actually participating in the conference. The check box is displayed. The display area 258 displays the file data stored in a specific storage area of the storage unit 2000, that is, the file name of the file data downloaded from the shared support server 6, and downloaded from the shared support server 6. The file name of the file data inside is also displayed. Further, a “Close” button 259 for closing the screen 250 is included in the lower right side of the event detail information screen 250.

  Next, when the user checks the check box of the user who actually participates in the names of prospective participants and presses the “Close” button 259, the reception unit 22 receives the selection of the participant. (Step S65). And the transmission / reception part 21 transmits the information which shows the user ID of each prospective participant, and the presence or absence of participation with respect to the sharing assistance server 6 (step S66). Thereby, the transmission / reception part 61 of the sharing support server 6 receives the user ID of each prospective participant and information indicating the presence / absence of participation.

  Next, the sharing support server 6 stores and manages the presence / absence of participation in the participation presence / absence column that has not been input in the schedule management DB 6003 (step S67).

  As described above, the user A uses the union (here, the conference room X) and the communication terminal (here, the electronic blackboard 2) to start the event (here, the policy decision meeting). Then, as shown in FIG. 28, the user A can hold a conference in the conference room X using the electronic blackboard 2. The display control unit 24 displays the remaining time in which the union can be used in the upper right area of the display 220. In this case, the display control unit 24 displays the time (remaining time) from the current time to the scheduled end time indicated by the event information selected in step S51.

  In addition, the display control unit 24 displays the icon r1 that is pressed when registering an action item, the icon r2 that is pressed when browsing the execution event history, and the material file stored in a specific storage area of the storage unit 2000. An icon r3 to be pressed when browsing and file data r4 of the material file are displayed. The icon r3 is an example of a selection image that receives a selection for displaying file data stored in a specific storage area. For example, when the user of the electronic blackboard 2 presses the icon r3, the reception unit 22 receives the selection of the icon r3, and the display control unit 24 stores the file of the material file stored in a specific storage area of the storage unit 2000. Data r4 is displayed. Note that the display control unit 24 of the electronic blackboard 2 not only receives the file data received in step S62, but also file data stored in advance in the storage unit 2000 or file data newly generated in the event that has been started. It may be displayed. In this case, the storage / reading processing unit 29 of the electronic blackboard 2 stores the file data generated or updated in the started event in a specific storage area of the storage unit 2000.

<Registration process of execution event history>
Subsequently, the execution event history registration process will be described with reference to FIGS. 29 to 35. 29 and 31 are sequence diagrams showing execution event history registration processing. FIG. 30 is a flowchart showing the speech text conversion process.

  First, the determination unit 25 of the electronic blackboard 2 determines the type of content processing in the started event (step S71). Specifically, when the content is sound data generated by recording by the image / sound processing unit 23, the determination unit 25 determines that the type of processing of the content is “recording”. When the content is image data acquired by snapshot (capture) by the image / sound processing unit 23, the determination unit 25 determines that the content processing type is “snapshot”. If the content is the document file data transmitted by the transmission / reception unit 21, the determination unit 25 determines that the type of content processing is “material transmission”.

  Next, the transmission / reception unit 21 transmits registration request information indicating a registration request for the generated content to the sharing support server 6 (step S72). In this case, the transmission / reception unit 21 automatically transmits registration request information every time content is generated. This registration request information includes an execution event ID, a content transmission source user ID, content data, content processing type information, and content processing (recording, snapshot, transmission) start date and time and end date and time. Yes. Thereby, the transmission / reception unit 61 of the shared support server 6 receives the registration request information.

  Next, the determination unit 65 of the shared support server 6 determines the type of content processing received based on the type information included in the registration request information received by the transmission / reception unit 61 (step S73). When the determination unit 65 determines that the type of content processing is “recording”, the transmission / reception unit 61 of the shared support server 6 transmits sound data, which is content data, to the voice-to-text conversion server 9 (step) S74). Thereby, the transmission / reception part 91 of the audio | voice text conversion server 9 receives sound data. If the type of content processing is other than “recording”, the sharing support server 6 proceeds to the processing of step S77 without performing the processing of steps S74 to S76.

  Next, the conversion unit 93 of the voice text conversion server 9 converts the sound data received by the transmission / reception unit 91 into text data (step S75). Here, the voice text conversion processing in the voice text conversion server 9 will be described with reference to FIG. First, the conversion unit 93 acquires information indicating the date and time when the sound data was received by the transmission / reception unit 91 (step S75-1). In addition, the information acquired by step S75-1 may be information indicating the date and time when the shared support server 6 receives the sound data or the date and time when the shared support server 6 transmits the sound data. In this case, the transmission / reception unit 91 of the voice text conversion server 9 receives the sound data transmitted from the shared support server 6 and the information indicating the date and time in step S74.

  Next, the conversion part 93 performs the text conversion process of the sound data received by the transmission / reception part 91 (step S75-2). And the conversion part 93 makes a process transfer to step S75-4, when the text conversion process of sound data is completed (YES of step S75-3). On the other hand, the conversion part 93 repeats the process of step S75-2 until the text conversion process of sound data is completed. And the conversion part 93 produces | generates the text data converted from the sound data (step S75-4). Thereby, the speech text conversion server 9 converts the sound data transmitted from the shared support server 6 into text data. The voice text conversion server 9 repeatedly executes the process shown in FIG. 30 every time it receives the sound data transmitted from the shared support server 6.

  Returning to FIG. 29, the description of the execution event history registration processing will be continued. The transmission / reception unit 91 transmits the text data converted by the conversion unit 93 to the shared support server 6 (step S76). Here, the transmission / reception part 91 transmits the information which shows the date acquired by step S75-1 to the shared assistance server 6 with text data. The transmission / reception unit 91 may transmit information indicating the date and time when the text data is generated by the conversion unit 93 to the shared support server 6 together with the text data. Thereby, the transmission / reception unit 61 of the shared support server 6 receives the text data.

  Next, the generation unit 64 generates a unique content processing ID for identifying the content processing generated by the event (step S77). Further, the generation unit 64 generates a URL of content data indicating the content content (step S78). Then, the storage / reading processing unit 69, for the content management DB 6005 (see FIG. 10B), for each execution event ID received in step S72, the content processing type, the content processing start date and time, and the end date and time. The content processing ID generated in step S77 and the URL indicating the storage destination of the content generated in step S78 are managed in association with each other (step S79). Here, when the type of content processing is “sound text reception”, the start date and time and end date and time of content processing are information indicating the date and time received in step S76. When the type of content processing is “audio text reception”, the start date and time and end date and time of content processing may be information indicating the date and time when the shared support server 6 received text data in step S76.

  Next, in FIG. 31, the storage / read processing unit 69 of the shared support server 6 searches the execution event management DB 6004 (see FIG. 10A) using the execution event ID received in step S72 as a search key. The corresponding project ID is read out (step S91). Next, the storage / reading processing unit 69 reads the corresponding organization ID by searching the user authentication management DB 6001 (see FIG. 9A) using the user ID of the content transmission source as a search key (step S100). S92).

  Next, the storage / read processing unit 69 reads the corresponding access ID and access password by searching the access management DB 6002 (see FIG. 9B) using the organization ID read in step S92 as a search key (step S92). S93).

  Next, the transmission / reception unit 61 transmits content registration request information indicating a content data registration request to the schedule management server 8 (step S94). The content registration request information includes the project ID read in step S91, the execution event ID received in step S72, the user ID of the transmission source, the content data, the start date and end date and time of content processing, and step S77. The content processing ID generated in step S78, the URL of the content data generated in step S78, the access ID read out in step S93, and the access password. Thereby, the transmission / reception unit 81 of the schedule management server 8 receives the content registration request information.

  Next, in the schedule management server 8, the authentication unit 82 authenticates the shared support server 6 using the access ID and the access password (step S95). Since this authentication is the same process as step S36, description thereof is omitted. Here, the description of the case where it is valid will be continued.

  Next, the storage / read processing unit 89 stores and manages various data (information) received in step S94 in the execution event history management DB 8008 (see FIG. 14A) (step S96). The storage / reading processing unit 89 stores various data (information) in the execution event history management DB 8008 in association with the project ID and execution event ID received in step S94. Thereby, the schedule management server 8 manages data having the same contents as those on the shared support server 6 side.

  Further, the generation unit 83 of the schedule management server 8 generates related information in which the content data received in step S94 is associated with each content generation time zone (step S97). Then, the storage / read processing unit 89 of the schedule management server 8 stores and manages the related information generated by the generating unit 83 in the related information management DB 8010 (step S98). As a result, the schedule management server 8 manages content data with different types of content processing in association with each content occurrence time.

  As described above, the electronic blackboard 2 can transmit the event ID of the event in the predetermined project and the content generated by executing the corresponding event to the schedule management server 8. Further, the schedule management server 8 can store the received content in the execution event history management DB 8008 for each event ID associated with the project ID. As a result, the shared system 1 can store the content generated by the event for each project by allowing the user to select which project the event belongs to at the start of the event.

(Action item registration process)
Here, processing when the generated content is an action item will be described with reference to FIGS. 32 to 35. FIG. 32 is a flowchart showing action item registration processing. FIG. 33 is an example of a screen for recognizing action items. FIG. 34 is a screen example showing a candidate list for executing an action item. FIG. 35 is an example of a screen showing a calendar for selecting an expiration date for an action item.

  First, in FIG. 28, when the user presses the icon r1, the accepting unit 22 accepts an action item registration request (step S71-1). Next, as shown in FIG. 33, the user draws an action item (here, “submit minutes”) on the drawing screen 260 a of the electronic blackboard 2 using the electronic pen 2500, and then the action When an image (drawn image) 261 showing the contents of an item is surrounded by a line (designated region) 262, the accepting unit 22 accepts designation of a predetermined region including the image 261, and the recognizing unit 26 is included in the predetermined region. Is recognized (step S71-2). Note that although FIG. 33 illustrates an example in which the image (drawn image) 261 is surrounded by a line (designated region) 262, the recognition unit 26 recognizes an area that is an arbitrary distance away from the designated region 262 as the image 261. It may be a configuration. The predetermined area is specified by drawing a predetermined shape such as a circle or a polygon with the electronic pen 2500, for example.

  Next, as shown in FIG. 34, the display control unit 24 displays the action item performer candidate list 265 on the drawing screen 260b (step S71-3). And if a user selects the specific performer who performs an action item using electronic pen 2500, reception part 22 will receive selection of a specific performer (Step S71-4).

  Next, as shown in FIG. 35, the display control unit 24 displays a calendar 267 for accepting designation of the execution deadline date of the action item on the drawing screen 260c (step S71-4). When the user selects a specific due date using the electronic pen 2500, the accepting unit 22 accepts the selection of the specific due date (step S71-5). The calendar 267 is an example of an expiration date designation screen. The deadline designation screen may be a date list or the like in which the day of the week is not described.

  Through such processing, the electronic blackboard 2 transmits content registration request information indicating an action item registration request to the shared support server 6 as a content registration request. This content registration request information includes an execution event ID indicating the event in which the action item has occurred, the user ID of the executor of the action item selected in step S71-4, and the action item recognized in step S71-2. The image data (here, the image data of “Submit minutes”) and the deadline for execution of the action item accepted in step 71-5 are included. That is, the transmission / reception unit 21 transmits the image data in the predetermined area as image data indicating the content of the action item generated by the event being executed. Thereby, the transmission / reception unit 61 of the shared support server 6 receives the content registration request information. The processing after the sharing support server 6 receives the content registration request information is the same as the processing shown in FIGS.

<Event end processing>
Next, processing for ending an event being executed will be described with reference to FIGS. 36 to 40. 36 and 37 are sequence diagrams showing event end processing. FIG. 38 is a diagram showing an event end screen on the electronic blackboard. FIG. 39 is a diagram showing a file data upload screen on the electronic blackboard. FIG. 40 shows a file data upload completion screen on the electronic blackboard.

  In FIG. 28, when the user closes the screen displayed on the display 220, the receiving unit 22 receives the end of the event being executed (step S301).

  Then, the transmitting / receiving unit 21 transmits execution event start / end information indicating the start date / time and end date / time of the execution event and file data registration request information indicating a file data registration request to the sharing support server 6 (step S1). S302). This execution event start / end information includes an execution event ID, an event name, an event start date and time, and an end date and time. The file data registration request information includes an execution event ID, a transmission source user ID, file data, and the start date and end date of content processing. Thereby, the transmission / reception unit 61 of the shared support server 6 receives the execution event start / end information and the file data registration request information.

  Next, the generation unit 64 of the sharing support server 6 generates a unique content processing ID for identifying the content processing generated by the event (step S303). Further, the generation unit 64 generates a URL of content data indicating the content content (step S304). Then, the storage / reading processing unit 69, for the content management DB 6005 (see FIG. 10B), for each execution event ID received in step S302, the type of content processing, the start date / time and end date / time of content processing. The content processing ID generated in step S303 and the URL indicating the storage destination of the content generated in step S304 are associated and managed (step 305).

  Next, the storage / reading processing unit 69 of the shared support server 6 searches the execution event management DB 6004 (see FIG. 10A) using the execution event ID received in step S72 as a search key, thereby corresponding project. The ID is read (step S306). Next, the storage / reading processing unit 69 reads the corresponding organization ID by searching the user authentication management DB 6001 (see FIG. 9A) using the user ID of the content transmission source as a search key (step S100). S307).

  Next, the storage / read processing unit 69 reads the corresponding access ID and access password by searching the access management DB 6002 (see FIG. 9B) using the organization ID read in step S92 as a search key (step S92). S308).

  Next, in FIG. 37, the transmission / reception unit 61 transmits the execution event start / end information received in step S302 and the file data registration request information indicating the file data registration request to the schedule management server 8 ( Step S309). The file data registration request information includes the project ID read in step S306, the execution event ID received in step S302, the user ID of the transmission source, file data, and the start date and end date and time of content processing, The content processing ID generated in step S303, the URL of the file data generated in step S304, the access ID and access password read in step S308 are included. Thereby, the transmission / reception unit 81 of the schedule management server 8 receives the execution event start / end information and the file data registration request information.

  Next, in the schedule management server 8, the authentication unit 82 authenticates the shared support server 6 using the access ID and the access password (step S310). Since this authentication is the same process as step S36, description thereof is omitted. Here, the description of the case where it is valid will be continued.

  Next, the storage / read processing unit 89 of the schedule management server 8 stores the execution event start / end information received in step 309 in the execution event management DB 8009 (see FIG. 14B) (step S311). . In this case, the storage / read processing unit 89 adds execution event start / end information for one record to the execution event management table of the execution event management DB 8009.

  Next, the storage / reading processing unit 89 stores and manages various data (information) received in step S309 in the execution event history management DB 8008 (step S312). The storage / reading processing unit 89 stores various data (information) including file data in the execution event history management DB 8008 (see FIG. 14A) in association with the project ID and execution event ID received in step S309. To do. Thereby, the schedule management server 8 manages the same file data as the sharing support server 6 side.

  Next, the transmission / reception unit 81 transmits file data registration information indicating that the file data has been registered to the sharing support server 6 (step S313). Thereby, the transmission / reception unit 61 of the shared support server 6 receives the file data registration information.

  Then, the transmission / reception unit 61 of the shared support server 6 transmits the file data registration information transmitted from the schedule management server 8 to the electronic blackboard 2 (step S314). Thereby, the transmission / reception unit 21 of the electronic blackboard 2 receives the file data registration information.

  Next, when the file data registration information is received by the transmission / reception unit 21, the storage / reading processing unit 29 of the electronic blackboard 2 deletes the file data stored in the specific storage area of the storage unit 2000 (step S315). . Thereby, the electronic blackboard 2 can reduce the risk of leakage of conference information and the like by deleting the file data that has been transmitted to the shared support server 6.

  Here, the screen transition of the screen displayed on the electronic blackboard 2 when the event being executed is terminated will be described. First, when the end of the event being executed by the receiving unit 22 is received in step S301, the display control unit 24 displays an event end screen 270 as shown in FIG. 38 on the display 508. . In the event end screen 270, a toolbar area 271, a file display area 272, a file upload selection area 273, a “Close” button 278 for proceeding with an end process of an event being executed, and an event end process being executed are cancelled. A “CANCEL” button 279 is included. In the tool bar area 271, images showing icons r1, r2, r3 as shown in FIG. 28 are displayed. In the file display area 272, file data images 272a, 272b, and 272c for identifying the file data of the material file stored in the specific storage area of the storage unit 2000 are displayed. The file upload selection area 273 includes a check box (an example of a selection area) that receives a selection as to whether or not the file data corresponding to the file data image displayed in the file display area 272 is to be uploaded to the sharing support server 6. It is. The event end screen 270 is an example of a selection screen.

  When the accepting unit 22 accepts selection of the “Close” button 278 with the file upload selection area 273 selected, the display control unit 24 displays a file upload screen 280a as shown in FIG. 39 on the display 220. Is displayed. The file upload screen 280 a is displayed on the display 220 when file data stored in a specific storage area of the storage unit 2000 is uploaded to the shared support server 6. The file upload screen 280a includes an event name 281 of an event to be ended, an event end date and time 282, a file data upload progress display area 283, and a “CANCEL” button 288 for interrupting (stopping) file data upload. Yes. In the upload progress display area 283, the number of file data to be uploaded (for example, “3” shown in FIG. 39) and the number of file data that has been uploaded (for example, “0” shown in FIG. 39). ) Is displayed.

  When the upload of the file data is completed, the display control unit 24 displays an upload completion screen 280b as shown in FIG. The upload completion screen 280b includes a “Close” button 288 that is pressed to end the event. When the upload completion screen 280b is displayed on the display 220, as shown in step S315, the storage / reading processing unit 29 of the electronic blackboard 2 stores the file data that has been uploaded in a specific storage area of the storage unit 2000. Delete from.

  On the other hand, in the state where the file upload screen 280a is displayed on the display 220, when the file data upload fails, the display control unit 24 specifies information for specifying the file data that failed to upload (for example, the file Name). Thereby, for example, when a failure or the like of the communication network 10 occurs, the event participant prints the file data created or edited by the event, or stores the file data in the USB memory 2600 connected to the electronic blackboard 2. By doing so, you can take home the file data that failed to upload.

  Further, when file data remains in a specific storage area of the storage unit 2000 even after the event ends, the storage / reading processing unit 29 of the electronic blackboard 2 starts, for example, the next event using the electronic blackboard 2. Sometimes file data stored in a specific storage area is deleted. Thereby, the electronic blackboard 2 can reduce the risk of leakage of conference information and the like.

<Execution event history browsing process>
Next, the execution event history browsing process will be described with reference to FIGS. 41 to 47. FIG. 41 and FIG. 42 are sequence diagrams showing execution event history browsing processing. FIG. 43 is a diagram showing a project list screen on a PC. FIG. 44 is a diagram showing an execution event list screen on the PC. 45 and 46 are diagrams showing execution event history screens. FIG. 47 is a diagram showing an action item screen on the PC. Note that the processing in steps S111 to S117 in FIG. 41 is the same as the processing in steps S201 to S207 in FIG.

  When the user presses the “View Execution Event History” button 543 on the initial screen 540 shown in FIG. 18, the accepting unit 52 accepts the viewing of the execution event history (Step S118).

  Then, the transmission / reception unit 51 transmits execution event history browsing request information indicating an execution event history browsing request to the schedule management server 8 (step S119). Thereby, the transmission / reception unit 81 of the schedule management server 8 receives the execution event history browsing request information.

  Next, the storage / reading processing unit 89 of the schedule management server 8 searches the project member management DB 8007 using the user ID and organization ID received in step S113 as search keys, thereby obtaining the corresponding project ID and project name. Read (step S120). Then, the transmission / reception unit 81 transmits the project ID and the project name to the PC 5 (step S121).

  Next, the generation unit 56 of the PC 5 generates a project list screen 560 as shown in FIG. 41 using the project ID and project name received in step S121 (step S122). In the PC 5, the display control unit 54 displays the project list screen 560 generated by the generation unit 56 on the display 508 (step S123). The project list screen 560 shows the same contents as the project list screen 240 displayed on the electronic blackboard 2, as shown in FIG. That is, the project icons 561 to 566 and the buttons 568 and 569 in FIG. 43 correspond to the project icons 241 to 246 and the buttons 248 and 249 in FIG. 26, respectively.

  Next, in FIG. 42, when the user A presses the project icon 561 with, for example, the mouse 512, the reception unit 52 receives the selection of the project indicated by the project icon 561 (step S124).

  Next, the transmission / reception unit 51 of the PC 5 transmits the project ID of the project selected in step S123 to the schedule management server 8 (step S125). Thereby, the schedule management server 8 receives the project ID.

  Next, in the schedule management server 8, the storage / read processing unit 89 reads the corresponding execution event ID by searching the execution event history management DB 8008 using the project ID received in step S125 as a search key (step S126). ). In this case, the storage / read processing unit 89 reads all execution event IDs associated with the project ID received in step S125. Then, the storage / read processing unit 89 reads the corresponding execution event start / end information by searching the execution event management DB 8009 using the execution event ID read in step S126 as a search key (step S127). This execution event start / end information includes an execution event ID, an event name, a start date / time, and an end date / time.

  Then, the transmission / reception unit 81 transmits the execution event ID, the event name, the start date / time, and the end date / time read in step S127 to the PC 5 (step S128). Thereby, the transmission / reception unit 51 of the PC 5 receives the execution event ID, the event name, the start date / time, and the end date / time.

  Next, the generation unit 56 of the PC 5 generates an execution event list screen 570 as shown in FIG. 44 using the data (information) received in step S128 (step S129). In the PC 5, the display control unit 54 displays the execution event list screen 570 generated by the generation unit 56 on the display 508 (step S130). As shown in FIG. 44, the execution event list screen 570 includes information 571 to 573 indicating execution events. For example, information 571 to 573 indicating execution events includes an execution event name, an event start date and time, and an end date and time. Information 571 to 573 indicating an execution event is an example of a history information selection area that accepts a selection for displaying history information indicating the execution content of the event. The lower right portion of the execution event list screen 570 includes a “close” button 575 that is pressed when the execution event list screen 570 is closed. Further, the lower left portion of the execution event list screen 570 includes an “action item” button 577 that is pressed when browsing an action item. The “action item” button 577 is an example of an action item selection area that accepts a selection for displaying an action item.

  Next, the reception unit 52 of the PC 5 receives selection of an execution event included in the execution event list screen 570 (step S131). Specifically, when the user selects information indicating an execution event included in the execution event list screen 570, the reception unit 52 receives selection of information indicating the execution event. Then, the transmission / reception unit 51 of the PC 5 transmits the execution event ID of the execution event selected by the reception unit 52 to the schedule management server 8 (step S132). Thereby, the transmission / reception unit 81 of the schedule management server 8 receives the execution event ID.

  Next, the storage / read processing unit 89 of the schedule management server 8 reads the corresponding execution event history information by searching the execution event history management DB 8008 using the execution event ID received in step S132 as a search key (step S112). S133). This execution event history information includes a content processing ID, a content processing type, a content processing start date and time, and an end date and time.

  Further, the storage / read processing unit 89 of the schedule management server 8 retrieves the related information by searching the related information management DB 8010 using the execution event ID received in step S132 as a search key (step S134). This related information includes a content generation time zone, a content processing ID, a content processing type, and a sequence number. The occurrence time zone of the content included in the related information is an example of time information.

  Then, the storage / reading processing unit 89 reads the content data indicating the details of the execution event history from the storage destination of the content data indicating the details of the execution event history read in step S133 (step S135). Then, the transmission / reception unit 81 transmits the read content processing ID, content processing type, content processing start date / time and end date / time (related information), and content data to the PC 5 (step S136). Thereby, the transmission / reception part 51 of PC5 receives various data (information).

  Next, the sound control unit 58 of the schedule management server 8 sets the playback location of the sound data that is the content data received in step S136 (step S137). In this case, the sound control unit 58 sets a playback location corresponding to the sound data associated with the content occurrence time zone “00:00” in the received related information as the playback location of the sound data.

  Next, the generation unit 56 of the PC 5 generates an execution event history screen 580 as shown in FIG. 45 using the related information and content data received in step S136 (step S138). More specifically, the generation unit 56 executes the execution event so that the image related to the text data that is the received content data is displayed in the text data display area 582 in the order of the sequence No included in the received related information. A history screen 580 is generated. Further, the generation unit 56 displays the execution event history screen 580 so that the image related to the screen data that is the received content data is displayed in the snapshot display area 583 in the order of the sequence No included in the received related information. Generate. Further, the generation unit 56 displays the execution event history screen 580 so that the playback point 581p included in the playback location display area 581 is displayed at the position related to the sound data set in step S137 in the entire playback time of the sound data. Is generated.

  Then, the display control unit 54 of the PC 5 displays the execution event history screen 580 generated by the generation unit 56 on the display 508 (step S139). Further, the sound control unit 58 of the PC 5 reproduces the sound data at the reproduction location set in step 137. As shown in FIG. 45, the execution event history screen 580 shows content data generated by the executed event for each type of content processing. In the execution event history screen 580, a playback location display area 581 for displaying the playback location of recorded data, a text data display area 582 for displaying audio text, a snapshot display area 583 for displaying a snapshot, and an action item are viewed. "Action item" button 584 pressed when the user clicks, "Material file" button 585 pressed when browsing the material used in the event, and "Pagination" pressed when displaying the pagination display area 589 described later A button "588 is included.

  Here, in the playback location display area 581, a playback point 581 p indicating the playback location at the total playback time, a slider 581 b indicating the playback history (playback process) of the recorded data, and a playback time display image showing the playback time at the total playback time. 581t is included. The playback point 581p and the slider 581b constitute a seek bar. The seek bar is an operation area for displaying the playback location of the recorded data and designating the playback location of the recorded data. The user can visually grasp where the recorded data is reproduced from the beginning to the end by the positions of the reproduction point 581p and the slider 581b. In addition, the user can move the playback point 581p using input means such as the mouse 507, and thereby play the recorded data from any playback location. The playback point 581p is an example of a playback location specifying image. The seek bar including the playback point 581p and the slider 581b is an example of a playback history display image.

  In the text data display area 582, text data 582a, 582b, 582c, 582d, and 582e are displayed in time series. Similarly, in the snapshot display area 583, snapshot (capture) images 583a, 583b, and 583c are displayed in time series. When the user moves the playback point 581p, the reception unit 52 receives the movement, and the display control unit 54 changes the display contents of the text data display area 582 and the snapshot display area 583 after the movement. Change to text data and snapshot images in the time zone. Thus, for example, if the user browses the image 583b, the user can easily grasp the time zone in which the pie chart was explained at the meeting, so the image related to the text data displayed in parallel with the image 583b 582c and 582d can be easily found. In this case, the images 583a and 583b are snapshot images of the entire display 220. The image 583c is an action item image that has been image-recognized (snapshot) in step S71-2.

  FIG. 46 shows an image displayed on the display 508 when the user presses the “page nation” button 588 shown in FIG. Here, “pagination” is navigation provided to move between pages when information is expanded and divided into a plurality of pages. For example, in the case of a Web page, “Pagination” indicates that a page with a lot of contents is divided into a plurality of pages, and links to each page are arranged. By using “Pagination”, the user can easily access and understand which page the user is viewing. “Pagination” is also referred to as “page division”, “page feed”, “paging”, and “pager”.

  When the user presses a “page nation” button 588, the accepting unit 52 accepts the press of the “page nation” button 588. As a result, the display control unit 54 displays a pagination display area 589 at the bottom of the execution event history screen 580 as shown in FIG. In this pagination display area 589, for example, an occurrence time zone of content in an event such as a meeting (here, every 5 minutes) is shown, and the same occurrence time zone as the time of the playback point of the playback point 581p is framed. (Elapsed time display area 589j). Note that the accepting unit 52 is in a waiting state until the “pagination” button 588 is depressed.

  Thereby, the shared system 1 can easily share an execution event history generated by an event belonging to the same project among members belonging to the same project. Further, the shared system 1 uses the project registration screen 520 displayed on the PC 5 to register or change members belonging to the project, so that the user can view the execution event history managed for each project. In addition, it is possible to omit processing such as browsing setting for each executed event.

  On the other hand, when the reception unit 52 of the PC 5 receives the selection of the “action item” button 577 on the execution event list screen 570 in step S131, the generation unit 56 displays the action item screen as shown in FIG. 590 is generated. Then, the display control unit 54 displays the action item screen 590 generated by the generation unit 56 on the display 508. As shown in FIG. 47, the action item screen 590 includes action item information 591 to 594. For example, the action item information 591 includes an image indicating the contents of the action item identified in FIG. 33, the user name selected in FIG. 34, and the expiration date designated in FIG. The lower right portion of the action item screen 590 includes a “close” button 599 that is pressed when the action item screen 590 is closed. In the action item screen 590 shown in FIG. 47, all action items associated with the project ID whose selection has been accepted in step S124 are displayed. 45, when the reception unit 52 receives the selection of the “action item” button 584 on the execution event history screen 580 shown in FIG. 45, the display control unit 54 similarly displays the action item on the display 508. A screen 590 is displayed.

  41 and 42, the case where the execution event history is browsed by the PC 5 has been described. However, even when the user presses the icon r2 in FIG. You can view the event history. 16 and 20, the case where the project registration and the schedule registration are performed by the PC 5 has been described. However, the project registration and the schedule registration can be performed by the electronic blackboard 2 by the same processing.

<< Main effects of embodiment >>
According to the present embodiment, as shown in FIGS. 25, 36, and 37, the electronic blackboard 2 transmits a transmission request for an execution event ID to the management system, and executes an execution event based on the transmitted transmission request. Receive the ID. When the electronic blackboard 2 receives the end of the event being executed, the electronic blackboard 2 transmits the received execution event ID and the file data used in the executed event to the management system. As a result, the electronic blackboard 2 does not require a separate process for storing the file data used in the event in association with the content generated by the event and storing it in the management system. There is an effect that can be.

  Further, as shown in FIG. 9C, FIG. 25, FIG. 36, and FIG. 37, the electronic blackboard 2 transmits the file data associated with the scheduled event ID received from the management system to the management system. . Thereby, the electronic blackboard 2 receives the file data registered in the management system as schedule information, and transmits the received file data to the management system as file data used for the executed event. Alternatively, file data can be managed in association with the executed event.

  Further, as shown in FIGS. 36, 37, and 38, the electronic blackboard 2 stores file data used in the event being executed in a specific storage area of the storage unit 2000, and receives the reception unit 52. When the end of the event is accepted by the above, the execution event ID and the file data stored in the specific storage area are transmitted to the management system. for that reason,

  As shown in FIGS. 36 and 37, the electronic blackboard 2 deletes the file data transmitted to the management system from the specific storage area. Thereby, the electronic blackboard 2 can reduce the risk of leakage of conference information and the like by deleting the file data that has been transmitted to the management system.

  Furthermore, as illustrated in FIG. 28, when the electronic blackboard 2 receives the selection of the icon r <b> 3 that receives the selection for displaying the file data stored in the specific storage area of the storage unit 2000 by the receiving unit 22. The file data stored in the specific storage area is displayed on the display. Thereby, the electronic blackboard 2 can display the file data used in the event being executed only by the user selecting the icon r3 displayed on the display 220.

  As shown in FIGS. 38, 39, and 40, the electronic blackboard 2 transmits the file data stored in the specific storage area to the management system when the end of the event is received by the receiving unit 22. When an event end screen 270 including a file upload selection area 273 that accepts selection of whether or not to be displayed is displayed on the display 220 and the selection of the file upload selection area 273 is accepted by the accepting unit 22, it is stored in a specific storage area Send file data to the management system. Thereby, the electronic blackboard 2 can transmit the file data to the management system in association with the end of the event, so that the file data used in the event is stored in the management system in association with the content generated by the event. Therefore, there is an effect that it is possible to suppress time and effort compared to the conventional method.

1 Shared system 2 Electronic blackboard (an example of a communication terminal)
3. Video conference terminal (an example of a communication terminal)
4 Car navigation system (an example of a communication terminal)
5 PC
6 Shared support server (an example of a management system)
8 Schedule management server (an example of a management system)
9 Voice-to-text conversion server 10 Communication network 21 Transmission / reception unit (an example of a first transmission unit, an example of a first reception unit, an example of a second transmission unit, an example of a second reception unit)
22 reception unit (an example of an event end reception unit, an example of an event start reception unit, an example of a selection reception unit)
24 display control unit (an example of display control means)
29 Storage / reading processing unit (an example of storage control means)
2000 storage unit (example of specific storage area)

JP, 2006-105241, A

Claims (14)

A communication terminal that communicates with a management system that manages content generated by an event being executed,
First transmission means for transmitting a transmission request of execution event identification information for identifying an event being executed to the management system;
First receiving means for receiving the execution event identification information from the management system based on the transmitted transmission request;
Event end accepting means for accepting the end of the event being executed;
A second transmission unit configured to transmit the received execution event identification information and the file data used in the executed event to the management system when the end is received by the event end reception unit;
A communication terminal comprising: The communication terminal according to claim 1, further comprising:
An event start receiving means for receiving the start of the specific event;
The communication request is a communication terminal that is a transmission request for execution event identification information for identifying a specific event whose start has been received by the event start receiving means. The communication terminal according to claim 1, further comprising:
Second receiving means for receiving, from the management system, file data associated with scheduled event identification information for identifying an event scheduled for execution;
The communication terminal, wherein the second transmission unit transmits the file data received by the second reception unit to the management system. The communication terminal according to claim 3, further comprising:
Comprising storage control means for storing file data used in the event being executed in a specific storage area;
When the end is accepted by the event end acceptance unit, the second transmission unit transmits the execution event identification information and the file data stored in the storage area to the management system.   The communication terminal according to claim 4, wherein the storage control unit stores the file data received by the second receiving unit in the specific storage area.   The communication terminal according to claim 4, wherein the storage control unit stores file data generated or updated in the executed event in the specific storage area.   The communication terminal according to any one of claims 4 to 6, wherein the specific storage area is a storage area provided for each of the executed events.   The communication terminal according to any one of claims 4 to 7, wherein the storage control unit deletes the file data transmitted by the second transmission unit from the specific storage area. The communication terminal according to any one of claims 4 to 8, further comprising:
Display control means for displaying on the display means a selection image for accepting selection for displaying the file data stored in the specific storage area;
Comprising selection accepting means for accepting selection of the selected image;
When the selection accepting unit accepts selection of the selected image, the display control unit causes the display unit to display the file data stored in the specific storage area. When the end is received by the event end receiving means, the display control means includes a selection screen including a selection area for receiving selection of whether to transmit the file data stored in the specific storage area to the management system Is displayed,
10. The device according to claim 4, wherein when the selection accepting unit accepts the selection of the selection area, the second transmission unit sends the file data stored in the specific storage area to the management system. The communication terminal as described in any one.   The communication terminal according to any one of claims 1 to 10, wherein the communication terminal is an electronic blackboard, a video conference terminal, or a car navigation device. The communication terminal according to any one of claims 1 to 11,
The management system;
Shared system with A communication method executed by a communication terminal that communicates with a management system that manages content generated by an executed event,
A first transmission step of transmitting an execution event identification information transmission request for identifying an event being executed to the management system;
Receiving the execution event identification information from the management system based on the transmitted transmission request;
An event end receiving step for receiving the end of the event being executed;
A second transmission step of transmitting the received execution event identification information and the file data used in the executed event to the management system when the end is accepted;
Communication method to execute.   A program causing a computer to execute the method according to claim 13.