JP2020087424A - Resource reservation system, information display method, server system, and information processing terminal - Google Patents

Abstract

To provide a resource reservation system configured to modify at least a part of information displayed on a meeting-room terminal.SOLUTION: A resource reservation system 100 includes: a server system including at least one meeting-room management server 30 storing reservation information on reservations of one or more resources; and a meeting-room terminal 90 for acquiring the reservation information from the server system and displaying the information. The meeting-room terminal 90 is arranged for each resource, and displays contents of the reservation information acquired from the meeting-room management server 30 modified in accordance with setting information that sets a display method of the reservation information.SELECTED DRAWING: Figure 1

Description

The present invention relates to a resource reservation system, an information display method, a server system, and an information processing terminal.

There is known a resource reservation system that accepts reservations for resources such as conference rooms. The conference room reservation person can make the terminal device communicate with the reservation management server and reserve the conference room by the browser operating on the terminal device.

An information processing terminal such as a meeting room terminal that communicates with the meeting management server is installed in the meeting room, and the information processing terminal can display the reservation information received from the meeting management server on a standby screen (for example, Patent Document 1). See 1.). In Patent Document 1, the conference management server transmits the entry application screen information for permitting the use of the reserved conference room to the floor monitor or the like installed on the floor of the conference room, and the floor monitor or the like makes the conference room reservation information. A system for displaying is disclosed.

However, the conventional resource reservation system has a problem that the information displayed by the information processing terminal cannot be changed. That is, the information processing terminal is installed in the meeting room, the entrance of the meeting room, or in the vicinity of the meeting room, for accepting check-in and check-out to the meeting room and displaying the reservation status of the meeting room. A person moving near the conference room terminal can see the conference name, participant names, and the like.

However, the meeting name may include the company's policy or the content of negotiation, and the participant name may include the important person, the business partner, or the negotiation partner. That is, the reservation information displayed on the standby screen by the information processing terminal may indicate important information of the company, and there is a risk that the important information may be unintentionally leaked.

In view of the above problems, it is an object of the present invention to provide a resource reservation system that can change at least a part of information displayed by an information processing terminal.

In view of the above problems, the present invention provides a server system including at least one information processing device that stores reservation information about reservations of one or more resources, and information processing that acquires and displays the reservation information from the server system. In the resource reservation system having a terminal, the information processing terminal is installed for each of the resources, and changes the display content of the reservation information that is changed according to the setting information that sets the display method of the reservation information. It is characterized by displaying.

It is possible to provide a resource reservation system capable of changing at least a part of the information displayed by the information processing terminal.

It is an example of a diagram for explaining the outline of the overall operation of the resource reservation system. It is a figure which shows the example standby screen which a conference room terminal displays. It is a system block diagram of an example of a resource reservation system. It is a hardware block diagram of an example of a conference management server. It is a hardware block diagram of an example of a conference room terminal. It is an example functional block diagram which shows the function of a reservation management server, a chat server, a meeting management server, and a registration terminal in block form. It is an example functional block diagram which shows the function of a terminal device and a conference room terminal in block form. It is a figure which shows an example of the reservation setting screen which a terminal device displays. It is a figure which shows an example of the secret information management screen which a registration terminal displays. It is a figure which shows an example of the secret setting management screen which a registration terminal displays. It is a figure which shows an example of the private setting edit screen which a registration terminal displays. It is a sequence diagram which shows an example of the procedure which makes the reservation information which a conference room terminal displays on a standby screen private. It is a figure which shows the meeting management information of an example which a meeting management server transmits to a meeting room terminal. It is an example flowchart figure which shows the procedure which a conference room terminal displays a reservation information on a standby screen. It is a functional block diagram of an example which shows the function of a reservation management server, a chat server, a meeting management server, and a registration terminal in block form (Example 2). It is a functional block diagram of an example which shows the function of a terminal unit and a conference room terminal in block form (Example 2). It is a figure which shows an example of the secret information management screen which a conference room terminal displays. It is a figure which shows an example of the secret setting management screen which a conference room terminal displays. It is a figure which shows an example of the private setting edit screen which a conference room terminal displays. It is an example sequence diagram which shows the procedure which makes the reservation information which a conference room terminal displays on a standby screen private. It is an example of a diagram for explaining an operation to hide any item of the reservation information. It is a functional block diagram of an example which shows the function of a reservation management server, a chat server, a meeting management server, and a registration terminal in block form (Example 3). FIG. 16 is a sequence diagram of an example showing a procedure for making the reservation information displayed on the standby screen by the conference room terminal private (Example 3).

Hereinafter, as an example of a mode for carrying out the present invention, a resource reservation system and an information display method performed by the resource reservation system will be described with reference to the drawings.

<Outline of resource reservation system>
First, the outline of the reservation system will be described with reference to FIG. FIG. 1 is an example of a diagram for explaining the outline of the overall operation of the resource reservation system 100.

A. The reservation person operates his/her terminal device 60 to communicate with the reservation management server 20 and reserves the conference room. The reservation management server 20 is a general-purpose cloud service (Office 365, G Suite (both are registered trademarks), etc.), but the conference room of an organization such as a company to which the reservation person belongs is registered.

B. The conference management server 30 is a server that controls the entire resource reservation system 100 based on the reservation state of the conference room. Since the conference management server 30 appropriately communicates with the reservation management server 20 to acquire the reservation information, the reservation management server 20 and the reservation information are synchronized.

C. The resource reservation system 100 or the administrator on the organization side can perform user registration and various settings in the conference management server 30. User registration means registering a user who is a target of various notifications using the chat server 10 (slack, Line, Microsoft Teams (all are registered trademarks), etc.). Further, since the notification is given via the bot that transmits a message as the conference management server 30, the bot provided by the chat server is also registered. Various settings include registration of the conference room terminal 90, setting of reminding timing, and the like.

D. The meeting management server 30 reminds the reservation person to hold the meeting at a certain time before the start time of the meeting in the reservation information. This suppresses empty reservations for the conference room. Further, the conference management server 30 notifies the user of the invitation code (invitation to the group) as necessary. Upon receiving the remind, the conference reservation person saves the information (conference identification information) for checking into the conference room in the terminal device 60. Check-in means to start using the meeting room.

E. A conference room terminal 90 is installed in each conference room 6, and the conference room terminal 90 downloads the reservation information of the conference held in this conference room on a regular basis. The conference room terminal 90 can display the schedule of the current day or the latest conference and the like so that the participants of the conference can confirm the schedule. A little before the start time of the meeting, the reservation person of the meeting room goes to the meeting room 6 and checks in. For example, the conference identification information is input to the conference room terminal 90, or the terminal device 60 is held over the conference room terminal 90 (the conference identification information is read, communication is performed, etc.).

F. Since the conference room terminal 90 transmits a check-in request to the conference management server 30, if the conference identification information can be authenticated, the conference room server 90 receives a response from the conference management server 30 that the check-in has been successful. The conference room terminal 90 displays that it is busy (in a conference). When the use start notification notifying the check-in cannot be confirmed by the fixed time with respect to the start time of the conference, the conference management server 30 cancels the reservation of the conference room 6 (cancel the reservation information when the conference room is not used for a predetermined time). The canceled status is transmitted to the conference room terminal 90 as the status included in the reservation information. In this case, since the conference room terminal 90 displays that the room is empty, any user can use the conference room 6.

G. The conference room terminal 90 controls the electronic device 70 in response to a request from the conference management server 30. For example, the power is turned on at the conference start time and turned off at the conference end time. By doing so, it is possible to improve the convenience when the participants of the conference operate the electronic device 70.

H. When the electronic device 70 has a video conference function, for example, the electronic device 70 can communicate with an electronic device (a video conference terminal 70x or the like) at another site 4 to hold a conference with another site. The PC 70y on which the application operates can also communicate with the electronic device 70. The reservation information includes destination information (destination communication ID) indicating the other base 4 in advance, and the electronic device 70 can automatically communicate with the video conference terminal 70x and the PC 70y.

I. When the reservation person finishes the conference, he/she presses the button of the conference room terminal 90 to check out, so that the conference room terminal 90 displays the next reservation situation. This allows any user to grasp the reservation status of the conference room.

<Example of standby screen of the present embodiment>
FIG. 2 is a diagram showing an example of a standby screen 501 displayed by the conference room terminal 90. FIG. 2A shows a standby screen 501 before the private information shown for comparison is made private. Details of the standby screen 501 will be described later. In the standby screen 501 of FIG. 2A, “Sample Co., Ltd. New Technology Workshop” is displayed as the conference name column 563. This meeting name column 563 includes the company name and the contents of the meeting, and there is a risk that important information may be unintentionally leaked.

Therefore, in the resource reservation system 100 of the present embodiment, the conference room terminal 90 keeps the preset non-public information private. FIG. 2B shows a standby screen 501 in which private information is private. In FIG. 2, “meeting” is displayed in the conference name column 563. Compared with FIG. 2A, the company name and the contents of the meeting are closed, and the risk of leaking important information can be reduced.

Specifically, the resource reservation system 100 of the present embodiment can set the reservation information to the non-disclosure when the reservation person reserves the conference room in the reservation management server 20. In addition, private information is registered in the conference management server 30. For example, it is assumed that non-public information “Headquarters” is registered.

When a reservation person reserves a conference room with a conference name of “meeting for determining policy of headquarters”, the conference management server 30 sets the reservation information to non-disclosure so that the content is not leaked to a third party. However, the conference management server 30 has an operation mode in which the item to be hidden is hidden even if the reservation person forgets the setting to hide it.

When the private setting is made, the conference management server 30 sets the item of the reservation information including the private information “Headquarters” to the private and transmits the reservation information to the conference room terminal 90. More specifically, the meeting management server 30 specifies an item to be closed (closed target item) for each piece of private information, and closes the closed target item associated with “Headquarters”. .. At least a part of the reservation information may be closed. The meeting room terminal 90 hides the non-disclosure target items on the standby screen 501, so that it is possible to prevent the fact that the “meeting for determining the policy of the headquarters” is being held in the conference room from being leaked to a third party. You can

<About terms>
A resource is a resource. The conference room and the equipment, devices, people (reception), and mechanisms that can be used in the conference room can be resources. Equipment that is hard to move among resources is called equipment. In this embodiment, for convenience of description, the term conference room is used as an example of a resource.

The reservation person is the person who has reserved the conference room, and the participants are participants in the conference. Reservers are often included in the participants, but need not be included. In some cases, the work performed by the reservation person in this embodiment can be performed by the participant. Those who collectively use the conference room are simply called users.

The setting information is information related to changing the display content of the reservation information. It includes the fact that the reservation information is changed. It may also include how to change. For example, hiding or fixed notation is included. It may also include information to be hidden.

The display content of the reservation information is the content when the reservation information is displayed. It does not have to be the entire reservation information, but refers to the part that is displayed.

<System configuration example>
FIG. 3 is a system configuration diagram of an example of the resource reservation system 100. The resource reservation system 100 can be mainly divided into an external network N2 and an internal network N1. The in-house network N1 refers to a network inside the firewall 73, and the outside network N2 is a network such as the Internet through which an unspecified number of communications are transmitted.

A reservation management server 20, a conference management server 30, and one or more chat servers 10 are connected to the external network N2, and each server can communicate as necessary. The terminal device 60 operated by the participants of the conference may be connected to the external network N2 as necessary.

The reservation management server 20 is realized by one or more information processing devices (computer systems) equipped with a general server OS and the like. A system related to the facility reservation provided by the reservation management server 20 is called a reservation management system. The reservation management server 20 has a calendar system and provides a web application for managing various schedules. Specifically, for example, it has the following functions.
・Acceptance of appointments can be confirmed by the reservation person ・Email is sent at a set date and time, such as 30 minutes before the appointment ・Each person can manage the appointments with multiple calendars (work, home, etc.) -The reservation management server 20 that shares a calendar with people in the same group manages users with accounts. An account is a user's right to use the service. On many systems users log in to the system using an account. Therefore, the account has a function of the system to uniquely identify the user (a function of identification information). In this embodiment, the reservation management server 20 transmits the reservation information of the account (domain) registered in advance to the conference management server 30. Alternatively, the conference management server 30 can obtain the reservation information of the conference room 6 from the reservation management server 20 by designating the account of the reservation management server 20 and requesting the reservation information by the conference management server 30. The account may be any information that can uniquely identify the user, such as e-mail, ID, and telephone number.

In the present embodiment, it is the reservation of the conference room 6 that is managed as the schedule, but the reservation management server 20 is not limited to the conference room 6 and can manage various schedules. In addition to the conference room 6, various electronic equipment rentals, parking reservations, rental offices, rental studios, rental cycles, rental cars, accommodation facilities such as hotels, rental spaces such as entertainment venues and lockers, etc. Available for booking.

Note that G Suite (registered trademark), Office365 (registered trademark), and the like are known as reservation management systems, but any reservation management system having the function described in the present embodiment may be used.

Further, in the present embodiment, information regarding the conference room 6 of the in-house network N1 is registered in advance in the reservation management server 20. That is, the reservation management server according to the conference room name, the conference room ID, the reservable time, the capacity of each conference room 6, the reservation unit, etc. of each conference room 6 in the company internal network of the company that uses the resource reservation system 100. 20 web apps have been customized. Therefore, the conference room 6 of the company that uses the resource reservation system 100 is linked with the reservation information.

The chat server 10 can be realized by one or more information processing devices (computer systems) equipped with a general server OS or the like. A chat system is a real-time sharing system provided by the chat server 10 for information such as text, voice, and video among a plurality of users. The chat server 10 notifies the terminal device 60 of information regarding the reservation of the conference room 6. In this embodiment, a plurality of chat servers 10 having different management entities may be included.

