JP7413660B2 - Communication terminals, shared systems, storage control methods and programs - Google Patents

Description

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

In recent years, electronic blackboards have been used at meetings in companies, educational institutions, government agencies, etc., which display a background image on the display and allow users to draw stroke images of letters, numbers, figures, etc. on this background image. (For example, Patent Document 1).

Furthermore, a technique is known that uses an application installed on an electronic whiteboard or the like to manage content such as files generated at an event such as a meeting (for example, Patent Document 2).

However, in conventional methods, in events such as meetings held using communication terminals such as electronic whiteboards, in order to allow users to refer to action items that occurred in past events, it is necessary to use a dedicated storage server, etc. It was necessary to introduce a new system. Therefore, there was a problem that it took time and cost to introduce the system.

In order to solve the above-mentioned problem, the invention according to claim 1 provides a communication terminal capable of communicating with a management server that manages action items that occur in an executed event, and a communication terminal that can communicate with a management server that manages action items that occur in an executed event. an event identification information transmitter that transmits event identification information to the management server; and an action item receiver that receives action item data indicating an action item that occurred in a past event associated with the event identification information from the management server. means, display control means for displaying one or more images indicating the received action item data on a display section of the communication terminal, and accepting selection of a specific image from among the one or more displayed images. and an import request accepting means that receives a request to import specific action item data shown in the specific image; , and storage control means for storing information in a storage unit.

According to the present invention, action items that occurred in past events can be imported into a communication terminal without introducing a new system.

1 is a schematic diagram of a shared system according to this embodiment. FIG. 2 is a hardware configuration diagram of an electronic whiteboard. FIG. 2 is a hardware configuration diagram of a video conference terminal. FIG. 2 is a hardware configuration diagram of a car navigation device. It is a hardware configuration diagram of a PC and a server. FIG. 2 is a software configuration diagram of the electronic whiteboard. FIG. 2 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 a content management table, and (B) is a conceptual diagram of a related event 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 server authentication management table, and (B) is a conceptual diagram of an execution event history management table. (A) A conceptual diagram of an execution event management table, and (B) a conceptual diagram of a related information management table. FIG. 3 is a conceptual diagram of a related event management table. FIG. 3 is a sequence diagram showing schedule registration processing. It is a figure showing a sign-in screen. This is an example of the initial screen of a PC. It is a figure showing a schedule input screen. FIG. 3 is a sequence diagram showing event start processing. FIG. 3 is a diagram showing a sign-in screen displayed on the electronic blackboard. FIG. 3 is a diagram showing a reservation list screen for a union. FIG. 3 is a sequence diagram showing event start processing. It is a figure showing a detailed information screen of an event. FIG. 3 is a diagram showing a display screen displayed on the electronic blackboard at the start of an event. FIG. 2 is an image diagram showing a state in which a user uses an electronic blackboard. FIG. 3 is a sequence diagram showing execution event history registration processing. 3 is a flowchart showing speech-to-text conversion processing. FIG. 3 is a sequence diagram showing execution event history registration processing. FIG. 3 is a sequence diagram showing event termination processing. FIG. 3 is a sequence diagram showing event termination processing. It is a diagram showing an event end screen on an electronic blackboard. FIG. 3 is a diagram showing a file data upload screen on an electronic blackboard. FIG. 3 is a diagram showing a file data upload completion screen on the electronic blackboard. FIG. 3 is a sequence diagram showing a process of capturing action item data that occurred in a past event. FIG. 3 is a diagram showing a display screen displayed on the electronic blackboard after signing in. It is a figure showing an event selection screen. FIG. 3 is a sequence diagram showing a process of capturing action item data that occurred in a past event. It is a figure showing an action item import screen. FIG. 3 is a sequence diagram showing action item data search processing. (A), (B) are diagrams showing event selection screens. It is a figure showing an action item list screen. 3 is a flowchart showing action item registration processing. This is an example of a screen for recognizing action items. This is an example screen showing a list of candidates for executing an action item. This is an example of a screen showing a calendar for selecting an expiration date for an action item.

The shared system 1 according to this embodiment will be described in detail below using the drawings. Note that in this embodiment, "file" refers to "electronic file."

<<Overview of system configuration>>
First, the outline of the configuration of the shared system 1 will be explained. FIG. 1 is a schematic diagram of a shared system according to this embodiment.

As shown in FIG. 1, the shared system 1 of this embodiment includes an electronic whiteboard 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 system. It is constructed by a server 8 and a speech-to-text conversion server 9.

Furthermore, the electronic blackboard 2, video conference terminal 3, car navigation device 4, PC 5, shared support server 6, schedule management server 8, and speech-to-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 a wired communication network but also a wireless communication network such as 3G (3rd Generation), WiMAX (Worldwide Interoperability for Microwave Access), or LTE (Long Term Evolution).

Further, the electronic blackboard 2 is used in the conference room X. Video conference terminal 3 is used in conference room Y. Furthermore, the union is subject to reservation by each user. The car navigation device 4 is used in the vehicle α. The vehicle α in this case is a vehicle to be car-shared. Vehicles include cars, motorcycles, bicycles, wheelchairs, etc.

"Common entity" refers to goods, services, spaces (rooms), places, or information that are used jointly by multiple people or groups. Conference room X, conference room Y, and vehicle α are examples of a shared entity shared by a plurality of users. An example of information given to a union is an account. For example, in a particular service provided on the Web, the number of accounts that can be used is limited to one.

The electronic whiteboard 2, video conference terminal 3, and car navigation device 4 are examples of communication terminals. The "communication terminal" is, for example, a terminal that becomes usable upon sign-in by the user (see S32 described below). Note that the communication terminal used in the vehicle α includes not only the car navigation device 4 but also a smartphone or a smart watch on which a car navigation application is installed.

The PC 5 is an example of a display terminal, and is an example of a registration device that registers reservations for use of each union and registers events scheduled to be executed by each user with respect to the schedule management server 8. The event is, for example, a conference, meeting, gathering, getting together, consultation, meeting, driving, riding, or moving.

The shared support server 6 is a computer, and provides support for each communication terminal to remotely share a common body.

The schedule management server 8 is a computer that manages reservations for each union and schedules for each user. The schedule management server 8 is an example of a management server.

The speech-to-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 shared support server 6, schedule management server 8, and speech-to-text conversion server 9 are referred to as a management system. Note that the management system may be, for example, a server that performs all or part of the functions of the shared support server 6, the schedule management server 8, and the speech-to-text conversion server 9.

<<Hardware configuration>>
Next, the hardware configuration of the device or terminal that constructs the shared system 1 will be explained using FIGS. 2 to 5.

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

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

The electronic whiteboard 2 also includes a capture device 211, a GPU 212, a display controller 213, a contact sensor 214, a sensor controller 215, an electronic pen controller 216, a short-range communication circuit 219, an antenna 219a of the short-range communication circuit 219, and a power switch 222. We are prepared.

Of these, the capture device 211 acquires image data displayed on a display 220, which is an example of a display unit (display means), via the display controller 213, and stores it 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 the output image from the capture device 211 or the GPU 212 to the display 220 or the like. The contact sensor 214 detects when the electronic pen 2500, the user's hand H, or the like comes into contact with the display 220. Sensor controller 215 controls processing of contact sensor 214. The contact sensor 214 performs coordinate input and coordinate detection using an infrared cutoff method. This method of inputting and detecting coordinates is such that two light receiving and emitting devices installed at both ends of the upper side of the display 220 emit a plurality of infrared rays in parallel to the display 220. This is a method of receiving light that is reflected by a reflecting member and returns along the same optical path as the light emitted by the light receiving element. The contact sensor 214 outputs the ID of the infrared rays emitted by the two light receiving and emitting devices blocked by the object to the sensor controller 215, and the sensor controller 215 identifies the coordinate position that is the contact position of the object. The electronic pen controller 216 communicates with the electronic pen 2500 to determine whether or not the display 220 is touched with the tip of the pen or the end of the pen. The near field communication circuit 219 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The power switch 222 is a switch for switching the power of the electronic whiteboard 2 ON/OFF.

Further, the electronic whiteboard 2 includes a bus line 210. The bus line 210 is an address bus, a data bus, etc. for electrically connecting each component such as the CPU 201 shown in FIG. 2.

Note that the contact sensor 214 is not limited to the infrared cutoff type, but can also be a capacitive type touch panel that identifies the touch position by detecting changes in capacitance, or a touch sensor that identifies the touch position by voltage changes between two opposing resistive films. Various detection means may be used, such as a resistive film type touch panel that detects the electromagnetic induction generated when a touch object contacts the display section, and an electromagnetic induction type touch panel that specifies the contact position. Furthermore, the electronic pen controller 216 may determine whether or not a portion of the electronic pen 2500 that the user grasps or other portions of the electronic pen is touched, in addition to the pen tip and the pen tail of the electronic pen 2500.

<Hardware configuration of video conference terminal>
FIG. 3 is a diagram showing a hardware configuration diagram of the video conference terminal. As shown in FIG. 3, the video conference terminal 3 includes a CPU 301, ROM 302, RAM 303, flash memory 304, SSD 305, media I/F 307, operation button 308, power switch 309, bus line 310, 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 a circuit 319 is provided. Among these, the CPU 301 controls the entire operation of the video conference terminal 3. The ROM 302 stores programs used to drive the CPU 301, such as IPL. RAM 303 is used as a work area for CPU 301. Flash memory 304 stores various data such as communication programs, image data, and sound data. The SSD 305 controls reading and writing of various data to the flash memory 304 under the control of the CPU 301. Note that an HDD may be used instead of the SSD. A media I/F 307 controls reading or writing (storage) of data to a recording medium 306 such as a flash memory. The operation button 308 is a button that is operated when selecting the destination of the video conference terminal 3, for example. The power switch 309 is a switch for switching the power of the video conference terminal 3 ON/OFF.

Further, the network I/F 311 is an interface for data communication using the communication network 10 such as the Internet. The CMOS sensor 312 is a type of built-in imaging means that images a subject and obtains image data under the control of the CPU 301. The image sensor I/F 313 is a circuit that controls driving of the CMOS sensor 312. The microphone 314 is a type of built-in sound collecting means for inputting sound. The sound input/output I/F 316 is a circuit that processes input/output of sound signals between the microphone 314 and the speaker 315 under the control of the CPU 301. Display I/F 317 is a circuit that transmits image data to external display 320 under the control of CPU 301. 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.

Further, the bus line 310 is an address bus, a data bus, etc. for electrically connecting each component such as the CPU 301 shown in FIG. 3.

The display 320 is a type of display unit (display means) configured with a liquid crystal or organic EL that displays an image of a subject, operation icons, and the like. Further, the display 320 is connected to the display I/F 317 via a cable 320c. This cable 320c may be a cable for analog RGB (VGA) signals, a cable for component video, DisplayPort, HDMI (High-Definition Multimedia Interface (registered trademark)), or DVI ( It may also be a cable for Digital Video Interactive) signals.

Note that 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 using a USB cable or the like. When an external camera is connected, the external camera is driven with priority over the built-in CMOS sensor 312 under the control of the CPU 301. Similarly, when an external microphone or external speaker is connected, the external microphone or speaker is given priority over the built-in microphone 314 and built-in speaker 315, respectively, under the control of the CPU 301. Driven by external speakers.

