JP7490978B2 - Information processing system, information processing device, program, and information processing method - Google Patents

Description

The present invention relates to an information processing system, an information processing device, a program, and an information processing method.

Conventionally, there have been known conference support systems that present documents to participants during a conference without each user having to carry a device that stores document files that are needed as reference information at each stage of the conference. In conventional conference support systems, the server records the fact that documents have been handed over, making it possible to perform information searches using the situation and context of the conference as keys (see, for example, Patent Document 1).

The meeting support system described in Cited Document 1 performs information searches using the status and context of a meeting as a key by having a server record the fact of document delivery. However, conventional meeting support systems do not perform analysis of meetings, such as whether unnecessary meetings are being held, whether meetings that are a nuisance to others are being held, or whether meetings are being held using secure and easily shared files.

The object of the embodiment of the present invention is to provide an information processing system capable of analyzing meetings using electronic devices.

In order to achieve the above-mentioned object, claim 1 of the present application provides an information processing system including an electronic device used in a conference, and an information processing device that performs analysis on the conference using the electronic device, the electronic device including an input unit that receives input in the conference using the electronic device from a user participating in the conference, a participant management unit that manages participants in the conference using the electronic device, and a conference schedule setting unit that acquires schedule information of the participants from an external service using external service setting information associated with the participants, and selects a conference using the electronic device from the schedule information of the participants, and the information processing device manages usage information of the electronic device in response to the input by the user in the conference. The system comprises a usage information management unit, a report information management unit that classifies meetings using the electronic device according to usage information of the electronic device and manages the classified results in order to present them, and a report site unit that displays the results classified by the report information management unit on the screen of a communicatively connected information processing terminal, wherein the usage information management unit manages the operation of selecting a meeting using the electronic device from the participant's schedule information as usage information of the electronic device, and the report information management unit classifies the meetings using the electronic device into meetings selected from the participant's schedule information and meetings not selected from the participant's schedule information, and manages the classified results in order to display them on the screen of the information processing terminal .

According to an embodiment of the present invention, it is possible to analyze meetings using electronic devices.

1 is a diagram illustrating an example of a configuration of an information processing system according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a hardware configuration of a computer according to the present embodiment. FIG. 2 is a diagram illustrating a hardware configuration of an example of an electronic whiteboard device according to the present embodiment. 1 is a functional configuration diagram of an example of an information processing system according to an embodiment of the present invention. FIG. 4 is a diagram illustrating an example of account information. FIG. 2 is a diagram illustrating an example of schedule information. FIG. 13 is a diagram illustrating an example of a user information list. FIG. 11 is a diagram illustrating an example of external service setting information. FIG. 13 is a diagram illustrating an example of electronic whiteboard usage information. FIG. 11 is a diagram illustrating an example of report information. FIG. 4 is a diagram illustrating an example of device attribute information. FIG. 13 is a diagram illustrating an example of a participant management information list. 1 is an external view of an electronic whiteboard device according to an embodiment; 1 is a flowchart illustrating an example of a flow of a meeting using an electronic whiteboard device. 13 is a flowchart illustrating an example of a participant addition reception process. 13 is a flowchart of an example of a process for selecting a schedule. 13 is a flowchart of an example of a sharing site selection process. 13 is a flowchart of an example of a process of reading from a sharing site. 13 is a flowchart of an example of a process for saving to a shared site. 1 is a flowchart illustrating an example of a flow of a meeting using an electronic whiteboard device. 11 is a flowchart of an example of a process for outputting a PC screen. FIG. 13 is an image diagram of an example of a UI displayed on the electronic whiteboard device. FIG. 13 is an image diagram of an example of a UI displayed on the electronic whiteboard device. FIG. 13 is an image diagram of an example of a UI displayed on the electronic whiteboard device. FIG. 13 is an image diagram of an example of a UI displayed on the electronic whiteboard device. 13 is a flowchart of an example of a process for authenticating and setting a host. 13 is a flowchart of an example of a process for obtaining and proposing a schedule. 13 is a flowchart of an example of a process for proposing a schedule. 13 is a flowchart illustrating an example of a process for adding a scheduled attendee to participant management information. 11 is a flowchart of an example of a process for connecting to a remote service. FIG. 13 is an image diagram of an example of a save notification email. 13 is a flowchart of an example of a process for updating electronic whiteboard usage information. 13 is a flowchart of an example of a process for updating report information. 13 is a flowchart of an example of a process for displaying a report site. FIG. 13 is an image diagram of an example of a report site screen. FIG. 13 is an image diagram of an example of a report site screen. FIG. 13 is an image diagram of an example of a report site screen. FIG. 13 is an image diagram of an example of a report site screen. FIG. 13 is an image diagram of an example of a report site screen. FIG. 13 is an image diagram of an example of a report site screen. FIG. 13 is an image diagram of an example of a report site screen. FIG. 13 is an image diagram of an example of a report site screen.

The following describes an embodiment of the present invention with reference to the drawings. In this embodiment, an example of a conference using an electronic whiteboard device is described. Note that a conference in this embodiment is a situation in which related parties gather to explain a specific purpose and exchange opinions, and includes various situations such as seminars and lectures that use electronic devices such as electronic whiteboard devices and projectors.

[First embodiment]
<System Configuration>
Fig. 1 is a configuration diagram of an example of an information processing system according to the present embodiment. In the information processing system 1 shown in Fig. 1, a user information server device 10, an external service group system 12, an electronic whiteboard device 14, a PC 15, a remote service server device 16, a usage information accumulation server device 17, and a report server device 18 are communicatively connected via a network 19 such as the Internet or a LAN.

The user information server device 10, the electronic whiteboard device 14, the usage information storage server device 17, and the report server device 18 constitute an electronic whiteboard system. The electronic whiteboard system provides functions related to the electronic whiteboard device 14 by operating in conjunction with an external service group system 12 outside the electronic whiteboard system.

The electronic whiteboard system also provides functions related to remote conferencing by working in conjunction with a remote service server device 16 external to the electronic whiteboard system. A remote conference is a conference, such as a web conference, in which video and audio are exchanged and materials are shared using an electronic whiteboard device 14 or a PC 15 that can be connected to a network 19, and is sometimes called a remote service or remote connection.

The external service group provided by the external service group system 12 refers to an integrated service such as Office365 (registered trademark) that is composed of, for example, a user service, a shared site service, an email service, and a schedule service (calendar service). The external service group is provided in a form in which services such as a user service, a shared site service, an email service, and a schedule service can be used with the same user account. The external service group provided by the external service group system 12 is also called groupware, and each service belonging to the same external service group can be used with the same authentication information (a combination of ID and password, an access token, etc.). These external service groups may be different for each user, and there may be one or more. The external service group system 12 is realized by one or more computers.

The user information server device 10 stores the user information list and external service setting information described below, and is used by the external service group system 12 or the electronic whiteboard device 14. The user information server device 10 may be shared by multiple electronic whiteboard devices 14, and does not have to be on the same network segment. The user information server device 10 may also be built into the electronic whiteboard device 14. The user information server device 10 is realized by one or more computers.

The electronic whiteboard device 14 is used in conferences attended by multiple users. The electronic whiteboard device 14 displays images drawn, for example, with an electronic pen or by hand. The electronic whiteboard device 14 can also display images from electronic files read from a USB memory, a PC connected via a cable, or the external service group system 12. Furthermore, the electronic whiteboard device 14 can also display images captured by a camera.

The electronic whiteboard device 14 can participate in a remote conference by connecting to the remote conference destination. The electronic whiteboard device 14 can remotely share image data and audio data between multiple devices participating in the remote conference, such as other electronic whiteboard devices, PCs, and smart devices. The electronic whiteboard device 14 is an example, and may be any electronic device that has a remote sharing function, such as a terminal, display, or projector of a remote conference system. The electronic whiteboard device 14 is an example of an electronic device used in a conference.

PC15 is an example of an information processing terminal, and is an example of a device that can participate in a remote conference by connecting to a remote conference destination. Note that information processing terminals that can participate in a remote conference may be PCs, smartphones, tablet terminals, etc.

The remote service server device 16 provides a remote conference service. The remote conference service allows devices connected to a remote conference destination to remotely share image data and audio data, allowing a remote conference to be held. For example, the remote service server device 16 allows devices such as an electronic whiteboard device 14 and a PC 15 connected to the same remote conference destination to hold a remote conference.

The usage information storage server device 17 receives usage information of the electronic whiteboard device 14 by the participants in the meeting from the electronic whiteboard device 14 and manages it. The report server device 18 classifies (groups, divides) the meetings by characteristics such as trend, type, and variety according to the usage information of the electronic whiteboard device 14 managed by the usage information storage server device 17, and manages report information including the results of the classification. The report server device 18 generates image data of a report site screen, described below, that presents the report information, and displays the report site screen on the user's information processing terminal. Note that in this embodiment, "classification" refers to grouping similar items according to a certain criterion and dividing the whole into several groups, and is not limited to the word "classification".