The shared information includes images, sounds, etc. and is not limited to text, but in the present embodiment, text is mainly used for notification for convenience of description. For example, the chat system may provide voice call functionality between groups. The voice call may be one-to-one or one-to-N (≧2). Therefore, in the present embodiment, when the chat system notifies the information regarding the reservation of the conference room 6, not only the text display but also the voice message output may be performed. Known chat systems include LINE (registered trademark; hereinafter abbreviated), slack (registered trademark), Microsoft Teams (registered trademark, abbreviated below), and the like, but a bot (predetermined in advance). A chat system capable of notifying one or a plurality of users from a program that executes a certain process).

Similarly, the chat server 10 manages the user with an account (different from the account of the reservation management server 20), but in principle, the conference management server 30 does not need to be aware of the account of the chat server 10. However, the conference management server 30 can specify any account of the chat server 10 to notify.

The conference management server 30 can be realized by one or more information processing devices (computer systems) equipped with a general server OS or the like. The conference management server 30 acquires the reservation information of the conference room 6 from the reservation management server 20 as a process related to the outside network N2, acquires the prospective participants set in the reservation information, and schedules the prospective participants at the set timing. The notification is transmitted to the group (or individual person such as a reservation person) of the chat server 10 associated with. In addition, as a process related to the in-house network N1, management of check-in and check-out to the conference room 6 is performed, and power supply of the electronic device 70 is controlled based on the reservation information of the conference room 6 acquired from the reservation management server 20. To do.

The conference management server 30 and the reservation management server 20 may be provided as one server or a service, and a system having such a plurality of servers is called a server system.

The in-house network N1 has a conference room 6, a work place 101 for prospective participants, a work place 102 for managers, etc. The prospective participants can access the outside network N2 from various places via the in-house network N1. The in-house network N1 is, for example, a LAN (Local Area Network). The conference room 6, the prospective participant's work place 101, and the manager's work place 102 are not necessarily LANs in the same company.

A conference room terminal 90 and an electronic device 70 are arranged in the conference room 6. The conference room terminal 90 and the electronic device 70 can communicate with each other via a small LAN or a dedicated line. The electronic device can be connected to the internal network N1 and the external network N2 without passing through the conference room terminal 90. The conference room terminal 90 and the electronic device 70 may communicate with each other wirelessly or by wire. Since the in-house network N1 is inside the firewall 73, it is difficult to directly communicate from the outside network N2 to the in-house network N1.

The conference room terminal 90 is an information processing terminal operated by participants of a conference such as a reservation person who uses the conference room 6. The conference room terminal 90 is installed on the desk of the conference room 6 or installed at the entrance of the conference room 6. A plurality of conference room terminals 90 may be installed in one conference room 6. The conference room terminal 90 can be realized by one or more information processing devices (computer systems) equipped with a general OS and the like.

The conference room terminal 90 transmits the conference room ID to the conference management server 30, and displays the reservation information of the conference room 6 of the day. Further, the reservation information is periodically requested and the changed reservation information is acquired. Further, control information such as power ON/OFF of the electronic device 70 is acquired from the conference management server 30. As a result, the conference room terminal 90 turns on and off the power of the electronic device 70.

The conference room terminal 90 also displays a standby screen 501 for check-in, check-out, etc., and communicates with the conference management server 30 to notify the conference management server 30 of check-in or check-out. At the time of check-in, the conference room terminal 90 transmits the conference identification information input from the reservation person and the conference room ID held in advance to the conference management server 30, so that the conference management server 30 uses the conference identification information and the conference room ID to It can be confirmed that the reservation person who reserved the conference room 6 uses the reserved conference room 6.

The electronic device 70 is various office devices that can be used in the conference room 6. For example, an electronic blackboard, a multifunction peripheral, a projector, a digital signage, a digital camera, etc. The electronic blackboard has a large display with a touch panel and detects the coordinates of the board surface designated by the user and connects the coordinates to display a stroke. In addition to this, it is possible to display an image of a connected PC or to communicate with an electronic blackboard at another site to synchronize strokes. The electronic blackboard may also be called an electronic information board or an electronic whiteboard.

The multi-function peripheral has functions such as a copying machine, a scanner, a printer, and fax transmission/reception, and is used for printing materials during a conference, copying materials, digitizing materials, and transmitting materials. A projector is a device that projects an image. For example, the terminal device 60 makes it possible to share the image by displaying the image displayed on the display on the screen or the like among the participants. Digital signage is a large display used to display any still or moving image. The digital camera is used by each participant to capture and store paper materials or materials displayed on an electronic blackboard.

A terminal device 60 capable of connecting to the in-house network N1 is arranged in the work place 101 of the prospective participant. The terminal device 60 may communicate by wire or wirelessly. The terminal device 60 is an information processing device used when a prospective participant (including a reservation person) reserves a conference room, but it is also supposed to be brought into the conference room. It is an information processing device carried by a prospective participant.

The terminal device 60 can be realized by one or more information processing devices (computer systems) equipped with a general OS or the like. The terminal device 60 is, for example, a smartphone, a tablet terminal, a PC (Personal Computer), a PDA (Personal Digital Assistant), a wearable PC (sunglasses type, wristwatch type, etc.). However, browser software having a communication function or application software dedicated to the chat server 10 or the reservation management server 20 may operate. For example, a car navigation system, a game machine, a television receiver, etc. can be the terminal device 60.

In the terminal device 60, dedicated application software (hereinafter referred to as chat application) operates on the chat server 10, and further dedicated application software (hereinafter referred to as conference application) operates on the resource reservation system 100. However, these may be replaced by browser software.

A registration terminal 50 capable of connecting to the in-house network N1 is arranged at the work place 102 of the administrator. The registration terminal 50 may communicate by wire or wirelessly. The registration terminal 50 is a terminal for the administrator to make various settings in the conference management server 30.

The registration terminal 50 may be the same information processing device as the terminal device 60. However, since it is mainly used for the administrator to set the conference management server 30, there is no need for a chat application or a conference application. The registration terminal 50 mainly communicates with the conference management server 30 using browser software and displays a web page.

<Hardware configuration>
<< Hardware configuration of conference management server >>
FIG. 4 is a hardware configuration diagram of an example of the conference management server 30. 3 is an example of a schematic hardware configuration diagram of a conference management server 30. FIG. The conference management server 30 includes a CPU 201 and a memory 202 that enables high-speed access to data used by the CPU 201. The CPU 201 and the memory 202 are connected via a system bus 203 to other devices or drivers of the conference management server 30, for example, a graphics driver 204 and a network driver (NIC) 205.

The graphics driver 204 is connected to an LCD (display device, an example of a display) 206 via a bus and monitors a processing result by the CPU 201. Further, the network driver 205 connects the conference management server 30 to the external network N2 at the transport layer level and the physical layer level to establish a session with another device.

An I/O bus bridge 207 is further connected to the system bus 203. On the downstream side of the I/O bus bridge 207, a storage device such as an HDD (hard disk drive) 209 via an I/O bus 208 such as PCI via IDE, ATA, ATAP80I, serial ATA, SCSI, USB, or the like. Are connected. The HDD 209 stores a program 209p that controls the entire conference management server 30. The HDD 209 may be an SSD (Solid State Drive). The program 209p may be distributed while being stored in a storage medium, or may be distributed from a program distribution server.

Further, an input device 210 such as a keyboard and a mouse (referred to as a pointing device) is connected to the I/O bus 208 via a bus such as a USB and receives an input and a command from an operator such as a system administrator. There is.

The illustrated hardware configuration of the conference management server 30 shows hardware elements that the conference management server 30 preferably has.

The hardware configuration diagrams of the reservation management server 20, the chat server 10, the registration terminal 50, and the terminal device 60 are the same as or different from those of the conference management server 30, but the resource reservation system 100 of the present embodiment will be described. There is no obstacle on the above. Further, since the conference management server 30, the reservation management server 20, and the chat server 10 are compatible with cloud computing, their hardware configurations are such that hardware resources are dynamically connected/disconnected according to the load. May be composed of Note that cloud computing refers to a usage mode in which resources on a network are used without being aware of specific hardware resources.

<< conference room terminal >>
FIG. 5 is a hardware configuration diagram of an example of the conference room terminal 90. Two hardware configuration examples of the conference room terminal 90 are shown. Note that the conference room terminal 90 in FIG. 5 is assumed to be a tablet device. The conference room terminal 90 in FIG. 5A includes a CPU 301, a ROM 302, a RAM 303, an EEPROM 304, a CMOS sensor 305, an acceleration/direction sensor 306, and a media drive 308.

The CPU 301 controls the entire operation of the conference room terminal 90. The ROM 302 stores a basic input/output program. The RAM 303 is used as a work area for the CPU 301. The EEPROM 304 reads or writes data under the control of the CPU 301. The CMOS sensor 305 images a subject and obtains image data under the control of the CPU 301. The acceleration/direction sensor 306 is an electronic magnetic compass, a gyro compass, an acceleration sensor, or the like that detects geomagnetism.

The media drive 308 controls reading or writing (storage) of data with respect to the medium 607 such as a flash memory. The media drive 308 has a configuration in which a medium 607 for reading the already recorded data or newly writing the data therein and storing the data is removable.

A program 604p executed by the CPU 301 is stored in the EEPROM 304. The program 604p is application software or OS for executing various processes in the embodiment. The program 604p may be distributed while being stored in the medium 607 or the like, or may be distributed from a program distribution server.

The CMOS sensor 305 is a charge-coupled device that converts light into electric charges and digitizes an image of a subject. The CMOS sensor 305 may be, for example, a CCD (Charge Coupled Device) sensor as long as it can image a subject. The CMOS sensor 305 can read a barcode or a two-dimensional barcode.

Furthermore, the conference room terminal 90 includes an RF tag reader/writer 322, an antenna I/F 323, and a vibration actuator 324. The RF tag reader/writer 322 communicates according to a standard such as NFC (Near Field Communication).

The vibration actuator 324 is a motor that vibrates the conference room terminal 90. For example, when the end time of the conference is approaching, the conference room terminal 90 vibrates to notify the participant of the fact.

Furthermore, the conference room terminal 90 includes a voice input unit 309, a voice output unit 310, an antenna 311, a communication unit 312, a wireless LAN communication unit 313, a short-range wireless communication antenna 314, a short-range wireless communication unit 315, a display 316, and a touch panel 317. And a bus line 319.

The voice input unit 309 converts voice into a voice signal. The voice output unit 310 converts a voice signal into voice. The communication unit 312 uses the antenna 311 to communicate with the nearest base station device using a wireless communication signal. The wireless LAN communication unit 313 performs wireless LAN communication conforming to the IEEE 802.11 standard.

The short-range wireless communication unit 315 is a communication device that uses the short-range wireless communication antenna 314 and that conforms to the communication standard of, for example, Bluetooth (registered trademark) or Bluetooth Low Energy (registered trademark).

The display 316 is a liquid crystal or an organic EL that displays an image of a subject, various icons, and the like. The touch panel 317 is placed on the display 316 and is configured by a pressure-sensitive or electrostatic panel, and detects a touch position on the display 316 by touching with a finger, a touch pen, or the like. The bus line 319 is an address bus, a data bus, or the like for electrically connecting the above-mentioned units.

In addition, the conference room terminal 90 includes a dedicated battery 618 and can be driven by either the battery 618 or a commercial power source. The voice input unit 309 includes a microphone for inputting voice. The audio output unit 310 includes a speaker that outputs audio.

FIG. 5B is also an example of a hardware configuration diagram of the conference room terminal 90. As shown in FIG. 5B, the conference room terminal 90 includes a CPU 701, a ROM 702, a RAM 703, an EEPROM 704, a CMOS sensor 705, an image sensor I/F 706, an acceleration/direction sensor 707, a media I/F 709, and GPS reception. The unit 711 is provided.

Of these, the CPU 701 controls the operation of the entire conference room terminal 90. The ROM 702 stores programs used for driving the CPU 701 such as the CPU 701 and the IPL. The RAM 703 is used as a work area for the CPU 701. The EEPROM 704 reads or writes various data such as applications under the control of the CPU 701. The CMOS (Complementary Metal Oxide Semiconductor) sensor 705 is a type of a built-in image pickup unit that obtains image data by capturing an image of a subject (mainly a self-portrait) under the control of the CPU 701. Note that instead of the CMOS sensor, an imaging means such as a CCD (Charge Coupled Device) sensor may be used. The image sensor I/F 706 is a circuit that controls driving of the CMOS sensor 705. The acceleration/direction sensor 707 is various sensors such as an electronic magnetic compass that detects geomagnetism, a gyro compass, and an acceleration sensor. The media I/F 709 controls reading or writing (storage) of data with respect to the recording medium 708 such as a flash memory. The GPS receiving unit 711 receives GPS signals from GPS satellites.

The conference room terminal 90 includes a long-distance communication circuit 712, a CMOS sensor 713, an image sensor I/F 714, a microphone 715, a speaker 716, a sound input/output I/F 717, a display 718, and an external device connection I/F (Interface) 719. The short-range communication circuit 720, the antenna 720a of the short-range communication circuit 720, and the touch panel 721 are provided.