Furthermore, the recording medium 306 is configured to be detachable from the video conference terminal 3. Furthermore, as long as it is a nonvolatile memory that reads or writes data under the control of the CPU 301, it is not limited to the flash memory 304, and an EEPROM or the like may be used.

<Hardware configuration of car navigation device>
FIG. 4 is a hardware configuration diagram of the car navigation device. 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 receiving section 409.

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

The car navigation device 4 also 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, a display It includes an I/F 418, an external device connection I/F 419, a short-range communication circuit 420, and an antenna 420a of the short-range communication circuit 420.

Of these, the long-distance communication circuit 411 receives traffic congestion information, road construction information, traffic accident information, etc. provided from infrastructure outside the vehicle, and conversely transmits information such as the vehicle's location and emergency life-saving signals to the outside. This is a circuit for 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 type of built-in imaging means that images a subject and obtains image data under the control of the CPU 401. The image sensor I/F 413 is a circuit that controls driving of the CMOS sensor 412. The microphone 414 is a type of built-in sound collection means for inputting audio. The sound input/output I/F 416 is a circuit that processes input/output of sound signals 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 means) such as a liquid crystal or organic EL display that displays an image of a subject, various icons, etc., and has a touch panel function. The touch panel is a type of input means for a user to operate the car navigation device 4. Display I/F 418 is a circuit that causes display 417 to display an image. 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. The car navigation device 4 also includes a bus line 410. The bus line 410 is an address bus, a data bus, etc. for electrically connecting each component such as the CPU 401 shown in FIG. 4.

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

Among these, the CPU 501 controls the operation of the entire PC 5. The ROM 502 stores programs used to drive the CPU 501 such as IPL. RAM 503 is used as a work area for 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 to the HD 504 under the control of the CPU 501. A media I/F 507 controls reading or writing (storage) of data to a recording medium 506 such as a flash memory. The display 508 displays various information such as a cursor, menu, window, characters, or images. The network I/F 509 is an interface for data communication using the communication network 10. The keyboard 511 is a type of input means that includes a plurality of keys for inputting characters, numbers, various instructions, and the like. The mouse 512 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, and the like. A CD-RW drive 514 controls reading and writing of various data on a CD-RW (Compact Disc-ReWritable) 513, which is an example of a removable recording medium. The speaker 515 outputs a sound signal under the control of the CPU 501.

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

Further, the shared support server 6 is constructed by a computer, and as shown in FIG. It includes an I/F 609, a keyboard 611, a mouse 612, a CD-RW drive 614, and a bus line 610. These are, in the PC 5, a 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. Since it has the same configuration as 510, the explanation will be omitted.

Furthermore, the schedule management server 8 is constructed by a computer, and as shown in FIG. It includes an I/F 809, a keyboard 811, a mouse 812, a CD-RW drive 814, and a bus line 810. These are, in the PC 5, a 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. Since it has the same configuration as 510, the explanation will be omitted.

The speech-to-text conversion server 9 is constructed by a computer, and as shown in FIG. It includes a network I/F 909, a keyboard 911, a mouse 912, a CD-RW drive 914, and a bus line 910. These are, in the PC 5, a 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. Since it has the same configuration as 510, the explanation will be omitted.

Note that each of the above programs may be an installable or executable file and may be recorded on a computer-readable recording medium and distributed. Examples of recording media include CD-R (Compact Disc Recordable), DVD (Digital Versatile Disk), Blu-ray Disc, SD card, and the like. Furthermore, the recording medium can be provided domestically or internationally as a program product. For example, a communication terminal such as the electronic whiteboard 2 implements the storage control method according to the present invention by executing the program according to the present invention.

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

<<Software configuration of electronic whiteboard>>
Next, computer software installed on the electronic whiteboard 2 will be explained using FIG. 6. Here, computer software (hereinafter referred to as software) refers to a program related to the operation of a computer and other information used for processing by a computer, which is equivalent to a program. A program is a set of instructions to a computer that are combined to produce a single result. Also, what is said to be similar to a program refers to something that cannot be called a program because it is not a direct command to a computer, but has properties similar to a program in that it specifies computer processing. For example, a data structure (a logical structure of data expressed by mutual relationships between data elements) corresponds to a program.

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

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

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

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

<<Functional configuration of shared system>>
Next, the functional configuration of this embodiment will be explained using FIGS. 7 to 14. FIG. 7 is a functional block diagram of the shared system. In FIG. 7, among the terminals, devices, and servers shown in FIG. 1, those related to the processes or operations described below are shown.

<Functional configuration of electronic blackboard>
As shown in FIG. 7, the electronic blackboard 2 includes a transmitting/receiving section 21, a receiving section 22, an image/sound processing section 23, a display control section 24, a determining section 25, a recognizing section 26, an acquisition/providing section 28, and a storage section 28. - It has a read processing section 29. Each of these units is a function or a means of functioning that is realized when any of the components shown in FIG. be. Further, the electronic whiteboard 2 has a storage unit 2000 constructed by the RAM 203, SSD 204, or USB memory 2600 shown in FIG.

(Functional configuration of electronic blackboard)
Next, each component of the electronic whiteboard 2 will be explained. The transmitting/receiving unit 21 is realized by commands from the CPU 201 shown in FIG. or information). The transmitter/receiver 21 is an example of an event identification information transmitter. Further, the transmitting/receiving unit 21 is an example of action item receiving means. Furthermore, the transmitter/receiver 21 is an example of event information receiving means. Further, the transmitting/receiving section 21 is an example of an event information transmitting means. Further, the transmitting/receiving unit 21 is an example of a search request transmitting means. Further, the transmitting/receiving unit 21 is an example of regular event information transmitting means.

The receiving unit 22 is mainly realized by commands from the CPU 201 shown in FIG. 2, as well as the contact sensor 214 and the electronic pen controller 216, and receives various inputs from the user. The reception unit 22 is an example of a selection means. Further, the reception unit 22 is an example of a capture request reception means. Furthermore, the reception unit 22 is an example of a setting means.

The image/sound processing unit 23 is realized by the command from the CPU 201 and the capture device 211 shown in FIG. 2, and stores image data displayed on the display 220. Further, the image/sound processing unit 23 is realized by the instructions from the CPU 201 and the GPU 212 shown in FIG. 2, 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 capturing an image of a subject with the camera 2400. Further, after the user's voice is converted into an audio signal by the microphone 2200, the image/sound processing unit 23 performs audio processing on the sound data related to this audio signal. Further, the image/sound processing unit 23 outputs an audio signal related to the sound data to the speaker 2300, and causes the speaker 2300 to output audio. The image/sound processing unit 23 also performs a process of converting drawn image data obtained by drawing on the display 220 with the electronic pen 2500 or hand H by the user into coordinate data. For example, when an electronic blackboard (2a) at an arbitrary base sends coordinate data to an electronic blackboard (2b) at another base, the electronic blackboard (2b) sends coordinate data to the electronic blackboard (2b) on the side of the other electronic blackboard (2b) based on the coordinate data. A drawing of the same content is displayed on the display 220.

The display control unit 24 is realized by the commands from the CPU 201 shown in FIG. 2 and the display controller 213 shown in FIG. It accesses the server 6 and displays various screen data. Specifically, the display control unit 24 starts and executes the Launcher 102 running on the OS 101 shown in FIG. A screen is displayed on the display 220. The display control unit 24 is an example of display control means.

The determining unit 25 is realized by instructions from the CPU 201 shown in FIG. 2, and performs various determinations.

The recognition unit 26 is realized by instructions from the CPU 201 shown in FIG. 2, and recognizes a specified area 262 surrounded on the display 220, as shown in FIG. 43, which will be described later.

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

The storage/read processing unit 29 is executed by the instructions from the CPU 201 and the SSD 204 shown in FIG. I do. Furthermore, the storage unit 2000 overwrites and stores image data and sound data that are received when communicating with other electronic whiteboards or video conference terminals each time they are received. Among these, an image is displayed on the display 220 using the image data before being overwritten, and sound is output from the speaker 2300 using the sound data before being overwritten. The storage/read processing unit 29 is an example of storage control means.

Note that the video conference terminal 3 and the car navigation device 4 have the same functions as the electronic whiteboard 2, so the description thereof will be omitted here.

<Functional configuration of PC>
The PC 5 includes a transmitter/receiver 51 , a receiver 52 , a display controller 54 , a generator 56 , a sound controller 58 , and a storage/read processor 59 . Each of these units is a function or functioning means that is realized when any of the components shown in FIG. . Furthermore, the PC 5 has a storage unit 5000 constructed by the HD 504 shown in FIG.

(Each functional configuration of PC)
Next, each component of the PC 5 will be explained. The transmitting/receiving unit 51 is realized by commands from the CPU 501 and network I/F 509 shown in FIG. 5, and transmits and receives various data (or information) to and from other terminals, devices, or systems via the communication network 10.

The receiving unit 52 is mainly realized by commands from the CPU 501 shown in FIG. 5, as well as a keyboard 511 and a mouse 512, and receives various inputs from the user.

The display control unit 54 is realized by instructions from the CPU 501 shown in FIG. 5, and displays images on the display 508, accesses the shared support server 6 using a web browser, and displays various screen data. do. Specifically, the display control unit 54 downloads a Web APP (Web Application) that includes at least HTML (HyperText Markup Language), CSS (Cascading Style Sheets), JAVA SCRIPT (registered trademark), etc., and uses the Web APP to The generated various image data are displayed on the display 508. The display control unit 54 causes the display 508 to display image data generated by HTML5 including data in the XML (Extensible Markup Language), JSON (JavaScript Object Notation), or SOAP (Simple Object Access Protocol) format.

The generation unit 56 is realized by instructions 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 generating unit 56 generates various image data using the content data received by the transmitting/receiving unit 51. For example, the generation unit 56 generates image data related to the text data, which is content image data, in order to render text data, which is content data, and display the rendered data. Rendering is a process of interpreting data written 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 instructions 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 instructions from the CPU 501 and the HDD controller 505 shown in FIG. 5, and stores various data in the storage unit 5000 and reads various data from the storage unit 5000 Perform processing.

<Functional configuration of shared support server>
The shared support server 6 includes a transmitting/receiving section 61 , an authentication section 62 , a creating section 63 , a generating section 64 , a determining section 65 , and a storage/reading processing section 69 . Each of these units has a function or functions that is realized when any of the components shown in FIG. It is a means. Further, the shared support server 6 has a storage unit 6000 constructed from the HD 604 shown in FIG. 5 and the like.

(User authentication management table)
FIG. 8(A) is a conceptual diagram showing a user authentication management table. In the storage unit 6000, a user authentication management DB 6001 is constructed, which includes a user authentication management table as shown in FIG. 8(A). In this user authentication management table, a user ID for identifying a user, a user name, an organization ID for identifying an organization to which the user belongs, and a password are managed in association with each other. Note that the organization ID also includes a domain name representing a group or organization for managing multiple computers on a communication network.

(Access management table)
FIG. 8(B) is a conceptual diagram showing the access management table. In the storage unit 6000, an access management DB 6002 is constructed, which includes an access management table as shown in FIG. 8(B). In this access management table, organization IDs, access IDs and access passwords necessary for authentication when accessing the schedule management server 8 are managed in association with each other. This access ID and access password are provided by the shared support server 6 to the schedule management server 8 via WebAPI (Application Programming Interface) using the HTTP (Hypertext Transfer Protocol) or HTTPS (Hypertext Transfer Protocol Secure) protocol. Necessary to use the provided services (functions). The schedule management server 8 manages a plurality of schedulers, and different organizations may use different schedulers, so management using an access management table is required.