The configuration of the information processing system 1 in FIG. 1 is an example. For example, at least some of the functions of the user information server device 10, the external service group system 12, the remote service server device 16, the usage information accumulation server device 17, and the report server device 18 may be provided in the electronic whiteboard device 14. The information processing system 1 in FIG. 1 may have at least some of the functions of the user information server device 10, the external service group system 12, the electronic whiteboard device 14, the remote service server device 16, the usage information accumulation server device 17, or the report server device 18 in information processing devices other than the user information server device 10, the external service group system 12, the electronic whiteboard device 14, the remote service server device 16, the usage information accumulation server device 17, and the report server device 18.

<Hardware Configuration>
"Computer"
The user information server device 10, the external service group system 12, the PC 15, the remote service server device 16, the usage information accumulation server device 17, and the report server device 18 shown in Fig. 1 are realized, for example, by a computer 500 having a hardware configuration shown in Fig. 2. Fig. 2 is a diagram showing an example of the hardware configuration of a computer according to this embodiment.

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

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

The display 506 displays various information such as a cursor, a menu, a window, characters, or an image. The external device connection I/F 508 is an interface for connecting various external devices. In this case, the external devices are, for example, a USB (Universal Serial Bus) memory or a printer. The network I/F 509 is an interface for data communication using the network 19. The data bus 510 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 501.

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

Electronic whiteboard device
3 is a hardware configuration diagram of an example of an electronic whiteboard device according to the present embodiment. As shown in FIG. 3, the electronic whiteboard device 14 includes a CPU 601, a ROM 202, a RAM 603, an SSD (Solid State Drive) 604, a network I/F 605, and an external device connection I/F 606.

Of these, the CPU 601 controls the overall operation of the electronic whiteboard device 14 according to a program. The ROM 602 stores the CPU 601 and programs used to drive the CPU 601, such as the IPL. The RAM 603 is used as a work area for the CPU 601. The SSD 604 stores various data, such as programs for the electronic whiteboard device 14.

The network I/F 605 controls communication with the network 19. The external device connection I/F 606 is an interface for connecting various external devices. In this case, the external devices are, for example, a USB memory 630 and external devices (a microphone 640, a speaker 650, and a camera 660).

The electronic whiteboard device 14 also includes a capture device 611, a GPU 612, a display controller 613, a contact sensor 614, a sensor controller 615, an electronic pen controller 616, an IC card reader 617, a short-range communication circuit 619, an antenna 619a of the short-range communication circuit 619, a power switch 622, and selection switches 623.

Of these, the capture device 611 displays video information as still images or moving images on the display of the external PC 670. The GPU (Graphics Processing Unit) 612 is a semiconductor chip that specializes in graphics. The display controller 613 controls and manages the screen display in order to output the output image from the GPU 612 to the display 680, etc.

The contact sensor 614 detects contact of the electronic pen 690, the user's hand H, or the like on the display 680. The sensor controller 615 controls the processing of the contact sensor 614. The contact sensor 614 inputs and detects coordinates using an infrared blocking method. The method of inputting and detecting coordinates is that two light receiving and emitting devices installed at both ends of the upper side of the display 680 emit multiple infrared rays parallel to the display 680, and receive the light that is reflected by a reflecting member installed around the periphery of the display 680 and returns along the same optical path as the optical path of the light emitted by the light receiving element.

The contact sensor 614 outputs the ID of the infrared light emitted by the two light receiving and emitting devices that was blocked by the object to the sensor controller 615, and the sensor controller 615 identifies the coordinate position that is the contact position of the object. The electronic pen controller 616 communicates with the electronic pen 690 to determine whether the tip or the end of the pen has touched the display 680.

The IC card reader 617 wirelessly reads identification information unique to the IC card 700 from the RF tag embedded in the IC card 700. The IC card reader 617 may be built into the electronic whiteboard device 14 or may be externally attached to the electronic whiteboard device 14. The IC card 700 may be built into a smart device such as a smartphone. The electronic whiteboard device 14 may use something other than the IC card reader 617 as long as it can obtain identification information that can identify the user, and may use a biometric authentication device (fingerprint, palm print, iris, face, etc.) or a barcode reader, etc.

The short-range communication circuit 619 is a communication circuit such as NFC or Bluetooth (registered trademark). The power switch 622 is a switch for switching the power of the electronic whiteboard device 14 on and off. The selection switches 623 are, for example, a group of switches for adjusting the brightness and color of the display 680.

Furthermore, the electronic whiteboard device 14 is equipped with a bus line 610. The bus line 610 is an address bus, a data bus, etc., for electrically connecting each component such as the CPU 601 shown in FIG. 3.

The contact sensor 614 is not limited to an infrared blocking type, and may use various detection means such as a capacitive touch panel that identifies the contact position by detecting a change in capacitance, a resistive film touch panel that identifies the contact position by a voltage change between two opposing resistive films, or an electromagnetic induction touch panel that identifies the contact position by detecting electromagnetic induction caused by a contacting object touching the display unit. The electronic pen controller 616 may also determine whether or not the tip and end of the electronic pen 690 have been touched, as well as the part of the electronic pen 690 that the user holds, or other parts of the electronic pen.

<Functional configuration>
The information processing system 1 according to the first embodiment is realized by, for example, the functional configuration shown in Fig. 4. Fig. 4 is a functional configuration diagram of an example of the information processing system according to the present embodiment. In the functional configuration of Fig. 4, configurations unnecessary for the description of the present embodiment are appropriately omitted.

The information processing system 1 in FIG. 4 includes a user information server device 10, an external service group system 12, an electronic whiteboard device 14, a PC 15, a remote service server device 16, a usage information accumulation server device 17, and a report server device 18. In FIG. 4, the external service group system "office.example.com" is shown as an example of the external service group system 12.

The external service group system 12 provides external services to users, such as a user service 30, a shared site service 32, a schedule service 34, and an email service 36. The user service 30 of the external service group system 12 stores account information, such as that shown in FIG. 5. FIG. 5 is a configuration diagram of an example of account information. As shown in FIG. 5, the user service 30 of the external service group system 12 stores a user ID, name, and email address as account information.

The schedule service 34 stores schedule information such as that shown in FIG. 6. FIG. 6 is a configuration diagram of an example of schedule information. The schedule service 34 registers and manages the user's planned activities and scheduled meetings using the schedule information in FIG. 6. As shown in FIG. 6, the schedule service 34 stores the schedule ID, plan name, plan type, schedule owner, start time and period, scheduled attendees, and remote service connection destination information as the schedule information. The plan ID is an example of plan identification information. The plan name is the name of the plan. The plan type is an example of information that distinguishes the plan as a user's planned activities and a user's scheduled meetings. The schedule owner is an example of information that identifies the user who owns the schedule information for that plan.

The start time and duration are an example of information that indicates the date and time when the event starts and the period from when the event starts to when it ends, and indicate the scheduled start time and scheduled end time (scheduled start and end times). Planned attendees are an example of information that indicates users who plan to attend (participate) in the event, and are an example of scheduled participants. The remote service connection destination information indicates the remote conference service and the connection destination for the remote conference, and is expressed, for example, by a https URL (Uniform Resource Locator) or a unique ID format.

In the remote service connection destination information "https://remoteservicea.com/meetingroom/134565" shown in the schedule information in FIG. 6, the domain part "remoteservicea.com" indicates the remote conference service, and the number string part "134565" indicates the connection destination. When the electronic whiteboard device 14 is connected to the connection destination "134565" of the remote conference service "remoteservicea.com", other electronic whiteboard devices and PC 15 can connect to the connection destination "134565" of the same remote conference service "remoteservicea.com" to hold a remote conference between devices connected to that remote conference destination.

The shared site service 32 provides a site (shared site) that is shared (used jointly) by multiple users. On the shared site, users can load/save files. In addition, shared sites can be created for each purpose. On a shared site, multiple users working for the same purpose (multiple users working in a group) can load/save files on the same shared site. Note that while an example of the shared site service 32 is shown in FIG. 4, a storage service may also be used.

The mail service 36 manages the email addresses of each user in the external service group system 12 and provides email functions to the users. The mail service 36 stores emails addressed to the user's email address in the external service group system 12.

The user information server device 10 has an external service setting information section 20 and a user information section 22. The user information section 22 stores, for example, a user information list as shown in FIG. 7. FIG. 7 is a configuration diagram of an example of a user information list. As shown in FIG. 7, the user information list stores a user ID, name, email address, external service setting ID, and identification information.

The email address is different from the email address in FIG. 5 and is, for example, an email address used in an intranet. The external service setting ID is information that identifies the external service setting information described below. The identification information is, for example, identification information unique to the IC card 700. According to the user information list in FIG. 7, the user's user ID, name, email address, and external service setting information can be identified from the identification information read from the user's IC card 700.

The external service setting information unit 20 stores external service setting information such as that shown in FIG. 8. FIG. 8 is a configuration diagram of an example of external service setting information. The external service setting information shown in FIG. 8 is setting information that differs for each user for using the external service group system 12. The external service setting information stores an external service setting ID, a user ID, address information, a user ID of an external service, and an authentication token of an external service.