Of these, the long-distance communication circuit 712 is a circuit that communicates with other devices via a communication network. The CMOS sensor 713 is a type of a built-in image pickup unit that obtains image data by capturing an image of a subject under the control of the CPU 701. The image sensor I/F 714 is a circuit that controls driving of the CMOS sensor 713. The microphone 715 is a built-in circuit that converts sound into an electric signal. The speaker 716 is a built-in circuit that converts electrical signals into physical vibrations and produces sounds such as music and voice. The sound input/output I/F 717 is a circuit that processes input/output of a sound signal between the microphone 715 and the speaker 716 under the control of the CPU 701. The display 718 is a kind of display means such as a liquid crystal or an organic EL (Electro Luminescence) for displaying an image of a subject and various icons. The external device connection I/F 719 is an interface for connecting various external devices. The near field communication circuit 720 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The touch panel 721 is a kind of input means for operating the conference room terminal 90 by the user pressing the display 718.

Further, the conference room terminal 90 includes a bus line 710. The bus line 710 is an address bus, a data bus, or the like for electrically connecting the respective constituent elements such as the CPU 701 shown in FIG.

<About function>
FIG. 6 is an example functional block diagram showing the functions of the reservation management server 20, the chat server 10, the conference management server 30, and the registration terminal 50 in block form.

<<Reservation management server>>
The reservation management server 20 has a communication unit 21 and a reservation information management unit 22. Each of these functional units included in the reservation management server 20 is realized by one of the components shown in FIG. 4 being operated by an instruction from the CPU 201 according to the program 209p loaded from the HDD 209 into the memory 202. Function or means.

The communication unit 21 transmits and receives various types of information to and from the conference management server 30 and the terminal device 60. The communication unit 21 transmits the screen information of the reservation setting screen to the terminal device 60 and receives the reservation setting from the terminal device 60. Also, the reservation information is transmitted to the conference management server 30.

The reservation information management unit 22 is a general Web server (Web application) that receives reservation information, and further manages reservation information registered by the user. When the reservation information is registered (or changed), the reservation information management unit 22 notifies the conference management server 30 of the reservation user's account, and via the communication unit 21 in response to a request from the conference management server 30 designating the account. And transmits the reservation information to the conference management server 30. The changed reservation information may be transmitted to the conference management server 30 without a request. A general web application is used as a method for the reservation person to reserve the conference room 6 in the reservation management server 20.

The reservation management server 20 has a storage unit 29. The storage unit 29 is realized by the memory 202, the HDD 209, and the like shown in FIG. A reservation information DB 291 (Data Base) is stored in the storage unit 29.

表１は予約情報ＤＢ２９１に記憶されている予約情報の一例を示す。予約情報は会議室６の予約状況を管理するための情報である。予約情報には、予約ＩＤに対応付けて予約者アカウント、会議名、会議室ＩＤ、開始時刻、終了時刻、参加予定者アカウント、及び、非公開フラグの各項目が登録されている。予約ＩＤは予約情報の１レコードを識別する識別情報である。ＩＤはIdentificationの略であり識別子や識別情報という意味である。ＩＤは複数の対象から、ある特定の対象を一意的に区別するために用いられる名称、符号、文字列、数値又はこれらのうち１つ以上の組み合わせをいう。予約ＩＤ以外のＩＤについても同様である。予約者アカウントは会議室６を予約した参加予定者のアカウントである。会議名は参加予定者が任意に付与した会議の名称である。会議室ＩＤは社内ネットワークにある会議室６を識別する識別情報である。開始時刻は会議室６が予約された時間帯の始期（会議が開始される時刻）であり、終了時刻は会議室６が予約された時間帯の終期（会議が終わる時刻）である。参加予定者アカウントは会議に参加する予定の参加予定者のアカウントである。なお、表１のアカウントはいずれも予約管理サーバ２０が発行したアカウントである。非公開フラグは、予約情報の登録時に予約者が設定した、予約情報を非公開とするか否かの設定である（図８の非公開設定欄）。

Table 1 shows an example of the reservation information stored in the reservation information DB 291. The reservation information is information for managing the reservation status of the conference room 6. In the reservation information, items of a reservation account, a conference name, a conference room ID, a start time, an end time, a prospective participant account, and a non-disclosure flag are registered in association with the reservation ID. The reservation ID is identification information that identifies one record of reservation information. ID is an abbreviation of Identification and means an identifier or identification information. The ID refers to a name, a code, a character string, a numerical value, or a combination of one or more of these, which is used to uniquely distinguish a specific object from a plurality of objects. The same applies to IDs other than the reservation ID. The reservation user account is an account of a prospective participant who reserved the conference room 6. The meeting name is the name of the meeting arbitrarily given by the prospective participants. The conference room ID is identification information for identifying the conference room 6 on the in-house network. The start time is the beginning of the time zone when the conference room 6 is reserved (the time when the conference starts), and the end time is the end of the time zone when the conference room 6 is reserved (the time when the conference ends). The prospective participant account is an account of a prospective participant who plans to participate in the conference. All the accounts in Table 1 are accounts issued by the reservation management server 20. The non-disclosure flag is a setting set by the reservation person when the reservation information is registered and is for setting whether or not to make the reservation information non-disclosure (non-disclosure setting column in FIG. 8).

<<Chat server>>
The chat server 10 includes a communication unit 11 and a text processing unit 12. Each of these functional units included in the chat server 10 is realized by any one of the configuration categories shown in FIG. Function or means.

The communication unit 11 transmits/receives various types of information to/from the conference management server 30. In this embodiment, the information about the reservation of the conference room, the information for identifying the bot (for example, the token), and the information for specifying the group of the notification destination are received from the conference management server 30. The information for identifying the bot has been previously notified from the chat server 10 as the bot identification information when the bot of the conference management server 30 is created. In addition, an individual account such as a subscriber may be designated. Further, the communication unit 11 transmits to the conference management server 30 a message indicating that the prospective participant has already read the information regarding the reservation for the conference room or the response of the prospective participant for the displayed information regarding the reservation for the conference room.

Based on the information for identifying the bot notified from the conference management server 30 and the information for specifying the notified group, the text processing unit 12 reserves the conference room 6 for the prospective participants who belong to the group as the information that the bot speaks. Send information about. The notification may be given only to the number of prospective participants, or may be given only to the reservation person or the notified user.

The text processing unit 12 can perform so-called push notification. A known mechanism provided by each OS is used for the push notification.

The chat server 10 also has a storage unit 19. The storage unit 19 is realized by the memory 202 and the HDD 209 of FIG. A group information DB 191 is stored in the storage unit 19.

表２はグループ情報ＤＢ１９１に記憶されているグループ情報の一例を示す。グループ情報は同じグループに属するメンバのアカウントが登録された情報である。グループ情報には、ワークスペースとチャンネルに対応付けて、メンバアカウント１〜ｎ（表２ではｎ＝４）、及び、ボットアカウントが登録されている。

Table 2 shows an example of group information stored in the group information DB 191. Group information is information in which accounts of members belonging to the same group are registered. In the group information, member accounts 1 to n (n=4 in Table 2) and bot accounts are registered in association with workspaces and channels.

The workspace is identification information for identifying organizations such as companies and departments. In this embodiment, a plurality of members belong to the workspace (for example, company A). The workspace is, for example, a URL, but may be unique. Further, the workspace has a plurality of channels according to the purpose of chat and the like. A channel is, for example, a group for members such as a group for product A and a group for product B with which common information is exchanged. Any of the members belonging to the workspace belongs to the channel. That is, the notification destination is specified by the workspace and the channel. However, since the method of identifying the notification destination differs depending on the chat system, if there is identification information that can uniquely identify the group, only that information may be used, or it may be identified by three or more pieces of information.

Channels are guaranteed unique. Member accounts 1 to n are accounts of members of the channel, and this account is issued by the chat server 10. In the present embodiment, the bot is registered as a member for notifying the information regarding the reservation of the conference room 6. The bot can be said as a representative of the conference management server 30 or a fictitious member. The bot's statement (text) is transmitted to the terminal devices 60 of the member accounts 1 to n.

The workspace and channel are managed by the conference management server 30 and serve as information for identifying the group to which the participant belongs.

<< Meeting Management Server >>
The conference management server 30 includes a communication unit 31, an information association unit 32, a reservation information acquisition unit 33, a notification determination unit 34, a control information generation unit 35, a control information response unit 36, a conference information notification unit 37, and a check-in management unit 38. The non-disclosure processing unit 39, the non-disclosure information registration reception unit 40, and the reservation information transmission unit 41. Each of these functional units included in the conference management server 30 is realized by one of the configuration categories shown in FIG. 4 being operated by an instruction from the CPU 201 according to the program 209p loaded from the HDD 209 into the memory 202. Function or means. The program 209p is distributed from a server for distributing the program or distributed while being stored in a storage medium.

The communication unit 31 transmits and receives various information to and from the reservation management server 20, the chat server 10, the registration terminal 50, and the terminal device 60. The communication unit 31 has a transmission unit 31a and a reception unit 31b. The receiving unit 31b receives the reservation information from the reservation management server 20, and receives the reservation information request from the conference room terminal 90. The receiving unit 31b also receives a check-in request from the conference room terminal 90. Further, the receiving unit 31b receives the association between the group and account of the chat system from the registration terminal 50 operated by the administrator. The transmission unit 31a transmits information regarding reservation of the conference room to the chat server 10 and transmits reservation information to the conference room terminal 90.

The information associating unit 32 mainly performs a process relating to the registration work in advance. That is, the registration of the domain is accepted from the registration terminal 50 operated by the administrator, registered in the customer domain DB 495, and the workspace and channel of the chat system transmitted from the registration terminal 50 are associated with the account of the reservation management server 20. It registers in correspondence information DB491.

The reservation information acquisition unit 33 specifies the account of the customer who uses the resource reservation system 100, acquires the reservation information from the reservation management server 20, and registers it in the meeting management information DB 493 as the meeting management information. The account of the registered or updated reservation information notified from the reservation management server 20 may be designated, or any account may be designated. At least a part of the reservation information of the reservation information of the reservation management server 20 is stored in the conference management information DB 493. The reservation information acquisition unit 33 acquires reservation information from the present to the future for a predetermined period of time among the reservation information held by the reservation management server 20. The predetermined period is determined by how many conferences ahead the notification regarding the reservation of the conference room 6 is given.

The notification determination unit 34 determines whether or not there is a reservation of the start time that satisfies the condition to be notified in the conference management information. For example, referring to the notification setting DB 496, it is determined that the notification will be given when the date and time set by calculating backward from the reservation start time comes. Alternatively, when the reservation information acquisition unit 33 acquires the reservation information from the reservation management server 20, the notification determination unit 34 may generate a task for notifying information regarding the reservation and register the task in the queue. The task saved in the queue is executed when the execution time (reminding time) arrives.

If the bots are divided according to their roles, such as a reminder bot and a reservation acceptance bot, the bot is specified according to the processing.

When the notification determining unit 34 determines that the notification determining unit 34 notifies, the conference information notifying unit 37 notifies the information regarding the reservation of the conference room 6 by specifying the information for identifying the bot (for example, a token in slack) and the information for specifying the group of the notification destination. The chat server 10 is requested to do so. It should be noted that although the notification is divided into several times, the meeting identification information is included in at least one of the notifications. The conference identification information is information for the conference management server 30 to confirm that the participants have the right to use the reserved conference room 6 in the reserved time zone. The meeting information notification unit 37 generates the meeting identification information at least before the final notification. The conference identification information is registered in the conference identification information DB 494.

The control information generation unit 35 refers to the conference management information, generates control information for the electronic device 70, and registers the control information in the control information DB 497. For example, the control information for turning on the power of the electronic device 70 is generated several minutes before the start time of the conference, and the control information for turning off the power of the electronic device 70 is generated when the checkout is detected. The control information is stored in the control information DB 497.

The control information response unit 36 receives an inquiry from the conference room terminal 90 in the conference room 6 as to whether there is control information, refers to the control information DB 497, and transmits the control information corresponding to the conference room 6 to the conference room terminal 90. ..

The check-in management unit 38 manages check-in/check-out to the conference room. Also, the status of the meeting mainly associated with check-in/check-out is registered in the meeting management information DB 493. Check-in is accepted 5-10 minutes before the start time of the meeting identified by the reservation ID. Then, when the set of the conference room ID and the conference identification information transmitted from the conference room terminal 90 is registered in the conference identification information DB 494, the check-in is permitted.

The non-disclosure processing unit 39 performs a process of non-disclosure of reservation information. First, the user setting priority mode for performing the process of making the reservation information private only when the effect of making the reservation information private (the private setting column of FIG. 8, the private flag of Table 1) is set, and the reservation information There is a compulsory mode in which the process of forcibly making private is carried out even when the fact of making private (non-public setting column of FIG. 8, private flag of Table 1) is not set. These modes are preset by the administrator. In the case of the user setting priority mode, the non-disclosure processing unit 39 determines whether or not the reservation information is non-disclosure (non-disclosure setting column in FIG. 8, non-disclosure flag: ON in Table 1) is set. .. In the case of the reservation information set to be closed, it is determined whether or not the reservation information includes private information by referring to the private information DB 498 described later. If it is included, create an indication that the corresponding non-disclosure target item is hidden or that it is fixed notation (non-disclosure setting). In the forced mode, regardless of whether or not there is a secret setting (even if the reservation information is not set to be secret), the secret information is included in the reservation information by referring to the secret information DB 498. If so, create an indication that the corresponding reservation information item is hidden or that it is fixed notation (non-disclosure setting).

The private information registration receiving unit 40 provides a web application that receives registration of private information from the registration terminal 50. That is, screen information of a private information management screen (FIGS. 9 to 11) described later is generated and transmitted to the registration terminal 50 via the communication unit 31, and registration of private information is accepted from the registration terminal 50. The private information that has received the registration is stored in the private information DB 498. The screen information is created by HTML, CSS (Cascade Style Sheet), JavaScript (registered trademark), or the like.

