JP7395825B2 - Display terminal, shared system, display control method and program - Google Patents

Description

The present disclosure relates to a display terminal, a shared system, a display 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, action items occur at events such as meetings. In order to prevent failure to execute an action item that occurs in an event, the user uses a PC or the like to access a server that manages schedules (schedules, dates, etc.) and registers action items. For example, Patent Document 2 discloses content for displaying action item information generated in past meetings on a terminal device.

However, in the conventional method, the action items registered in the scheduler's server etc. are displayed on the terminal device etc. in the order in which they are recorded, so it takes time and effort for the user to find the desired action item that he or she wants to check. There was an issue.

In order to solve the above-mentioned problem, the invention according to claim 1 is a display terminal capable of communicating with a management system that manages action items that occur in an executed event, the display terminal displaying a plurality of items related to responses to the action items. a receiving means for receiving action item data including data from the management system; a display screen including a list of the plurality of received action item data; and a display screen including a list of the plurality of received action item data, Display control means for causing a display unit to display a registration screen for registering the created data in the management system, including an input area for inputting a storage destination and an attachment button to be pressed when attaching the created data. On the display screen, the selection of the first selected image in a specific item among the plurality of items is accepted, and on the registration screen, the input to the storage destination entered in the input area or the attachment button is accepted . a reception unit that accepts registration of the creation data in response to the attachment of the creation data, and when the selection of the first selection image is accepted, the display control unit controls the display of the plurality of images included in the display screen. The action item data is rearranged and displayed according to the content of the data of the specific item.

According to the present invention, an effect is achieved in that a user can easily find an action item that he or she wants to check.

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. It is a software configuration diagram of a PC. 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 an execution event management table, and (B) is a conceptual diagram of a content management table. (A) is a conceptual diagram of a user authentication management table, (B) is a conceptual diagram of a user management table, and (C) is a conceptual diagram of a union management table. (A) is a conceptual diagram of a union reservation management table, and (B) is a conceptual diagram of an event management table. (A) is a conceptual diagram of a server authentication management table, and (B) is a conceptual diagram of a project member management table. (A) A conceptual diagram of an execution event history management table, and (B) a conceptual diagram of an execution event management table. (A) A conceptual diagram of a related information management table, and (B) a conceptual diagram of an action item 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 project list screen. It is a figure showing a detailed information screen 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. 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. 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 execution event history viewing processing. FIG. 3 is a sequence diagram showing execution event history viewing processing. It is a diagram showing a project list screen on a PC. It is a diagram showing an execution event list screen on a PC. It is a diagram showing an execution event history screen on a PC. It is a diagram showing an execution event history screen on a PC. FIG. 7 is a sequence diagram showing display processing of an action item screen. It is a diagram showing an action item screen on a PC. 12 is a flowchart illustrating a process for rearranging action item data according to a deadline date. FIG. 3 is a diagram showing an action item screen in which action item data is sorted in order of expiry date. 12 is a flowchart illustrating a process for rearranging action item data according to correspondence status. FIG. 7 is a diagram showing an action item screen in which action item data is sorted by correspondence status. FIG. 7 is a sequence diagram showing a process for changing the correspondence state. This is an example of a screen when the compatibility status change button is selected. This is an example of a screen showing a state candidate list. It is a diagram showing an action item screen whose compatibility status has been changed. This is an example of a screen when a link button is selected. This is an example of a screen showing a registration screen for created data. 12 is a flowchart showing a process of sorting action item data according to the person in charge. FIG. 3 is a diagram showing an action item screen in which action item data is sorted by person in charge.

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. 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 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 the display 220 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 blackboard 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. The 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 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 (registered trademark) (High-Definition Multimedia Interface) (registered trademark). ) or DVI (Digital Video Interactive) signal cable.

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 means such as a liquid crystal or organic EL that displays images of the 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. Display 508 is an example of a display unit. 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 display 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 blackboard>>
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 2. As shown in FIG. 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.

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. 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.

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

The minutes application 5502a and the browser 5502b are applications that use various data sent from the schedule management server 8 to generate and display an execution event history screen that is the minutes of events executed by the electronic blackboard 2. be. Note that although FIG. 7 shows an example in which two external applications, the minutes application 5502a and the browser 5502b, are installed on the PC 5, 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. 8 to 15. FIG. 8 is a functional block diagram of the shared system. Note that, in FIG. 8, among the terminals, devices, and servers shown in FIG. 1, those related to the processing or operation described below are shown.