The address information and the user ID of the external service are examples of connection information to the external service group system 12. The authentication token of the external service is an example of authentication information for the external service group system 12.

The electronic whiteboard device 14 comprises a conference schedule setting unit 40, a remote service client 42, a participant management unit 44, a writing and display unit 46, an IC card detection unit 48, a shared site management unit 50, and an input unit 52. The IC card detection unit 48 reads identification information from the IC card 700 of the detected user. The participant management unit 44 manages the participants of the conference using a participant management information list such as that shown in FIG. 12.

Figure 12 is a diagram showing an example of a participant management information list. The participant management information list stores the user ID of a user recognized as a participant of the conference, information indicating whether the participant with that user ID is the organizer, the external service setting information of that user, and the email address of that user. For example, the participant management unit 44 identifies user information from the user information list of Figure 7 using the identification information read by the IC card detection unit 48, and adds and stores participant management information in accordance with the identified user information in the participant management information list of Figure 12.

The participant management information list in Figure 12 shows an example in which the participant with user ID "user001" is the organizer among participants with user IDs "user001," "user002," and "user005."

The participant management unit 44 also notifies the usage information management unit 60 of the usage information accumulation server device 17 of the usage information. Specifically, when the use of the electronic whiteboard device 14 begins and the first participant (host) is added, the participant management unit 44 notifies the device ID, the time when the conference starts, and the user ID of the host. Thereafter, during the conference, the participant management unit 44 notifies the device ID and the user ID of the participant each time a participant is added. Furthermore, when the use of the electronic whiteboard device 14 ends, the participant management unit 44 notifies the device ID and the time when the conference ends.

The writing display unit 46 accepts writings made by users to the electronic whiteboard device 14 and displays the contents of the writings. The shared site management unit 50 displays a shared site selection screen, which will be described later. The shared site management unit 50 has a function for searching for shared sites and a function for allowing a shared site to be selected from the search results. When a shared site is selected, the shared site management unit 50 notifies the usage information management unit 60 of the device ID and the shared site name as usage information.

The shared site management unit 50 also displays a shared site loading screen (described later) for loading a file from the selected shared site. When a file from the shared site is loaded, the shared site management unit 50 notifies the usage information management unit 60 of the device ID and the file name as usage information.

The shared site management unit 50 also displays a shared site save screen, described below, for saving the display contents of the electronic whiteboard device 14 as a file on the shared site. When a file is saved on the shared site, the shared site management unit 50 notifies the usage information management unit 60 of the device ID and file name as usage information. The shared site management unit 50 provides a function on the shared site save screen to email the URL (link) of the file saved on the shared site. The email address to which the shared site management unit 50 sends the URL of the file saved on the shared site is a user managed as a participant by the participant management unit 44.

The conference schedule setting unit 40 has a user interface for setting conference schedules, communicates with the schedule service 34 to obtain the schedule information in FIG. 6, and displays the user's conference schedule and allows the user to select one, allowing the user to set up the conference to be held. When a conference is set up, the conference schedule setting unit 40 notifies the usage information management unit 60 of the device ID, schedule name, schedule owner, etc.

The conference schedule setting unit 40 can also connect to a remote service using remote service connection destination information included in the schedule information for the conference to be held. When connected to the remote service, the conference schedule setting unit 40 notifies the usage information management unit 60 of the device ID and the remote service connection destination information.

The remote service client 42 functions as a client for using the remote conference service of the remote service server device 16. The remote service client 42 is realized, for example, by an application for using the remote conference service, a web browser, etc.

In this embodiment, the remote service is connected to using the remote service connection destination information included in the schedule information in FIG. 6, but other remote service connection destination information may be used to connect to the remote service. For example, by adding the remote service connection destination information as an item to the user information list in FIG. 7, when the use of the electronic whiteboard device 14 is started, after the organizer is added for the first time, a button for connecting to the remote service may be prepared using the remote service connection destination information in the organizer's user information list.

The input unit 52 accepts a screen projection from the host via wired communication such as HDMI (registered trademark) or wireless communication such as Miracast (registered trademark), and displays it on the writing display unit 46. When the input unit 52 is connected to the host via wired communication such as HDMI or wireless communication such as Miracast, it notifies the usage information management unit 60 of the device ID and the fact that it has been connected to the host via wired communication such as HDMI or wireless communication such as Miracast.

The usage information accumulation server device 17 has a configuration including a usage information management unit 60 and an electronic whiteboard usage information storage unit 62. The usage information management unit 60 stores and manages the electronic whiteboard usage information shown in FIG. 9, for example, in the electronic whiteboard usage information storage unit 62. FIG. 9 is a configuration diagram of an example of electronic whiteboard usage information. As shown in FIG. 9, the electronic whiteboard usage information stores a device ID, a time, and an event. When the usage information management unit 60 receives a notification from the meeting schedule setting unit 40, the participant management unit 44, the shared site management unit 50, and the input unit 52, it adds the information of the notification to the electronic whiteboard usage information in FIG. 9.

Figure 9 shows an example of usage information used up to "2018 11/11 10:55" on an electronic whiteboard device 14 with device ID "K100029." The event "Start meeting" indicates the event at the start of the meeting. The event "End meeting" indicates the event at the end of the meeting.

The event "Add user User ID" indicates an event in which a user with a user ID starts using the electronic whiteboard device 14. The event "Schedule Set Schedule Name" indicates an event in which a meeting schedule is set. The event "Connect to RemoteMeeting" indicates an event in which a remote connection is made.

The event "Select site shared site name" indicates an event of selecting a shared site. The event "Load file name" indicates an event of reading from a shared site. The event "Save to/path name" indicates an event of saving to a shared site. The event "Input from device name" indicates an event of connecting to the host via wired communication such as HDMI or wireless communication such as Miracast.

For example, in the electronic whiteboard usage information of FIG. 9, Mary with user ID "user001" holds the IC card 700 over the IC card reader 617 at "12:01" and begins using the electronic whiteboard device 14 with device ID "K100029". In addition, an event with event ID "sch-1" is set at "12:02". At the same time, Sato with user ID "user002" and Suzuki with user ID "user005" hold the IC card 700 over the IC card reader 617 and begin using the electronic whiteboard device 14 with device ID "K100029". In addition, a shared site with the shared site name "Abc Project" is selected at "12:05".

At "12:06", "EquipmentList.pdf" is loaded from the shared site. Also, at "12:06", "ConsumablesList.pdf" is loaded from the shared site. Also, the display contents of the electronic whiteboard device 14 are saved as a file at "12:49" with the path name "/blueprint" on the shared site. Also, the meeting ends at "12:50".

In addition, in the electronic whiteboard usage information of FIG. 9, Mary with user ID "user001" holds the IC card 700 over the IC card reader 617 at "2018 11/11 10:01" and begins using the electronic whiteboard device 14 with device ID "K100029."

At "10:02," Sato with user ID "user002" holds IC card 700 over IC card reader 617 and begins using electronic whiteboard device 14 with device ID "K100029." At "10:03," a PC (host) is connected via wired communication such as HDMI or wireless communication such as Miracast. At "10:55," the conference ends.

The report server device 18 has a configuration including a report information management unit 70, a report site unit 72, a device attribute information storage unit 74, and a report information storage unit 76. The report information management unit 70 acquires electronic whiteboard usage information from the usage information accumulation server device 17 at any timing (e.g., once an hour), classifies meetings as described below, and updates the report information as shown in FIG. 10.

Figure 10 is a diagram showing an example of report information. Figure 10(a) is an example of report information for a conference record. Figure 10(b) is an example of report information for read event information. Figure 10(c) is an example of report information for remote conference event information.

The report information in FIG. 10(a) has the following items: meeting ID, schedule name, organizer, participants, device ID, and time. The meeting ID is an ID that is determined arbitrarily when the report information is created. The meeting ID is assigned by regarding the events "Start meeting" to "End meeting" in the electronic whiteboard usage information as one meeting.

The schedule name is set to the "schedule name" of the schedule information set during the meeting. The organizer is set to the user ID of the first user added. The participants are set to the user IDs of all users added during the meeting. The device ID is set to the ID of the electronic whiteboard device 14 used in the meeting at the time of the "Start meeting" event.

By using the report information in FIG. 10(a), the report site unit 72 can classify meetings held using the electronic whiteboard device 14 into meetings with reservations and meetings without reservations.

The report information in FIG. 10(b) has the following items: conference ID, read method, and file. The conference ID is the same as in FIG. 10(a). The read method is set to "Site" when a file is read from a shared site. The file is set to the file read from the shared site. The read method is set to "PC" when screen projection from the host is accepted via wired communication such as HDMI or wireless communication such as Miracast. If the read method is "PC", the file field is left blank.

By using the report information in FIG. 10(b), the report site unit 72 can classify meetings held using the electronic whiteboard device 14 into meetings held using a shared site and meetings held using screen projection from an information processing terminal such as a PC.