The reservation information transmission unit 41 transmits the reservation information (conference management information) stored in the conference management information DB 493 in response to the request from the conference room terminal 90. The reservation information transmission unit 41 may transmit in the JSON format, the XML format, the CVS (Comma-Separated Values) format, or the like. Since the reservation information is repeatedly transmitted, it is advantageous to use a format having a small capacity.

The conference management server 30 also has a storage unit 49. The storage unit 49 is realized by the memory 202, the HDD 209, and the like shown in FIG. The storage unit 49 stores a correspondence information DB 491, a meeting management information DB 493, a meeting identification information DB 494, a customer domain DB 495, a notification setting DB 496, a control information DB 497, and a non-disclosure information DB 498.

表３は対応付情報ＤＢ４９１に記憶されている対応付情報の一例を示す。対応付情報は予約管理システムのアカウントとチャットシステムのグループを対応付ける情報である。対応付情報は、ワークスペース、チャンネル及びメンバアカウント１〜ｎ（表ではｎ＝４）の各項目を有する。ワークスペースとチャンネルは上記のとおりである。メンバアカウント１〜ｎには予約管理サーバ２０が発行した各参加者のアカウントが登録される。また、表３に示すようにチャットシステムのアカウントが登録されてよい。グループに対して通知を行うためには予約管理サーバ２０に対して会議を予約したユーザの予約管理サーバ２０のアカウントと通知先のグループ及びチャンネルを特定するための情報（本実施形態ではワークスペースとチャンネル名）があればよく、必ずしもグループに所属するすべてのメンバのアカウントが登録されている必要はない。ただし、個人ユーザ宛に通知する場合、それぞれのチャットシステムのアカウント情報が必要なため、表３のように登録されていてもよい。

Table 3 shows an example of the association information stored in the association information DB 491. Correspondence information is information that associates an account in the reservation management system with a group in the chat system. The correspondence information has items of workspace, channel, and member accounts 1 to n (n=4 in the table). The workspace and channels are as described above. The account of each participant issued by the reservation management server 20 is registered in the member accounts 1 to n. Moreover, as shown in Table 3, an account of the chat system may be registered. In order to notify the group, information for identifying the account of the user who reserved the conference with respect to the reservation management server 20 and the group and channel of the notification destination (workspace in this embodiment). Channel name), and it is not always necessary to register the accounts of all members who belong to the group. However, when notifying to an individual user, account information of each chat system is required, and thus the registration may be performed as shown in Table 3.

表４は会議管理サーバ３０の会議管理情報ＤＢ４９３が記憶する会議管理情報の一例を示す。会議管理情報ＤＢ４９３には予約情報が記憶されるので、表４では表１の予約情報ＤＢ２９１との相違を説明する。表４の会議管理情報は予約者の表記名、予約者の所属名、参加者の表記名、参加者の所属名、及び、ステータスの項目を有する。予約者の表記名は予約者の氏名などである。予約者の所属名は予約者が所属する部署名である。参加者の表記名は参加者の氏名などである。参加者の所属名は参加者が所属する部署名である。会議管理サーバ３０ではアカウントと表記名、所属名などを対応付けたユーザ情報を保持しているか利用可能なので、アカウントが分かればこれらも判明する。なお、予約管理サーバ２０から送信される時点で予約者の表記名、予約者の所属名、参加者の表記名、参加者の所属名が含まれていてもよい。

Table 4 shows an example of the conference management information stored in the conference management information DB 493 of the conference management server 30. Since the reservation information is stored in the conference management information DB 493, Table 4 explains the difference from the reservation information DB 291 in Table 1. The conference management information in Table 4 includes items such as the name of the reservation person, the name of the reservation person, the name of the participant, the name of the participant, and the status. The name of the person who made the reservation is the name of the person who made the reservation. The affiliation name of the reservation person is the department name to which the reservation person belongs. Participant's notation name is the participant's name, etc. The affiliation name of the participant is the department name to which the participant belongs. Since the conference management server 30 holds or can use user information in which the account is associated with the notation name, the affiliation name, and the like, it can be known if the account is known. It should be noted that at the time of transmission from the reservation management server 20, the name of the person who made the reservation, the name of the person who made the reservation, the name of the person making the participant, and the name of the person making the participant may be included.

The status means the status of the reservation. For example, statuses such as notification of information regarding reservation of the conference room 6, confirmation of use, check-in, check-out, or cancellation (cancellation) are registered.

表５は会議識別情報ＤＢ４９４に記憶されている会議識別情報管理情報の一例を示す。会議識別情報管理情報は会議室６の予約ごとに会議識別情報を管理する情報である。会議識別情報管理情報は、予約ＩＤ、会議室ＩＤ、及び、会議識別情報の各項目を有する。これらについてはステータスを除き予約情報と同じであり（予約管理サーバ２０から受信した予約情報）、既出であるため説明は省略する。なお、予約ＩＤが登録されているのは、同じ会議室６の予約を識別するためである。

Table 5 shows an example of the conference identification information management information stored in the conference identification information DB 494. The conference identification information management information is information for managing the conference identification information for each reservation in the conference room 6. The conference identification information management information has items of a reservation ID, a conference room ID, and conference identification information. These are the same as the reservation information except for the status (reservation information received from the reservation management server 20), and the description thereof is omitted because it has already been described. The reservation ID is registered in order to identify the reservation for the same conference room 6.

表６は顧客ドメインＤＢ４９５に記憶されている顧客ドメイン情報の一例を示す。顧客ドメイン情報は顧客のドメインと顧客の管理者のアカウントを管理する情報である。顧客ドメイン情報には顧客のドメイン名と顧客の管理者アカウントが対応付けて登録されている。表６の顧客のドメインは予約管理サーバ２０が発行したアカウント（メールアドレス）のドメインである。また、管理者アカウントは、顧客の管理者（代表する）のアカウントである。なお、表６のアカウントは予約管理サーバ２０が発行したものである。

Table 6 shows an example of customer domain information stored in the customer domain DB 495. The customer domain information is information for managing the customer domain and the account of the customer administrator. In the customer domain information, the customer domain name and the customer administrator account are registered in association with each other. The customer domain in Table 6 is the domain of the account (email address) issued by the reservation management server 20. Further, the administrator account is an account of a customer administrator (representative). The accounts in Table 6 are issued by the reservation management server 20.

表７は通知設定ＤＢ４９６に記憶されている通知設定情報の一例を示す。通知設定情報は顧客ごとに通知に関する設定を保持する。通知設定情報には、顧客ドメイン名と通知設定が対応付けて登録されている。通知設定には、会議の開始時刻のどのくらい前に、会議室６の予約に関する情報を通知するかのタイミングが設定されている。あるいは決まった日時が設定されていてもよい。また、タイミングは１つである必要はなく、１つの顧客に複数回の通知設定が登録されていてもよい。

Table 7 shows an example of the notification setting information stored in the notification setting DB 496. The notification setting information holds the setting related to the notification for each customer. In the notification setting information, the customer domain name and the notification setting are registered in association with each other. In the notification setting, the timing at which the information about the reservation of the conference room 6 is notified before the conference start time is set. Alternatively, a fixed date and time may be set. Further, the timing does not have to be one, and one customer may be registered with the notification setting a plurality of times.

表８は制御情報ＤＢ４９７に記憶されている制御情報の一例を示す。制御情報は会議室６の電子機器７０を制御するための情報である。制御情報は、会議室ＩＤ、及び、制御内容の各項目を有する。制御内容は、電子機器７０の具体的な制御方法である。会議管理サーバ３０は電子機器７０ごとに詳細な制御内容を設定できる。また、制御する時刻が登録されないのは、社外ネットワークの会議管理サーバ３０から会議室端末９０に送信することが困難であり、会議室端末９０が会議管理サーバ３０にアクセスし、この時、制御情報が生成されていれば制御内容を送信するからである。

Table 8 shows an example of the control information stored in the control information DB 497. The control information is information for controlling the electronic device 70 in the conference room 6. The control information has a conference room ID and each item of control content. The control content is a specific control method of the electronic device 70. The conference management server 30 can set detailed control contents for each electronic device 70. If the control time is not registered, it is difficult to transmit from the conference management server 30 of the outside network to the conference room terminal 90, and the conference room terminal 90 accesses the conference management server 30. This is because the control content is transmitted if is generated.

表９（ａ）は非公開情報ＤＢ４９８に記憶されている非公開情報に関する設定の一例を示し、表９（ｂ）は固定表記情報の一例を示す。まず、非公開情報ＤＢ４９８は非公開情報、非公開設定名、非公開対象項目、非公開方法、及び、実行する/しない、の各項目を有している。非公開情報は予約情報に含まれている場合に非公開の対象となる情報である。非公開文字列や非公開ワードということができる。非公開設定名は、非公開情報が見つかった予約情報をどのように非公開とするかに関する非公開設定の名称である。操作を容易にするため管理者が非公開設定名を選択すると非公開対象項目と非公開方法が決まるようになっている。非公開対象項目は予約情報のどの項目を非公開にするかを示す。このように、表示に関する情報には非公開にする項目が含まれうる。非公開方法は非公開情報を固定表記とするか非表示とするかを示す。実行する/しないは、対応する非公開情報を非公開とする処理を会議管理サーバ３０が実行するかどうか示す。後述するようにこれらの各設定は管理者が行うことができる。

Table 9(a) shows an example of the settings relating to the private information stored in the private information DB 498, and Table 9(b) shows an example of the fixed notation information. First, the non-disclosure information DB 498 has non-disclosure information, non-disclosure setting name, non-disclosure target item, non-disclosure method, and execution/non-execution items. The non-public information is information to be non-public when included in the reservation information. It can be called a secret character string or a secret word. The private setting name is the name of the private setting regarding how to make the reservation information in which the private information is found private. In order to facilitate the operation, when the administrator selects the private setting name, the private target item and private method are determined. The non-disclosure target item indicates which item of the reservation information is made non-disclosure. As described above, the information regarding the display may include an item to be hidden. The non-disclosure method indicates whether the non-disclosure information is fixed or hidden. Execution/non-execution indicates whether or not the conference management server 30 executes a process of disclosing the corresponding non-public information. As will be described later, each of these settings can be made by the administrator.

The non-public information DB 498 is associated with the conference room ID, and can be constructed for each conference room. As a result, for example, it becomes possible to set non-public information peculiar to the appointment information of the executive conference in the executive conference room. However, the non-public information DB 498 may be common to all conference rooms or a plurality of conference rooms.

The fixed notation information is information that replaces the non-disclosure target item when the non-disclosure method of the non-disclosure information is the fixed notation. A specific fixed notation is associated with the fixed notation ID, and the conference room terminal 90 can identify the fixed notation by the fixed notation ID. The fixed notation information may be downloaded from the conference management server 30 when the conference room terminal 90 is initially set, or may be transmitted to the conference room terminal 90 together with the reservation information.

Table 9(c) is operation mode setting information in which the user setting priority mode or the forced mode is set. The administrator can set the user setting priority mode or the compulsory mode in advance. The default operation mode when not set by the administrator is the forced mode. This can improve security. It is preferable that the operation mode setting information can be set for each conference room. For example, the conference room in which an important conference is held is set to the forced mode, and the conference room in which only a general conference is held is set to the user setting priority mode.

Even if the administrator forgets to make the private setting on the registration terminal 50, it is possible to change the display content and suppress the leakage of confidential information. The conference management server 30 can change the reservation content into a unified expression. Further, individual display settings can be made even in the conference room terminal 90 provided for each conference room (resource).

<< registration terminal >>
The registration terminal 50 has a communication unit 51, an operation reception unit 52, and a display control unit 53. Each of these functional units included in the registration terminal 50 is realized by any one of the components illustrated in FIG. 4 being operated by an instruction from the CPU 201 according to the program 209p loaded from the HDD 209 into the memory 202. Function or means. The program 209p is distributed from a server for distributing the program or distributed while being stored in a storage medium.

The registration terminal 50 is a terminal for an administrator to make various settings regarding the conference room via a web page provided by the conference management server 30. One of these settings is the setting of non-public information shown in Table 9. The terminal device 60 may be used to set the private information. The functions of the communication unit 51, the operation reception unit 52, and the display control unit 53 included in the registration terminal 50 are the same as those of the terminal device 60, and the details will be described together with the terminal device 60.

<< terminal device >>
FIG. 7 is an example functional block diagram showing the functions of the terminal device 60 and the conference room terminal 90 in block form. The function of the electronic device 70 will be described as needed.

The terminal device 60 includes a communication unit 61a, an operation receiving unit 61b, a display control unit 61c, a chat communication unit 62, a text display unit 63, an application communication unit 64, a server communication unit 65, a display control unit 66, an application communication unit 67, and , A terminal communication unit 68. Each of these functional units included in the terminal device 60 is a function realized by any one of the configurations illustrated in FIG. 4 being operated by an instruction from the CPU 201 according to the program 209p expanded from the HDD 209 to the memory 202. Or means. The program 209p is distributed from a server for distributing the program or distributed while being stored in a storage medium. Since the chat application 60a and the conference application 60b are operating in the terminal device 60, the program 209p includes the chat application 60a and the conference application 60b.

The communication unit 61a transmits and receives various information to and from the conference management server 30 and the reservation management server 20. While the chat application 60a communicates with the chat server 10 and the conference application 60b communicates with the conference management server 30, the communication unit 61 can communicate with any server. The communication unit 61a may be provided as a browser function, for example.

The operation reception unit 61b receives various operations of the participant on the terminal device 60. The display control unit 61c interprets screen information of various screens and displays the screen information on the LCD 206. The operation reception unit 61b and the display control unit 61c have, for example, a browser function and can execute a Web application. For example, the display control unit 61c displays the reservation setting screen received from the reservation management server 20, and the operation receiving unit 61b receives the reservation information set by the reservation person.