(Schedule management table)
FIG. 8(C) is a conceptual diagram showing the schedule management table. A schedule management DB 6003 configured by a schedule management table as shown in FIG. 8(C) is constructed in the storage unit 6000. In this schedule management table, for each scheduled event ID and execution event ID, the organization ID, the user ID of the person making the reservation, whether or not this person is participating, the name of the person making the reservation, the scheduled start time, the scheduled end time, the event name, etc. The user ID of the participant, presence or absence of participation by other participants, names of other participants, 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 event that has actually been executed or an event that is being executed among the reserved events. The execution event ID is an example of execution event identification information for identifying an event that has been executed or an event that is being executed. Furthermore, the scheduled event ID and the executed event ID are examples of event identification information. The reservation person name is the name of the person who reserved the common entity, and is, for example, the name of the organizer when the common entity is a conference room, and is, for example, the name of the driver when the common entity is a vehicle. The scheduled start time indicates the scheduled time to start using the union. The scheduled end time indicates the scheduled end time of use of the union. The event name indicates the name of the event scheduled to be executed by the reservation person. The user IDs of 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 include unions. In other words, users in this case include not only the person making the reservation and other participants, but also the union. The file data is file data of a material file used in the event corresponding to the scheduled event ID, which is registered by user A using a schedule input screen 550 (see FIG. 18), which will be described later. Further, 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 PowerPoint file, an Excel file, or the like.

(Content management table)
FIG. 9(A) is a conceptual diagram showing a content management table. In the storage unit 6000, a content management DB 6005 is constructed, which includes a content management table as shown in FIG. 9(A). In this content management table, a content processing ID, content processing type, content content, and content processing start date and time and end date and time are associated and managed for each execution event ID. Here, the content is the content of an executed event that occurs at an event such as a conference, or materials used at the event. Types of content processing include recording, snapshots, audio text reception, action item generation, and document sending. Further, the content processing ID is identification information for identifying the content processing that occurred in each event.

Here, the content includes history information indicating the execution details of the event and action items caused by the executed event. The history information is data such as recorded data, snapshots, audio text, or materials. A snapshot is a process of acquiring a display screen at a certain point in time of an event being executed as image data. Note that a snapshot is also called, for example, capture or image recognition.

When the type of content processing is "recording", the content includes a URL indicating a storage location of recorded sound data. Furthermore, when the type of content processing is "snapshot", the content includes a URL indicating a storage location of image data of a screen acquired by snapshot (capture). Capturing means saving an image (still image, moving image) displayed on the display 220 as image data. Furthermore, when the type of content processing is "audio text reception", the content includes a URL indicating a storage location of the text data of the received audio text.

Here, an action item indicates the content of an action that occurs at an event such as a meeting and that a person related to the event should respond to. When the content processing type is "Action item generation", the content includes the user ID of the person executing the action item, the deadline for completing the action item, and the URL indicating the storage location of the image data representing the action item. including.

(Related event management table)
FIG. 9(B) is a conceptual diagram showing a related event management table. In the storage unit 6000, a related event management DB 6006 is constructed, which includes a related event management table as shown in FIG. 9(B). In this related event management table, related event IDs and execution event IDs are managed in association with each other. The related event ID is identification information for identifying multiple related events. The related event is an event that is held regularly, such as a regular meeting, or an event that is held repeatedly multiple times. The related event ID is generated by the schedule management server 8 at the time of schedule registration.

(Each functional configuration of the shared support server)
Next, each functional configuration of the shared support server 6 will be explained in detail. In the following, when explaining each functional configuration of the shared support server 6, the main components for realizing each functional configuration of the shared support server 6 among the components shown in FIG. Also explain the relationship.

The transmitting/receiving unit 61 of the shared support server 6 shown in FIG. 7 is realized by the command from the CPU 601 shown in FIG. 5 and the network I/F 609 shown in FIG. to send and receive various data (or information) to and from other terminals, devices, or systems.

The authentication unit 62 is realized by instructions from the CPU 601 shown in FIG. Authentication is performed by determining whether the information is authentic.

The creation unit 63 is realized by instructions from the CPU 601 shown in FIG. 5, and creates the information as shown in FIG. A reservation list screen 230 is created.

The generation unit 64 is realized by instructions from the CPU 601 shown 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 instructions from the CPU 601 shown in FIG. 5, and performs various determinations. This determination will be described later.

The storage/read processing unit 69 is realized by instructions from the CPU 601 shown in FIG. 5 and the HDD controller 605 shown in FIG. Performs processing such as reading out various stored data.

<Functional configuration of schedule management server>
The schedule management server 8 includes a transmitting/receiving section 81 , an authentication section 82 , a generating section 83 , and a storage/reading processing section 89 . Each of these units has a function or function that is realized when any of the components shown in FIG. It is a means. Furthermore, the schedule management server 8 has a storage unit 8000 constructed by the HD 804 shown in FIG. Storage unit 8000 is an example of storage means.

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

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

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

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

(Event management table)
FIG. 11(B) is a conceptual diagram showing the event management table. In the storage unit 8000, an event management DB 8005 is constructed, which is composed of an event management table as shown in FIG. 11(B). This event management table manages schedule information in which each piece of information is associated. The schedule information is managed in association with a user ID, user name, scheduled event start date and time, scheduled event end date and time, and event name for each organization ID. Among these, the scheduled event start date and time indicates the scheduled start date and time when the event is to be 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, day, hour, minute, second, and time zone, but in FIG. 11(B), due to space limitations, year, month, day, hour, and minute are also indicated. Further, in the event management table, file data of material files used in the event indicated in the schedule information is managed in association with the schedule event ID and related event ID.

(Server authentication management table)
FIG. 12(A) is a conceptual diagram showing the server authentication management table. In the storage unit 8000, a server authentication management DB 8006 is constructed, which includes a server authentication management table as shown in FIG. 12(A). In this server authentication management table, access IDs and access passwords 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 shared support server 6.

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

(Execution event management table)
FIG. 13(A) is a conceptual diagram showing an execution event management table. In the storage unit 8000, an execution event management DB 8009 is constructed, which is composed of an execution event management table as shown in FIG. 13(A). In this execution event management table, the event name, event start date and time, and end date and time are associated and managed for each execution event ID. This execution event management DB 8009 manages information regarding actually executed events among the schedule information managed in the event management DB 8005.

(Related information management table)
FIG. 13(B) is a conceptual diagram showing the related information management table. In the storage unit 8000, a related information management DB 8010 is constructed, which includes a related information management table as shown in FIG. 13(B). In this related information management table, related information in which each piece of information (data) is associated is managed for each execution event ID. The related information is managed in association with the content generation time period, sound data, audio text data, and screen data. The content occurrence time zone indicates the elapsed time from the start date and time of the event at the time when the content occurred in the executed event. The time period in which content occurs is an example of time information. The sound data also includes a content processing ID and a content type. The audio text data and screen data include a content processing ID, content type, and sequence number. The sequence number indicates the chronological order in which content processing occurred for each of audio text data and screen data.

(Related event management table)
FIG. 14 is a conceptual diagram showing a related event management table. A related event management DB 8013 configured by a related event management table as shown in FIG. 14 is constructed in the storage unit 8000. In this related event management table, a scheduled event ID and an execution event ID are managed in association with each related event ID. For example, at the time of schedule registration, the schedule management server 8 stores the scheduled event ID in association with the related event ID (see step S29). Further, the schedule management server 8 stores the execution event ID in association with the related event ID at the end of the event, for example (see step S312).

(Functional configuration of schedule management server)
Next, each functional configuration of the schedule management server 8 will be explained in detail. In the following, when explaining each functional configuration of the schedule management server 8, the main components for realizing each functional configuration of the schedule management server 8 among the components shown in FIG. Also explain the relationship.

The transmission/reception unit 81 of the schedule management server 8 shown in FIG. 7 is realized by the command from the CPU 801 shown in FIG. 5 and the network I/F 809 shown in FIG. to send and receive various data (or information) to and from other terminals, devices, or systems. The transmitting/receiving unit 81 is an example of action item transmitting means.

The authentication unit 82 is realized by instructions from the CPU 801 shown in FIG. Authentication is performed by determining whether the information is authentic. Further, the authentication unit 82 performs authentication by determining whether the information (access ID and access password) sent from the shared support server 6 is information registered in advance in the server authentication management DB 8006.

The generation unit 83 is realized by instructions from the CPU 801 shown in FIG. 5, and has a function of generating related information to be registered in the related information management DB 8010.

The storage/read processing unit 89 is realized by instructions from the CPU 801 shown in FIG. 5 and the HDD controller 805 shown in FIG. Performs processing such as reading out various stored data. The storage/read processing section 89 is an example of a storage means.

<Functional configuration of speech-to-text conversion server>
The speech-to-text conversion server 9 includes a transmitting/receiving section 91, a converting section 93, and a storage/reading processing section 99. Each of these units is a function or functioning means that is realized when any of the components shown in FIG. . The speech-to-text conversion server 9 also has a storage unit 9000 constructed by the HD 904 shown in FIG.

(Functional configuration of speech-to-text conversion server)
Next, each functional configuration of the speech-to-text conversion server 9 will be explained in detail. In the following, when explaining each functional configuration of the speech-to-text conversion server 9, the main components for realizing each functional configuration of the speech-to-text conversion server 9 among the components shown in FIG. Also explain the relationship.

The transmission/reception unit 91 of the speech-to-text conversion server 9 shown in FIG. 7 is realized by the command from the CPU 901 shown in FIG. 5 and the network I/F 909 shown in FIG. Send and receive various types of data (or information) to and from other terminals, devices, or systems.

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

The storage/read processing unit 99 is realized by the commands from the CPU 901 shown in FIG. 5 and the HDD controller 905 shown in FIG. Performs processing such as reading out various stored data.

Note that each of the above IDs is an example of identification information. Further, the organization ID includes a company name, a business office name, a department name, a region name, and the like. User IDs include employee numbers, driver's license numbers, My Numbers in Japan's social security and tax number system, etc.

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

<Schedule registration process>
Here, a process in which reservation person A (Rikotaro) registers his own schedule from PC 5 to schedule management server 8 will be explained using FIGS. 15 to 18. FIG. 15 is a sequence diagram showing the schedule registration process. FIG. 16 is a diagram showing the sign-in screen. FIG. 17 is an example of the initial screen of the PC. FIG. 18 is a diagram showing a schedule input screen.

First, when the user A operates the keyboard 511 or 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. Display (step S11). This sign-in screen 530 includes an input field 531 for entering the user ID and organization ID of the user, an input field 532 for entering the password, a sign-in button 538 to be pressed when signing in, and a sign-in button 538 for signing in. A cancel button 539 is included to be pressed when canceling. Here, the user ID and organization ID are user A's e-mail address. The user name part of the e-mail address is the user ID, and the domain name part is the organization ID. Note that the input field 531 may be an input field for inputting a user ID and an organization ID separately, instead of an e-mail address.