The report information in FIG. 10(c) has the conference ID and remote service connection destination information as items. The conference ID is the same as in FIG. 10(a). In the report information in FIG. 10(c), a row (record) is added for each conference connected to a remote conference destination. In the example of FIG. 10, the conference with conference ID "8826918" is not connected to the remote conference destination, so there is no row for conference ID "8826918" in FIG. 10(c).

By using the report information in FIG. 10(c) and the device attribute information in FIG. 11, the report site unit 72 can classify remote conferences held using the electronic whiteboard device 14 into remote conferences held in a conference room and remote conferences held in an open space.

The report site unit 72 also acquires device attribute information and report information from the report information management unit 70, and displays a report site screen (described below) presenting the classification results on the user's information processing terminal. The device attribute information has a structure, for example, as shown in FIG. 11. FIG. 11 is a diagram showing an example of device attribute information.

The device attribute information in FIG. 11 has the items of device ID and installation location. The device attribute information in FIG. 11 is an example of information indicating the installation location of the electronic whiteboard device 14 identified by the device ID. Note that the installation location "Meeting Room" indicates an example of a space with partitioned walls, such as a conference room. Also, the installation location "Open Space" indicates an example of a space within a room that has no partitions, such as an open space.

By using the device attribute information in FIG. 11, the report site unit 72 can classify meetings held using the electronic whiteboard device 14 into meetings held in a conference room and meetings held in an open space.

The configuration in FIG. 4 is an example, and other configurations are also possible. For example, each part of the electronic whiteboard device 14 may be composed of two devices, or each part of the electronic whiteboard device 14 other than the IC card detection unit 48 and the writing display unit 46 may be realized by a server device. Furthermore, each part of the electronic whiteboard device 14 other than the IC card detection unit 48 and the writing display unit 46 may be included in the user information server device 10 without changing the device configuration, or the user information unit 22 and the external service setting information unit 20 of the user information server device 10 may be included in different devices without changing the device configuration. Furthermore, the remote service server device 16 may be composed of multiple devices.

<Functional Overview of the Electronic Whiteboard Device>
Fig. 13 is an external view of an electronic whiteboard device according to an embodiment. As shown in Fig. 13, the electronic whiteboard device 14 includes a display 680, a camera 660, and an IC card reader 617. In addition, an operation panel 900, which will be described later, is displayed on the display 680. The electronic whiteboard device 14 according to an embodiment has at least the following functions 1 to 5.

<<Function 1: Electronic whiteboard function>>
The electronic whiteboard device 14 allows writing on the electronic whiteboard with an electronic pen 690 or a finger. The electronic whiteboard device 14 can transmit image data of the image of the content written on the electronic whiteboard by email or store it in storage or the like provided by the storage service of the external service group system 12. The electronic whiteboard device 14 can also display files such as meeting materials and edit files.

<<Function 2: Authentication function>>
The electronic whiteboard device 14 can obtain authentication information and the like using an IC card reader 617, a camera 660, a biometric authentication device, and the like, and can perform user authentication based on the authentication information and the like. The electronic whiteboard device 14 can perform user authentication by itself, or by having an external device perform user authentication. The IC card reader 617 can perform user authentication by obtaining authentication information, such as identification information unique to the IC card 700, from the IC card 700, and determining whether the authentication information matches with the user information list in FIG. 7. User authentication can also be performed by face authentication, which extracts features from a face image captured by the camera 660 and determines whether the features match with features registered in the user information list.

<<Function 3: External service linkage function>>
The electronic whiteboard device 14 can cooperate with the external service group system 12. For example, the electronic whiteboard device 14 can obtain schedule information of a user authenticated by the authentication function from an external service using external service setting information of the user, and can send information such as writing on the board during a meeting and files by email to the email addresses of the scheduled attendees of the meeting. Also, for example, the electronic whiteboard device 14 can access storage provided by a storage service of the external service group system 12 of the user authenticated, obtain files, share files with other devices, and transfer files to other devices.

<<Function 4: Remote sharing function>>
The electronic whiteboard device 14 is capable of sharing the screen displayed on the electronic whiteboard device 14, collaborative editing (executing the electronic whiteboard function remotely), sharing images and videos of remote conference participants captured by the camera 660, and sharing audio from the microphone 640, among multiple information processing devices (other electronic whiteboard devices 14, PCs, etc.) installed at remote locations. Screen sharing means that the same content is displayed (remote sharing) on each of multiple information processing devices installed at remote locations, and the content is used for discussing in a remote conference, etc. Collaborative editing of a screen means writing on the same screen from multiple information processing devices, editing files, etc.

<<Function 5: Other functions>>
The electronic whiteboard device 14 may be equipped with applications similar to those that run on general PCs or smart devices, such as a web browser and an email application.

The above functions are realized by the cooperation of the hardware and software of the electronic whiteboard device 14. The software also includes software that operates in cooperation with multiple software programs of the electronic whiteboard device 14 and an external device.

<Processing>
The information processing system 1 according to the first embodiment holds a conference using the electronic whiteboard device 14, for example, in a procedure as shown in Fig. 14. Fig. 14 is a flowchart showing an example of the flow of a conference using the electronic whiteboard device.

In step S10, the electronic whiteboard device 14 starts up, displays the operation panel 900 shown in FIG. 13, and waits for login using the IC card 700. The organizer of the meeting holds his/her IC card 700 over the IC card detection unit 48.

When the IC card detection unit 48 detects the IC card 700, the electronic whiteboard device 14 proceeds to step S12, identifies user information from the identification information read from the IC card 700, and authenticates and sets the user as the organizer. In this embodiment, the first authenticated user is set as the organizer of the meeting. The authentication and setting in step S12 may be ID/password authentication or face authentication. The participant management unit 44 adds the authenticated user to the participant management information list as the organizer.

Proceeding to step S14, the participant management unit 44 notifies the usage information management unit 60 of the usage information accumulation server device 17 of the time, the event of the start of the conference, and the event of the start of use by the user, along with the device ID.

Proceeding to step S16, the electronic whiteboard device 14 displays, for example, an operation panel 1000 as shown in FIG. 22 as a user interface (hereinafter referred to as UI). FIG. 22 is an image diagram of an example of a UI displayed on the electronic whiteboard device. The operation panel 1000 in FIG. 22 displays a participant list 1002, an end meeting button 1004, a schedule selection button 1006, a shared site selection button 1008, a shared site load button 1010, and a shared site save button 1012. Note that in the operation panel 1000 in FIG. 22 displayed in step S16, only the organizer "Mary" is displayed in the participant list 1002.

In step S18, the electronic whiteboard device 14 starts accepting additional participants. FIG. 15 is a flowchart of an example of the process of accepting additional participants. When the process of accepting additional participants starts in step S40, the electronic whiteboard device 14 waits for login by a user other than the organizer using an IC card 700 or the like.

Users other than the organizer also hold their IC cards 700 over the IC card detection unit 48. When the IC card 700 is detected, the electronic whiteboard device 14 proceeds to step S42, identifies the user information from the identification information read from the IC card 700, and authenticates and sets the user as a participant of the conference. The electronic whiteboard device 14 adds the user who has been authenticated and set as a participant of the conference to the participant list 1002. The electronic whiteboard device 14 also notifies the usage information management unit 60 of the usage information accumulation server device 17 of the device ID, the time, and the event when the added participant starts using the device.

Returning to step S20 in FIG. 14, the electronic whiteboard device 14 assumes that the schedule selection button 1006 has been pressed. When the schedule selection button 1006 is pressed, the electronic whiteboard device 14 starts schedule selection. FIG. 16 is a flowchart of an example of the schedule selection process.

In step S50, the electronic whiteboard device 14 acquires the organizer's schedule information from the schedule service 34. Note that the operation panel 1000 remains displayed even after the schedule selection button 1006 is pressed. In step S52, the electronic whiteboard device 14 acquires the participant management information list of FIG. 12.

In step S54, the electronic whiteboard device 14 uses the schedule information to display the schedule proposal screen 1020 of FIG. 22. The schedule proposal screen 1020 of FIG. 22 displays the schedule name, start time, end time, schedule owner, scheduled attendees, and remote service connection information.

On the schedule proposal screen 1020 in FIG. 22, by pressing the Set/Load button 1022, the schedule and remote service connection destination displayed on the schedule proposal screen 1020 can be set as the schedule to be used.

When the schedule to be used is set, in step S56, the electronic whiteboard device 14 adds the scheduled attendees of the set schedule to the participant management information list of FIG. 12 so as not to cause any duplications, and notifies the usage information management unit 60 of the usage information accumulation server device 17 of the device ID, the event of setting the meeting schedule, and the event of starting usage.

In step S58, the electronic whiteboard device 14 displays the set schedule as shown on the operation panel 1000a in FIG. 22, and adds the scheduled attendees of the set schedule to the participant list 1002 so that there are no duplications.

In step S60, the electronic whiteboard device 14 determines whether the set schedule includes remote service connection destination information. If the set schedule includes remote service connection destination information, the electronic whiteboard device 14 uses the remote service connection destination information to connect to the remote service and displays the screen 1040 of the remote service client 42. The electronic whiteboard device 14 also notifies the usage information management unit 60 of the usage information accumulation server device 17 of the device ID and the remote connection event.