The chat communication unit 62 of the chat application 60a transmits/receives various information to/from the chat server 10. In the present embodiment, the information related to the reservation of the conference room 6 is received from the chat server 10, and the chat server 10 is notified that it has been read, whether the conference room 6 is used or canceled, and the like.

The text display unit 63 of the chat application 60a displays the text (information regarding the reservation of the conference room 6) transmitted from the chat server 10. For example, the speaker is the bot and the text is displayed as if the bot had typed.

The application communication unit 64 of the chat application 60a calls the conference application 60b and transmits the conference identification information to the conference application 60b. Since the chat server 10 sends the information for identifying the conference application 60b to the terminal device 60 when notifying the information about the reservation of the conference room 6, the chat application 60a specifies the conference application 60b to the OS and identifies the conference. Request notification of information. The OS can activate the conference application 60b.

The server communication unit 65 of the conference application 60b communicates with the conference management server 30. For example, the two-dimensional code including the conference identification information is acquired from the conference management server 30. The two-dimensional code is used for authentication at check-in. It may be several digits for authentication.

The display control unit 66 of the conference application 60b displays a two-dimensional code including the conference identification information on the LCD 206. The application communication unit 67 of the conference application 60b acquires various kinds of information (such as conference identification information included in the information regarding the reservation of the conference room 6) from the chat application 60a via the OS.

The terminal communication unit 68 communicates with the conference room terminal 90 and transmits conference identification information and the like. The terminal communication unit 68 detects the presence of the conference room terminal 90 by short-range wireless communication such as Bluetooth (registered trademark), and transmits the conference identification information when detecting the conference room terminal 90. Further, the function (displaying an image) of displaying the two-dimensional code is provided to the conference room terminal 90.

<< conference room terminal >>
The conference room terminal 90 includes a server communication unit 91, a terminal device communication unit 92, an operation reception unit 93, a display control unit 94, an electronic device communication unit 95, and a reservation information request unit 96. Each of these functional units included in the conference room terminal 90 is a function realized by one of the configurations shown in FIG. 5 being operated by an instruction from the CPU 301 according to a program 604p loaded from the EEPROM 304 to the RAM 303. Or means. This program 604p is distributed from a server for distributing the program or distributed while being stored in a storage medium.

The server communication unit 91 communicates with the conference management server 30 by using the server URL 993 as a destination. Since the conference room terminal 90 exists in the company network, it is difficult for the conference management server 30 to communicate with the conference room terminal 90. Therefore, the server communication unit 91 communicates with the conference management server 30 using a communication technique such as polling (which periodically communicates with the conference management server 30) or WebSocket. The server communication unit 91 may communicate with a communication protocol such as HTTP, and the communication protocol is not particularly limited.

The server communication unit 91 of the present embodiment receives the reservation information, and at the time of check-in, the terminal device communication unit 92 transmits the conference identification information received from the terminal device 60 or the conference identification information manually input to the conference management server 30. To do. Further, the server communication unit 91 receives the control information from the conference management server 30.

The terminal device communication unit 92 communicates with the terminal device 60. In this embodiment, conference identification information and the like are received. When the conference identification information is manually input, the terminal device communication unit 92 may be omitted. The terminal device communication unit 92 is realized by the CPU 301 of FIG. 5 executing the program 604p to control the short-range wireless communication unit 315 or the RF tag reader/writer 322.

The electronic device communication unit 95 communicates with the electronic device 70. In this embodiment, the control information received by the server communication unit 91 is transmitted to the electronic device 70. The electronic device communication unit 95 is realized by the CPU 301 in FIG. 5 executing the program 604p to control the wireless LAN communication unit 313.

The display control unit 94 displays the screen generated by the terminal application 90a on the display 316. This screen is a standby screen 501 that allows check-in and check-out. The display control unit 94 of the present embodiment determines whether or not the reservation information (specifically, the conference management information in Table 4) is set to be non-public. The non-disclosure target item to which the setting is associated is hidden or fixed. As the fixed notation to be instructed, the fixed notation information of Table 9(b) is transmitted from the conference management server 30, or the same fixed notation is stored in the storage unit 99 of the conference room terminal 90.

The operation reception unit 93 receives various operations on the conference room terminal 90. For example, it accepts check-in, input of meeting identification information by hand, or accepts check-out.

The reservation information requesting unit 96 repeatedly transmits the conference room ID 991 stored in the storage unit 99 to the conference management server 30 via the server communication unit 91 at the regular timing of acquiring the reservation information. As a response, the reservation information request unit 96 acquires the reservation information via the server communication unit 91. Reservation information should be acquired only when there is a change. The timing is a cycle of every few seconds to several minutes. If the cycle is shorter, the reservation information can be updated earlier, but the communication load will be higher, so it is determined in consideration of both. In this embodiment, it is set to 30 seconds, for example. Further, at least the conference management information (reservation information) of the conference room 6 of the day can be received via the server communication unit 91.

The conference room terminal 90 also has a storage unit 99. The storage unit 99 is realized by the ROM 302 and the EEPROM 304 shown in FIG. The storage unit 99 stores a conference room ID 991 for specifying a conference room, a server URL 993 of the conference management server 30, a conference room name 994 displayed on the standby screen 501, and an IP address 997 of the electronic device 70.

<Example of reservation setting screen displayed on the terminal>
FIG. 8 shows an example of the reservation setting screen 400 displayed by the terminal device 60. Note that FIG. 8 is a simplified screen example, and items not described in the present embodiment are omitted.

The reservation setting screen 400 includes a conference name input field 401, a start date input field 402a, a start time input field 402b, an end date input field 403a, an end time input field 403b, a conference room selection field 404, a private setting field 405, and It has a participant name column 406. The reservation person logs in to the reservation management server 20 with the account of the reservation management server 20, and inputs necessary items on the reservation setting screen 400.

The conference name input field 401 is a field in which the reservation person inputs an arbitrary conference name. Generally, a conference name that allows the content of the conference to be understood is entered. In the start date input field 402a and the end date input field 403a, for example, the date selected from the calendar displayed by the operation of the reservation person is input. In the start time input field 402b and the end time input field 403b, for example, a time list every 15 minutes is displayed in a pull-down manner, and the time selected by the reservation person is input.

In the conference room selection field 404, a list of conference rooms 6 is displayed in a pull-down format so that a reservation person can arbitrarily select a conference room. The displayed conference room is a conference room that is vacant in the time zone specified by the start date input field 402a, the start time input field 402b, the end date input field 403a, and the end time input field 403b.

The non-disclosure setting column 405 is a column in which the reservation person sets the setting as to whether or not the information of this conference is kept secret (corresponding to the non-disclosure flag in Table 1). The secret flag is referred to by the conference management server 30 when the operation mode is the user setting priority mode, and is not referred to when the operation mode is the forced mode. In the user setting priority mode, if the non-public setting column 405 is checked, it is set to non-public (non-public flag is ON), and if not checked, it is not set to non-public (non-public flag is OFF). The participant name column 406 is a column in which the registrant inputs an arbitrary participant name. For example, the participant name set in the past can be input without re-input by the cookie function of the browser.

<Setting private information>
Next, a method of setting private information will be described with reference to FIGS. 9 to 11. FIG. 9 shows an example of the private information management screen 600. The secret information management screen 600 has items of a check box column 601, a secret information column 602, a secret setting name column 603, and a delete button 604.

The non-public information column 602 is information for searching all information included in the reservation information. When the reservation information includes the same information as the non-public information in the non-public information column 602, the non-public target item (see FIG. 11) of the reservation information is non-public (non-display or fixed notation). When the operation mode is the compulsory mode, the reservation information including the same information as the private information is private even if the private setting field 405 is not checked on the reservation setting screen 400 of FIG. As a result, even if the reservation person forgets to check the non-public setting column, the non-public information can be kept private.

The private setting name column 603 is the name of the private setting. The administrator can easily set the non-disclosure target item and the non-disclosure method by selecting the name of the non-disclosure setting. That is, the non-disclosure setting name can determine the non-disclosure target item and the non-disclosure method (see Table 9(a)). The delete button 604 is a button for the administrator to delete one record (a set of a check box, secret information, and secret setting name).

The check box column 601 is a column for setting whether or not to search the corresponding private information with the reservation information. That is, it is possible to set whether or not the private setting of one record is valid. The setting of the check box column 601 corresponds to “execute/not execute” in Table 9(a).

The record at the bottom of the secret information management screen 600 is blank, and the administrator can input new secret information. When the private setting name field 603 is pressed, the private setting names created in the past are displayed in a pull-down display. Detailed settings of each private setting will be described with reference to FIGS. 10 and 11. When new private information is input, a new blank record is added to the bottom of the private information management screen 600.

The private information management screen 600 also has a save button 605 and a cancel button 606. The save button 605 saves the edit state from when the registration terminal 50 opens the private information management screen 600 until the save button 605 is pressed. The cancel button 606 discards the edit state from when the private information management screen 600 is opened until the cancel button 606 is pressed.

FIG. 10 is an example of the private setting management screen 610 displayed by the registration terminal 50. The private setting management screen 610 is a screen for the administrator to edit or add private settings. The private setting management screen 610 has a check box column 611, a private setting name column 612, an edit button 613, and a delete button 614.

The check box column 611 is a column for the administrator to set whether or not to use the private setting of the private setting name column 612. If the check box column 611 is checked, the private setting can be used, and if it is not checked, the private setting cannot be used.

The edit button 613 is a button for editing the content of the private setting specified in the private setting name column 612. When the edit button 613 is pressed, the private setting edit screen 620 of FIG. 11 is displayed. The delete button 614 is a button for deleting the private setting specified in the private setting name column 612 from the private setting management screen 610.

Further, the non-public setting management screen 610 has an add button 615. The add button 615 is a button for newly adding and displaying a private setting on the private setting management screen 610. When the add button 615 is pressed, the private setting edit screen 620 of FIG. 11 is displayed.

FIG. 11 shows an example of the private setting edit screen 620. The private setting edit screen 620 includes a private setting name column 621, a private target item column 622, a private method column 623, a fixed notation selection button 624, a fixed notation addition button 627, a completion button 625, and a cancel button 626. Have

The secret setting name column 621 is a column for the administrator to edit the name when saving the secret setting. When the administrator edits the existing private setting, the private setting name before editing is displayed in advance. The non-disclosure target item column 622 is a column that the administrator selects from the reservation information by displaying a pull-down menu of items to be made non-disclosure. All items included in the reservation information and information linked to the account can be items that are not disclosed, but for example, the conference name, attendee name, appointment person name, attendee affiliation name, appointment person Affiliation name, etc. can be selected. In addition, it is preferable that items that should not be kept secret, such as the conference start time and the conference end time, cannot be selected as non-disclosure target items.

Since the administrator can arbitrarily select the non-public target item in the non-public target item column 622, not only the item including the non-public information but also the item including no non-public information can be set to non-public. Generally, an item including non-public information should be made non-public, so that an item including non-public information may be set in the non-public target item column 622.

Further, the number of non-disclosure target items is not limited to one, and two or more items may be set. In this case, the non-disclosure setting edit screen 620 may have a plurality of non-disclosure target item columns 622.

In the non-disclosure method column 623, when the non-disclosure target item is made non-disclosure, whether it is hidden or fixed is displayed by, for example, a pull-down menu, and the selection of the administrator is accepted. When the administrator selects a fixed notation in the non-disclosure method column 623, a fixed notation selection button 624 is displayed. When the fixed notation selection button 624 is pressed, the fixed notations already registered are displayed, for example, in a pull-down menu, and the administrator's selection is accepted. The fixed notation addition button 627 is a button for the administrator to add a fixed notation. The administrator can add a new fixed notation by pressing the fixed notation addition button 627. Therefore, the fixed notation can be added to the fixed notation information in Table 9(b).

The completion button 625 is a button for saving the edit state from when the registration terminal 50 opens the non-disclosure setting edit screen 620 until the completion button 625 is pressed. The cancel button 626 is a button for discarding the edit state from when the private setting edit screen 620 is opened until the cancel button 626 is pressed.

<Operating procedure>
FIG. 12 is a sequence diagram of an example showing a procedure in which the conference room terminal 90 hides the reservation information displayed on the standby screen 501.

S1: The administrator operates the registration terminal 50 to cause the registration terminal 50 to communicate with the conference management server 30. The private information registration acceptance unit 40 of the conference management server 30 transmits the screen information of the screens shown in FIGS. 9 to 11 to the registration terminal 50 as a Web application. The communication unit 51 of the registration terminal 50 receives the screen information, and the display control unit 53 of the registration terminal 50 displays the screens shown in FIGS. 9 to 11. When the administrator sets the non-public information, the operation reception unit 52 receives the non-public information, the non-public setting name, the non-public item, the non-public method, and the execution/non-execution, and the communication unit 51 confers these. It is transmitted to the management server 30. The secret information registration receiving unit 40 of the conference management server 30 registers these in the secret information DB 498.

S2: The reservation person reserves the conference room with respect to the reservation management server 20 at an arbitrary timing. That is, the reservation person displays the reservation setting screen shown in FIG. 8 on the terminal device 60 (an example of the reservation terminal), and the conference name, the conference start date, the conference start time, the conference end date, the conference end time, the participants, Enter the meeting room and private settings. The operation reception unit 61b of the terminal device 60 receives these reservation information. The communication unit 61a transmits the reservation information to the reservation management server 20.

S3: The communication unit 21 of the reservation management server 20 receives the reservation information, and the reservation information management unit 22 registers the reservation information in the reservation information DB 291.