Next, when User A enters his or her user ID and organization ID in the input field 531, enters his or her password in the input field 532, and presses the sign-in button 538, the reception unit 52 prompts the user to sign in. The request is accepted (step S12). Then, the transmitting/receiving unit 51 of the PC 5 transmits sign-in request information indicating a request for sign-in to the schedule management server 8 (step S13). This sign-in request information includes the information (user ID, organization ID, and password) accepted in step S12. Thereby, the transmitting/receiving 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 S14). Specifically, in the user authentication management DB 8001 (see FIG. 10(A)), the storage/read processing unit 89 stores the user information corresponding to the set of user ID, organization ID, and password received in step S13. Search for a set of ID, organization ID, and password. If there is a corresponding pair, the authentication unit 82 determines that the requesting user A is an authorized user. If there is no corresponding pair, the authentication unit 82 determines that user A is an unauthorized (unauthorized) user. If it is not valid, the transmitting/receiving unit 81 notifies the PC 5 that it is not valid, but here we will continue to explain the case where it is valid.

Next, the transmitter/receiver 81 transmits the authentication result to the PC 5 (step S15). Thereby, the transmitting/receiving unit 51 of the PC 5 receives the authentication result.

Next, when the generation unit 56 of the PC 5 receives the authentic authentication result in step 15, it generates an initial screen 540 as shown in FIG. 17 (step S16). Then, the display control unit 54 of the PC 5 displays an initial screen 540 as shown in FIG. 17 on the display 508 (step S17). This initial screen 540 includes a "schedule registration" button 541 for registering a schedule, and a "view execution event history" button 543 for viewing the execution event history. Here, when the user presses the "schedule registration" button 541, the reception unit 52 accepts 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 transmitting/receiving unit 81 of the schedule management server 8 receives the schedule registration request.

Next, the storage/read processing unit 89 of the schedule management server 8 searches the user management DB 8002 (see FIG. 10(B)) using the organization ID received in step S13 as a search key, thereby searching all corresponding The user ID and all user names are read (step S20). Then, the transmitting/receiving unit 81 transmits schedule input screen information to the PC 5 (step S21). This schedule input screen information includes all user IDs and all user names read out in step S20. All the user names also include the name of the reservation person who is the user A who made the input for sign-in in step S12. Thereby, the transmitting/receiving unit 51 of the PC 5 receives the schedule input screen information.

Next, in the PC 5, the generation unit 56 generates a schedule input screen 550 using the schedule input screen information received in step S21. (Step S22). Then, the display control unit 24 of the PC 5 displays a schedule input screen 550 as shown in FIG. 18 on the display 508 (step S23).

On 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 a scheduled start date and time of event execution (union use) are input. an input field 553 for inputting the scheduled end date and time of the event execution (use of the union), an input field 555 for inputting notes such as an agenda, and a display area for displaying the reservation person's name. 556, Selection menu 557 for selecting the participant name of a participant other than the person making the reservation, "OK" button 558 to be pressed when registering a reservation, canceling the content being input or entered A "CANCEL" button 559 is included. The reservation user name is the name of the user who made the input to sign in to the PC 5 in step S12. A mouse pointer p1 is also displayed. Furthermore, the schedule input screen 550 includes a selection menu t1 for selecting events input in other items as related events. The selection menu t1 includes selectable information such as whether the related event can be executed, the frequency of execution, or the date of execution. Here, the regular event information is information about whether or not a related event can be executed, the frequency of execution, or the date of execution, selected from the selection menu t1.

Note that an e-mail address may be entered in the input field 552. Furthermore, when a union name is selected in the selection menu 557, the union is also added as another participant.

Next, user A enters predetermined items in input fields 551 to 555, uses mouse pointer p1 to select the name of the user who wants to participate in the event (user name) from selection menu 557, When regular event information is selected and set from the selection menu t1 and the "OK" button 558 is pressed, the reception unit 52 receives input of schedule information (step S24). Then, the transmitting/receiving unit 51 transmits the schedule information to the schedule management server 8 (step S25). This schedule information includes the event name, union ID (or union name), scheduled start date and time, scheduled end date and time, regular event information, user ID of each participant, and memo. In addition, on the schedule input screen 550, if a union ID is input in the input field 552, this union ID is transmitted, and if a union name is input in the input field 552, this union name is transmitted. is sent. Further, on the schedule input screen 550, a user name is selected in the selection menu 557, but since the user ID has also been received in step S21, the user ID corresponding to the user name is transmitted. Thereby, the transmitting/receiving 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. 10(C)) using the union ID (or union name) received in step S25 as a search key to find the corresponding union. name (or union ID) is read out (step S26).

Next, the storage/read processing unit 89 stores the reservation information in the union reservation management DB 8004 (see FIG. 11(A)) (step S27). In this case, the storage/read processing unit 89 adds one record of reservation information 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 usage start date and time in the union reservation management DB 8004 corresponds to the scheduled start date and time in the schedule information. Further, the scheduled usage end date and time in the union reservation management DB 8004 corresponds to the scheduled end date and time in the schedule information.

Further, the storage/read processing unit 89 stores the schedule information in the event management DB 8005 (see FIG. 11(B)) (step S28). In this case, the storage/read processing unit 89 adds one record of schedule information to the event management table of the event management DB 8005 managed by the scheduler registered in advance. The schedule information is configured based on the schedule information received in step S25. Specifically, the generation unit 83 generates a scheduled event ID and a related event ID based on the schedule information received in step S25. Here, when the regular event information included in the schedule information received in step S25 indicates that a regular event or a repeated event is to be executed, the generation unit 83 generates a scheduled event ID for each event. Furthermore, the generation unit 83 generates one related event ID for associating each scheduled event ID. Then, the storage/read processing unit 89 stores schedule information for each generated schedule event ID and related event ID in the event management DB 8005. 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. Furthermore, the scheduled end date and time of the event in the event management DB 8005 corresponds to the scheduled end date and time in the schedule information. Furthermore, the storage/read processing unit 89 stores the related event ID and scheduled event ID generated in step S28 in association with each other in the related event management DB 8013 (see FIG. 14) (step S29).

As described above, user A can register his or her own schedule in the schedule management server 8. Although FIGS. 15 to 18 describe the case where the schedule is registered using the PC 5, the schedule may be registered using the electronic whiteboard 2, the video conference terminal 3, or the car navigation device 4 through similar processing.

<Event start processing>
Here, with reference to FIGS. 19 to 25, a process of holding a conference with other participants using the electronic blackboard 2 in a conference room X reserved by a reservation person A (Rikotaro) will be described. FIGS. 19 and 22 are sequence diagrams showing event start processing. FIG. 20 is a diagram showing a sign-in screen displayed on the electronic blackboard. FIG. 21 is a diagram showing a reservation list screen for a union. FIG. 23 is a diagram showing a detailed event information screen. FIG. 24 is a diagram showing a display screen displayed on the electronic blackboard after signing in. FIG. 25 is an image diagram showing how a user uses the electronic blackboard.

First, when user A presses the power switch 222 of the electronic whiteboard 2, the reception unit 22 of the electronic whiteboard 2 receives a power ON request from the user (step S31). When the reception unit 22 accepts the power ON request, the Launcher 102 shown in FIG. 6 starts up. Then, the display control unit 24 of the electronic blackboard 2 displays the sign-in screen 110 for signing in on the display 220, as shown in FIG. 20 (step S32). This sign-in screen 110 includes a selection icon 111 that is pressed when user A signs in using his or her own IC card, and a selection icon 111 that user A presses to sign in using his or her own IC card. It includes a selection icon 113 that is pressed when signing in by entering a password, and a power icon 115 that is pressed when turning off the power without signing in.

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 inputting the user's e-mail address and password, the receiving unit 22 receives the sign-in request (step S33). Then, the transmitting/receiving unit 21 transmits sign-in request information indicating a sign-in request to the shared support server 6 (step S34). This sign-in request information includes the information accepted in step S33 (user ID, organization ID, and password), time zone information of the country or region where the electronic blackboard 2 is installed, and the communication terminal (here, the electronic blackboard 2) includes the user ID, organization ID, and password. Thereby, the transmitting/receiving 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 of the user A received in step S34 (step S35). Specifically, the storage/reading processing unit 69 uses the user ID, organization ID, and password of user A received in step S34 as a search key to search in the user authentication management DB 6001 (see FIG. 8(A)). , searches for a set of user ID, organization ID, and password that corresponds to the above-received set of user ID, organization ID, and password of user A. If there is a corresponding pair, the authentication unit 62 determines that the requesting user A is an authorized user. If there is no corresponding pair, the authentication unit 62 determines that the requesting user A is an unauthorized (unauthorized) user. If it is not valid, the transmitting/receiving unit 61 notifies the electronic blackboard 2 that it is not valid, but here we will continue to explain the case where it is valid.

Next, the storage/read processing unit 69 of the shared support server 6 searches the access management DB 6002 (see FIG. 8(B)) using the organization ID of user A received in step S34 as a search key. The access ID and access password are read out (step S36).

Next, the transmitting/receiving unit 61 transmits reservation request information indicating a request for reservation information of the union and schedule request information indicating a request for user schedule information to the schedule management server 8 (step S37). The reservation request information and schedule request information include the time zone information, the user ID and organization ID of the communication terminal received in step S34, and the access ID and password read out in step S36. Thereby, the transmitting/receiving 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 shared support server 6 using the access ID and the access password (step S38). Specifically, the storage/read processing unit 89 stores the set of access ID and access password corresponding to the set of access ID and access password received in step S37 in the server authentication management DB 8006 (see FIG. 12(A)). Search for. If there is a corresponding pair, the authentication unit 82 determines that the requesting shared support server 6 is an authorized accesser. If there is no corresponding pair, the authentication unit 82 determines that the requesting shared support server 6 is an unauthorized (unauthorized) accessor. If it is not valid, the transmitting/receiving unit 81 notifies the shared support server 6 that it is not valid, but here we will continue to explain the case where it is valid.

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 to search the union reservation management DB 8004 (FIG. 11) managed by the specified scheduler. By searching for A), the corresponding reservation information is read out (step S39). In this case, the storage/reading processing unit 89 reads the reservation information whose usage start date and time is today.

Furthermore, the storage/reading processing unit 89 searches the specified event management DB 8005 (see FIG. 12(B)) using the user ID of the communication terminal received in step S37 as a search key. The schedule information is read out (step S40). In this case, the storage/reading processing unit 89 reads out schedule information in which the scheduled event start date and time is today. If the schedule management server 8 is located in a different country or region from the communication terminal such as the electronic whiteboard 2, the time zone is set to match the country or region where the communication terminal is installed based on the time zone information. I'm making adjustments.

Next, the transmitting/receiving unit 81 transmits the reservation information read out in step S39 and the schedule information read out in step S40 to the shared support server 6 (step S41). Thereby, the transmitting/receiving unit 61 of the shared support server 6 receives the reservation information and schedule information.

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 S41 (step S42). Then, the transmitting/receiving unit 61 transmits reservation list information indicating the contents of the reservation list to the electronic blackboard 2 (step S43). Thereby, the transmitting/receiving section 21 of the electronic whiteboard 2 receives the reservation list information.