Returning to step S22 in FIG. 14, it is assumed that the shared site selection button 1008 has been pressed on the electronic whiteboard device 14. When the shared site selection button 1008 is pressed, the shared site management unit 50 of the electronic whiteboard device 14 starts selecting a shared site. FIG. 17 is a flowchart of an example of the shared site selection process.

In step S70, the electronic whiteboard device 14 displays a shared site selection screen 1100 as shown in FIG. 23. FIG. 23 is an image diagram of an example of a UI displayed on the electronic whiteboard device. The shared site selection screen 1100 displays an input field 1102 for search keywords for the shared site, a search button, search results, and a settings button 1104. The search results display the shared site name and a check box for selecting the shared site.

When a search keyword for the shared site is entered in the input field 1102 and the search button is pressed, the process proceeds to step S72, and the electronic whiteboard device 14 executes a search for the shared site using, for example, a site search API of the shared site service 32. The electronic whiteboard device 14 obtains the search results for the shared site from the shared site service 32.

The process proceeds to step S74, and the electronic whiteboard device 14 displays the search results for the shared site on the shared site selection screen 1100. On the shared site selection screen 1100 of FIG. 23, by pressing the Set button 1104, the shared site with the shared site name "Abc Tech" selected by the check box 1106 can be set as the shared site to be used.

When the shared site to be used is set, in step S76, the electronic whiteboard device 14 notifies the usage information management unit 60 of the usage information accumulation server device 17 of the set shared site together with the device ID by a shared site selection event. The electronic whiteboard device 14 also displays the set shared site as shown on the operation panel 1000c in FIG. 23.

Returning to step S24 in FIG. 14, it is assumed that the shared site load button 1010 has been pressed on the electronic whiteboard device 14. When the shared site load button 1010 is pressed, the shared site management unit 50 of the electronic whiteboard device 14 starts loading from the shared site. FIG. 18 is a flowchart of an example of the process of loading from the shared site.

In step S80, the shared site management unit 50 of the electronic whiteboard device 14 obtains information about the shared site to be read from the shared site service 32. For example, the shared site management unit 50 obtains information about the folder structure and files of the shared site to be read from the shared site service 32 using the shared site name as a key.

In step S82, the electronic whiteboard device 14 displays a shared site loading screen 1200 as shown in FIG. 24. FIG. 24 is an image diagram of an example of a UI displayed on the electronic whiteboard device. The shared site loading screen 1200 displays a selection field for files on the shared site and a load button 1202.

After a file on the shared site is selected, when the Read button 1202 is pressed, the shared site management unit 50 downloads the file on the shared site from the shared site service 32 in step S84. In step S86, the writing display unit 46 of the electronic whiteboard device 14 displays the downloaded file.

In step S88, the shared site management unit 50 notifies the usage information management unit 60 of the usage information accumulation server device 17 of the file read from the shared site together with the device ID by a read event from the shared site.

During the meeting, the electronic whiteboard device 14 displays the meeting screen and accepts operations such as writing on the electronic whiteboard device 14 by the user in step S26 of FIG. 14.

In step S28, the electronic whiteboard device 14 assumes that the shared site save button 1012 on the operation panel 1000d shown in FIG. 25 has been pressed. FIG. 25 is an image diagram of an example of a UI displayed on the electronic whiteboard device.

When the shared site save button 1012 is pressed, the shared site management unit 50 of the electronic whiteboard device 14 starts saving to the shared site. Figure 19 is a flowchart of an example of the process of saving to the shared site.

In step S90, the shared site management unit 50 of the electronic whiteboard device 14 obtains information about the shared site to which the data is to be saved from the shared site service 32. For example, the shared site management unit 50 obtains information about the folder structure of the shared site to which the data is to be saved from the shared site service 32 using the shared site name as a key. The shared site management unit 50 also obtains the participant management information list of FIG. 12 from the participant management unit 44.

In step S92, the shared site management unit 50 of the electronic whiteboard device 14 displays the shared site save screen 1300 of FIG. 25. The shared site save screen 1300 displays a field for selecting a destination folder from the folders of the selected shared site, a field for inputting the file name of the saved file, a check box 1304 for selecting whether or not to email a link to the saved file, a list of email recipients, and a save button 1302. When displaying the shared site save screen 1300, the electronic whiteboard device 14 uses the participant management information list of FIG. 12 to display the list of email recipients.

For example, when a user presses the save button 1302, the shared site management unit 50 of the electronic whiteboard device 14 acquires the board contents from the writing display unit 46 in step S94. In step S96, the shared site management unit 50 saves the file of the acquired board contents in the selected destination folder, using the shared site name and the destination folder path as keys. At this time, the shared site management unit 50 receives a URL for the saved file (a link to the saved file).

In addition, if the check box 1304 is selected to send a link to the saved file by email, the electronic whiteboard device 14 will send a save notification email, such as that shown in Figure 31, with the link to the saved file written in the body of the email, to all destinations in the email destination list or to some of the destinations selected by the check box, etc.

Figure 31 is an image diagram of an example of a save notification email. The body of the save notification email 1400 contains a URL that can open the file saved on the shared site. Note that the URL is just an example, and any information that can open the file saved on the shared site can be used, and may be written as the shared site name and file path, for example. Furthermore, instead of a URL, the save notification email 1400 may also include an attachment of a file of the blackboard contents.

In step S98, the shared site management unit 50 notifies the usage information management unit 60 of the usage information accumulation server device 17 of the file saved on the shared site together with the device ID by a save event to the shared site.

Returning to step S30 in FIG. 14, the electronic whiteboard device 14 assumes that the End Meeting button 1004 on the operation panel 1000d has been pressed. When the End Meeting button 1004 is pressed, the electronic whiteboard device 14 notifies the usage information management unit 60 of the usage information accumulation server device 17 of the end of the meeting event. In steps S32 and S34, the electronic whiteboard device 14 stops accepting additional participants and notifies the usage information management unit 60 of the usage information accumulation server device 17.

The information processing system 1 according to the first embodiment can also hold a conference using the electronic whiteboard device 14, for example, in the procedure shown in FIG. 20. FIG. 20 is a flowchart showing an example of the flow of a conference using the electronic whiteboard device. The flowchart in FIG. 20 is an example of using screen projection from a PC connected via wired communication such as HDMI or wireless communication such as Miracast, without selecting a schedule or a shared site.

Steps S100 to S108 are the same as steps S10 to S18 in FIG. 14. In step S110, the electronic whiteboard device 14 waits for an operation from the user. When the input unit 52 of the electronic whiteboard device 14 receives a screen projection from a PC connected by a display cable, for example, in step S112, it performs processing such as that shown in FIG. 21.

Figure 21 is a flowchart of an example of a process for outputting a PC screen. In step S120, the input unit 52 of the electronic whiteboard device 14 accepts a screen projection from a PC connected, for example, via a display cable, and displays the PC screen on the writing and display unit 46. In step S122, the input unit 52 notifies the usage information management unit 60 of the usage information accumulation server device 17 of the device ID and an event of the reading method "PC" connected to the host via wired communication such as HDMI or wireless communication such as Miracast.

Returning to step S114 in FIG. 20, the electronic whiteboard device 14 assumes that the End Meeting button 1004 on the operation panel 1000d has been pressed. When the End Meeting button 1004 is pressed, the electronic whiteboard device 14 notifies the usage information management unit 60 of the usage information accumulation server device 17 of the end of the meeting event. In steps S116 and S118, the electronic whiteboard device 14 stops accepting additional participants and notifies the usage information management unit 60 of the usage information accumulation server device 17.

In step S12 of FIG. 14, the organizer is authenticated and set, for example, according to the procedure shown in FIG. 26. FIG. 26 is a flowchart of an example of the process of authenticating and setting the organizer. FIG. 26 shows the process after the IC card detection unit 48 of the electronic whiteboard device 14 detects the IC card 700 and reads the identification information from the IC card 700.

Proceeding to step S200, the participant management unit 44 acquires the identification information read by the IC card detection unit 48 from the IC card 700. Proceeding to step S202, the participant management unit 44 refers to the user information list shown in FIG. 7 and identifies the user of the identification information acquired in step S200 from the user information list shown in FIG. 7. The participant management unit 44 also refers to the external service setting information shown in FIG. 8 and identifies the external service setting information of the identified user from the external service setting information in FIG. 8. Proceeding to step S204, the participant management unit 44 adds the identified user to the participant management information list in FIG. 12 as the organizer and manages it.

For example, the IC card detection unit 48 detects the IC card 700 of "Mary Smith" shown in the user information list in FIG. 7 and reads the identification information "ICCARD-123" from the IC card 700. In step S200, the participant management unit 44 obtains the identification information "ICCARD-123" from the IC card detection unit 48. Proceeding to step S202, the participant management unit 44 queries the external service setting information unit 20 and the user information unit 22 of the user information server device 10 based on the obtained identification information "ICCARD-123".