S4: The communication unit 21 of the reservation management server 20 notifies the conference management server 30 that the reservation information has been updated by designating the account of the reservation person.

S5: The communication unit 31 of the conference management server 30 receives the fact that the reservation information has been updated, and the reservation information acquisition unit 33 requests the reservation information from the reservation management server 20 by designating an account and acquires it. Note that the reservation information may be designated by information specifying the reservation, such as the reservation ID or the conference room name and the reservation start date and time.

S6: The non-disclosure processing unit 39 of the conference management server 30 determines whether or not the reservation information includes non-disclosure information registered in the non-disclosure information DB 498. When the operation mode is the forced mode, it is not necessary to determine whether or not the non-disclosure setting is checked (non-disclosure flag) at the time of determination. When the operation mode is the user setting priority mode, it is determined whether or not non-public information is included only in the reservation information for which the non-public setting is checked (non-public flag: ON).

S7: The non-disclosure processing unit 39 of the conference management server 30 performs a process for non-disclosure of the non-disclosure target item of the reservation information including the non-disclosure information. That is, a non-disclosure method is created for each non-disclosure target item and the non-disclosure setting is associated with the conference management information. FIG. 13 shows the conference management information including the secret setting.

S8: The reservation information requesting unit 96 of the conference room terminal 90 requests the conference room reservation information by designating the conference room ID to the conference management server 30 at regular intervals. As a result, the conference management server 30 can acquire the reservation information after a certain time has elapsed since the registration of the reservation information.

S9: When the display control unit 94 of the conference room terminal 90 acquires the reservation information from the conference management server 30, the display control unit 94 starts the process of updating the standby screen 501.

S10: The display control unit 94 of the conference room terminal 90 determines whether each reservation information acquired from the conference management server 30 includes a non-disclosure setting.

S11: The display control unit 94 of the conference room terminal 90 reflects the non-disclosure setting on the reservation information and displays the standby screen 501. That is, the non-disclosure target item designated by the non-disclosure setting is made non-display or fixed notation according to the designated non-disclosure method.

<Reservation information sent by the conference management server to the conference room terminal>
FIG. 13 shows an example of conference management information transmitted from the conference management server 30 to the conference room terminal 90. In FIG. 13, a secret setting item is added to the conference management information in Table 4. In the reservation information of reservation ID=001, the conference name is “autonomous driving conference with Sample Co., Ltd.” and includes the non-public information “Sample Co., Ltd.” in Table 9(a). According to Table 9(a), since the meeting target item and the non-disclosure method are not displayed as the non-disclosure target item, the non-disclosure setting in FIG. 13 is set as follows.
"Items to be hidden → Meeting name Hide method → Hide"
In the reservation information of reservation ID=002, the reservation person is “e@xfoof.com”, but the notation name of the account “e@xfoof.com” is “Ichiro Sato”. Although “Ichiro Sato” is registered in the non-public information in Table 9(a), according to Table 9(a), the non-public target item is the subscriber and the non-public method is the fixed notation 5, so that FIG. Then, the private settings are set as follows.
"Items to be closed to the user → How to hide the reservation person → Fixed notation 5"
The display control unit 94 of the conference room terminal 90 displays the non-disclosure target item displayed on the standby screen 501 in a hidden or fixed notation based on the reservation information as shown in FIG. When the non-disclosure method is hidden, the non-disclosure processing unit 39 of the conference management server 30 may delete the non-disclosure target item of the reservation information. Similarly, when the non-disclosure method is fixed notation, the non-disclosure processing unit 39 of the conference management server 30 may replace the non-disclosure target item of the reservation information with the fixed notation in Table 9(b). This allows the conference room terminal 90 to display the reservation information as in the conventional case.

However, since the reservation information transmitted to the meeting room terminal 90 includes the original information, the reservation person inputs the meeting identification information into the meeting room terminal 90, so that the meeting name of the secret information, the reservation person, and the participants. Etc., and after the conference has started, there are cases where it is desired to display the conference name, reservations, participants, etc. of non-public information, so reservation information that is not hidden or fixed notation as shown in FIG. It is also effective that the conference room terminal 90 receives.

<Processing of conference room terminals>
FIG. 14 is a flowchart of an example showing a procedure in which the conference room terminal 90 displays the reservation information on the standby screen 501. The process of FIG. 14 is executed when the reservation information is displayed on the standby screen 501. Since the reservation information displayed on the standby screen 501 includes not only the latest (next) reservation information but also the reservation information scheduled for the current day, the displayed reservation information is the target of the processing in FIG. Becomes

First, the reservation information requesting unit 96 of the conference room terminal 90 acquires reservation information (S100-1). The display control unit 94 refers to the item of secret setting of the reservation information (S100-2). Here, it is assumed that the reservation information is associated with the non-public setting. Subsequent processing is performed in parallel for each conference name, reservation person name, reservation person belonging name, participant name, and participant belonging name. It may be performed in order.

First, for the conference name, the display control unit 94 of the conference room terminal 90 determines whether the conference room is a non-disclosure target item (S101). If the determination in step S101 is No, the display control unit 94 displays the conference name included in the reservation information (S102).

If the determination in step S101 is Yes, the display control unit 94 determines whether the non-disclosure method is non-display or fixed notation (S103).

When the non-disclosure method is the fixed notation, the display control unit 94 replaces the conference name with the fixed notation (S104). When the non-disclosure method is hidden, the display control unit 94 hides the conference name (S105). It should be noted that the non-display means that the conference name is displayed in a blank character.

In steps S201 to S205, the reservation person's name is similarly processed, in steps S301 to S305, the reservation person's affiliation name is similarly processed, in steps S401 to S405, the participant name is similarly processed, and in steps S501 to S505, the participation is performed. The same applies to the affiliation name of the person.

<About the standby screen>
The standby screen shown in FIG. 2 will be supplemented. FIG. 2 shows an example of a standby screen 501 displayed by the conference room terminal 90 when the conference room is a vacant room but within a predetermined time until the start time of the next conference. On the standby screen 501, a current status column 561, a conference room name column 562, a conference name column 563, a start time column 564, an end time column 565, a room entry button 568, a reservation column 567 thereafter, and the like are displayed. ing.

The current status column 561 shows the status of the conference room at the current time. The display control unit 94 of the conference room terminal 90 displays the status of the reservation information in the current status column 561. If there is no reservation information reserved at the current time, the display control unit 94 displays “vacant room” (until the next reservation can be checked in) or “waiting for entry” (next room) in the current status column 561. After the check-in for the reservation is possible) is displayed.

The conference room name column 562 displays the conference room name stored in the storage unit 99. The conference name field 563 shows the conference name included in the reservation information. When the check-in based on the next reservation becomes possible, the display control unit 94 displays the conference name in the conference name column 563, hides it, or displays it in a fixed notation.

In the start time column 564 and the end time column 565, the start time and the end time included in the reservation information are displayed. Since FIG. 2 is a standby screen in which check-in based on the next reservation is possible, the end time of the next conference from the start time of the next conference is displayed in the start time column 564 and the end time column 565.

In the subsequent reservation column 567, according to the reservation information, the start time and the end time of each conference reserved after the present are displayed. The entry button 568 is displayed when the current status column 561 is “waiting for entry”. The room entry button 568 is a button for the user to check in. When this button is pressed, the reservation person can input the meeting identification information. In the reservation person name field 570, reservation person information is displayed, hidden, or fixedly written according to the non-disclosure setting.

In FIG. 2A, the participant name, the reservation member's affiliation name, and the participant's affiliation name are not displayed, but when these are also displayed on the standby screen 501, the conference room terminal 90 is not disclosed. Can be

<Summary>
As described above, in the resource reservation system according to the present embodiment, the conference room terminal 90 hides the items that are set to be hidden and the reservation information is displayed on the standby screen 501. The risk of leaking important information can be reduced.

In the first embodiment, the conference management server 30 performs the non-public process of changing and displaying the display content of the reservation information, but in the present embodiment, the resource reservation system in which the conference room terminal 90 performs the non-public process will be described.

In this embodiment, the system configuration example of FIG. 3 and the hardware configuration examples of FIGS. 4 and 5 can be used.

<About function>
FIG. 15 is an example functional block diagram showing the functions of the reservation management server 20, the chat server 10, the conference management server 30, and the registration terminal 50 in block form. FIG. 16 is an example functional block diagram showing the functions of the terminal device and the conference room terminal in block form. In FIG. 15 and FIG. 16, the constituent elements denoted by the same reference numerals as those in FIG. 6 perform the same functions, and therefore, only the main constituent elements of this embodiment may be mainly described. First, the functions of the reservation management server 20, the chat server 10, the registration terminal 50, and the terminal device 60 may be the same as in the first embodiment.

<< Meeting Management Server >>
The conference management server 30 of this embodiment does not include the non-disclosure processing unit 39 and the non-disclosure information registration receiving unit 40. The conference room terminal 90 has these functions.

<< Conference room terminal >>
The conference room terminal 90 has a secret processing unit 97 and a secret information registration acceptance unit 98.

The non-disclosure processing unit 97 performs a process of non-disclosure of the reservation information according to the reservation information received from the conference management server 30. First, the user setting priority mode for performing the process of making the reservation information private only when the effect of making the reservation information private (the private setting column of FIG. 8, the private flag of Table 1) is set, and the reservation information There is a compulsory mode in which the process of forcibly making private is carried out even when the fact of making private (non-public setting column of FIG. 8, private flag of Table 1) is not set. These modes are preset by the administrator. In the case of the user setting priority mode, the non-disclosure processing unit 97 determines whether or not the reservation information is non-disclosure (non-disclosure setting column in FIG. 8, non-disclosure flag: ON in Table 1) is set. .. In the case of the reservation information set to be closed, it is determined whether or not the reservation information includes private information by referring to the private information DB 999 described later. If it is included, create an indication that the corresponding non-disclosure target item is hidden or that it is fixed notation (non-disclosure setting). In the case of the forced mode, even if the reservation information is not set to be made private, referring to the private information DB 999, if the private information is included in the reservation information, the corresponding reservation information item is selected. Create the fact that it is hidden or that it is fixed (non-public setting). The reservation information to which the secret setting is added is stored in the conference room reservation information DB 998.

The non-disclosure information registration receiving unit 98 displays a non-disclosure information management screen (FIGS. 17 to 19) described later, and receives registration regarding non-disclosure information from the administrator. The private information that has received the registration is stored in the private information DB 999.

Further, the conference room terminal 90 has a conference room reservation information DB 998 and a non-public information DB 999 in the storage unit 99.

表１０は、会議室予約情報ＤＢ９９８に記憶されている予約情報の一例である。表１０の説明では主に表４の会議管理情報ＤＢ４９３との相違を説明する。会議室予約情報ＤＢ９９８には非公開設定の項目がある。非公開設定の項目は非公開対象項目と非公開方法を有している。これらは次述する非公開情報ＤＢ９９９に基づいて設定されている。

Table 10 is an example of the reservation information stored in the conference room reservation information DB 998. In the description of Table 10, differences from the conference management information DB 493 of Table 4 will be mainly described. The conference room reservation information DB 998 has an item of private setting. The item of non-disclosure setting has a non-disclosure target item and a non-disclosure method. These are set based on the private information DB 999 described below.

表１１（ａ）は非公開情報ＤＢ９９９に記憶されている非公開情報に関する設定の一例を示す（非公開情報記憶手段の一例）。まず、非公開情報ＤＢ９９９は非公開情報、非公開設定名、非公開対象項目、非公開方法、及び、実行する/しない、の各項目を有している。非公開情報は予約情報に含まれている場合に非公開の対象となる情報である。非公開文字列や非公開ワードということができる。非公開設定名は、非公開情報が見つかった予約情報をどのように非公開とするかに関する非公開設定の名称である。操作を容易にするため管理者が非公開設定名を選択すると非公開対象項目と非公開方法が決まるようになっている。非公開対象項目は予約情報のどの項目を非公開にするかを示す。非公開方法は非公開情報を固定表記とするか非表示とするかを示す。実行する/しないは、非公開情報を非公開とする処理を会議管理サーバ３０が実行するかどうか示す。後述するようにこれらの各設定は管理者が行うことができる。非公開方法が固定表記の場合、固定表記の具体的内容も設定されている。

Table 11(a) shows an example of settings related to non-public information stored in non-public information DB 999 (an example of non-public information storage means). First, the non-disclosure information DB 999 has non-disclosure information, non-disclosure setting name, non-disclosure target item, non-disclosure method, and execution/non-execution items. The non-public information is information to be non-public when included in the reservation information. It can be called a secret character string or a secret word. The private setting name is the name of the private setting regarding how to make the reservation information in which the private information is found private. In order to facilitate the operation, when the administrator selects the private setting name, the private target item and private method are determined. The non-disclosure target item indicates which item of the reservation information is made non-disclosure. The non-disclosure method indicates whether the non-disclosure information is fixed or hidden. Whether to execute or not indicates whether or not the conference management server 30 executes a process of disclosing secret information. As will be described later, each of these settings can be made by the administrator. If the private method is fixed notation, the specific contents of the fixed notation are also set.

Table 11(b) is operation mode setting information in which the user setting priority mode or the forced mode is set. The administrator can set the user setting priority mode or the compulsory mode in advance. The default operation mode when not set by the administrator is the forced mode. This can improve security.

The fixed notation information in Table 9(b) does not exist because the fixed notation is directly set in the reservation information in this embodiment.