<Functional configuration of electronic blackboard>
As shown in FIG. 8, 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 realized by one of the components shown in FIG. 8 operating in accordance with an instruction from the CPU 201 according to a program expanded from the SSD 204 onto the RAM 203, or a means for functioning. 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 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 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 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 a command from the CPU 201 shown in FIG. 2, and recognizes a specified area 262 surrounded on the display 220, as shown in FIG. 31, 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.

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 transmitter/receiver 51 is an example of a receiver.

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 reception unit 52 is an example of reception means.

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 accesses the shared support server 6 or the schedule management server 8 by, for example, starting and running the minutes application 5502a or the browser 5502b running on the OS 5501 shown in FIG. . Then, 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, etc., and displays various image data generated by the Web APP. , is 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 display control unit 54 is an example of display control means.

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. The generation unit 56 generates image data related to the text data that is content image data, for example, in order to render text data that 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. 9(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 is composed of a user authentication management table as shown in FIG. 9(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. 9(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. 9(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. 9(C) is a conceptual diagram showing the schedule management table. In the storage unit 6000, a schedule management DB 6003 is constructed, which includes a schedule management table as shown in FIG. 9(C). 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 actually executed event among the reserved events. The execution event ID is an example of execution event identification information for identifying an event being executed. 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. 19), 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.

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

(Content management table)
FIG. 10(B) is a conceptual diagram showing the 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. 10(B). In this content management table, the content processing ID, type of content processing, 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. Here, the content is the content of an execution event that occurred in an event such as a meeting in a certain project, or materials used in 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 content processing type is "recording", the content includes a URL indicating the storage location of the recorded sound data. Further, when the type of content processing is "snapshot", the content includes a URL indicating the storage location of the image data of the screen acquired by the snapshot (capture). Capturing means saving an image (still image, moving image) displayed on the display 220 as image data. Further, 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 in an event such as a meeting in a certain project, 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.

(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 transmission/reception unit 61 of the shared support server 6 shown in FIG. 8 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 parts has a function or functions realized by one 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.

(User authentication management table)
FIG. 11(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 is composed of a user authentication management table as shown in FIG. 11(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. 11(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. 11(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. 11C is a conceptual diagram showing the union management table. In the storage unit 8000, a union management DB 8003 is constructed, which includes a union management table as shown in FIG. 11(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. 12A 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. 12(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. 12(A), due to space limitations, year, month, day, hour, and minute are also indicated.

(Event management table)
FIG. 12(B) is a conceptual diagram showing the event management table. In the storage unit 8000, an event management DB 8005 is constructed, which includes an event management table as shown in FIG. 12(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. 12(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.

(Server authentication management table)
FIG. 13(A) is a conceptual diagram showing a server authentication management table. In the storage unit 8000, a server authentication management DB 8006 is constructed, which is composed of a server authentication management table as shown in FIG. 13(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.

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

(Execution event history management table)
FIG. 14A is a conceptual diagram showing an execution event history management table. In the storage unit 8000, an execution event history management DB 8008 is constructed, which is composed of an execution event history management table as shown in FIG. 14(A). In this execution event history 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 project ID and 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. 14(B) is a conceptual diagram showing the 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. 14(B). 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. 15(A) is a conceptual diagram showing a related information management table. A related information management DB 8010 configured by a related information management table as shown in FIG. 15(A) is constructed in the storage unit 8000. In this related information management table, related information in which each piece of information (data) is associated is managed for each project ID and execution event ID. The related information is managed in association with the content generation time 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.

(Action item management table)
FIG. 15(B) is a conceptual diagram showing the action item management table. In the storage unit 8000, an action item management DB 8011 is constructed, which includes an action item management table as shown in FIG. 15(B). In this action item management table, action item data is managed in which information (data) of a plurality of items related to responses to action items are associated with each project ID and execution event ID. The action item data is associated with the content of the action item, the user ID of the person performing the action item, the deadline for completing the action item, the status of response to the action item, and output generated by response to the action item. It is well managed. The content of the action item includes a URL indicating a storage location of image data indicating the received action item. Further, the status of response to an action item is expressed as "ToDo" or "Doing" for an action item that requires response, and is indicated as "Doing" for an action item that has already been addressed. The state of the action item is changed using a corresponding state change button 716 on an action item screen 710, etc., which will be described later. Furthermore, the output includes a URL indicating the storage location of the creation data created in response to the action item.

(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. 8 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 transmitter/receiver 81 is an example of a transmitter.

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.

<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. 8 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 a reservation person A (Rikotaro) registers his/her own schedule from the PC 5 to the schedule management server 8 will be explained using FIGS. 16 to 19. FIG. 16 is a sequence diagram showing the schedule registration process. FIG. 17 is a diagram showing the sign-in screen. FIG. 18 is an example of the initial screen of the PC. FIG. 19 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 it (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. 11(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 authentication result is received in step 15, the generation unit 56 of the PC 5 generates an initial screen 540 as shown in FIG. 18 (step S16). Then, the display control unit 54 of the PC 5 displays an initial screen 540 as shown in FIG. 18 on the display 508 (step S17). This initial screen 540 includes a "schedule registration" button 541 for registering a schedule, and an "execution event history viewing" button 543 for viewing action items. 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. 11(B)) using the organization ID received in step S13 as a search key, thereby searching all the 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. 19 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 usage) 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.

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 the "OK" button 558 is pressed, the receiving 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, 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. 11(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. 12(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. 12(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. 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.

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

<Event start processing>
Here, with reference to FIGS. 20 to 26, 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. 20 and 23 are sequence diagrams showing event start processing. FIG. 21 is a diagram showing a sign-in screen displayed on the electronic blackboard. FIG. 22 is a diagram showing a union reservation list screen. FIG. 24 is a diagram showing the project list screen. FIG. 25 is a diagram showing a detailed event information screen. FIG. 26 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 whiteboard 2 displays the sign-in screen 110 for signing in on the display 220, as shown in FIG. 21 (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 performing , and a power icon 115 that is pressed when turning off the power without signing in.

Next, when the user A presses the selection icon 111 or the selection icon 113 and communicates with the short-range communication circuit 219 such as an IC card reader or inputs his/her e-mail address and password, The reception unit 22 accepts 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 time zone information of the country or region where the electronic whiteboard 2 is installed, the user ID and organization ID of the communication terminal (here, the electronic whiteboard 2), and a 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 (step S35). Specifically, the storage/reading processing unit 69 uses the user ID, organization ID, and password received in step S35 as search keys to search the received information in the user authentication management DB 6001 (see FIG. 9(A)). Search for a set of user ID, organization ID, and password that corresponds to the set of user ID, organization ID, and password. 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. 9(B)) using the organization ID received in step S34 as a search key, thereby searching for the corresponding access ID and The access password is read (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. 13(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. 12) 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 storage/read processing unit 89 searches the project member management DB 8007 (see FIG. 13(B)) using the user ID of the communication terminal received in step S37 as a search key, thereby determining whether the communication terminal is used. The project IDs and project names of all projects including the user ID are read out (step S41).

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

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

Next, in the electronic whiteboard 2, the display control unit 24 displays a reservation list screen 230 as shown in FIG. 22 on the display 220 (step S45). 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. 23, when the user A presses the start button 235s with, for example, the electronic pen 2500, the reception unit 22 accepts the selection of the event indicated by the event information 235 (step S51). Then, the display control unit 24 displays a project list screen 240 as shown in FIG. 24 on the display 220 based on the project ID and project name received in step S42 (step S52). The project list screen 240 includes project icons 241 to 246 indicating each project. The project list screen 240 also includes an "OK" button 248 to be pressed to confirm the selected project icon, and a "CANCEL" button 249 to cancel the selection of the project icon.

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

Next, the transmitting/receiving unit 21 of the electronic blackboard 2 transmits, to the shared support server 6, a scheduled event ID indicating the scheduled event selected in step S51 above, and a project ID indicating the project selected in step S53 above. (Step S54). The process in step S54 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 selected scheduled event ID and the selected project ID.

Next, in the shared support server 6, the generation unit 64 generates a unique execution event ID (step S55). Then, the storage/reading processing unit 69 manages the execution event ID generated in step S55, the reservation event ID received in step S54, the user ID and organization ID of the reservation person, and the event information in association with each other (step S56). 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 S42. 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/reading processing unit 69 manages the project ID received in step S54 and the execution event ID generated in step S55 in association with each other (step S57).

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 S58). The file data transmission request information includes the event ID received in step S54, the user ID and organization ID of the communication terminal received in step S34, and the access ID and access password read out in step S36. There is. 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. 12(B)) using the event ID received in step S58 as a search key to find information associated with the event ID. The stored file data is read out (step S59). Then, the transmitting/receiving unit 81 transmits the file data read in step S59 to the shared support server 6 (step S60). 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 S54 with the execution event ID generated in step S55, and stores the file data received in step S60. It is stored and managed in the schedule management DB 6003 (step S61).

Then, the transmitting/receiving unit 61 transmits the execution event ID generated in step S55 and the file data received in step S60 to the electronic whiteboard 2 (step S62). 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 S63). Here, the file data transmitted from the shared support server 6 is stored in a specific storage area of the storage unit 2000. Therefore, 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.

Next, the display control unit 24 displays a detailed information screen 250 of the selected event on the display 220, as shown in FIG. 25 (step S64). 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 who made the reservation shown in FIG. 19 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 S65). 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 S66). 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/absence of participation is stored and managed in the participation/non-input column that has not been entered (step S67).

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 whiteboard 2). Then, as shown in FIG. 26, user A can hold a meeting in conference room X using electronic blackboard 2. Note that the display control unit 24 displays the remaining time that the union can be used in the upper right area of the display 220. In this case, the display control unit 24 displays the time (remaining time) between the current time and the scheduled end time indicated by the event information selected in step S51.

The display control unit 24 also displays an icon r1 that is pressed when registering an action item, an icon r2 that is pressed when viewing the execution event history, and a material file stored in a specific storage area of the storage unit 2000. An icon r3 that is pressed when viewing and file data r4 of the material file are displayed. The icon r3 is an example of a selection image that accepts a selection for displaying file data stored in a specific storage area. For example, when the user of the electronic blackboard 2 presses the icon r3, the reception unit 22 accepts the selection of the icon r3, and the display control unit 24 selects a document file stored in a specific storage area of the storage unit 2000. Display data r4.

<Execution event history registration process>
Next, the execution event history registration process will be described using FIGS. 27 to 33. 27 and 29 are sequence diagrams showing execution event history registration processing. FIG. 28 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. 28. 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. 28 every time it receives sound data transmitted from the shared support server 6.

Returning to FIG. 27, 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). The storage/read processing unit 69 then updates the content management DB 6005 (see FIG. 10B) with the content processing type, content processing start date and time, and end date and time 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 type of content processing is "audio text reception", the start date and time and end date and time of content processing are information indicating the date and time when the content processing was received in step S76. Note that when the content processing type is "audio text reception", the start date and time and end date and time of the content processing may be information indicating the date and time when the shared support server 6 received the text data in step S76.

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

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

Next, the transmitting/receiving unit 61 transmits content registration request information indicating a content data registration request to the schedule management server 8 (step S94). This content registration request information includes the project ID read out in step S91, 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, and step S77. The content processing ID generated in step S78, the URL of the content data generated in step S78, and the access ID and access password read out in step S93 are included. Thereby, the transmitting/receiving unit 81 of the schedule management server 8 receives the content registration request information.

Next, in the schedule management server 8, the authentication unit 82 authenticates the shared support server 6 using the access ID and the access password (step S95). 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 S94 in the execution event history management DB 8008 (see FIG. 14(A)) (step S96). The storage/read processing unit 89 stores various data (information) in the execution event history management DB 8008 in association with the project ID and execution event ID received in step S94. Thereby, the schedule management server 8 manages the same data as the shared support server 6 side.

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

Furthermore, the storage/read processing unit 89 of the schedule management server 8 stores and manages the action items included in the content data received in step S94 in the action item management DB 8011 (step S99). Thereby, the schedule management server 8 manages action item data including data of a plurality of items related to responses to action items for each action item.

As described above, the electronic whiteboard 2 can transmit to the schedule management server 8 the event ID of an event in a predetermined project and the content generated by the execution of the corresponding event. Furthermore, the schedule management server 8 can store the received content in the execution event history management DB 8008 for each event ID associated with the project ID. Thereby, the shared system 1 can store content generated by an event for each project by having the user select which project the event belongs to when starting the event.

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

First, in FIG. 30, when the user presses the icon r1, the reception unit 22 accepts a request to register an action item (step S71-1). Next, as shown in FIG. 31, 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. 31 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. 32, 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. 33, 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 (in this case, image data of "submit minutes") and the deadline for execution of the action item accepted in step 71-5. 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. 27 and 29, and therefore the description thereof will be omitted.

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

In FIG. 26, 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). The storage/read processing unit 69 then updates the content management DB 6005 (see FIG. 10B) with the content processing type, content processing start date and time, and end date and time 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/reading processing unit 69 of the shared support server 6 searches the execution event management DB 6004 (see FIG. 10(A)) using the execution event ID received in step S72 as a search key to find the corresponding project. The ID is read (step S306). Next, the storage/reading processing unit 69 reads out the corresponding organization ID by searching the user authentication management DB 6001 (see FIG. 9(A)) using the user ID of the content sender as a search key (step S307).

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

Next, in FIG. 35, 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 S309). This file data registration request information includes the project ID read out in step S306, the execution event ID received in step S302, the sender's user ID, the file data, the start date and time of content processing, and the end date and time. The content processing ID generated in step S303, the URL of the file data generated in step S304, and the access ID and access password read in step S308 are included. 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 S310). 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 309 in the execution event management DB 8009 (see FIG. 14(B)) (step S311). . 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 S309 in the execution event history management DB 8008 (see FIG. 14(A)) (step S312). The storage/read processing unit 89 stores various data (information) including file data in the execution event history management DB 8008 in association with the project ID and execution event ID received in step S309. Thereby, the schedule management server 8 manages the same file data as the shared support server 6 side.

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 S315). 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 S316). . 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. 36 on the display 220. . This event end screen 270 includes a toolbar area 271, a file display area 272, a file upload selection area 273, a "Close" button 278 for proceeding with the end process of the currently running event, and a "Close" button 278 for canceling the end process of the currently running event. A "CANCEL" button 279 is included. In the toolbar area 271, an image showing icons r1, r2, and r3 as shown in FIG. 26 is displayed. 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 accepts the 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. 37 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 event end date and time 282, 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. 37) and the number of file data that have been uploaded (for example, "0" shown in FIG. 37). ) 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. 38. 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 the file data created or edited at the event, or store the 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.

<Viewing execution event history>
Next, the execution event history viewing process will be described using FIGS. 39 to 45. FIGS. 39 and 40 are sequence diagrams showing execution event history viewing processing. FIG. 41 is a diagram showing a project list screen on a PC. FIG. 42 is a diagram showing an execution event list screen on the PC. FIGS. 43 and 44 are diagrams showing execution event history screens. FIG. 45 is a diagram showing an action item screen on the PC. Note that the processing in steps S111 to S117 in FIG. 39 is the same as the processing in steps S11 to S17 in FIG. 16, so a description thereof will be omitted.

When the user presses the "view execution event history" button 543 on the initial screen 540 shown in FIG. 18, the reception unit 52 accepts viewing of the execution event history (step S118).

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

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

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

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

Next, the transmitting/receiving unit 51 of the PC 5 transmits the project ID of the project selected in step S124 above to the schedule management server 8 (step S125). Thereby, the schedule management server 8 receives the project ID.

Next, in the schedule management server 8, the storage/read processing unit 89 reads out the corresponding execution event ID by searching the execution event history management DB 8008 using the project ID received in step S125 as a search key (step S126). ). In this case, the storage/read processing unit 89 reads all execution event IDs associated with the project ID received in step S125. Then, the storage/read processing unit 89 searches the execution event management DB 8009 using the execution event ID read out in step S126 as a search key, thereby reading out the corresponding execution event start/end information (step S127). 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.

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

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

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

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

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

Furthermore, the storage/reading processing unit 89 reads content data indicating the contents of the execution event history from the storage location of the content data indicating the contents of the execution event history read out in step S133 (step S135). Further, the storage/read processing unit 89 reads action item data indicating data related to correspondence to the action item from the content data indicating the contents of the execution event history read out in step S133 (step S136). Then, the transmitting/receiving unit 81 transmits the read related information, content data, and action item data to the PC 5 (step S137). Thereby, the transmitting/receiving unit 51 of the PC 5 receives the related information, content data, and action item data.

Next, the sound control unit 58 of the schedule management server 8 sets the playback location of the sound data, which is the content data received in step S137 (step S138). In this case, the sound control unit 58 sets, among the received related information, the playback location corresponding to the sound data associated with the content generation time zone "00:00" as the playback location of the sound data.

Next, the generation unit 56 of the PC 5 generates an execution event history screen 580 as shown in FIG. 43 using the related information and content data received in step S137 (step S139). More specifically, the generation unit 56 generates an execution event to display images related to text data, which is received content data, in the text data display area 582 in the order of sequence numbers included in the received related information. A history screen 580 is generated. The generation unit 56 also generates the execution event history screen 580 so as to display images related to the screen data, which is the received content data, in the snapshot display area 583 in the order of the sequence numbers included in the received related information. generate. Furthermore, the generation unit 56 generates the execution event history screen 580 so that the playback point 581p included in the playback location display area 581 is displayed at the position related to the sound data set in step S138 during the entire playback time of the sound data. generate.

Then, the display control unit 54 of the PC 5 causes the execution event history screen 580 generated by the generation unit 56 to be displayed on the display 508 (step S140). Further, the sound control unit 58 of the PC 5 plays back the sound data at the playback location set in step S138. As shown in FIG. 43, the execution event history screen 580 shows content data generated by executed events for each type of content processing. The execution event history screen 580 includes a playback part display area 581 that displays the playback part of recorded data, a text data display area 582 that displays audio text, a snapshot display area 583 that displays snapshots, and a case where action items are viewed. "Action item" button 584, which is pressed when viewing the materials used in the event, "Material file" button 585, which is pressed when viewing the materials used in the event, and "Pagination" button, which is pressed when displaying the pagination display area 589, which will be described later. Button" 588 is included.

Here, the playback point display area 581 includes a playback point 581p indicating the playback point in the total playback time, a slider 581b indicating the playback history (playback process) of the recorded data, and a playback time display image indicating the playback time in the total playback time. 581t is included. Further, the playback point 581p and the slider 581b constitute a seek bar. The seek bar is an operation area that displays the playback location of the recorded data and also specifies the playback location of the recorded data. The user can visually grasp which part of the recorded data is being played back from the beginning to the end by the position of the playback point 581p and the slider 581b. Furthermore, the user can move the playback point 581p using an input means such as the mouse 507, thereby playing back the recorded data from any playback location. The playback point 581p is an example of a playback location specific image. Further, a seek bar including a playback point 581p and a slider 581b is an example of a playback history display image.

Further, in the text data display area 582, text data 582a, 582b, 582c, 582d, and 582e are displayed in chronological order from top to bottom. Similarly, in the snapshot display area 583, snapshot (captured) images 583a, 583b, and 583c are displayed in chronological order from top to bottom. In this way, the text data display area 582 and the snapshot display area 583 are displayed in parallel in chronological order. As a result, by viewing the image 583b, for example, the user can easily grasp the time period in which the pie chart was explained at the meeting. 582c and 582d can be easily found. In this case, images 583a and 583b are snapshot images of the entire display 220. Further, the image 583c is an image of the action item subjected to image recognition (snapshot) in step S71-2.

Further, FIG. 44 shows an image displayed on the display 508 when the user presses the "Pagination" button 588 shown in FIG. 43. Here, "Pagination" is a navigation provided for moving between pages when information is developed or divided into multiple pages. For example, in the case of a web page, "pagination" refers to dividing a page with a lot of content into multiple pages and arranging links to each page. Using pagination makes it easier for users to access and understand which page they are viewing. Note that "pagination" is also referred to as "page division," "page turning," "paging," and "pager."

When the user presses the "Pagination" button 588, the reception unit 52 accepts the press of the "Pagination" button 588. Thereby, the display control unit 54 displays a pagination display area 589 at the bottom of the execution event history screen 580, as shown in FIG. This pagination display area 589 shows, for example, the time period in which content occurs in an event such as a conference (here, every 5 minutes), and the same time period as the time of the playback part of the playback point 581p is displayed. (Elapsed time display area 589j). Note that until the reception unit 52 receives the press of the "Pagination" button 588, the receiving unit 52 is in a waiting state for the press.

Thereby, the shared system 1 can easily share execution event history caused by events belonging to the same project among members belonging to the same project. In addition, the shared system 1 allows users to view the execution event history managed for each project by registering or changing members belonging to the project using the project registration screen 520 displayed on the PC 5. Additionally, processing such as viewing settings for each executed event can be omitted.

<Action item viewing process>
Next, a process for viewing action items generated by an executed event will be described using FIGS. 45 to 58. FIG. 45 is a sequence diagram showing the action item screen display process. FIG. 46 is a diagram showing an action item screen on the PC.

When the user presses the "action item" button 584 on the execution event history screen 580 shown in FIG. 43 or 44, the reception unit 52 of the PC 5 accepts the selection of the "action item" button 584 (step S401). .

Next, the generation unit 56 of the PC 5 generates an action item screen 710 as shown in FIG. 46 using the action item data received in step S137 (step S402). Then, the display control unit 54 of the PC 5 displays the action item screen 710 generated by the generation unit 56 on the display 508 (step S403). As shown in FIG. 46, the action item screen 710 shows action item data for each action item, including data on a plurality of items related to responses to action items generated by executed events. . The action item screen 710 includes, for example, information indicating the content of the action item, the person in charge of responding to the action item (executor), the deadline for completing the action item, and the status of responding to the action item as action item data. It is shown. The content of the action item is the image data of the action item subjected to image recognition (snapshot) in step S71-2.

The action item screen 710 also includes a person-in-charge selection button 711 that is pressed to select the person in charge, a deadline date selection button 713 that is pressed to select the deadline date, and a selection button 713 to select the state of response to the action item. A response state selection button 715 is pressed to change the response state to each action item, and response state change buttons 716a to 716f are pressed to change the response state to each action item (hereinafter, if there is no need to differentiate, the response state change button is pressed) 716), a link button 717 that is pressed when registering created data (output) created in response to an action item, and a search for action item data using a keyword entered in an input area 718a. A search button 718 that is pressed when closing the action item screen 710, a "close" button 719 that is pressed when closing the action item screen 710, and a mouse pointer 720 are included.

On the action item screen 710 shown in FIG. 46, a list of the plurality of action item data received in step S137 is displayed in a viewable manner. In addition, the person in charge selection button 711, deadline date selection button 713, and response status selection button 715 are pressed to rearrange the plurality of action item data displayed on the action item screen 710 according to the content of each item. This is a sort button. The person in charge selection button 711, the deadline date selection button 713, and the response status selection button 715 are examples of the first selection image.

(Switching the display of action item screen)
Here, a process for switching the display of the action item screen 710 displayed on the PC 5 will be described using FIGS. 47 to 58. First, a process for rearranging the action item data displayed on the action item screen 710 according to the expiration date will be described using FIGS. 47 and 48. FIG. 47 is a flowchart showing a process for rearranging action item data according to the deadline date. FIG. 48 is a diagram showing an action item screen in which action item data is sorted in order of deadline date.

First, in FIG. 47, when the user uses the mouse pointer 720 to press the deadline date selection button 713 on the action item screen 710 shown in FIG. (Step S411).

Next, the generation unit 56 of the PC 5 rearranges the plurality of action item data included in the action item screen 710 in descending order of deadline date (step S412). Specifically, the generation unit 56 extracts the data of the expiration date item included in the plurality of action item data received in step S137, and sets the action item data to the expiration date according to the extracted expiration date data. Sort by earliest. Then, the display control unit 54 of the PC 5 displays the action item screen 710a generated by the generation unit 56 on the display 508 (step S413).

FIG. 48 shows an action item screen 710a displayed on the display 508 in step S413. The action item screen 710a shown in FIG. 48 shows a state in which the deadline date selection button 713 is pressed by the mouse pointer 720. The plurality of action item data shown on the action item screen 710a are sorted in descending order of deadline date. In this way, by receiving the selection of the deadline date selection button 713 by the reception unit 52, the PC 5 can rearrange and display the action item data in descending order of deadline date. Therefore, the PC 5 can, for example, allow the user to preferentially confirm the content of an action item whose deadline is approaching and needs to be dealt with quickly. Note that the PC 5 may be configured to have the reception unit 52 accept a selection of the deadline date selection button 713, and then rearrange and display the action item data in descending order of deadline date.

Next, a process of rearranging the action item data displayed on the action item screen 710 according to the state of correspondence to the action item will be described with reference to FIGS. 49 and 50. FIG. 49 is a flowchart showing a process for rearranging action item data according to correspondence status. FIG. 50 is a diagram showing an action item screen in which action item data is sorted by correspondence state.

First, in FIG. 49, when the user uses the mouse pointer 720 to press the support state selection button 715 on the action item screen 710 shown in FIG. (Step S421).

Next, the generation unit 56 of the PC 5 sorts the plurality of action item data included in the action item screen 710 by corresponding state (step S422). Specifically, the generation unit 56 extracts data of items in a compatible state included in the plurality of action item data received in step S137, and converts the action item data into a compatible state according to the extracted data in a compatible state. Sort by. For example, the generation unit 56 rearranges the action item data so that data indicating a state in which a response to the action item is required, such as a response state of "ToDo" or "Doing", is displayed at the top. On the other hand, the generation unit 56 rearranges the action item data so that data indicating a state in which the response to the action item is not required (has been handled), such as a response status of "Done", is displayed at the bottom. Then, the display control unit 54 of the PC 5 displays the action item screen 710b generated by the generation unit 56 on the display 508 (step S423).

FIG. 50 shows the action item screen 710b displayed on the display 508 in step S423. The action item screen 710b shown in FIG. 50 shows a state in which the corresponding state selection button 715 is pressed by the mouse pointer 720. The plurality of action item data shown on the action item screen 710b are sorted by corresponding state. In this case, the action item screen 710b displays the action item data sorted in the order of correspondence status "ToDo", "Doing", and "Done". In this manner, the PC 5 can display the action item data sorted by the corresponding state by receiving the selection of the corresponding state selection button 715 by the reception unit 52. Therefore, the PC 5 can, for example, allow the user to preferentially confirm the contents of action items that require response. Note that the display format of the correspondence status such as "ToDo", "Doing", and "Done" is not limited to this. Further, the PC 5 may be configured not to display action item data for which response has been completed (for example, action item data whose response status is "Done") on the action item screen 710b.

Next, a process for changing the correspondence state of action item data displayed on the action item screen 710 will be described using FIGS. 51 and 56. FIG. 51 is a sequence diagram showing the processing for changing the correspondence status. FIG. 52 is an example of a screen when the correspondence status change button is selected. FIG. 53 is an example of a screen showing a state candidate list. FIG. 54 is a diagram showing an action item screen in which the corresponding state has been changed. FIG. 55 is an example of a screen when the link button is selected. FIG. 56 is an example of a screen showing a registration screen for created data.

First, in FIG. 51, when the user uses the mouse pointer 720 to press the change correspondence state button 716 on the action item screen 710c-1 as shown in FIG. 716 is accepted (step S431). The correspondence status change button 716 is an example of the second selection image. The action item screen 710c-1 shown in FIG. 52 shows a state in which the change correspondence state button 716a is selected.

Next, the display control unit 54 displays the state candidate list 721 on the action item screen 710c-2, as shown in FIG. 53 (step S432). The status candidate list 721 includes a check box to be pressed to select the changed compatible status, an "OK" button 721a to be pressed to change the compatible status, and an "OK" button 721a to be pressed to cancel (end) the change process. A "CANCEL" button 721b is included. Then, when the user uses the mouse pointer 720 to select the check box of the changed support state and selects the "OK" button 721a, the reception unit 52 accepts the selection of the changed support state (step S433 ). The action item screen 710c-2 shown in FIG. 53 shows a state in which "Done" is selected as the changed response state.

Then, the display control unit 54 displays an action item screen 710c-3 as shown in FIG. 54 on the display 508 (step S424). As shown in FIG. 54, on the action item screen 710c-3, the correspondence state of the action item data corresponding to the correspondence state change button 716a has been changed from "ToDo" to "Done". In this way, the PC 5 can change the correspondence state of specific action item data by receiving input from the specific correspondence state change button 716 through the reception unit 52.

Next, when the user uses the mouse pointer 720 to press the link button 717 on the action item screen 710c-4 as shown in FIG. 55, the reception unit 52 accepts the selection of the link button 717 (step S435). . The action item screen 710c-4 shown in FIG. 55 shows a state in which the link button 717a corresponding to the action item data whose correspondence state has been changed is selected.

Next, as shown in FIG. 56, the display control unit 54 displays a registration screen 723 on the action item screen 710c-5 for registering creation data (apput) created in response to the action item. is displayed (step S436). The registration screen 723 includes an input area 723a for entering the URL of the save destination of the created data, an "attach" button 723b that is pressed when attaching a data file of the created data, and an "attach" button 723b that is pressed when registering the created data. This includes a "Register" button 723c to cancel (end) the registration process, and a "CANCEL" button 723d to be pressed to cancel (end) the registration process. Then, when the user uses the mouse pointer 720 to input into the input area 723a or registers a data file using the "Attach" button 723b, and selects the "Register" button 723c, the reception unit 52 receives the created data. Registration is accepted (step S437).

Next, the transmitting/receiving unit 51 of the PC 5 transmits action item data including the response state changed by the process of step S433 and the creation data accepted by the process of step S437 to the schedule management server 8 (step S438). Thereby, the transmitting/receiving unit 81 of the schedule management server 8 receives the action item data transmitted from the PC 5. Then, the storage/read processing unit 89 of the schedule management server 8 updates the action item data by storing the action item data received in step S438 in the action item management DB 8011 (step S439). Thereby, the schedule management server 8 manages the action item data in which the response to the action item has been completed and the creation data has been registered. In this way, the PC 5 can register the created data created in response to the action item in the schedule management server 8 as an output. Therefore, the PC 5 can prevent a situation in which the result (output) for the action item is not known even though the response to the action item has been completed (the response status is "Done"). Note that if there is no need to register the output to the action item, the processes of steps S435 to S437 are omitted.

Next, a process of sorting the action item data displayed on the action item screen 710 according to the person in charge of responding to the action item will be described using FIGS. 57 and 58. FIG. 57 is a flowchart showing a process of sorting action item data according to the person in charge. FIG. 58 is a diagram showing an action item screen in which action item data is sorted by person in charge.

First, in FIG. 57, when the user uses the mouse pointer 720 to press the person in charge selection button 711 on the action item screen 710 shown in FIG. (Step S441).

Next, the generation unit 56 of the PC 5 sorts the plurality of action item data included in the action item screen 710 by person in charge (step S442). Specifically, the generation unit 56 extracts the data of the item of the person in charge (the person who executes the action item) included in the plurality of action item data received in step S137, and generates the data according to the extracted response state data. , sort the action item data by person in charge. For example, the generation unit 56 sorts the action item data in descending order of the number of associated action items. Then, the display control unit 54 of the PC 5 displays the action item screen 710d generated by the generation unit 56 on the display 508 (step S443).

FIG. 58 shows an action item screen 710d displayed on the display 508 in step S443. The action item screen 710d shown in FIG. 58 shows a state in which the person-in-charge selection button 711 is pressed by the mouse pointer 720. The plurality of action item data shown on the action item screen 710d are sorted by person in charge. In this case, on the action item screen 710d, the action item data is displayed in the order in which the persons in charge are "Goro Kondo," "Jim Berger," and "Yoshio Yamashita." In this way, the PC 5 can rearrange and display the action item data by the person in charge by accepting the selection of the person in charge selection button 711 by the reception unit 52. Therefore, the PC 5 can, for example, allow the user to confirm the contents of action items that the user himself/herself needs to respond to all at once. Note that the PC 5 may be configured to have the reception unit 52 accept a selection of the person in charge selection button 711, and then rearrange and display the action item data in descending order of the person in charge with fewer associated action items. In addition, when the reception unit 52 accepts the input of the person in charge name in the input area 718a included in the action item screen 710 and the selection of the search button 718, the PC 5 displays the person in charge input in the input area 718a at the top. The configuration may be such that the action item data is rearranged and displayed as shown in FIG.

As described above, the PC 5 can rearrange and display action item data according to items related to responses to action items. Therefore, the user of the PC 5 can easily find the action item that he or she wants to check.

In addition, in the above explanation, an example was explained in which action item data is sorted and displayed according to the content of each item, but the PC 5 uses the reception unit 52 to select each selection button (person in charge selection button 711, deadline date selection The action item data may be filtered by accepting a selection of the button 713 or the corresponding state selection button 715). In this case, the person in charge selection button 711, the deadline date selection button 713, and the response status selection button 715 are filter buttons that switch multiple action item data displayed on the action item screen 710 according to the content of each item. .

Further, in the above description, an example was explained in which action items associated with a specific project ID and execution event ID are displayed, but the PC 5 can display other project IDs or execution event IDs registered in the schedule management server 8. The configuration may be such that the action item associated with the action item is displayed on the action item screen 710. For example, in the execution event list screen 570 shown in FIG. are displayed in a list on the action item screen 710.

<<Main effects of the embodiment>>
According to this embodiment, as shown in FIGS. 45 to 58, the PC 5 (an example of a display terminal) has a schedule management server 8 (an example of a management system) that manages action items that occur in executed events. ) is a display terminal that can communicate with Further, the transmitting/receiving unit 51 (an example of a receiving unit) of the PC 5 receives action item data including data of a plurality of items related to responses to the action item from the schedule management server 8, and the display control unit 54 (an example of a display control unit) In one example), an action item screen 710 (an example of a display screen) including a list of a plurality of received action item data is displayed on the display 508 (an example of a display unit), and the reception unit 52 (an example of a reception means) On the action item screen 710, a selection of a first selection image (eg, person in charge selection button 711, deadline date selection button 713, or response state selection button 715) for a specific item among a plurality of items is accepted. Then, when the selection for the first selection image is accepted, the display control unit 54 rearranges and displays the plurality of action item data included in the action item screen 710 according to the content of the data of the specific item. . Thereby, the user of the PC 5 can easily find the action item that he or she wants to check.

Further, according to the present embodiment, as shown in FIGS. 45 to 58, action item data included in the action item screen 710 (an example of a display screen) is an action item that occurred in an event being executed. Contains image data generated by the event that shows the content of the event. Thereby, the user of the PC 5 can easily understand the contents of the action item by checking the action item screen 710.

Further, according to the present embodiment, as shown in FIGS. 45 to 58, the action item screen 710 (an example of a display screen) displays created data created in response to an action item on the schedule management server. 8 (an example of a management system) includes a link button 717 (an example of a registration image). Thereby, the PC 5 can prevent a situation in which the result (output) for the action item is not known even though the response to the action item has been completed (the response status is "Done"). .

Further, according to the present embodiment, as shown in FIGS. 45 to 58, the display control unit 54 (an example of display control means) of the PC 5 (an example of a display terminal) If the selection for the first selection image (an example of the first selection image) is accepted, a plurality of action item data included in the action item screen 710 (an example of a display screen) are sorted and displayed by corresponding state. Thereby, the PC 5 can, for example, have the user confirm the contents of the action item that needs to be dealt with preferentially.

Further, according to the present embodiment, as shown in FIGS. 45 to 58, the reception unit 52 (an example of a reception means) of the PC 5 (an example of a display terminal) displays an action item screen 710 (an example of a display screen). ), the display control unit 54 (an example of a display control means) , when the selection of the corresponding state change button 716 is accepted, an action item screen 710c-3 (an example of a display screen) in which the corresponding state of the specific action item has been changed is displayed. Thereby, the user of the PC 5 can, for example, change the display of the response status of the action item for which response has been completed.