The user information unit 22 performs a search using the requested identification information "ICCARD-123", identifies the user information of the user ID "user001", and returns this to the participant management unit 44 of the electronic whiteboard device 14. The external service setting information unit 20 also performs a search using the identified user ID "user001", identifies the external service setting information "connect1a" shown in FIG. 8, and returns this to the participant management unit 44 of the electronic whiteboard device 14.

The participant management unit 44 also queries the external service setting information unit 20 for the email address of the external service setting information "connect1a". The external service setting information unit 20 uses "eyJhbGc11...", which is the authentication token for the external service of the external service setting information "connect1a", to identify the email address "office1@office.example.com" of the user ID "office1" from the user service 30, and returns it to the participant management unit 44 of the electronic whiteboard device 14.

In step S204, the participant management unit 44 can add the user with user ID "user001" as the organizer to the participant management information list of FIG. 12 and manage the user, and can also manage the external service setting information "connect1a" of the user with user ID "user001". As a result, the meeting organizer "Mary Smith" is saved in the participant management information list shown in FIG. 12 in association with the user ID "user001", the external service setting ID "connect1a", and the email address "office1@office.example.com".

In step S50 of FIG. 16, a schedule is acquired and proposed, for example, according to the procedure shown in FIG. 27. FIG. 27 is a flowchart of an example of a process for acquiring and proposing a schedule.

In step S210, the meeting schedule setting unit 40 of the electronic whiteboard device 14 obtains the meeting schedule included in the organizer's schedule information for the day from the schedule service 34 based on the organizer's user ID obtained by authentication.

To obtain the organizer's meeting schedule for the day, the meeting schedule setting unit 40 obtains the organizer's external service setting information from the user information server device 10 based on the organizer's user ID obtained by authentication, and obtains the meeting schedule information for the day of the user identified by the external service setting information by requesting it from the schedule service 34 based on the obtained organizer's external service setting information.

In addition, the conference schedule setting unit 40 may not acquire external service setting information, but may simply specify the organizer's user ID and request the user information server device 10 to acquire conference schedule information. The user information server device 10 may identify external service setting information based on the acquired organizer's user ID, acquire conference schedule information from the schedule service 34 based on the identified external service setting information, and return the acquired conference schedule information to the electronic whiteboard device 14. In other words, the electronic whiteboard device 14 may not directly exchange information with the schedule service 34, but may acquire the conference schedule information from the schedule service 34 via another server or the like.

In step S212, the conference schedule setting unit 40 determines whether or not there is a scheduled conference acquired in step S210. If there is no scheduled conference, the conference schedule setting unit 40 skips the process of step S214. If there is a scheduled conference, the conference schedule setting unit 40 performs the process of proposing a schedule in step S214, for example, as shown in FIG. 28.

Figure 28 is a flowchart of an example of the schedule proposal process. In step S220, the meeting schedule setting unit 40 extracts meeting schedules whose "start time and duration" are closest to the current time from the organizer's meeting schedule for that day obtained in step S210. For example, the meeting schedule setting unit 40 extracts meeting schedules whose current time falls between 15 minutes before the scheduled start time and the scheduled end time. Since there may be multiple meeting schedules extracted in step S220, the meeting schedule setting unit 40 extracts the meeting schedule with the latest scheduled start time from the extracted meeting schedules in step S222.

In step S224, the conference schedule setting unit 40 determines whether or not there is a scheduled conference extracted in step S222. If there is a scheduled conference extracted in step S222, the conference schedule setting unit 40 proceeds to step S226 and sets the scheduled conference to the proposed schedule. If there is no scheduled conference extracted in step S222, the conference schedule setting unit 40 skips the processing of step S226.

For example, in step S210, the meeting schedule setting unit 40 of the electronic whiteboard device 14 uses the external service setting information "connect1a" of the organizer "Mary Smith" of the user ID "user001" returned from the user information server device 10 to obtain meeting schedules with schedule IDs "sch-1" and "sch-2" included in the organizer's schedule information for the day from the schedule service 34. The meeting schedule setting unit 40 determines whether there are any meeting schedules obtained in step S210.

As there are multiple scheduled meetings with schedule IDs "sch-1" and "sch-2", it is possible that multiple scheduled meetings are obtained, so it is necessary to determine one schedule to propose to the user for setting as a scheduled meeting. For this reason, the meeting schedule setting unit 40 performs the schedule proposal process in step S214, for example, as shown in FIG. 28.

For example, assume that a person enters the conference room at 11:55 on November 10, 2018, and activates the electronic whiteboard device 14. In step S214, the meeting schedule setting unit 40 extracts the meeting schedule with schedule ID "sch-1" whose start time and duration are close to the current time "November 10, 2018, 11:55" from the meeting schedules with schedule IDs "sch-1" and "sch-2" that are the organizer's meeting schedules for that day obtained in step S210.

In general, conference rooms and meeting spaces are often reserved and operated in 30-minute increments, such as 30 minutes or 60 minutes, so the extraction conditions used to extract meeting schedules in step S220 can accommodate cases where people enter and start using the room a little early, as in the example above, or enter and start using the room a little late.

In addition, because the threshold is set to 15 minutes, half the time unit of 30 minutes for a meeting, for example, if a huddle-style meeting is started at 9:30 without any scheduled meetings, a meeting with a start time of 12:00 will not be mistakenly proposed. As for the start time for advance preparation, it is rare for advance preparation to begin more than 15 minutes before the scheduled start time, so this is a reasonable setting value.

These extraction conditions may be changeable by the organizer. Also, if multiple meeting plans are extracted in step S214, no proposed schedule may be displayed and the plan proposal screen 1020 may not be displayed.

In step S58 of FIG. 16, a process is performed to add the scheduled attendees of the proposed meeting to the participant management information list of FIG. 12, for example, using the procedure shown in FIG. 29. FIG. 29 is a flowchart of an example process for adding scheduled attendees to participant management information.

In step S230, the participant management unit 44 queries the external service setting information unit 20 for the external service setting information of the current participant. Proceeding to step S232, the participant management unit 44 removes any participants whose user ID matches the organizer's user ID from the list of planned attendees included in the organizer's schedule information.

The processes in steps S234 to S240 are performed for all scheduled attendees included in the list of scheduled attendees from which the organizer's user ID was excluded in step S232. Proceeding to step S234, the participant management unit 44 queries the user information unit 22 for user information corresponding to the user ID of the external service of the scheduled attendee.

If there is user information corresponding to the user ID of the external service, proceed to step S238, where the participant management unit 44 adds the user IDs of the scheduled attendees to the participant management information list of FIG. 12. Then, in step S240, the participant management unit 44 notifies the usage information management unit 60 of the usage information accumulation server device 17 of the addition of a participant due to the start of usage event. If there is no user information corresponding to the user ID of the external service, the participant management unit 44 skips the processing of steps S168 to S170.

For example, when the set/read button 1022 on the schedule proposal screen 1020 shown in FIG. 22 is pressed, the process proceeds to step S230, and the participant management unit 44 queries the external service setting information unit 20 for the external service setting information "connect1a" of the current participant (organizer).

Proceeding to step S232, the participant management unit 44 excludes "office1", which is the user ID of the organizer's external service, from the list of planned attendees included in the schedule information of the organizer "user001".

Next, the process proceeds to step S234, where the participant management unit 44 queries the user information server device 10 for user information corresponding to the external service user IDs "office2" and "office5" of the remaining scheduled attendees.

Because there are user IDs "user002" and "user005" corresponding to the user IDs "office2" and "office5" of the external service, the user information server device 10 proceeds to step S238 and returns the user IDs "user002" and "user005" to the participant management unit 44. The participant management unit 44 adds the user IDs "user002" and "user005" to the participant management information list. Then, in step S240, the participant management unit 44 notifies the usage information management unit 60 of the usage information accumulation server device 17 of the addition of participants with user IDs "user002" and "user005" due to the start of usage event.

By using this procedure, in this embodiment, the schedule information registered in the organizer's schedule service 34 can be set and read as a meeting schedule on the electronic whiteboard device 14, making it easy to put a participant who has not been authenticated using an IC card 700 into a participating state, or to put a participant without an IC card 700 into a participating state.

The process of connecting to a remote conference service is performed, for example, according to the procedure shown in FIG. 30. FIG. 30 is a flowchart of an example of the process of connecting to a remote service. When connecting to a remote service, the conference schedule setting unit 40 uses the domain portion, etc., included in the remote service connection destination information to determine the remote service in step S250.

Proceeding to step S252, the conference schedule setting unit 40 determines the remote service client 42 to be started according to the remote service determined in step S250, and starts the remote service client 42. Note that if the determined remote service is not supported, the conference schedule setting unit 40 does not start the remote service client 42. In this way, security is improved by not starting the remote service client 42 if the determined remote service is not supported. Also, the method of notifying the remote service client 42 to be started of the remote service connection destination information differs for each remote service client 42.

In the case of a remote service client 42 that can connect to a remote service using the dedicated application "remoteservicea.exe," the remote service connection destination information can be notified to the remote service client 42 by starting the application with, for example, the connection destination "134565" as an argument.