Note that in Table 11(a), the non-public information is associated with the non-public target item and the non-public method, but if the non-public information is simply made private, a list of non-public information is registered. Good. Further, even if the conference management server 30 learns information (company name, proper noun, post, etc.) that should be kept secret by machine learning in advance, and regards this information as secret information and searches for secret information. Good. In this case, there is no need to list the private information. Similarly, the conference management server 30 may learn the correspondence between the non-disclosure target item and the non-disclosure method in the non-disclosure information set by the administrator, and apply the learning result to unknown non-disclosure information.

<Setting private information>
Next, a method for setting private information will be described with reference to FIGS. FIG. 17 shows an example of the private information management screen 600 displayed by the conference room terminal 90. The secret information management screen 600 has items of a check box column 601, a secret information column 602, a secret setting name column 603, and a delete button 604.

The non-public information column 602 is information for searching all information included in the reservation information. If the reservation information includes the same information as the non-public information in the non-public information column 602, the non-public target item (see FIG. 19) of the reservation information is non-public (non-display or fixed notation). When the operation mode is the compulsory mode, the reservation information including the same information as the private information is private even if the private setting field 405 is not checked on the reservation setting screen 400 of FIG. As a result, even if the reservation person forgets to check the non-public setting column, the non-public information can be kept private.

The private setting name column 603 is the name of the private setting. The administrator can easily set the non-disclosure target item and the non-disclosure method by selecting the name of the non-disclosure setting. That is, the non-disclosure setting name can determine the non-disclosure target item and the non-disclosure method. The delete button 604 is a button for the administrator to delete one record (a set of a check box, secret information, and secret setting name).

The check box column 601 is a column for setting whether or not to search the corresponding private information with the reservation information. That is, it is possible to set whether or not the private setting of one record is valid. The setting in the check box column 601 corresponds to “execute/not execute” in Table 11(a).

The record at the bottom of the secret information management screen 600 is blank, and the administrator can input new secret information. When the private setting name field 603 is pressed, the private setting names created in the past are displayed in a pull-down display. Detailed settings of each private setting will be described with reference to FIGS. 18 and 19. When new private information is input, a new blank record is added to the bottom of the private information management screen 600.

The private information management screen 600 also has a save button 605 and a cancel button 606. The save button 605 saves the edit state from when the registration terminal 50 opens the private information management screen 600 until the save button 605 is pressed. The cancel button 606 discards the edit state from when the private information management screen 600 is opened until the cancel button 606 is pressed.

FIG. 18 is an example of the non-disclosure setting management screen 610 displayed by the conference room terminal 90. The private setting management screen 610 is a screen for the administrator to edit or add private settings. The private setting management screen 610 has a check box column 611, a private setting name column 612, an edit button 613, and a delete button 614.

The check box column 611 is a column for the administrator to set whether or not to use the private setting of the private setting name column 612. If the check box column 611 is checked, the private setting can be used, and if it is not checked, the private setting cannot be used.

The edit button 613 is a button for editing the content of the private setting specified in the private setting name column 612. When the edit button 613 is pressed, the private setting edit screen 630 of FIG. 19 is displayed. The delete button 614 is a button for deleting the private setting specified in the private setting name column 612 from the private setting management screen 610.

Further, the non-public setting management screen 610 has an add button 615. The add button 615 is a button for newly adding and displaying a private setting on the private setting management screen 610. When the add button 615 is pressed, the private setting edit screen 630 of FIG. 19 is displayed.

FIG. 19 shows an example of the private setting edit screen 630 displayed by the conference room terminal 90. The non-public setting edit screen 630 has a non-public setting name column 631, a check box column 632, a non-disclosure target item column 633, a non-disclosure method column 634, a completion button 635, and a cancel button 636.

The secret setting name column 631 is a column for the administrator to edit the name when saving the secret setting. When the administrator edits the existing private setting, the private setting name before editing is displayed in advance. The non-disclosure target item column 633 shows a list of the items that can be made non-disclosure among the items of the reservation information. All items included in the reservation information and information linked to the account can be items that are not disclosed, but for example, the conference name, attendee name, appointment person name, attendee affiliation name, appointment person Affiliation name, etc. can be selected. In addition, it is preferable that items that should not be kept secret, such as the conference start time and the conference end time, cannot be selected as non-disclosure target items.

Since the administrator can arbitrarily select the non-public target item in the non-public target item column 633, not only the items including the non-public information but also the items including no non-public information can be set to non-public. Generally, items including non-public information should be made non-public, and thus items including non-public information may be set in the non-public target item column.

The non-disclosure method column 634 is a column for the administrator to select whether the non-disclosure target item is non-disclosure or is not displayed. The administrator can select the hidden radio button 634a or the fixed notation radio button 634b. When the administrator selects the fixed notation radio button 634b, a specific fixed notation can be input.

The check box column 632 is a column for the administrator to set whether or not the combination of the non-disclosure target item and the non-disclosure method is used by the conference room terminal 90 for the non-disclosure setting. The administrator can make only arbitrary items private.

The completion button 635 is a button for saving the editing state from when the administrator opens the non-public setting editing screen 630 until the completion button 635 is pressed. The cancel button 636 is a button for canceling the edit state from when the administrator opens the non-public setting edit screen 630 to when the cancel button 636 is pressed.

<Operating procedure>
FIG. 20 is a sequence diagram of an example showing a procedure in which the conference room terminal 90 hides the reservation information displayed on the standby screen 501.

S1: The administrator operates the conference room terminal 90 to display the screens shown in FIGS. When the administrator sets non-public information, the operation receiving unit 93 receives non-public information, non-public setting name, non-public target item, non-public method, and execute/not execute (check box column 601), and Is registered in the private information DB 999.

S2: The reservation person reserves the conference room with respect to the reservation management server 20 at an arbitrary timing. That is, the reservation person displays the reservation setting screen shown in FIG. 8 on the terminal device 60, and the conference name, the conference start date, the conference start time, the conference end date, the conference end time, the participant, the conference room, and the non-conference. Enter the public settings. The operation reception unit 61b of the terminal device 60 receives these reservation information. The communication unit 61a transmits the reservation information to the reservation management server 20.

S3: The communication unit 21 of the reservation management server 20 receives the reservation information, and the reservation information management unit 22 registers the reservation information in the reservation information DB 291.

S4: The communication unit 21 of the reservation management server 20 notifies the conference management server 30 that the reservation information has been updated by designating the account of the reservation person.

S5: The communication unit 31 of the conference management server 30 receives the fact that the reservation information has been updated, and the reservation information acquisition unit 33 requests the reservation information from the reservation management server 20 by designating an account and acquires it. Note that the reservation information may be designated by information specifying the reservation, such as the reservation ID or the conference room name and the reservation start date and time.

S6: The reservation information requesting unit 96 of the conference room terminal 90 requests the reservation information of the conference room by designating the conference room ID to the conference management server 30 at regular intervals. As a result, the conference management server 30 can acquire the reservation information after a certain time has elapsed since the registration of the reservation information.

S7: When the display control unit 94 of the conference room terminal 90 acquires the reservation information from the conference management server 30, it starts the update process of the standby screen 501.

S8: The non-disclosure processing unit 97 of the conference room terminal 90 determines whether or not the reservation information includes non-disclosure information registered in the non-disclosure information DB 999. When the operation mode is the forced mode, it is not necessary to determine whether or not the non-disclosure setting is checked (non-disclosure flag) at the time of determination. When the operation mode is the user setting priority mode, it is determined whether or not non-public information is included only in the reservation information for which the non-public setting is checked (non-public flag: ON).

S9: The non-disclosure processing unit 97 of the conference room terminal 90 performs a process for making the non-disclosure target item of the reservation information including non-disclosure information non-disclosure. That is, a non-disclosure setting including a non-disclosure target item and a non-disclosure method is created and associated with the reservation information. The conference room reservation information DB 998 in Table 10 will be described as an example.

In the reservation information of reservation ID=001, the conference name is "autonomous driving conference with Sample Co., Ltd." and includes the private information "Sample Co., Ltd." in Table 11(a). According to Table 11(a), since the meeting target item and the non-disclosure method are not displayed as non-disclosure target items, the non-disclosure setting in Table 10 is set as follows.
"Items to be hidden → Meeting name Hide method → Hide"
In the reservation information of reservation ID=002, the reservation person is “e@xfoof.com”, but the notation name of the account “e@xfoof.com” is “Ichiro Sato”. Although "Ichiro Sato" is registered in the private information in Table 11(a), according to Table 11(a), the non-public target item is the reservation person and the private method is the fixed notation "hyphen". In Table 10, the secret settings are set as follows.
"Items to be closed to the user → How to hide the reservation person → Hyphen"
S10: The display control unit 94 of the conference room terminal 90 determines whether or not the reservation information is included in each reservation information. The display control unit 94 displays the non-disclosure target item displayed on the standby screen 501 in the non-display or fixed notation based on the non-disclosure setting shown in Table 10.

S11: The reservation person or the participant can manually register the non-public information from the standby screen 501 displayed by the conference room terminal 90. The process of step S11 will be described with reference to FIG.

After that, the procedure in which the conference room terminal 90 displays the reservation information on the standby screen 501 may be the same as in FIG. 14 of the first embodiment.

<When private information is displayed>
Although the conference room terminal 90 performs the process of associating the non-disclosure setting with the reservation information described in FIG. 20, information that should not be disclosed may be displayed. In this case, the reservation person or the participant can hide any item of the reservation information on the spot. This will be described with reference to FIG. FIG. 21 is an example of a diagram for explaining an operation of making an arbitrary item of reservation information private.

FIG. 21A shows a standby screen 501 similar to that of FIG. 2, and the standby screen 501 has a private setting button 571. The secret setting button 571 is a button (display component) for displaying the secret information management screen 600 shown in FIG. When the reservation person or the participant presses the private setting button 571, the conference room terminal 90 displays the private information management screen 600 as shown in FIG. Thereby, the reservation person or the administrator can register the non-public information from the conference room terminal 90. Thereafter, similar to FIGS. 18 and 19, if the screen transition is performed, the non-disclosure target item and the non-disclosure method can be registered. Therefore, the reservation person or the administrator can register any non-public information on the spot to make any item of the reservation information private.

Further, the operation reception unit 93 receives the non-disclosure target item, the non-disclosure method, and the non-disclosure information (for example, the conference name, the reservation person, the participant, the reservation member's belonging name, a part of the participant's belonging name, or Since all) is registered in the private information DB 999 of the conference room terminal 90, reservation information displayed in the future can be made private if the same private information is included.

The conference room terminal 90 may authenticate the reservation person or the participant before accepting the setting of the non-public information. For example, if the private setting edit screen 630 is displayed only when the conference identification information is correct, it is possible to prevent a third party from arbitrarily making the reservation information private.

<About the standby screen>
A supplement will be given to the standby screen shown in FIG. FIG. 21A shows an example of a standby screen 501 displayed by the conference room terminal 90 when the conference room is a vacant room but is within a predetermined time until the start time of the next conference. On the standby screen 501, a current status column 561, a conference room name column 562, a conference name column 563, a start time column 564, an end time column 565, a room entry button 568, a reservation column 567 thereafter, and the like are displayed. ing.

The current status column 561 shows the current status of the conference room. The display control unit 94 of the conference room terminal 90 displays the status of the reservation information in the current status column 561. If there is no reservation information reserved at the current time, the display control unit 94 displays “vacant room” (until the next reservation can be checked in) or “waiting for entry” (next room) in the current status column 561. After the check-in for the reservation is possible) is displayed.

The conference room name column 562 displays the conference room name 994 stored in the storage unit 99. The conference name field 563 shows the conference name included in the reservation information. When the check-in based on the next reservation becomes possible, the display control unit 94 displays the conference name in the conference name column 563, hides it, or displays it in a fixed notation.

In the start time column 564 and the end time column 565, the start time and the end time included in the reservation information are displayed. Since FIG. 21A is a standby screen in which check-in based on the next reservation is possible, the end time of the next conference from the start time of the next conference is displayed in the start time column 564 and the end time column 565. ..

In the subsequent reservation column 567, according to the reservation information, the start time and the end time of each conference reserved after the present are displayed. The entry button 568 is displayed when the current status column 561 is “waiting for entry”. The room entry button 568 is a button for the user to check in. When this button is pressed, the reservation person can input the meeting identification information. In the reservation person name field 570, reservation person information is displayed, hidden, or fixedly written according to the non-disclosure setting.

In FIG. 21A, the participant name, the reservation member's belonging name, and the participant's belonging name are not displayed. However, when these are also displayed on the standby screen 501, the conference room terminal 90 is not disclosed. Can be

<Summary>
As described above, in the resource reservation system of the present embodiment, the conference room terminal 90 displays the reservation information by making the items set to non-public on the standby screen 501 non-public, so that the reservation screen is unintentionally displayed. The risk of leaking important information can be reduced.

In the second embodiment, the conference room terminal 90 searches the reservation information for non-disclosure information and makes the non-disclosure information included in the reservation information non-disclosure. However, the conference management server 30 (cloud side) sets the non-disclosure setting to the reservation information. Can also be associated. It is also possible to perform both at the conference room terminal 90 and the conference management server 30. In this embodiment, a resource reservation system 100 that performs a non-disclosure process in both the conference room terminal 90 and the conference management server 30 will be described.

In the present embodiment, the system configuration of FIG. 3 and the hardware configurations of FIGS. 4 and 5 will be described.

<About function>
FIG. 22 is a functional block diagram of an example showing the functions of the reservation management server 20, the chat server 10, the conference management server 30, and the registration terminal 50 of the present embodiment in a block form. In the description of FIG. 22, differences from FIG. 15 will be mainly described.