Further, according to the present embodiment, as shown in FIGS. 45 to 58, the display control unit 54 (an example of display control means) of the PC 5 (an example of a display terminal) If the selection for the first selection image (an example of the first selection image) is accepted, a plurality of action item data included in the action item screen 710 (an example of a display screen) are sorted and displayed in descending order of deadline date. Thereby, the PC 5 can, for example, allow the user to preferentially confirm the content of an action item whose deadline is approaching and needs to be dealt with quickly.

Further, according to the present embodiment, as shown in FIGS. 45 to 58, the display control unit 54 (an example of a display control means) of the PC 5 (an example of a display terminal) has a person-in-charge selection button 711 (an example of a display control means). If the selection for the first selection image (an example of the first selection image) is accepted, a plurality of action item data included in the action item screen 710 (an example of a display screen) are sorted by person in charge and displayed. Thereby, the PC 5 can, for example, allow the user to confirm all the contents of action items that the user himself/herself needs to respond to.

＜＜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)
5 PC (an example of display terminal)
6 Shared support server 8 Schedule management server (an example of a management system)
9 Speech-to-text conversion server 10 Communication network 21 Transmission/reception section 22 Reception section 24 Display control section 29 Storage/reading processing section 51 Transmission/reception section (an example of receiving means)
52 Reception Department (an example of reception means)
53 Display control unit (an example of display control means)
508 Display (example of display part)
710, 710a, 710b, 710c, 710d Action item screen (example of display screen)
711 Person in charge selection button (an example of the first selection image)
713 Deadline date selection button (an example of the first selection image)
715 Compatible state selection button (an example of the first selection image)
716 Compatibility status change button (an example of the second selection image)
81 Transmitting/receiving unit (an example of transmitting means)