Next, in the electronic whiteboard 2, the display control unit 24 displays a reservation list screen 230 as shown in FIG. 21 on the display 220 (step S44). This reservation list screen 230 includes a display area 231 that displays a union name (here, a place name) and a display area 232 that displays today's date and time. Further, on the reservation list screen 230, event information 235, 236, 237, etc. indicating the event using today's main community (here, conference room X) is displayed. Each event information includes, for each event, the scheduled start time and end time of use of the union, the event name, and the name of the person who reserved the union (reserver name). The event information includes start buttons 235s, 236s, 237s, etc. that are pressed when the user specifies an event to start.

Next, in FIG. 22, when the user A presses the start button 235s using, for example, the electronic pen 2500, the reception unit 22 accepts the selection of the event indicated by the event information 235 (step S51). Next, the transmitting/receiving unit 21 of the electronic whiteboard 2 transmits the scheduled event ID and related event ID indicating the event selected in step S51 above to the shared support server 6 (step S52). The process in step S52 is a process for requesting transmission of execution event identification information. Thereby, the transmitting/receiving unit 61 of the shared support server 6 receives the scheduled event ID and related event ID indicating the selected event.

Next, in the shared support server 6, the generation unit 64 generates a unique execution event ID (step S53). Then, the storage/reading processing unit 69 manages the execution event ID generated in step S53, the reservation event ID received in step S52, the user ID and organization ID of the reservation person, and the event information in association with each other (step S54). Note that the user ID and organization ID of the reservation person, and event information are IDs and information based on the reservation information and schedule information received in step S41. Note that at this point, there is no entry in the participation/non-participation column in the reservation management table (see FIG. 9(C)).

Next, the storage/read processing unit 69 stores and manages the related event ID received in step S52 and the execution event ID generated in step S53 in association with each other (step S55).

Next, in the shared support server 6, the transmitting/receiving unit 61 transmits file data transmission request information indicating a transmission request for file data registered in the schedule management server 8 to the schedule management server 8 (step S56). The file data transmission request information includes the scheduled event ID received in step S52, the user ID and organization ID of the communication terminal received in step S34, and the access ID and access password read out in step S36. ing. Thereby, the transmitting/receiving unit 81 of the schedule management server 8 receives the file data transmission request information.

Next, the storage/reading processing unit 89 of the schedule management server 8 searches the event management DB 8005 (see FIG. 11(B)) using the scheduled event ID received in step S56 as a search key. The associated file data is read (step S57). Then, the transmitting/receiving unit 81 transmits the file data read in step S57 to the shared support server 6 (step S58). Thereby, the transmitting/receiving unit 61 of the shared support server 6 receives the file data.

Next, the storage/read processing unit 69 of the shared support server 6 associates the scheduled event ID received in step S52 with the execution event ID generated in step S53, and stores the file data received in step S58. It is stored and managed in the schedule management DB 6003 (step S59).

Then, the transmitting/receiving unit 61 transmits the execution event ID generated in step S53 and the file data received in step S58 to the electronic whiteboard 2 (step S60). Thereby, the transmitting/receiving unit 21 of the electronic whiteboard 2 receives the execution event ID and the file data.

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

Next, the display control unit 24 displays a detailed information screen 250 of the selected event on the display 220, as shown in FIG. 23 (step S62). The event detailed information screen 250 includes a display area 251 for the event name, a display area 252 for the scheduled event time (scheduled start time and scheduled end time), and a display area 253 for the reservation person's name. Further, the event detailed 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 is displayed for displaying identification information (eg, file name) for identifying data. In the display area 257, the name of the person making the reservation shown in FIG. 18 and the names of other selected participants are displayed, and the name of each scheduled participant is used to check who is actually participating in the conference. checkbox is displayed. In addition, the display area 258 displays the file name of the file data stored in a specific storage area of the storage unit 2000, that is, the file data downloaded from the shared support server 6. The file name of the file data inside is also displayed. Further, the lower right side of the event detailed information screen 250 includes a "close" button 259 for closing the detailed information screen 250.

Next, when the user checks the checkbox of the user who is actually participating among the names of the planned participants and presses the "Close" button 259, the reception unit 22 accepts the selection of the participant. (Step S63). Then, the transmitting/receiving unit 21 transmits the user ID of each prospective participant and information indicating whether or not they will participate to the shared support server 6 (step S64). Thereby, the transmitting/receiving unit 61 of the shared support server 6 receives the user ID of each prospective participant and information indicating whether or not they will participate.

Next, in the shared support server 6, in the schedule management DB 6003, the presence or absence of participation is stored and managed in the participation/non-input column that has not been entered (step S65).

As described above, user A starts an event (here, a policy decision meeting) using the common body (here, conference room X) and the communication terminal (here, electronic blackboard 2). When the event starts, the display control unit 24 of the electronic blackboard 2 causes the display 220 to display a display screen 100a as shown in FIG. 24. FIG. 24 is a diagram showing a display screen displayed on the electronic blackboard at the start of an event. The display screen 100a shown in FIG. 24 includes a menu bar 121, time information 124 indicating the elapsed time from the start of the event or the remaining time until the end of the event, and a power icon 117 that is pressed when turning off the power to the electronic whiteboard 2. It is included. The menu bar 121 is an example of an operation display screen (window) of the Launcher 102. This menu bar 121 includes a plurality of operation icons 125 (125a to 125j) that are selected (pressed) when performing various processes during event execution. The operation icon 125a is selected (pressed) to view detailed information of the event being executed. The operation icon 125b is selected (pressed) when starting various external applications 103. The operation icon 125c is selected (pressed) when viewing file data stored in a specific storage area of the storage unit 2000. The operation icon 125d is selected (pressed) when switching the display of the application display screen of the external application 103 that is currently running. The operation icon 125e is selected (pressed) when changing the screen size of the application display screen of the external application 103. The operation icon 125f is selected (pressed) when performing various operations related to the event being executed. The operation icon 125g is selected (pressed) when capturing the display screen 100 displayed on the display 220. The operation icon 125h is selected (pressed) when ending an event in progress. The operation icon 125i is selected (pressed) when starting the browser application 103c to perform a search using the browser. The operation icon 125j is selected (pressed) when inputting characters, numbers, or the like.

Here, various icons included in the display screen displayed on the electronic blackboard 2 are an example of a "reception area." The reception area may include not only images such as icons and buttons, but also characters such as "change" or a combination of images and characters. The images here may be not only symbols and figures, but also illustrations, patterns, and other images that can be visually recognized by the user. Further, selection (pressing) of various icons is an example of an operation on various icons. Operations on various icons include, for example, an input operation on the display 220 using the electronic pen 2500, a double click or single click with a mouse, which is an example of an input means included in the PC 2700, and a keyboard, which is an example of an input means included in the PC 2700. Examples include the input operations used.

Then, as shown in FIG. 25, user A can hold a meeting in conference room X using electronic blackboard 2. The display control unit 24 of the electronic blackboard 2 causes the display 220 to display, as the event execution screen R, the menu bar 120 in which the menu bar 121 included in the display screen 100a is reduced and the file data r4 of the document file. For example, when the user A of the electronic blackboard 2 presses the operation icon 125c, the reception unit 22 receives the selection of the operation icon 125c, and the display control unit 24 displays the information stored in a specific storage area of the storage unit 2000. Display the file data r4 of the file. Note that the display control unit 24 of the electronic blackboard 2 displays not only the file data received in step S60, but also file data stored in advance in the storage unit 2000, or file data newly generated in an event that has been started. It may be displayed. In this case, the storage/read processing unit 29 of the electronic whiteboard 2 stores file data generated or updated in the event that has been started in a specific storage area of the storage unit 2000.

<Execution event history registration process>
Next, the execution event history registration process will be described using FIGS. 26 to 28. 26 and 28 are sequence diagrams showing execution event history registration processing. FIG. 27 is a flowchart showing the speech-to-text conversion process.

First, the determination unit 25 of the electronic whiteboard 2 determines the type of content processing in the event that is being started (step S71). Specifically, when the content is sound data generated by recording by the image/sound processing unit 23, the determining unit 25 determines that the type of content processing is “recording”. If the content is image data acquired by a snapshot (capture) by the image/sound processing unit 23, the determining unit 25 determines that the content processing type is “snapshot”. If the content is material file data transmitted by the transmitting/receiving section 21, the determining section 25 determines that the content processing type is "material transmission".

Next, the transmitting/receiving unit 21 transmits registration request information indicating the generated content registration request to the shared support server 6 (step S72). In this case, the transmitter/receiver 21 automatically transmits registration request information every time content occurs. This registration request information includes the execution event ID, the user ID of the content sender, content data, content processing type information, and the start date and time and end date and time of content processing (recording, snapshot, transmission). There is. Thereby, the transmitting/receiving unit 61 of the shared support server 6 receives the registration request information.

Next, the determining 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 transmitting/receiving unit 61 (step S73). Then, when the determining unit 65 determines that the type of content processing is "recording", the transmitting/receiving 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 transmitter/receiver section 91 of the speech-to-text conversion server 9 receives the sound data. Note that if the type of content processing is other than "recording", the shared support server 6 moves to the process of step S77 without performing the processes of steps S74 to S76.

Next, the converter 93 of the speech-to-text conversion server 9 converts the sound data received by the transmitter/receiver 91 into text data (step S75). Here, the speech-to-text conversion process in the speech-to-text conversion server 9 will be explained using FIG. 27. First, the converter 93 acquires information indicating the date and time when the sound data was received by the transmitter/receiver 91 (step S75-1). Note that the information acquired in step S75-1 may be information indicating the date and time when the shared support server 6 received the sound data or the date and time when the shared support server 6 transmitted the sound data. In this case, the transmitting/receiving unit 91 of the speech-to-text conversion server 9 receives the sound data and the information indicating the date and time transmitted from the shared support server 6 in step S74.

Next, the conversion unit 93 executes text conversion processing of the sound data received by the transmission/reception unit 91 (step S75-2). Then, when the text conversion process of the sound data is completed (YES in step S75-3), the conversion unit 93 moves the process to step S75-4. On the other hand, the conversion unit 93 repeats the process of step S75-2 until the audio data text conversion process is completed. The conversion unit 93 then generates text data converted from the sound data (step S75-4). Thereby, the speech-to-text conversion server 9 converts the sound data sent from the shared support server 6 into text data. The speech-to-text conversion server 9 repeatedly executes the process shown in FIG. 27 every time it receives sound data transmitted from the shared support server 6.

Returning to FIG. 26, the description of the execution event history registration process will be continued. The transmitter/receiver 91 transmits the text data converted by the converter 93 to the shared support server 6 (step S76). Here, the transmitting/receiving unit 91 transmits information indicating the date and time acquired in step S75-1 to the shared support server 6 along with the text data. Note that the transmitter/receiver 91 may transmit information indicating the date and time when the text data was generated by the converter 93 to the shared support server 6 along with the text data. Thereby, the transmitting/receiving 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 that occurred due to the event (step S77). Furthermore, the generation unit 64 generates a URL of content data indicating the contents of the content (step S78). Then, the storage/read processing unit 69 stores the type of content processing, the start date and time, and the end date and time of the content processing in the content management DB 6005 (see FIG. 9A) for each execution event ID received in step S72. , the content processing ID generated in step S77, and the URL indicating the storage location of the content generated in step S78 are managed in association with each other (step S79). Here, when the content processing type is "audio text reception", the start date and time and end date and time of the content processing are the date and time when the sound data was converted to text data. Here, the date and time when the sound data was converted to text data is information indicating the date and time obtained in step S75-1, which is received together with the text data in step S76. Note that the date and time when the audio data was converted to text data may be the date and time when the text data was received by the transmitting/receiving unit 61 of the shared support server 6, and the date and time when the text data was transmitted by the transmitting/receiving unit 91 of the voice-to-text conversion server 9. It may be the date and time when the Furthermore, if the type of content processing is "audio text reception", the start date and time and end date and time of content processing may be the same as the start date and time and end date and time of content processing related to the audio data to be converted into text. .