In the functional block diagram of FIG. 22, the conference management server 30 has a non-disclosure processing unit 39 and a non-disclosure information registration receiving unit 40. These functions may be the same as the non-public processing unit 39 and the non-public information registration receiving unit 40 (or the non-public processing unit 97 and the non-public information registration receiving unit 98 described in FIG. 16) described in FIG. 6. However, the private information registration receiving unit 40 provides a Web application that receives registration of private information from the registration terminal 50. That is, the screen information of the screens of FIGS. 17 to 19 is generated and transmitted to the registration terminal 50 via the communication unit 31, and the registration regarding the private information is accepted from the registration terminal 50. The non-public information that has received the registration is stored in the non-public information DB 498 of the conference management server. The screen information is created by HTML, CSS (Cascade Style Sheet), JavaScript (registered trademark), or the like.

In addition, a private information DB 498 is constructed in the storage unit 49. The configuration of the private information DB 498 may be the same as in Table 11. By registering non-public information or the like different from the non-public information DB 999 of the conference room terminal 90 in the non-public information DB 498, it is possible to easily make the information that should not be made public.

The functional block diagram of the conference room terminal 90 may be the same as that in FIG. Therefore, the administrator can register information relating to non-public information in the conference management server 30 and the conference room terminal 90. Further, as described with reference to FIG. 21, the reservation person or the participant can also register the information on the secret information in the conference room terminal 90.

<Regarding reservation information>
In this embodiment, since the private setting is associated with the reservation information also in the meeting management server 30, the private setting is registered in the meeting management information DB 493.

表１２は、会議管理サーバ３０が有する会議管理情報ＤＢ４９３が記憶している会議管理情報を示す。表１２の説明では主に表４との相違を説明する。会議管理サーバ３０の非公開処理部３９が非公開設定を予約情報に対応付けるため、会議管理情報ＤＢ４９３が非公開設定の項目を有している（非公開設定（サーバ作成））。

Table 12 shows the conference management information stored in the conference management information DB 493 of the conference management server 30. In the description of Table 12, differences from Table 4 will be mainly described. Since the non-disclosure processing unit 39 of the conference management server 30 associates the non-disclosure setting with the reservation information, the conference management information DB 493 has an item of non-disclosure setting (non-disclosure setting (server creation)).

表１３は、会議室端末９０が有する会議室予約情報ＤＢ９９８が記憶している会議管理情報を示す。表１３の説明では主に表１０との相違を説明する。会議管理サーバ３０の非公開処理部３９が作成した非公開設定に加え、会議室端末９０の非公開処理部９７が非公開設定を予約情報に対応付けるため、２つの非公開設定（非公開設定（サーバ作成）と（非公開設定（会議室端末サーバ作成））が予約情報に対応付けられている。

Table 13 shows the conference management information stored in the conference room reservation information DB 998 included in the conference room terminal 90. In the description of Table 13, differences from Table 10 will be mainly described. In addition to the private setting created by the private processing unit 39 of the conference management server 30, the private processing unit 97 of the conference room terminal 90 associates the private setting with the reservation information. Server creation) and (private setting (meeting room terminal server creation)) are associated with the reservation information.

The display control unit 94 of the conference room terminal 90 performs a process of making the reservation information of the standby screen private based on each of the two private settings of the reservation information in Table 13. In Table 13, for convenience of explanation, the two secret settings are the same, but if the secret information, the secret item, or the secret method is different between the conference management server 30 and the conference room terminal 90, the conference management server is different. Different private settings can be associated with the reservation information between 30 and the conference room terminal 90. Therefore, the reservation information is double-checked, which makes it easy to keep information that should not be disclosed.

<Operating procedure>
FIG. 23 is a sequence diagram of an example showing a procedure in which the conference room terminal 90 hides the reservation information displayed on the standby screen 501.

S21: The administrator operates the registration terminal 50 to cause the registration terminal 50 to communicate with the conference management server 30. The private information registration acceptance unit 40 of the conference management server 30 transmits the screen information of the screens shown in FIGS. 17 to 19 to the registration terminal 50 as a Web application. The communication unit 51 of the registration terminal 50 receives the screen information, and the display control unit 53 of the registration terminal 50 displays the screens shown in FIGS. 17 to 19. When the administrator sets the information regarding the non-public information, the operation reception unit 52 receives the non-public information, the non-public setting name, the non-disclosure target item, the non-disclosure method, and the execution/non-execution (check box column 601), The communication unit 51 transmits these to the conference management server 30. The secret information registration receiving unit 40 of the conference management server 30 registers these in the secret information DB 498 of the conference management server 30.

S22: Further, the administrator operates the conference room terminal 90 to display the screens shown in FIGS. 17 to 19. When the administrator sets the information related to the non-public information, the operation reception unit 93 receives the non-public information, the non-public setting name, the non-public item, the non-public method, and the execution/non-execution (check box column 601), These are registered in the private information DB 999 included in the conference room terminal 90.

S23 to S26: The same as steps S2 to S5 in FIG.

S27: The secret processing unit 39 of the conference management server 30 determines whether or not the reservation information includes the secret information registered in the secret information DB 498. When the operation mode is the forced mode, it is not necessary to determine whether or not the non-disclosure setting is checked (non-disclosure flag) at the time of determination. When the operation mode is the user setting priority mode, it is determined whether or not non-public information is included only in the reservation information for which the non-public setting is checked (non-public flag: ON).

S28: The non-disclosure processing unit 39 of the conference management server 30 performs a process for making the non-disclosure target item of the reservation information including non-disclosure information non-disclosure. That is, a non-disclosure method is created for each non-disclosure target item and the non-disclosure setting is associated with the reservation information. As a result, the conference management information in Table 12 is created.

S29 to S32: The same as steps S6 to S9 in FIG. As a result, the conference management information in Table 13 is created.

S33: The display control unit 94 of the conference room terminal 90 determines whether each reservation information includes one or more non-public settings. There may be 0, 1 or 2 private settings. The display control unit 94 displays the non-disclosure target item displayed on the standby screen 501 in the non-display or fixed notation based on the reservation information as shown in Table 13.

S34: The reservation person or the participant can manually set to be closed from the standby screen displayed by the conference room terminal 90.

In the present embodiment, both the conference management server 30 and the conference room terminal 90 are set to keep the reservation information private, but even if only the conference management server 30 performs the process of keeping the reservation information private. Good.

<Summary>
Therefore, according to the resource reservation system of the present embodiment, in addition to the effects of the first and second embodiments, not only the conference room terminal 90 but also the conference management server performs a process of keeping private information private, so that it is made public. This makes it easier to keep information that should not be disclosed private. For example, the administrator can set private information common to each conference room in the meeting management server 30 and register private information in the conference room terminal 90 individually.

<Other application examples>
The best mode for carrying out the present invention has been described above with reference to the embodiments, but the present invention is not limited to these embodiments, and various modifications can be made without departing from the gist of the present invention. And substitutions can be added.

For example, although it has been described that the administrator registers private information, the conference management server 30 may automatically detect private information from private information. In this case, the conference management server 30 learns information to be kept secret by machine learning in advance, regards this information as secret information, and searches for secret information.

A plurality of conference management servers 30 may exist, or the functions of the conference management server 30 may be distributed to the plurality of servers. Further, the reservation management server 20 and the conference management server 30 may be integrated.

The resource reservation system 100 of this embodiment can also be called a Web service. Web services are various services provided by applying Internet-related technologies. For example, a conference room lending service and various rental services can be cited. A system that uses a Web service is called a usage system.

In addition, the configuration examples of FIGS. 6 and 7 shown in the above embodiment are divided according to the main functions in order to facilitate understanding of the processing of the resource reservation system 100. However, the present invention is not limited by the division method or name of each processing unit. The resource reservation system 100 can be divided into more processing units according to the processing content. It is also possible to divide one processing unit so as to include more processing.

Each function of the embodiments described above can be realized by one or a plurality of processing circuits. Here, the “processing circuit” in the present specification is a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, or designed to execute each function described above. Devices such as ASICs (Application Specific Integrated Circuits), DSPs (digital signal processors), FPGAs (field programmable gate arrays), and conventional circuit modules are included.

The private information DB 498 is an example of a private information storage unit, the private processing unit 39 is an example of a private processing unit, and the communication unit 31 is an example of a transmission unit.

10 chat server 20 reservation management server 30 conference management server 60 terminal device 70 electronic device 90 conference room terminal 100 resource reservation system

JP, 2013-020368, A

Claims (26)

A resource reservation system including: a server system including at least one information processing device that stores reservation information related to reservation of one or more resources; and an information processing terminal that acquires and displays the reservation information from the server system. There
The resource reservation system, wherein the information processing terminal is installed for each resource and displays the display content of the reservation information changed according to the setting information that sets the display method of the reservation information. The resource reservation according to claim 1, wherein the information processing terminal displays the reservation information in which at least a part of the reservation information acquired from the server system is made private according to the setting information. system. The resource reservation according to claim 1 or 2, wherein the information processing terminal displays the setting information in which at least a part of the reservation information acquired from the server system is hidden or changed to a fixed notation. system. The resource reservation system according to claim 1, wherein the setting information includes an item of the reservation information that is changed and displayed. The resource reservation system according to claim 1, wherein the setting information includes an indication that the reservation information is hidden or that the reservation information is changed to a fixed notation. The setting information is information indicating that the meeting name item included in the reservation information is closed, and the information processing terminal hides the meeting name set in the meeting name item. The resource reservation system according to any one of claims 1 to 5. The setting information is information indicating that the item of the reservation person name included in the reservation information is not disclosed, and the information processing terminal does not disclose the reservation person name set in the item of the reservation person. The resource reservation system according to claim 1, wherein: The setting information is information indicating that the participant name item included in the reservation information is not disclosed, and the information processing terminal does not disclose the participant name set in the participant name item. The resource reservation system according to any one of claims 1 to 7, wherein: The setting information is information indicating that the item of the belonging name of the reservation person included in the reservation information is not disclosed, and the information processing terminal is a reservation person set in the item of the belonging name of the reservation person. The resource reservation system according to any one of claims 1 to 8, wherein the belonging name of the resource reservation system is not disclosed. The setting information is information indicating that the item of the belonging name of the participant included in the reservation information is not disclosed, and the information processing terminal is a participant set in the item of the belonging name of the participant. The resource reservation system according to any one of claims 1 to 9, wherein the affiliation name of is not disclosed. The server system is
Private information storage means for storing private information that is made private,
When the reservation information includes the private information stored in the private information storage unit, private processing means for creating the setting information,
The resource reservation system according to any one of claims 1 to 10, further comprising: The resource reservation system according to claim 11, wherein the non-public information stored in the non-public information storage means is associated with a conference room. The said information processing terminal makes a predetermined private information contained in the said reservation information received from the said server system private, The any one of the Claims 1-3 characterized by the above-mentioned. Resource reservation system. The information processing terminal refers to a non-public information storage unit that stores the non-public target item to be non-public among the items of the reservation information and the non-public information in association with each other,
14. The resource reservation system according to claim 13, wherein the non-disclosure target item associated with the non-public information included in the reservation information received from the server system is made non-public. The resource reservation system according to claim 14, wherein the information processing terminal accepts registration of the non-public information. The resource reservation system according to claim 15, wherein the information processing terminal receives the association between the non-public information and the non-public target item and registers the non-public information in the non-public information storage unit. On the screen where the information processing terminal displays the reservation information, a display component that accepts registration of the private information is displayed,
The resource reservation system according to claim 15 or 16, wherein at least registration of the non-public information is accepted when the display component is pressed. 15. The information processing terminal hides the conference name set in the conference name item when the non-disclosure target item is a conference name item included in the reservation information. The resource reservation system according to any one of items 1 to 17. When the non-disclosure target item is the item of the reservation person name included in the reservation information, the information processing terminal keeps the reservation person name set in the item of the reservation person name private. The resource reservation system according to any one of claims 14 to 18. When the non-disclosure target item is a participant name item included in the reservation information, the information processing terminal keeps the participant name set in the participant name item private. The resource reservation system according to any one of claims 14 to 19. 21. The information processing terminal further changes and displays the display content of the reservation information acquired from the server system according to the setting information received from the server system. The resource reservation system according to any one of items. A reservation terminal that receives the reservation information of the resource and transmits the reservation information to the server system,
The reservation terminal is capable of accepting a non-public setting to make the reservation content of the reservation information at least non-public to other devices, and transmitting the non-public setting to the server system,
The server system or the information processing terminal can change the display content of the reservation information based on the setting information regardless of the presence or absence of the non-disclosure setting transmitted from the reservation terminal. The resource reservation system according to any one of Items 1 to 21. The resource is a meeting room,
The information processing terminal is installed in each conference room,
23. The reservation information of the conference held in the conference room in which the information processing terminal is installed is acquired from the server system, and the reservation information of the conference held at the current time is displayed. The resource reservation system according to any one of items. Information performed by a resource reservation system including a server system including an information processing device that stores reservation information related to reservation of one or more resources, and an information processing terminal that acquires and displays the reservation information from the server system Display method,
The information display method, wherein the information processing terminal is installed for each resource and displays the display content of the reservation information changed according to the setting information that sets the display method of the reservation information. What is claimed is: 1. A server system including one or more information processing devices for transmitting reservation information about reservations of one or more resources to an information processing terminal via a network,
Private information storage means for storing private information that is made private,
When the reservation information includes the non-public information stored in the non-public information storage means, a non-public processing means that creates setting information that sets the display method of the reservation information,
Transmitting means for transmitting the reservation information and the setting information to the information processing terminal,
A server system comprising: An information processing terminal that acquires the reservation information from a server system including at least one information processing device that stores reservation information regarding reservation of one or more resources,
An information processing terminal, which is installed for each resource and displays the display content of the reservation information that is changed according to the setting information that sets the display method of the reservation information.

Images