In addition, in the case of a remote service client 42 that can connect to a remote service using a web browser, the remote service connection destination information can be input as a URL into the web browser, thereby notifying the remote service client 42 of the remote service connection destination information.

The method of connecting to a remote service, such as using a dedicated application or a web browser, differs for each remote service, and the connection method corresponding to the remote service determined in step S250 is used to connect to the remote service determined.

The arguments and URL that notify the remote service client 42 to be started of the remote service connection destination information may use the remote service connection destination information as is, or may extract and use a portion of it, or may rewrite a portion of it.

In addition, if the remote service connection destination information uses a custom URL scheme, the conference schedule setting unit 40 can determine a dedicated application that is launched with that custom URL scheme, and launch it with the connection destination as an argument, thereby notifying the remote service client 42 of the remote service connection destination information.

Proceeding to step S254, the conference schedule setting unit 40 notifies the usage information management unit 60 of the usage information accumulation server device 17 of the remote service connection destination information together with the device ID by a remote connection event.

Figure 32 is a flowchart of an example of a process for updating electronic whiteboard usage information. Every time the usage information management unit 60 of the usage information accumulation server device 17 receives an event notification from the electronic whiteboard device 14, in step S260, it updates the electronic whiteboard usage information stored in the electronic whiteboard usage information storage unit 62.

The report information management unit 70 of the report server device 18 acquires electronic whiteboard usage information from the usage information accumulation server device 17 at predetermined intervals (e.g., once an hour) and updates the information for reports (report information).

Figure 33 is a flowchart of an example of a process for updating report information. In step S270, the report information management unit 70 acquires electronic whiteboard usage information from the usage information accumulation server device 17.

In step S272, the report information management unit 70 uses the electronic whiteboard usage information acquired in step S270 to update the report information of the meeting record in FIG. 10(a). For example, the report information management unit 70 regards the events "Start meeting" to "End meeting" from the electronic whiteboard usage information in FIG. 9 as one meeting and issues a meeting ID. The report information management unit 70 searches for the events "Add user" and "Schedule Set" in the electronic whiteboard usage information regarded as one meeting, determines the schedule name, organizer, and participants, and creates one line of report information in the meeting record in FIG. 10(a). The organizer is the user of the event "Add user" that follows the event "Start meeting".

In step S274, the report information management unit 70 uses the electronic whiteboard usage information acquired in step S270 to update the report information in the read event information in FIG. 10(b). For example, the report information management unit 70 searches for the events "Load" and "Input from PC" for each conference of the conference ID in the conference record in FIG. 10(a). The report information management unit 70 creates a line in FIG. 10(b) with the conference of the event "Load" set as the read method "Site". The report information management unit 70 also creates a line in FIG. 10(b) with the conference of the event "Input from PC" set as the read method "PC".

In step S276, the report information management unit 70 uses the electronic whiteboard usage information acquired in step S270 to update the report information of the remote conference event information in FIG. 10(c). For example, the report information management unit 70 searches for the "Connect" event for each conference with the conference ID in the conference record in FIG. 10(a), determines the remote service connection destination information, and creates one line of report information for the remote conference event information in FIG. 10(c).

The report site unit 72 of the report server device 18 displays the report site on an information processing terminal such as a PC 15, for example, in the procedure shown in FIG. 34. FIG. 34 is a flowchart of an example of a process for displaying the report site.

In step S280, the report site unit 72 opens the report site using a web browser or the like, prompting the user to log in and waiting for input of login information such as an ID and password. The login information used here may be, for example, an account used to log in to the electronic whiteboard device 14.

When the user successfully logs in, in step S282, the report site unit 72 acquires the report information of the conference record in FIG. 10(a), the report information of the read event information in FIG. 10(b), and the report information of the remote conference event information in FIG. 10(c). In step S284, the report site unit 72 acquires the device attribute information in FIG. 11. Note that in step S282, it is possible to acquire only the report information of FIG. 10(a) to (c) of the conference held in the group to which the user who logged in in step S280 belongs. This group may include a company, a team, a tenant, etc. The group information is managed in advance by linking it to each device and each user. In step S282, it is sufficient to acquire only the report information of the conference whose device ID or organizer is linked to the group to which the logged-in user belongs. This makes it possible to create a report site screen for the group to which the user belongs.

In steps S286 to S290, the report site unit 72 determines the conference efficiency results, remote conference results, and PC-less results from the report information of the conference record of FIG. 10(a), the report information of the read event information of FIG. 10(b), the report information of the remote conference event information of FIG. 10(c), and the device attribute information of FIG. 11, which were acquired in step S282.

In step S292, the report site unit 72 displays a report site screen, described below, on the user's information processing terminal based on the determined meeting efficiency results, remote meeting results, and PC-less results.

The meeting efficiency results are determined, for example, as follows. For example, the report site unit 72 calculates the number of scheduled meetings (A) and the number of unscheduled meetings (B) during the month from the "Time" and "Schedule Name" items in the report information of the meeting record in FIG. 10(a). The report site unit 72 then determines that "there is a possibility that there are many unnecessary meetings" if "A ≧ B". The report site unit 72 also determines that "there are few unnecessary meetings" if "A < B".

Figure 35 is an image diagram of an example of a report site screen. Figure 35 is an example of the display of the "Meeting efficiency" page of the report site screen 1500 when it is determined that there are "few unnecessary meetings." The report site screen 1500 in Figure 35 shows an example of a message stating that there are "few unnecessary meetings" and a graph plotted from the number of scheduled (reserved) meetings and the number of unscheduled (no reservations) meetings for the current month.

Figure 36 is an image diagram of an example of a report site screen. Figure 36 is an example of the display of the "Meeting efficiency" page of report site screen 1500 when it is determined that "there is a possibility that there are many unnecessary meetings." Report site screen 1500 in Figure 36 shows an example of a message stating that "useless meetings are likely being held" and a graph plotted from the number of scheduled (reserved) meetings and the number of unscheduled (no reservations) meetings for the current month.

The remote conference result is determined, for example, as follows. The report site unit 72 creates a list of conference IDs for the current month from the items "Time" and "Conference ID" of the report information of the conference record in FIG. 10(a), for example. Furthermore, the report site unit 72 creates a list of remote conference IDs for the current month based on the list of conference IDs for the current month and the report information of the remote conference event information in FIG. 10(c).

Next, based on the report information of the conference record in FIG. 10(a) and the list of remote conference IDs for the current month, the report site unit 72 calculates the number of remote conferences held for each device ID. From the number of remote conferences held for each device ID and the device attribute information in FIG. 11, the report site unit 72 calculates the number of remote conferences held in the conference room (C) and the number of remote conferences held in the open space (D).

Then, the report site unit 72 determines that "the impact of the remote conference on the surrounding area is small" if (D/(C+D)) x 100 ≦ 20%. The report site unit 72 determines that "the impact of the remote conference on the surrounding area is large" if (D/(C+D)) x 100 > 20%.

Figure 37 is an image diagram of an example of a report site screen. Figure 37 is an example of the display of the "Remote Conference" page of report site screen 1500 when it is determined that "the remote conference has little impact on the surrounding area." Report site screen 1500 in Figure 37 shows an example of a message to the effect that "the remote conference is not causing a nuisance to those around you" and a graph drawn from the number of remote conferences held in conference rooms during the month (C) and the number of remote conferences held in open spaces (D).

Figure 38 is an image diagram of an example of a report site screen. Figure 38 is an example of the display of the "Remote conference" page of report site screen 1500 when it is determined that "remote conferences have a large impact on those around you." Report site screen 1500 in Figure 38 shows an example of a message to the effect that "remote conferences are causing a nuisance to those around you" and a graph drawn from the number of remote conferences held in conference rooms during the month (C) and the number of remote conferences held in open spaces (D).

The PC-less result is determined, for example, as follows: The report site unit 72 creates a list of conference IDs for last month's conferences and a list of conference IDs for the current month from the items "Time" and "Conference ID" of the report information of the conference record in FIG. 10(a), for example.

Furthermore, the report site unit 72 calculates the number of shared site reads last month (E), the number of PC inputs last month (F), the number of shared site reads this month (G), and the number of PC inputs this month (H) based on the list of conference IDs for last month's conferences, the list of conference IDs for the current month's conferences, and the report information for the read event information in Figure 10 (b).

Then, the report site unit 72 determines that "the PC-less movement is progressing" if E/(E+F)≦G/(G+H). The report site unit 72 also determines that "the PC-less movement is not progressing" if E/(E+F)>G/(G+H).

Figure 39 is an image diagram of an example of a report site screen. Figure 39 is an example of the display of the "PC-less" page on report site screen 1500 when it is determined that "PC-less is progressing." Report site screen 1500 in Figure 39 shows an example of a message to the effect that "PC-less is progressing," along with a graph plotted from the number of shared site reads last month (E), the number of PC inputs last month (F), the number of shared site reads this month (G), and the number of PC inputs this month (H).