Next, in FIG. 28, the storage/read processing unit 69 of the shared support server 6 searches the user authentication management DB 6001 (see FIG. 8(A)) using the user ID received in step S72 as a search key. The corresponding organization ID is read out (step S91).

Next, the storage/read processing unit 69 searches the access management DB 6002 (see FIG. 8(B)) using the organization ID read in step S91 as a search key, thereby reading out the corresponding access ID and access password (step S92).

Next, the transmitting/receiving unit 61 transmits execution event history registration request information indicating a content data registration request to the schedule management server 8 (step S93). This execution event history registration request information includes the execution event ID received in step S72, the sender's user ID, content data, the start date and time and end date and time of content processing, the content processing ID generated in step S77, It includes the URL of the content data generated in step S78, and the access ID and access password read out in step S92. Thereby, the transmitting/receiving unit 81 of the schedule management server 8 receives the execution event history 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 S94). This authentication is the same process as step S36, so the explanation will be omitted. Here, we will continue to explain cases where it is legal.

Next, the storage/read processing unit 89 stores and manages the various data (information) received in step S93 in the execution event history management DB 8008 (see FIG. 12(B)) (step S95). The storage/read processing unit 89 stores various data (information) in the execution event history management DB 8008 in association with the execution event ID received in step S93. Thereby, the schedule management server 8 manages the same data as the shared support server 6 side.

Furthermore, the generation unit 83 of the schedule management server 8 generates related information that associates the content data received in step S93 for each content generation time slot (step S96). Here, the occurrence time period of the content included in the related information is generated using the start date and time of the event stored in the event management DB 8005 and the start date and time and end date and time of the content processing stored in the execution event history management DB 8008. Ru. That is, the content occurrence time zone indicates the elapsed time from the start date and time of the event at the time when the content occurred in the executed event. Then, the storage/reading processing unit 89 of the schedule management server 8 generates the data generated by the generation unit 83 in association with the execution event ID received in step S93 in the related information management DB 8010 (see FIG. 13(B)). The associated information is stored and managed (step S97). Thereby, the schedule management server 8 manages content data of different types of content processing in association with each content generation time.

As described above, the electronic whiteboard 2 can transmit the execution event ID of the event being executed and the content generated by the corresponding event to the schedule management server 8. Furthermore, the schedule management server 8 can store the received content in the execution event history management DB 8008 for each execution event ID. This allows the shared system 1 to store content generated by executed events for each event.

<Event end processing>
Next, a process for terminating an event in progress will be described using FIGS. 29 to 33. FIGS. 29 and 30 are sequence diagrams showing event termination processing. FIG. 31 is a diagram showing the event end screen on the electronic blackboard. FIG. 32 is a diagram showing a file data upload screen on the electronic blackboard. FIG. 33 is a diagram showing a file data upload completion screen on the electronic blackboard.

In FIG. 29, when user A closes the screen displayed on display 220, reception unit 22 accepts 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 and time and end date and time of the execution event, and file data registration request information indicating a file data registration request to the shared support server 6 (step S302). This execution event start and end information includes an execution event ID, an event name, a start date and time, and an end date and time of the event. Further, this file data registration request information includes an execution event ID, a sender user ID, file data, and the start date and time and end date and time of content processing. Thereby, the transmitting/receiving 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 shared support server 6 generates a unique content processing ID for identifying the content processing that occurred due to the event (step S303). Furthermore, the generation unit 64 generates a URL of content data indicating the contents of the content (step S304). Then, the storage/read processing unit 69 stores the type of content processing, the start date and time, and the end date and time of the content processing in the content management DB 6005 (see FIG. 9A) for each execution event ID received in step S302. , the content processing ID generated in step S303, and the URL indicating the storage location of the content generated in step S304 are managed in association with each other (step 305).

Next, the storage/read processing unit 69 of the shared support server 6 searches the user authentication management DB 6001 (see FIG. 8(A)) using the user ID received in step S72 as a search key. The organization ID is read (step S306).

Next, the storage/read processing unit 69 searches the access management DB 6002 (see FIG. 8(B)) using the organization ID read in step S91 as a search key, thereby reading out the corresponding access ID and access password (step S307).

Next, in FIG. 30, the transmitting/receiving unit 61 transmits the execution event start/end information received in step S302 and file data registration request information indicating a file data registration request to the schedule management server 8 ( Step S308). This file data registration request information includes the execution event ID received in step S302, the sender's user ID, the file data, the start date and time of content processing, the end date and time, the content processing ID generated in step S303, It includes the URL of the file data generated in step S304, and the access ID and access password read out in step S307. Thereby, the transmitting/receiving 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 S309). This authentication is the same process as step S36, so the explanation will be omitted. Here, we will continue to explain cases where it is legal.

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

Next, the storage/read processing unit 89 stores and manages the various data (information) received in step S308 in the execution event history management DB 8008 (step S311). The storage/read processing unit 89 stores various data (information) including file data in the execution event history management DB 8008 (see FIG. 12(B)) in association with the execution event ID received in step S308. Thereby, the schedule management server 8 manages the same file data as the shared support server 6 side. Furthermore, the storage/read processing unit 89 stores the execution event ID received in step S308 in the related event management DB 8013 (see FIG. 14) (step S312). In this case, the storage/read processing unit 89 stores the scheduled event ID received in step S56 in association with the execution event ID received in step S308.

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

Then, the transmitting/receiving 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 transmitting/receiving section 21 of the electronic whiteboard 2 receives the file data registration information.

Next, when the file data registration information is received by the transmitter/receiver 21, the storage/read processing unit 29 of the electronic whiteboard 2 deletes the file data stored in a specific storage area of the storage unit 2000 (step S315). . Thereby, the electronic blackboard 2 can reduce the risk of leakage of meeting information, etc. by deleting file data that has already been sent to the shared support server 6.

Here, the screen transition of the screen displayed on the electronic blackboard 2 when the event in progress is ended will be explained. First, in step S301, when the reception unit 22 accepts the termination of the event being executed, the display control unit 24 displays an event termination screen 270 as shown in FIG. 31 on the display 220. . This event end screen 270 includes a file display area 272, a file upload selection area 273, a "Close" button 278 for proceeding with the end processing of the event in progress, and a "CANCEL" button 278 for canceling the end processing of the event in progress. ” button 279 is included. In the file display area 272, file data images 272a, 272b, and 272c for identifying file data of material files stored in a specific storage area of the storage unit 2000 are displayed. The file upload selection area 273 includes a check box that accepts a selection as to whether or not to upload the file data corresponding to the file data image displayed in the file display area 272 to the shared support server 6.

When the reception unit 22 receives a 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. 32 on the display 220. Display. This file upload screen 280a is displayed on the display 220 when file data stored in a specific storage area of the storage unit 2000 is being uploaded to the shared support server 6. The file upload screen 280a includes an event name 281 of the event to end, an end date and time 282 of the event, a file data upload progress display area 283, and a "CANCEL" button 288 for interrupting (cancelling) the file data upload. There is. The upload progress display area 283 displays the number of file data to be uploaded (for example, "3" shown in FIG. 32) and the number of file data that have been uploaded (for example, "0" shown in FIG. 32). ) is displayed.

Then, when the file data upload is completed, the display control unit 24 displays an upload completion screen 280b as shown in FIG. 33. The upload completion screen 280b includes a "Close" button 288 to be pressed to end the event. When the upload completion screen 280b is displayed on the display 220, the storage/read processing unit 29 of the electronic whiteboard 2 stores the uploaded file data in a specific storage area of the storage unit 2000, as shown in step S315. Delete from.

On the other hand, if uploading of file data fails while the file upload screen 280a is displayed on the display 220, the display control unit 24 displays information for identifying the file data for which the upload has failed (for example, the file name). As a result, for example, when a failure occurs in the communication network 10, event participants can print file data created or edited at the event, or store file data in the USB memory 2600 connected to the electronic whiteboard 2. By doing this, you can bring back the file data that failed to upload.

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

<Execution of related events>
Next, a process for executing related events registered in the schedule management server 8 will be described using FIGS. 34 to 41. FIGS. 34 and 37 are sequence diagrams showing the process of capturing action item data that occurred in past events. FIG. 35 is a diagram showing a display screen displayed on the electronic blackboard after signing in. FIG. 36 is a diagram showing the event selection screen. FIG. 38 is a diagram showing an action item import screen. Note that the process for starting the event is the same as the process shown in FIGS. 19 to 25, and therefore the description thereof will be omitted. Further, the description will be made assuming that the display screen 100a (see FIG. 24) is displayed on the display 220 of the electronic whiteboard 2.

First, when user A presses the operation icon 125f included in the display screen 100a, the reception unit 22 of the electronic blackboard 2 accepts the selection of the operation icon 125f (step S481). The display control unit 24 of the electronic blackboard 2 causes the display screen 100b as shown in FIG. 35 to be displayed on the display 220 (step S482). This display screen 100b includes an operation content display area 390 that is displayed when the operation icon 125f is selected. The operation content display area 390 includes an action item list icon 330 that is pressed when viewing a list of action items, an action item registration icon 350 that is pressed when registering an action item that has occurred due to an event that is being executed, It includes an action item import icon 360 that is pressed when importing an action item that occurred due to a past event.

Next, when the user A presses the action item import icon 360, the reception unit 22 of the electronic blackboard 2 accepts the selection of the action item import icon 360 and accepts a request to send related event information (step S483). ). Then, the transmitting/receiving unit 21 of the electronic whiteboard 2 transmits a related event information transmission request to the shared support server 6, requesting transmission of related event information (step S484). This related event information transmission request includes an execution event ID for identifying the event being executed and user A's user ID. In this case, the execution event ID is the execution event ID received in the process of step S60 when the event starts, and the user ID is the user ID received in the process of step S33 when the event starts. Thereby, the transmitting/receiving unit 61 of the shared support server 6 receives the related event information transmission request.

The storage/read processing unit 69 of the shared support server 6 searches the user authentication management DB 6001 (see FIG. 8(A)) using the user ID received in step S484 as a search key to find the corresponding organization ID. Read out (step S485).

Next, the storage/read processing unit 69 searches the access management DB 6002 (see FIG. 8(B)) using the organization ID read in step S485 as a search key, thereby reading out the corresponding access ID and access password (step S485). S486). Then, the storage/read processing unit 69 reads out the corresponding related event ID by searching the related event management DB 6006 (see FIG. 9(B)) using the execution event ID received in step S484 as a search key. S487).