JP2016-105241A JP 2018-32097 Publication

Claims (12)

A display terminal capable of communicating with a management system that manages action items that occur in an executed event,
receiving means for receiving action item data including data on a plurality of items related to responses to the action item from the management system;
A display screen containing a list of the plurality of received action item data, an input area for inputting the save destination of the created data created in response to the action item , and a button to press when attaching the created data. display control means for displaying on a display unit a registration screen for registering the created data in the management system, including an attachment button to be displayed;
On the display screen, the selection of the first selected image in a specific item among the plurality of items is accepted, and on the registration screen, the input to the storage destination entered in the input area or the creation using the attachment button is accepted. a reception means for accepting registration of the created data for data attachment ;
When the selection for the first selection image is accepted, the display control means rearranges and displays the plurality of action item data included in the display screen according to the content of the data of the specific item. Display terminal. 2. The display terminal according to claim 1, wherein the action item data includes image data generated by an event that is being executed and indicates the contents of the action item that occurred in the event. The data of the specific item indicates the state of response to the action item, and when the selection for the first selection image is accepted, the display control means controls the display of the plurality of action items included in the display screen. The display terminal according to claim 1 or 2, wherein the action item data that requires the response is displayed at the top of the data. When the selection for the first selection image is accepted, the display control means causes the action item data for which the response has been completed to be displayed at the bottom of the plurality of action item data included in the display screen. The display terminal according to item 3. The accepting means accepts a selection for a second selection image included in the display screen for changing the corresponding state of a specific action item,
5. The display terminal according to claim 3, wherein when the selection of the second selection image is accepted, the display control means displays the display screen in which the correspondence state of the specific action item has been changed. The data of the specific item indicates a deadline date for responding to the action item;
5. When the selection of the first selection image is accepted, the display control means rearranges and displays the plurality of action item data included in the display screen in descending order of the deadline date. A display terminal according to any one of the above. The data of the specific item indicates a person in charge of responding to the action item,
7. When the selection of the first selection image is accepted, the display control means causes the plurality of action item data included in the display screen to be displayed after being sorted by person in charge. The display terminal described in paragraph 1. 8. The first selection image is a sort button for sorting the plurality of action item data included in the display screen according to the content of the specific item. Display terminal. The display according to any one of claims 1 to 8, wherein the first selection image is a filter button that switches the plurality of action item data to be displayed on the display screen according to the content of the specific item. terminal. A shared system comprising the display terminal according to any one of claims 1 to 9 and the management system,
The management system includes:
A shared system comprising transmitting means for transmitting the action item data to the display terminal. A display control method executed by a display terminal capable of communicating with a management system that manages action items that occur in an executed event, the method comprising:
a receiving step of receiving action item data including data on a plurality of items related to responses to the action item from the management system;
A display screen containing a list of the plurality of received action item data, an input area for inputting the save destination of the created data created in response to the action item , and a button to press when attaching the created data. a first display control step of displaying on a display unit a registration screen for registering the created data to the management system, including an attachment button to be displayed;
On the display screen, the selection of the first selected image in a specific item among the plurality of items is accepted, and on the registration screen, the input to the storage destination entered in the input area or the creation using the attachment button is accepted. a reception step of accepting registration of the created data for data attachment ;
If the selection of the first selection image is accepted, a second display control step of rearranging and displaying the plurality of action item data included in the display screen according to the content of the data of the specific item; and,
Display control method to perform. A program that causes a computer to execute the method according to claim 11.