Figure 40 is an image diagram of an example of a report site screen. Figure 40 is an example of the display of the "PC-less" page of report site screen 1500 when it is determined that "PC-less progress is not progressing." Report site screen 1500 in Figure 40 shows an example in which a message stating "PC-less progress is not progressing" is displayed, along with a graph drawn from the number of shared site reads last month (E), the number of PC inputs last month (F), the number of shared site reads this month (G), and the number of PC inputs this month (H).

Other examples of report sites that the report site unit 72 of the report server device 18 displays on an information processing terminal such as a PC 15 include a report site screen 1500 that displays the ratio of the number of remote conferences to the number of conferences other than remote conferences, a report site screen 1500 that displays the ratio of the number of conferences that were saved as files to the number of conferences that were not saved as files, and a report site screen 1500 that displays the ratio of the number of conferences that were loaded as files to the number of conferences that were not loaded as files.

As described above, according to the first embodiment, meetings using the electronic whiteboard device 14 can be classified and the type of meeting being held can be analyzed.

Second Embodiment
The report site screens 1500 in Figs. 35 to 40 are only examples, and messages may be omitted as shown in Figs. 41 and 42. Figs. 41 and 42 are image diagrams of examples of report site screens. Fig. 41 is an example in which messages are omitted from the report site screen 1500 shown in Fig. 35. Fig. 42 is an example in which messages are omitted from the report site screen 1500 shown in Fig. 36. In addition, the report site screens 1500 in Figs. 35 to 40 are examples in which conferences are classified into two categories, but examples in which conferences are classified into three or more categories, such as conferences in which shared site reading was performed, conferences in which PC input was performed, and conferences in which neither shared site reading nor PC input was performed, may be displayed.

In the information processing system 1 of FIG. 1, at least some of the functions of the user information server device 10, the external service group system 12, the remote service server device 16, the usage information accumulation server device 17, and the report server device 18 may be realized by cloud computing.

The present invention is not limited to the specifically disclosed embodiment described above, and various modifications and variations are possible without departing from the scope of the claims. It goes without saying that the information processing system 1 described in this embodiment is only one example, and there are various system configuration examples depending on the application and purpose.

Each function of the above-described embodiments can be realized by one or more processing circuits. In this specification, the term "processing circuit" includes a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, and devices such as an ASIC (Application Specific Integrated Circuit), DSP (digital signal processor), FPGA (field programmable gate array), and conventional circuit modules designed to execute each function described above.

The devices described in the examples are merely illustrative of one of several computing environments for implementing the embodiments disclosed herein.

In one embodiment, the user information server device 10 includes multiple computing devices, such as a server cluster. The multiple computing devices are configured to communicate with each other via any type of communication link, including a network 19, shared memory, etc., to perform the processing disclosed herein. Similarly, the electronic whiteboard device 14 can include multiple computing devices configured to communicate with each other.

Furthermore, the user information server device 10 and the electronic whiteboard device 14 can be configured to share the disclosed processing steps in various combinations. For example, the process performed by a given unit can be performed by the electronic whiteboard device 14. Similarly, the function of a given unit can be performed by the electronic whiteboard device 14. Also, the elements of the user information server device 10 and the electronic whiteboard device 14 can be integrated into one server device or separated into multiple devices.

The devices that can be connected to the remote conference destination are not limited to the electronic whiteboard device 14 and the PC 15, but may be, for example, a PJ (Projector), an output device such as digital signage, a HUD (Head Up Display) device, industrial machinery, an imaging device, a sound collection device, medical equipment, network home appliances, automobiles (Connected Cars), mobile phones, game consoles, PDAs (Personal Digital Assistants), digital cameras, wearable PCs, etc.

REFERENCE SIGNS LIST 1 Information processing system 10 User information server device 12 External service group system 14 Electronic whiteboard device 15 PC
16 Remote service server device 17 Usage information accumulation server device 18 Report server device 19 Network 20 External service setting information section 22 User information section 30 User service 32 Shared site service 34 Schedule service 36 Mail service 40 Conference schedule setting section 42 Remote service client 44 Participant management section 46 Writing display section 48 IC card detection section 50 Shared site management section 52 Input section 60 Usage information management section 62 Electronic whiteboard usage information storage section 70 Report information management section 72 Report site section 74 Device attribute information storage section 76 Report information storage section 1500 Report site screen

JP 2005-84969 A

Claims (9)

An information processing system including an electronic device used in a conference and an information processing device that performs an analysis of the conference using the electronic device,
The electronic device includes:
an input unit that receives input from users participating in a conference using the electronic device;
a participant management unit for managing participants in a conference using the electronic device;
a conference schedule setting unit that acquires schedule information of the participant from an external service using external service setting information associated with the participant, and selects a conference in which the electronic device is to be used from the schedule information of the participant;
Equipped with
The information processing device includes:
a usage information management unit that manages usage information of the electronic device in response to the input by the user in the conference;
a report information management unit that classifies the conferences using the electronic devices according to the usage information of the electronic devices and manages the classified results in order to present them;
a report site section for displaying the results classified by the report information management section on a screen of an information processing terminal communicably connected thereto;
Equipped with
The usage information management unit manages an operation of selecting a conference in which the electronic device is to be used from schedule information of the participants as usage information of the electronic device;
The report information management section classifies the conferences using the electronic device into conferences selected from the schedule information of the participants and conferences not selected from the schedule information of the participants, and manages the classification results so as to display them on the screen of the information processing terminal.
An information processing system comprising : The electronic device further includes a remote service client that connects to a remote service based on remote service connection destination information registered in the schedule information of the participant,
2. The information processing system according to claim 1 , wherein the usage information management unit manages an operation of connecting to the remote service as usage information of the electronic device. the electronic device further includes a shared site management unit that reads a file from a shared site service associated with the participant and saves the file in the shared site service by using external service setting information associated with the participant;
3. The information processing system according to claim 1 , wherein the usage information management unit manages an operation of reading a file from the shared site service and an operation of saving a file to the shared site service as usage information of the electronic device. The input unit displays a screen of an information processing terminal communicatively connected on a display,
4. The information processing system according to claim 1 , wherein the usage information management section manages an operation of displaying a screen of the information processing terminal as usage information of the electronic device. The information processing system described in claim 2, characterized in that the report information management unit classifies, among the conferences using the electronic devices, conferences held by connecting to a remote service into conference rooms and conferences held in open spaces by using device attribute information containing information indicating the installation location of the electronic devices , and manages the classified results for display on the screen of the information processing terminal. The information processing system according to claim 3, characterized in that the report information management unit classifies meetings using the electronic device into meetings held by displaying a file read from the shared site service on a display and meetings held by displaying the screen of the information processing terminal on a display, and manages the classified results for display on the screen of the information processing terminal. An information processing device that is used in a conference, is communicatively connected to an electronic device that accepts input from users participating in the conference, and performs analysis on the conference using the electronic device,
a usage information management unit that manages usage information of the electronic device in response to the input by the user in the conference;
a report information management unit that classifies the meetings using the electronic device according to the usage information of the electronic device and manages the classified results in order to present them;
a report site section for displaying the results classified by the report information management section on a screen of an information processing terminal communicably connected thereto;
Equipped with
the usage information management unit manages an operation of selecting a conference using the electronic device from schedule information of a participant of the conference using the electronic device as usage information of the electronic device;
The report information management section classifies the conferences using the electronic device into conferences selected from the schedule information of the participants and conferences not selected from the schedule information of the participants, and manages the classification results so as to display them on the screen of the information processing terminal.
An information processing device comprising : An information processing device that is used in a conference, is communicatively connected to an electronic device that accepts input from users participating in the conference, and performs analysis on the conference using the electronic device,
a usage information management unit that manages usage information of the electronic device in response to the input by the user in the conference;
a report information management unit that classifies the conferences in which the electronic devices were used according to the usage information of the electronic devices and manages the classified results in order to present them;
a report site section for displaying the results classified by the report information management section on a screen of an information processing terminal communicably connected thereto;
Function as a
the usage information management unit manages an operation of selecting a conference using the electronic device from schedule information of a participant of the conference using the electronic device as usage information of the electronic device;
The report information management section classifies the conferences using the electronic device into conferences selected from the schedule information of the participants and conferences not selected from the schedule information of the participants, and manages the classification results so as to display them on the screen of the information processing terminal.
A program characterized by . 1. An information processing method executed in an information processing device that is used in a conference, is communicatively connected to an electronic device that accepts input from users participating in the conference, and performs an analysis of the conference using the electronic device, comprising:
managing usage information of electronic devices in response to the input by the user in the conference;
A step of classifying the conferences using the electronic device according to the usage information of the electronic device, and managing the classified results for presentation;
a step of displaying the results of classification performed in the step of managing the results of classification for presentation on a screen of an information processing terminal communicably connected to the information processing terminal;
having
The step of managing the usage information includes managing an operation of selecting a conference using the electronic device from schedule information of a participant of the conference using the electronic device as usage information of the electronic device;
The step of managing the classified results for presentation includes classifying the conferences using the electronic devices into conferences selected from the schedule information of the participants and conferences not selected from the schedule information of the participants, and managing the classified results for display on a screen of the information processing terminal.
An information processing method comprising :

Images