Next, the transmitting/receiving unit 61 of the shared support server 6 transmits a related event information transmission request to the schedule management server 8, requesting transmission of related event information (step S488). This related event information transmission request includes the related event ID read out in step S487, and the access ID and access password read out in step S486. Thereby, the transmitting/receiving unit 81 of the schedule management server 8 receives the related event information transmission request.

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 S489). This authentication is the same process as step S36, so the explanation will be omitted. Here, we will continue to explain cases where it is legal. Next, the storage/read processing unit 89 of the schedule management server 8 searches the related event management DB 8013 (see FIG. 14) using the related event ID received in step S488 as a search key to find the corresponding execution event ID. Read out (step S490). Then, the storage/read processing unit 89 reads out the corresponding event information by searching the execution event management DB 8009 (see FIG. 13(A)) using the execution event ID read in step S490 as a search key (step S491). .

Next, the transmitting/receiving unit 81 of the schedule management server 8 transmits related event information, which is the event information read in step S491, to the shared support server 6 (step S492). Thereby, the transmitting/receiving unit 61 of the shared support server 6 receives the related event information. Then, the transmitting/receiving unit 61 of the shared support server 6 transmits (transfers) the related event information received in step S492 to the electronic whiteboard 2 (step S493). Thereby, the transmitting/receiving unit 21 of the electronic whiteboard 2 receives the related event information.

The display control unit 24 of the electronic whiteboard 2 causes the display 220 to display an event selection screen 370a as shown in FIG. 36 (step S494). This event selection screen 370a includes a related event information display area 371 where the related event information received in step S493 is displayed in a selectable manner, a search area 375 for searching for action items that occurred due to past events, and an event selection screen 370a. A "close" button 379 is included for closing the selection screen 370a. In addition, the related event information display area 371 includes a repeat flag 371a indicating that this related event is an event that is held repeatedly. Furthermore, the search area 375 includes an input field 375a for inputting a predetermined keyword, and a "search" button 375b that is pressed when searching for an action item using the keyword input in the input field 375a. It is.

Next, in FIG. 37, when the user A presses the related event information display area 371, the reception unit 22 of the electronic blackboard 2 accepts the selection of the related event information display area 371, and requests the transmission of an action item. (Step S501). Then, the transmitting/receiving unit 21 of the electronic blackboard 2 transmits an action item transmission request requesting transmission of an action item to the shared support server 6 (step S502). This action item transmission request includes related event information whose selection was accepted in step S501. Thereby, the transmitting/receiving unit 61 of the shared support server 6 receives the action item transmission request. Next, the transmitting/receiving unit 61 of the shared support server 6 transmits (transfers) the action item transmission request received in step S502 to the schedule management server 8 (step S503). Thereby, the transmitting/receiving unit 81 of the schedule management server 8 receives the action item transmission request.

The storage/read processing unit 89 of the schedule management server 8 searches the execution event history management DB 8008 (see FIG. 12(B)) using the execution event ID included in the related event information received in step S503 as a search key. , reads the corresponding execution event history information (step S504).

Next, the transmitting/receiving unit 81 of the schedule management server 8 transmits the action item data included in the execution event history information read in step S504 to the shared support server 6 (step S505). Thereby, the transmitting/receiving unit 61 of the shared support server 6 receives the action item data transmitted from the schedule management server 8. Further, the transmitting/receiving unit 61 of the shared support server 6 transmits (transfers) the action item data received in step S505 to the electronic blackboard 2 (step S506). Thereby, the transmitting/receiving unit 21 of the electronic whiteboard 2 receives the action item data transmitted from the shared support server 6.

The display control unit 24 of the electronic whiteboard 2 causes the display 220 to display an action item capture screen 380 as shown in FIG. 38 (step S507). This action item import screen 380 includes an import target display area 381 where action item data to be imported is displayed, and a "CANCEL" button 389 that is pressed to interrupt (cancel) the action item import process. , and an "Import" button 389 that is pressed when importing action item data to be imported. The action item data to be captured is the action item data received in step S506. Among these, the capture target display area 381 includes preview images 381a to 381d indicating the action item data received in step S506. User A can confirm the contents of the action item data to be captured using the preview images 381a to 381d.

Next, when user A presses the "Import" button 389, the reception unit 22 of the electronic whiteboard 2 accepts the selection of the "Import" button 389 and accepts the request to import the action item (step S508). Then, the storage/read processing unit 29 of the electronic whiteboard 2 stores the action item data received in step S506 in the storage unit 2000 (step S509). Thereby, the electronic whiteboard 2 can import action item data generated by past events.

Next, the transmitting/receiving unit 21 of the electronic whiteboard 2 transmits registration request information indicating a registration request for the action item stored (captured) in step S509 to the shared support server 6 (step S510). This registration request information includes the execution event ID of the event being executed, the user ID of the sender of the action item data, and the action item data stored in step S509. Thereby, the transmitting/receiving unit 61 of the shared support server 6 receives the registration request information.

The generation unit 64 of the shared support server 6 generates a unique content processing ID for identifying the action item data included in the registration request information received in step S510 (step S511). Further, the generation unit 64 generates a URL of the storage destination of the action item data (step S512). The storage/read processing unit 69 then stores the type of content processing, the start date and time of the content processing, and the end date and time of the content processing in association with the execution event ID received in step S510 in the content management DB 6005 (see FIG. 9(A)). The date and time, the content processing ID generated in step S511, and the URL indicating the storage location of the action item data generated in step S512 are managed (step S513). Here, the type of content processing is "action item generation", and the start date and time and end date and time of content processing are information indicating the date and time when the action item data was received in step S510. Note that the start date and time and end date and time of content processing may be information indicating the start date and time and end date and time of content processing that are included in the execution event history information read in step S504.

Next, the transmitting/receiving unit 61 transmits execution event history registration request information indicating a content data registration request to the schedule management server 8 (step S514). This execution event history registration request information includes the execution event ID received in step S510, the sender user ID, action item data, the content processing ID generated in step S511, and the action item generated in step S512. It includes the URL of the data, and the start date and time and end date and time of the content processing stored in step S513. Thereby, the transmitting/receiving unit 81 of the schedule management server 8 receives the execution event history registration request information.

The storage/read processing unit 89 stores and manages the various data (information) received in step S514 in the execution event history management DB 8008 (see FIG. 12(B)) (step S515). The storage/read processing unit 89 stores various data (information) in the execution event history management DB 8008 in association with the execution event ID received in step S514. Thereby, the schedule management server 8 manages the same data as the shared support server 6 side. The schedule management server 8 can manage action item data imported into the electronic whiteboard 2 by an event being executed in association with the execution event ID of the event.

Note that, in step S508, the reception unit 22 of the electronic whiteboard 2 may be configured to accept a request to import specific action item data from among the action item data received in step S506. In this case, when the user A selects a preview image (381a to 381d) included in the import target display area 381 and presses the "Import" button 389, the reception unit 22 imports the preview image shown in the selected preview image. Accept requests to import specific action item data. Then, the storage/read processing unit 29 of the electronic whiteboard 2 causes the storage unit 2000 to store the specific action item data for which the reception unit 22 has received a request for import. This allows the electronic whiteboard 2 to capture only the action item data selected by the user from among the action item data received in step S506.

Next, a process of searching for action item data that occurred due to past events will be described using FIGS. 39 and 40. FIG. 39 is a sequence diagram showing action item data search processing. FIG. 40 is a diagram showing the event selection screen. Note that the process until the event selection screen 370b is displayed on the display 220 of the electronic whiteboard 2 is the same as the process from step S481 to step S493 shown in FIG. 34, and therefore a description thereof will be omitted. The process shown in FIG. 39 is a process when event information of an event related to the event being executed is not stored in the schedule management server 8 and related event information is not received in step S493.

If the related event information is not received in step S493, the display control unit 24 of the electronic whiteboard 2 causes the display 220 to display an event selection screen 370b as shown in FIG. 40(A) (step S521). Unlike the event selection screen 370a (see FIG. 36), this event selection screen 370b does not include a related event display area 371 because related event information has not been received. Therefore, when the user A inputs a predetermined keyword (for example, "policy decision meeting") into the input field 375a and presses the "search" button 375b, the reception unit 22 selects the "search" button 375b. The search request is accepted (step S522). Then, the transmitter/receiver 21 transmits an execution event search request to the shared support server 6, requesting a search for an execution event (step S523). This execution event search request includes the input data input into the input field 375a in step S522. Thereby, the transmitting/receiving unit 61 of the shared support server 6 receives the execution event search request. Next, the transmitting/receiving unit 61 of the shared support server 6 transmits (transfers) the execution event search request received in step S523 to the schedule management server 8 (step S524). Thereby, the transmitting/receiving unit 81 of the schedule management server 8 receives the execution event search request.

Next, the storage/read processing unit 89 of the schedule management server 8 searches the execution event management DB 8009 (see FIG. 13(A)) using the input data included in the search request received in step S524 as a search key. Accordingly, the corresponding event information is read out (step S525). Specifically, the storage/reading processing unit 89 searches for an event name shown in the execution event management table that constitutes the execution event management DB 8009, and if an event name corresponding to the input data exists, the storage/reading processing unit 89 searches Read information. Note that the schedule management server 8 may be configured to search only event information that the user who is the source of the search request has reference authority among the event information managed in the execution event management DB 8009. In this case, the transmitting/receiving unit 81 of the schedule management server 8 receives, from the shared support server 6, the execution event ID of the event in which the user who sent the search request participated in step S524. Then, the storage/read processing unit 89 of the schedule management server 8 searches only the event information corresponding to the execution event ID received by the transmission/reception unit 81 from among the event information stored in the execution event management DB 8009.

Then, the transmitting/receiving unit 81 transmits the search result including the event information read in step S525 to the shared support server 6 (step S526). Thereby, the transmitting/receiving unit 61 of the shared support server 6 receives the search results. Further, the transmitting/receiving unit 61 of the shared support server 6 transmits (transfers) the search results received in step S526 to the electronic whiteboard 2 (step S527). Thereby, the transmitting/receiving section 21 of the electronic whiteboard 2 receives the search results.

Then, the display control unit 24 of the electronic whiteboard 2 causes the display 220 to display an event selection screen 370c as shown in FIG. 40(A) (step S528). This event selection screen 370c includes a search result display area 373 in which event information included in the search results received in step S527 is displayed. When the user A presses the search result display area 373, the reception unit 22 of the electronic whiteboard 2 accepts the selection of the search result display area 373. Then, the shared system 1 executes a process of importing action item data corresponding to the selected event information, similar to the process shown in FIG. 37.

As a result, the electronic whiteboard 2 displays not only action item data generated by events related to the event being executed, but also actions generated by past events by search processing using a predetermined keyword input by user A. Item data can be imported. Although FIGS. 39 and 40 describe the case in which the electronic blackboard 2 does not receive related event information, the shared system 1 can also handle the cases shown in FIGS. 39 and 40 even when the electronic blackboard 2 receives related event information. The configuration may be such that the search process shown in FIG. In this case, the event selection screen 370a displays a related event display area 371 and a search result display area 373 that can be selected by the user.

Next, with reference to FIG. 41, a display screen that is displayed when viewing action item data in an event that is being executed will be described. FIG. 41 is a diagram showing an action item list screen. This action item list screen 340 is a display screen displayed on the display 220 when the reception unit 22 accepts the selection of the action item list icon 330 included in the display screen 100b shown in FIG. The action item list screen 340 displays information regarding the agenda of the event being executed, attendees, attached files, action items, and the conclusion of the event being executed. These pieces of information include the information shown in the schedule list information received in step S43, file data stored in a specific storage area of the storage unit 2000, action items that occur in the event being executed, and information imported in step S509. This is action item data.

The action item list screen 340 includes, as action items, an image showing the action item, an executor of the action item, and an execution deadline of the action item. The action item list screen 340 includes an "Import" tag 341 indicating that the action item data is imported data, an icon 343 that is pressed to enlarge the action item image, and an icon 343 that is pressed to close the action item list screen. ``Close'' button 349 is included.

This allows the user to check the action items that occurred in the event being executed as well as the action items that occurred in past events and that were captured in the electronic blackboard 2 during the event that is being executed. be able to.

(Action item registration process)
Here, with reference to FIGS. 42 to 45, the registration process of an action item that occurs in an event that is being executed will be described. FIG. 42 is a flowchart showing action item registration processing. FIG. 43 is an example of a screen for recognizing action items. FIG. 44 is an example of a screen showing a list of candidates for executing an action item. FIG. 45 is an example of a screen showing a calendar for selecting the expiration date of an action item.

First, in FIG. 42, when the user presses the operation icon 125f included in the display screen 100a shown in FIG. 34 and presses the action item registration icon 350 included in the display screen 100b shown in FIG. 22 receives an action item registration request (step S71-1). Next, as shown in FIG. 43, after the user draws an action item (here, "submit minutes") on the drawing screen 260a of the electronic blackboard 2 using the electronic pen 2500, an action When an image (drawn image) 261 showing the contents of the item is surrounded by a line (specified area) 262, the reception unit 22 accepts the designation of a predetermined area including the image 261, and the recognition unit 26 detects the areas included in the predetermined area. The image 261 is recognized (step S71-2). Although FIG. 43 describes an example in which an image (drawn image) 261 is surrounded by a line (designated area) 262, the recognition unit 26 recognizes an area that is an arbitrary distance away from the designated area 262 as the image 261. It may be a configuration. The predetermined area is specified, for example, by drawing a preset predetermined shape such as a circle or a polygon with the electronic pen 2500.

Next, as shown in FIG. 44, the display control unit 24 displays the action item executor candidate list 265 on the drawing screen 260b (step S71-3). Then, when the user uses the electronic pen 2500 to select a specific executor who will execute the action item, the reception unit 22 accepts the selection of the specific executor (step S71-4).

Next, as shown in FIG. 45, the display control unit 24 displays a calendar 267 on the drawing screen 260c for accepting the designation of the execution deadline of the action item (step S71-4). Then, when the user selects a specific deadline date using the electronic pen 2500, the reception unit 22 accepts the selection of the specific deadline date (step S71-5). Note that the calendar 267 is an example of a deadline date designation screen. The deadline designation screen may be a date list or the like that does not include days of the week or the like.

Through such processing, the electronic whiteboard 2 transmits content registration request information indicating an action item registration request to the shared support server 6 as a content registration request. The content registration request information includes the execution event ID indicating the event in which the action item occurred, the user ID of the executor of the action item selected in step S71-4, and the user ID of the action item recognized in step S71-2. It includes image data (here, image data of "submit minutes") and the deadline for execution of the action item accepted in step S71-6. That is, the transmitting/receiving unit 21 transmits the data of the image within the predetermined area as image data indicating the content of the action item that occurred in the event being executed. Thereby, the transmitting/receiving unit 61 of the shared support server 6 receives the content registration request information. Note that the process after the shared support server 6 receives the content registration request information is the same as the process shown in FIGS. 26 and 28, and therefore the description thereof will be omitted.

<<Main effects of the embodiment>>
According to this embodiment, as shown in FIGS. 34 to 41, the electronic whiteboard 2 can communicate with the schedule management server 8 (an example of a management server) that manages action items that occur in executed events. It is a communication terminal. In addition, the electronic whiteboard 2 transmits an execution event ID (an example of event identification information) for identifying the event being executed to the management server, and also sends an execution event ID (an example of event identification information) for identifying an event that is being executed, and Receives action item data indicating the action item that has been completed from the management server. Then, the electronic whiteboard 2 stores the received action item data in the storage unit 2000. Thereby, the electronic whiteboard 2 can import action items that occurred in past events into the electronic whiteboard 2 without introducing a new system with guaranteed security. In addition, the electronic blackboard 2 allows the user to check the action items of past events by importing action items that occurred in past events during the event being executed, thereby allowing the event to be executed efficiently. can.

Further, according to the present embodiment, as shown in FIGS. 34 to 36, the electronic blackboard 2 (an example of a communication terminal) displays past events associated with an execution event ID (an example of event identification information). event information indicating the contents of is received from the schedule management server 8 (an example of a management server), the received event information is displayed on the display 220 (an example of a display unit), and the event information displayed on the display 220 is displayed. Accept selection. Then, the electronic whiteboard 2 transmits the event information whose selection has been accepted to the schedule management server 8, and receives action item data indicating the action item that occurred in the event indicated by the transmitted event information from the schedule management server 8. Receive. Thereby, the electronic blackboard 2 can import action items of past events indicated by the event information selected by the user.

Furthermore, according to the present embodiment, as shown in FIGS. 39 and 40, the electronic blackboard 2 (an example of a communication terminal) sends a search request for searching for past events to the schedule management server 8 ( (an example of a management server), and receives predetermined event information from the schedule management server 8 as a response to the search request. As a result, the electronic whiteboard 2 can capture not only events related to pre-registered events in progress, but also action item data generated in desired events managed by the schedule management server 8.

Further, according to the present embodiment, as shown in FIGS. 37 and 38, the electronic blackboard 2 (an example of a communication terminal) displays images (for example, preview images 381a to 381d) indicating received action item data. ) is displayed on the display 220 (an example of a display unit), and a request to capture action item data indicated by the image displayed on the display 220 is accepted. Then, when the import request is accepted, the electronic whiteboard 2 stores the received action item data in the storage unit 2000. As a result, the electronic whiteboard 2 displays on the display 220 an image showing the action item data transmitted from the schedule management server 8 (an example of a management server), thereby informing the user of the content of the action item data to be captured. It can be confirmed.

Further, according to the present embodiment, as shown in FIGS. 37 and 38, the electronic whiteboard 2 (an example of a communication terminal) can display an image (for example, a preview image) displayed on a display 220 (an example of a display unit). A request to capture specific action item data indicated by a specific image among the images 381a to 385d) is accepted, and the specific action item data is stored in the storage unit 2000. Thereby, the electronic whiteboard 2 can capture only the action item data selected by the user from among the action item data transmitted from the schedule management server 8 (an example of a management server).

Further, according to the present embodiment, as shown in FIGS. 15, 18, and 34 to 41, the shared system 1 includes an electronic blackboard 2 (an example of a communication terminal) and a schedule management server 8 (management (an example of a server). The electronic whiteboard 2 sets related events among the plurality of events to be executed, and transmits periodic event information indicating the set related events to the schedule management server 8. In addition, the schedule management server 8 associates and stores execution event IDs (an example of event identification information) that identify multiple events based on the regular event information, and selects from the electronic blackboard 2 among the stored event identification information. Event identification information associated with the transmitted event identification information is specified, and action item data associated with the specified event identification information is transmitted to the electronic blackboard 2. As a result, the shared system 1 registers related events in the schedule management server 8, thereby allowing the electronic blackboard 2 to import action item data that occurred in past events related to the event being executed. Can be done.

＜＜Supplement＞＞
Each function of the embodiments described above can be realized by one or more processing circuits. Here, the term "processing circuit" as used herein refers to a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, or a processor designed to execute each function explained above. This includes devices such as ASIC (Application Specific Integrated Circuit), DSP (digital signal processor), FPGA (field programmable gate array), SOC (System on a chip), GPU (Graphics Processing Unit), and conventional circuit modules. .

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 device (an example of communication terminal)
6 Shared support server 8 Schedule management server (an example of a management server)
10 Communication network 21 Transmission/reception unit (an example of an event identification information transmission means, an example of an action item reception means, an example of an event information reception means, an example of an event information transmission means, an example of a search request transmission means, an example of a regular event information transmission means) )
22 Reception unit (an example of a selection means, an example of an import request reception means, an example of a setting means)
24 Display control unit (an example of display control means)
29 Storage/reading processing unit (an example of storage control means)
81 Transmission/reception unit (an example of action item transmission means)
89 Storage/reading processing unit (an example of specifying means)
102 Launcher (an example of the second application)
103 External application (an example of the first application)
220 Display (example of display section)
320 Display (example of display section)
417 Display (example of display section)
2000 Storage unit 8000 Storage unit (an example of storage means)

JP2016-105241A Japanese Patent Application Publication No. 2006-146415

Claims (8)

A communication terminal capable of communicating with a management server that manages action items that occur in an executed event,
event identification information transmitting means for transmitting event identification information for identifying an event being executed to the management server;
action item receiving means for receiving action item data indicating an action item that occurred in a past event associated with the event identification information from the management server;
Display control means for displaying one or more images indicating the received action item data on a display unit of the communication terminal;
an import request receiving unit that receives a selection of a specific image from among the one or more displayed images, thereby accepting a request to capture specific action item data indicated by the specific image;
storage control means for storing specific action item data indicated by the specific image in a storage unit when the capture request is accepted;
A communication terminal equipped with. The communication terminal according to claim 1,
comprising event information receiving means for receiving event information indicating details of past events associated with the event identification information from the management server,
The display control means causes the display unit to display the event information received by the event information reception means,
The communication terminal further includes:
Selection means for accepting a selection of event information displayed on the display unit;
Event information transmitting means for transmitting event information for which the selection has been accepted to the management server,
The action item receiving means is a communication terminal that receives action item data indicating an action item that occurred in the event indicated by the event information transmitted by the event information transmitting means from the management server. The communication terminal according to claim 2,
search request sending means for sending a search request for searching past events to the management server;
The event information receiving means is a communication terminal that receives predetermined event information from the management server as a response to the search request. The communication terminal according to any one of claims 1 to 3 ,
a first application that causes the event to be executed;
a second application that runs on an operating system and launches the first application;
A communication terminal equipped with. A shared system comprising the communication terminal according to any one of claims 1 to 4 and the management server,
The communication terminal is
a setting means for setting related events among the plurality of events to be executed;
comprising regular event information transmitting means for transmitting regular event information indicating a related event set by the setting means to the management server,
The management server is
storage means for storing event identification information that identifies a plurality of events in association with each other based on the periodic event information;
A shared system with 6. The shared system according to claim 5 ,
The management server is
identification means for identifying event identification information associated with the event identification information transmitted from the communication terminal among the event identification information stored in the storage means;
action item transmitting means for transmitting action item data associated with event identification information identified by the identifying means to the communication terminal;
A shared system with A storage control method executed by a communication terminal capable of communicating with a management server that manages action items that occur in an executed event, the method comprising:
a sending step of sending event identification information for identifying an event being executed to the management server;
a receiving step of receiving action item data indicating an action item that occurred in a past event associated with the event identification information from the management server;
a display control step of displaying one or more images indicating the received action item data on a display unit of the communication terminal;
a receiving step of receiving a request to import specific action item data indicated by the specific image by accepting a selection of a specific image from the one or more displayed images;
a storage control step of storing specific action item data indicated by the specific image in a storage unit when the capture request is accepted;
A memory control method that performs A program that causes a computer to execute the method according to claim 7 .