Seat management device, system, method, and program

Abstract

To appropriately grasp the state of a user being present and absent at / from a seat which has not preliminarily been registered.SOLUTION: A seat management device (1) comprises: a storage unit (11) for storing seat management information (111) that includes a user's seating state in each of a plurality of seats; an acceptance unit (12) for accepting seating state information that includes a seating state and seat position indicating the present or absent of seating detected by a sensor installed at each seat; and an update unit (13) for updating the seat management information (111) in accordance with the seat presence state information. When the seating state indicates seating and the seating state information includes the identification information on a user detected by a sensor, the update unit (13) updates the seat management information (111) while associating the seat position included in the seating state information, the identification information, and the seating state with one another, and when the seating state indicates not seating, the update unit updates the seat management information (111) while associating the seat position included in the seating state information with the seating state.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a seat management device, system, method, and program, and more particularly to a seat management device, system, method, and program for managing the occupancy status of seats.

Background Art

[0002] With the business reform, the number of companies adopting the free-address system where each person can freely select the seat for business is increasing. This is for the purpose of activating communication with members of other departments and changing the mood by sitting on various seats instead of always sitting on the same seat, leading to an improvement in work efficiency.

[0003] Patent Document 1 discloses a technique related to an information processing device that displays a floor map including a plurality of seats and a conference room, and displays the schedule of a user whose seat position is registered in advance at the seat position of the user on the floor map. In particular, in Patent Document 1, the current position of the user is specified based on the position information of the wireless access point accessed by the user's PC.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, in Patent Document 1, the seat position used by the user must be registered in advance. Therefore, there is a problem that it cannot cope with flexible seat use such as the free-address system.

[0006] This disclosure is made to solve these problems and aims to provide a seat management device, system, method, and program for appropriately understanding the occupancy and vacancy status of users in seats that have not been registered in advance. [Means for solving the problem]

[0007] The seat management device according to the first aspect of this disclosure is A storage unit that stores seat management information, including the occupancy status of users at each of multiple seats, A reception unit receives occupancy status information, including the occupancy status (indicating whether or not a seat is occupied) and the seat location, as detected by sensors installed at each seat. An update unit that updates the seat management information according to the aforementioned occupancy status information, Equipped with, The aforementioned update unit is If the occupancy status indicates that the person is occupying, and the occupancy status information includes user identification information detected by the sensor, the seat management information is updated by associating the seat location, the identification information, and the occupancy status included in the occupancy status information. If the seating status indicates no seating, the seating management information is updated by associating the seating location and seating status included in the seating status information.

[0008] The seat management system relating to the second aspect of this disclosure is A storage device that stores first seat management information, including the occupancy status of users at each of multiple seats, Multiple sensors installed in each of the aforementioned multiple seats, Equipped with a seat management device, The aforementioned seat management device is, A reception unit that receives occupancy status information including the occupancy status, which indicates whether or not someone is present, and the seat location, as detected by each of the aforementioned multiple sensors, An update unit updates the first seat management information according to the aforementioned seating status information, Equipped with, The aforementioned update unit is If the occupancy status indicates that the seat is occupied, and the occupancy status information includes user identification information detected by the sensor, the first seat management information is updated by associating the seat location, the identification information, and the occupancy status included in the occupancy status information. If the seating status indicates no seating, the first seating management information is updated by associating the seating location and seating status included in the seating status information.

[0009] The seat management method relating to the third aspect of this disclosure is: A computer equipped with a storage unit that stores seat management information, including the occupancy status of users at each of multiple seats, The system receives occupancy status information, including the occupancy status (indicating whether or not a seat is occupied) and the seat location, as detected by sensors installed at each seat. If the occupancy status indicates that the person is occupying, and the occupancy status information includes user identification information detected by the sensor, the seat management information is updated by associating the seat location, the identification information, and the occupancy status included in the occupancy status information. If the seating status indicates no seating, the seating management information is updated by associating the seating location and seating status included in the seating status information.

[0010] The seat management program relating to the fourth aspect of this disclosure is: A computer equipped with a storage unit that stores seat management information, including the occupancy status of users at each of multiple seats, A process that receives occupancy status information, including the occupancy status (indicating whether or not a seat is occupied) and the seat location, as detected by sensors installed at each seat. If the occupancy status indicates that the user is present, and the occupancy status information includes user identification information detected by the sensor, the process of updating the seat management information by associating the seat location, the identification information, and the occupancy status included in the occupancy status information, If the aforementioned occupancy status indicates no occupancy, the process of updating the seat management information by associating the seat location and said occupancy status included in the occupancy status information, Make it run. [Effect of the Invention]

[0011] According to the present disclosure, it is possible to provide a seat management device, system, method, and program for appropriately grasping the occupancy and departure states of users in unregistered seats. [Brief Description of the Drawings]

[0012] [Figure 1] It is a block diagram showing the configuration of the seat management device according to Embodiment 1. [Figure 2] It is a flowchart showing the flow of the seat management method according to Embodiment 1. [Figure 3] It is a block diagram showing the overall configuration of the seat management system according to Embodiment 2. [Figure 4] It is a block diagram showing the configuration of the occupancy / departure detection sensor according to Embodiment 2. [Figure 5] It is a block diagram showing the configuration of the individual identification sensor according to Embodiment 2. [Figure 6] It is a block diagram showing the configuration of the management terminal according to Embodiment 2. [Figure 7] It is a block diagram showing the configuration of the schedule management server according to Embodiment 2. [Figure 8] It is a diagram showing an example of the schedule information according to Embodiment 2. [Figure 9] It is a block diagram showing the configuration of the seat management server according to Embodiment 2. [Figure 10] It is a diagram showing an example of the seat management information according to Embodiment 2. [Figure 11] It is a flowchart showing the flow of the occupancy / departure detection process according to Embodiment 2. [Figure 12] It is a flowchart showing the flow of the individual identification process according to Embodiment 2. [Figure 13] It is a flowchart showing the flow of the process of the management terminal according to Embodiment 2. [Figure 14]This flowchart shows the processing flow of the schedule management server according to this second embodiment. [Figure 15] This flowchart shows the flow of the seat management information update process according to this second embodiment. [Figure 16] This is a sequence diagram showing the flow of the seat management information update process when occupancy is detected according to this second embodiment. [Figure 17] This is a sequence diagram showing the flow of the seat management information update process when a seat is left unattended according to this second embodiment. [Figure 18] This is a sequence diagram showing the flow of the seat list display process according to this second embodiment. [Figure 19] This is a diagram illustrating the concept of user position and movement within the floor according to this second embodiment. [Figure 20] This figure shows an example of a floor seating list display according to this second embodiment. [Figure 21] This is a block diagram showing the overall configuration of the seat management system according to this third embodiment. [Figure 22] This is a block diagram showing the configuration of the seat management server according to this third embodiment. [Figure 23] This flowchart shows the flow of the seat management information update process according to this third embodiment. [Modes for carrying out the invention]

[0013] Embodiments of the present disclosure will be described in detail below with reference to the drawings. In each drawing, the same or corresponding elements are denoted by the same reference numerals, and redundant explanations will be omitted where necessary for clarity.

[0014] <Embodiment 1> Figure 1 is a block diagram showing the configuration of the seat management device 1 according to this embodiment 1. The seat management device 1 is a computer for managing the occupancy status of users at each of multiple seats. Here, each seat is equipped with a first sensor (not shown) that detects the occupancy status indicating whether or not a user is present, and a second sensor (not shown) that identifies the identification information of the occupant user. The second sensor identifies the individual by reading identification information from an ID card held by the user or by biometric authentication, etc. The first and second sensors (sensor group) may be integrated. The seat management device 1 and the sensor group are connected by a communication network (not shown; hereafter, the communication network will also be simply referred to as the network) or by a predetermined wireless communication. The network may be wired or wireless, and the type of communication protocol may be irrelevant. Each sensor shall notify the seat management device 1 of the occupancy status information, which includes the detected information (occupancy status and user identification information) and the location information of the seat where it is installed (seat location).

[0015] The seat management device 1 comprises a storage unit 11, a reception unit 12, and an update unit 13. The storage unit 11 stores seat management information 111. The seat management information 111 is information including the occupancy status of a user at each of multiple seats. The reception unit 12 receives occupancy status information, which includes the occupancy status (whether or not a user is occupying a seat) and the seat location, as detected by sensors installed at each seat. The reception unit 12 may receive occupancy status information directly from each sensor, or it may receive occupancy status information via other terminals or communication devices (not shown). The update unit 13 updates the seat management information 111 according to the occupancy status information. If seat management information 111 corresponding to a particular seat is not registered, the update unit 13 generates seat management information 111 based on the occupancy status information and registers it in the storage unit 11. Here, the seat management device 1 determines whether the occupancy status included in the occupancy status information received by the reception unit 12 indicates that a user is occupying a seat. The seat management device 1 then determines whether the seat status information includes user identification information detected by the sensor if the seat status indicates that a seat is occupied. The update unit 13 updates the seat management information 111 by associating the seat location, identification information, and seat status included in the seat status information if the seat status indicates that a seat is occupied and the seat status information includes user identification information. The update unit 13 also updates the seat management information 111 by associating the seat location and seat status included in the seat status information if the seat status indicates that a seat is not occupied.

[0016] Figure 2 is a flowchart showing the flow of the seat management method according to this embodiment 1. First, the reception unit 12 receives occupancy status information directly or indirectly from the sensor group (S11). Next, the seat management device 1 determines whether the occupancy status included in the occupancy status information indicates that a seat is occupied, and whether the occupancy status information includes user identification information detected by the sensor (S12). If the result in step S12 is YES, the update unit 13 updates the seat management information 111 by associating the seat location, identification information, and occupancy status included in the occupancy status information (S13). If the result in step S12 is NO, the seat management device 1 determines whether the occupancy status included in the occupancy status information indicates that a seat is not occupied (S14). If the result in step S14 is YES, the update unit 13 updates the seat management information 111 by associating the seat location and occupancy status included in the occupancy status information (S15). If the result in step S14 is NO, it means that the seating status indicates that the seat is occupied, and the seating status information does not include the user's identification information. In this case, for example, the update unit 13 may update the seating management information 111 by associating the seat location and the seating status indicating that the seat is occupied included in the seating status information.

[0017] In this embodiment, the occupancy status detected by sensors installed at each seat is managed for each seat using seat management information 111. In particular, if user identification information is detected by the sensor when the user is occupying a seat, this identification information is registered in the seat management information 111 as well. In other words, when a user uses any of the seats, prior registration is not required, and the occupancy status is automatically registered by the seat management device 1. Furthermore, even after registration, the seat management information 111 is updated according to the occupancy status information notified according to the sensor detection status. Therefore, when a user leaves a seat, the seat management information 111 is also automatically registered (updated). As a result of the above, this embodiment makes it possible to appropriately grasp the occupancy and vacancy status of users in seats that have not been registered in advance by referring to the seat management information 111.

[0018] The seat management device 1 includes a processor, memory, and storage device (not shown in the diagram). The storage device stores a computer program that implements the seat management method according to this embodiment. The processor loads the computer program from the storage device into the memory and executes it. This allows the processor to perform the functions of the reception unit 12 and the update unit 13.

[0019] Alternatively, the reception unit 12 and the update unit 13 may each be implemented with dedicated hardware. Furthermore, some or all of the components of each device may be implemented by general-purpose or dedicated circuits, processors, etc., or combinations thereof. These may be composed of a single chip or multiple chips connected via a bus. Some or all of the components of each device may be implemented by a combination of the aforementioned circuits, etc., and programs. Furthermore, a CPU (Central Processing Unit), GPU (Graphics Processing Unit), FPGA (field-programmable gate array), quantum processor (quantum computer control chip), etc., can be used as the processor.

[0020] Furthermore, if some or all of the components of the seat management device 1 are implemented by multiple information processing devices or circuits, these devices may be centrally located or distributed. For example, the information processing devices or circuits may be implemented in a form in which each is connected via a communication network, such as a client-server system or a cloud computing system. Also, the functions of the seat management device 1 may be provided in SaaS (Software as a Service) format.

[0021] <Embodiment 2> This second embodiment is a specific example of the first embodiment described above. Figure 3 is a block diagram showing the overall configuration of the seat management system 1000 according to this second embodiment. The seat management system 1000 comprises a plurality of seats 101 to 10n (where n is a natural number of 2 or more), a management terminal 200, a network 300, a schedule management server 400, a seat management server 500, and PCs (Personal Computers) 601 to 60m (where m is a natural number of 2 or more). The seats 101, etc. are a group of seats whose occupancy status is managed by the seat management system 1000. Each of the seats 101, etc. may be located on the same or different floors, or in different buildings. Each seat 101 is equipped with an occupancy / absence detection sensor 1011 and a personal identification sensor 1012. The occupancy / absence detection sensor 1011 and the personal identification sensor 1012 are communicated with each other. The same applies to other seats; for example, seat 10n is equipped with an occupancy / absence detection sensor 10n1 and a personal identification sensor 10n2. The occupancy / absence detection sensor 10n1 and the personal identification sensor 10n2 are communicated with each other.

[0022] Here, each of the presence / absence detection sensors 1011 to 10n1 and the personal identification sensors 1012 to 10n2 are connected to the management terminal 200 in a communicative manner. These may also be connected to the management terminal 200 via the network 300. Furthermore, the management terminal 200, the schedule management server 400, the seat management server 500, and PC 601 to 60m are connected via the network 300. Here, the network 300 is a wired or wireless communication line, such as a LAN (Local Area Network) or the Internet.

[0023] The presence / absence detection sensor 1011 is a sensor for detecting whether a user is present or absent from seat 101. Figure 4 is a block diagram showing the configuration of the presence / absence detection sensor 1011 according to this second embodiment. The presence / absence detection sensor 1011 includes a timer 10111, a detection unit 10112, and a notification unit 10113. The timer 10111 periodically notifies the detection unit 10112 of a detection instruction at predetermined intervals.

[0024] The detection unit 10112 determines whether a user is currently seated in seat 101 in response to a detection instruction from the timer 10111. If the detection unit 10112 determines that a user is seated, it outputs a seated status to the notification unit 10113 indicating that the user is seated. If the detection unit 10112 determines that the user is not seated, it outputs a seated status to the notification unit 10113 indicating that the user is not seated (away). The detection unit 10112 can use, for example, a pressure sensor. Alternatively, the detection unit 10112 may detect the presence or absence of a user near seat 101 using an infrared sensor or the like. In that case, this embodiment is not limited to seats 101 with chairs, but can also be applied to standing seats.

[0025] The notification unit 10113 notifies the personal identification sensor 1012 of the detected occupancy status in accordance with the output from the detection unit 10112. The notification unit 10113 may also notify the management terminal 200 of the occupancy status and the seat location of seat 101.

[0026] Thus, the presence / absence detection sensor 1011 waits for a certain period of time and operates upon notification from the timer 10111. Note that the timer 10111 is not mandatory. In that case, the presence / absence detection sensor 1011 will operate based on the timing of seating or departure detection by the detection unit 10112. Note that other presence / absence detection sensors 10n1, etc., have the same configuration as the presence / absence detection sensor 1011, so their illustration and detailed explanation are omitted.

[0027] Returning to Figure 3, we continue the explanation. The personal identification sensor 1012 is a sensor that identifies the personal information (identification information, user ID (employee number, etc.)) of the user of seat 101. Figure 5 is a block diagram showing the configuration of the personal identification sensor 1012 according to this embodiment 2. The personal identification sensor 1012 comprises a receiving unit 10121, a personal identification unit 10122, and a notification unit 10123. The receiving unit 10121 receives the presence / absence status from the presence / absence detection sensor 1011. When the receiving unit 10121 receives the presence status, it notifies the personal identification unit 10122 of this fact.

[0028] The personal identification unit 10122 performs personal identification processing in response to notifications from the receiving unit 10121. If a user is present (seated) at seat 101, the personal identification unit 10122 can identify the individual by performing identity verification processing for that user. Specifically, the personal identification unit 10122 identifies user information such as the user ID of the user currently present at seat 101. However, even if a user is present (seated) at seat 101, personal identification may fail, or if the user leaves the seat, personal identification may not be possible.

[0029] The personal identification unit 10122 may be, for example, a reader / writer capable of reading an ID card that can identify an individual, such as an employee ID card. Alternatively, the personal identification unit 10122 may be a biometric authentication device that acquires biometric information from a user and performs biometric authentication by matching it with pre-registered biometric information. For example, the personal identification unit 10122 may be equipped with a fingerprint reader and identify the user ID by fingerprint authentication. Alternatively, the personal identification unit 10122 may be equipped with a camera and identify the user ID by facial authentication using an image of the user's face captured by the camera. In addition, other technologies that utilize captured images can be applied to biometric authentication and biometric information. For example, the biometric information may be data (feature quantities) calculated from physical characteristics unique to an individual, such as fingerprints, voiceprints, veins, retina, or iris patterns. Furthermore, the identity verification process for identifying an individual may not be biometric authentication, and the identity verification information may not be biometric information. For example, identity verification information may include, but is not limited to, a combination of ID and password, or an electronic certificate.

[0030] The notification unit 10123 notifies the management terminal 200 of the presence status information, including the presence status and the seat location of seat 101. In particular, when the user ID is identified by the personal identification unit 10122, the notification unit 10123 notifies the management terminal 200 of the identified user ID, the presence status, and the seat location of seat 101. Note that other personal identification sensors 10n2, etc., have the same configuration as personal identification sensor 1012, so their illustration and detailed explanation are omitted.

[0031] Thus, the personal identification sensor 1012 operates in response to a notification from the presence / absence detection sensor 1011. Alternatively, if the presence / absence detection sensor 1011 independently notifies the management terminal 200 of the presence status and seat location as described above, the personal identification sensor 1012 may also notify the management terminal 200 of the user ID and seat location, which are identified independently of the presence / absence detection sensor 1011. In that case, the personal identification sensor 1012 may be equipped with a timer equivalent as described above and operate in response to a notification from the timer.

[0032] Returning to Figure 3, we continue the explanation. The management terminal 200 is an information processing device that receives occupancy status information from each of the personal identification sensors 1012 to 10n2 and transmits each occupancy status information to the seat management server 500 via the network 300. The management terminal 200 may also receive occupancy status and seat location information from each of the occupancy / absence detection sensors 1011 to 10n1. In that case, the management terminal 200 can generate seat status information by combining the seat status and user ID for seats with common seat locations and transmit the generated seat status information to the seat management server 500. The management terminal 200 does not need to be connected to all personal identification sensors or occupancy / absence detection sensors. In that case, the seat management system 1000 may have multiple management terminals 200. For example, the management terminal 200 may be installed on each floor and receive information from personal identification sensors, etc., corresponding to seats on the same floor. Furthermore, the management terminal 200 may internally manage (register) the seat management information described later. Furthermore, if the presence status of the management terminal 200 indicates that the user is away from their seat, the terminal 200 queries the schedule management server 400 for the current schedule information of the user ID registered in the seat management information.

[0033] Figure 6 is a block diagram showing the configuration of the management terminal 200 according to this second embodiment. The management terminal 200 comprises a storage unit 210, a memory 220, a communication unit 230, and a control unit 240. The storage unit 210 is an example of a storage device such as a hard disk or flash memory. The storage unit 210 stores a program 211 and seat management information 212. The program 211 is a computer program in which some of the processing of the seat management method according to this second embodiment is implemented.

[0034] The seat management information 212 is information for managing the occupancy status of a group of seats under the management terminal 200. The seat management information 212 is information that associates seat location 2121, user information 2122, and occupancy status 2123. The seat location 2121 is seat identification information that allows the location of the seat to be determined. The user information 2122 is information that includes the user ID. The user information 2122 may also include personal information such as the user's name and affiliation. However, the value of the user information 2122 may be empty if the user occupying the seat could not be identified. The occupancy status 2123 is information that indicates whether the user is occupying the seat or not.

[0035] Memory 220 is a volatile storage device such as RAM (Random Access Memory), and is a storage area for temporarily holding information when the control unit 240 is operating. The communication unit 230 is a communication interface with the network 300.

[0036] The control unit 240 is a processor, or control device, that controls each component of the management terminal 200. The control unit 240 loads program 211 from the storage unit 210 into memory 220 and executes program 211. In this way, the control unit 240 realizes the functions of the receiving unit 241, determination unit 242, identification unit 243, transmission unit 244, and update unit 245.

[0037] The receiving unit 241 receives information from the personal identification sensor 1012, etc. (or the presence / absence detection sensor 1011, etc.). For example, the receiving unit 241 receives presence status information from the personal identification sensor 1012, etc.

[0038] The determination unit 242 determines whether the presence status included in the received presence status information indicates presence or absence. The determination unit 242 also determines whether the presence status included in the received presence status information indicates absence (away).

[0039] If the occupancy status indicates no occupancy, the identification unit 243 refers to the seat management information 212 and attempts to identify the user information 2122 (user ID) associated with the seat location 2121 included in the received occupancy status information.

[0040] When the user ID is identified by the identification unit 243, the transmission unit 244 sends a query for the current schedule information corresponding to that user ID to the schedule management server 400 via the network 300. In other words, if the presence status is "away," the transmission unit 244 queries the current schedule information of the user who was present until immediately before. The transmission unit 244 also sends the received presence status information to the seat management server 500 via the network 300.

[0041] The update unit 245 generates seat management information 212 (second seat management information) according to the received occupancy status information and registers or updates it in the storage unit 210. Specifically, the update unit 245 extracts the seat location and occupancy status from the received occupancy status information. Then, the update unit 245 generates and updates seat management information 212 by associating the extracted seat location and occupancy status. Furthermore, if the received occupancy status information includes a user ID, the update unit 245 generates and updates seat management information 212 by associating the user ID, seat location, and occupancy status.

[0042] Returning to Figure 3, we continue the explanation. The schedule management server 400 is an information processing device that manages the schedule information (schedules) of multiple users. The schedule management server 400 transmits the current schedule information of the corresponding user to the seat management server 500 in response to an inquiry from the management terminal 200. The schedule management server 400 can also be called the schedule management server. Figure 7 is a block diagram showing the configuration of the schedule management server 400 according to this embodiment 2. The schedule management server 400 comprises a storage unit 410, a memory 420, a communication unit 430, and a control unit 440. The storage unit 410 is an example of a storage device such as a hard disk or flash memory. The storage unit 410 stores a program 411 and schedule management information 412. The program 411 is a computer program that implements some of the processing of the seat management method according to this embodiment 2.

[0043] Schedule management information 412 is information for managing the schedule information of users under the jurisdiction of the seat management system 1000. Schedule management information 412 is associated with user information 4121, date 4122, time zone 4123, content 4124, and location 4125. User information 4121 includes the user ID. Date 4122 indicates the date of the schedule information. Time zone 4123 includes the time zone of the schedule information, for example, the scheduled start time and end time. Content 4124 indicates the content of the schedule. For example, content 4124 may include going out, meetings, etc. Location 4125 indicates the destination or meeting room. Figure 8 shows an example of schedule information 412 according to this embodiment 2. Note that the components and examples of schedule management information 412 are not limited to these.

[0044] Memory 420 is a volatile memory device such as RAM, and is a storage area for temporarily holding information when the control unit 440 is operating. Communication unit 430 is a communication interface with the network 300.

[0045] The control unit 440 is a processor, or control device, that controls each component of the schedule management server 400. The control unit 440 loads program 411 from the storage unit 410 into memory 420 and executes program 411. In this way, the control unit 440 realizes the functions of the receiving unit 441, the determination unit 442, the identification unit 443, the transmission unit 444, and the update unit 445.

[0046] The receiving unit 441 receives inquiries from the management terminal 200 regarding the current schedule information of a specific user. The inquiries include the user ID. The receiving unit 441 also receives requests from the PC 601 for registration, modification, or deletion of schedule information.

[0047] The determination unit 442 refers to the schedule management information 412 and determines whether the current schedule information corresponding to the user information 4121 (user ID) included in the query is already registered.

[0048] If the identification unit 443 determines that the current schedule information is already registered, it obtains (identifies) the date 4122, time zone 4123, content 4124, and location 4125 associated with the user information 4121 included in the query from the schedule management information 412 as schedule information.

[0049] If the user's current schedule information for the inquiry is already registered, the transmitting unit 444 sends (notifies) the schedule information to the seat management server 500. If the user's current schedule information for the inquiry is not registered, the transmitting unit 444 sends (notifies) the seat management server 500 that there is no corresponding schedule information. In addition, if the user's current schedule information for the inquiry is not registered, the transmitting unit 444 may also notify the seat management server 500 of information indicating that the user is temporarily away from their seat.

[0050] The update unit 445 updates the schedule management information 412 in response to the received registration request, change request, or deletion request.

[0051] Returning to Figure 3, we continue the explanation. The seat management server 500 is an information processing device that manages information such as the user currently using seat 101, their occupancy status, reason for absence, and expected return date. The seat management server 500 updates seat management information according to occupancy status information received from the management terminal 200 and schedule information received from the schedule management server 400. In addition, the seat management server 500 returns a seat list screen based on the seat management information in response to a seat list request from PC 601 or the like.

[0052] Figure 9 is a block diagram showing the configuration of the seat management server 500 according to this second embodiment. The seat management server 500 comprises a storage unit 510, a memory 520, a communication unit 530, and a control unit 540. The storage unit 510 is an example of a storage device such as a hard disk or flash memory. The storage unit 510 stores a program 511 and seat management information 512. The program 511 is a computer program in which some of the processing of the seat management method according to this second embodiment is implemented.

[0053] The seat management information 512 is information for managing the occupancy status of a group of seats under the jurisdiction of the seat management system 1000. The seat management information 512 is information associated with seat location 5121, user information 5122, occupancy status 5123, reason for absence 5124, and planned return date 5125. The seat location 5121, user information 5122, and occupancy status 5123 are the same information as the seat location 2121, user information 2122, and occupancy status 2123 described above. The reason for absence 5124 is information indicating the reason for absence for users whose occupancy status 5123 indicates "not occupying". Examples of reasons for absence 5124 include "out of the office," "in a meeting," or "temporarily away." However, the reason for absence 5124 is not limited to these. The return-to-seat schedule 5125 is information indicating the scheduled time for a user whose occupancy status 5123 is "not occupied" to return to their seat. The return-to-seat schedule 5125 may also be scheduled information for when the user is away from their seat (including the scheduled end time). Figure 10 shows an example of seat management information 512 according to this second embodiment. Note that the components and examples of seat management information 512 are not limited to these.

[0054] Memory 520 is a volatile memory device such as RAM, and is a storage area for temporarily holding information when the control unit 540 is operating. Communication unit 530 is a communication interface with the network 300.

[0055] The control unit 540 is a processor, or control device, that controls each component of the seat management server 500. The control unit 540 loads program 511 from the storage unit 510 into memory 520 and executes program 511. In this way, the control unit 540 realizes the functions of the receiving unit 541, the determination unit 542, the identification unit 543, the transmission unit 544, and the update unit 545.

[0056] The receiving unit 541 is an example of the reception unit 12 described above. The receiving unit 541 receives presence status information from the management terminal 200 via the network 300. The receiving unit 541 also receives schedule information from the schedule management server 400 via the network 300. Furthermore, the receiving unit 541 receives seat list requests from PC 601, etc., via the network 300.

[0057] The determination unit 542 determines whether the presence status included in the received presence status information indicates that the user is present. If the presence status indicates that the user is present, the determination unit 542 also determines whether the received presence status information includes a user ID.

[0058] The identification unit 543 identifies the reason for absence and the expected return date based on the schedule information received while the user is away from their seat. For example, if the schedule information indicates a meeting, the identification unit 543 determines (identifies) the reason for absence as being in a meeting. Also, if the schedule information indicates going out, the identification unit 543 determines (identifies) the reason for absence as being out. Furthermore, the identification unit 543 determines (identifies) the scheduled end time included in the schedule information as the expected return date (time). Also, if no schedule information is received while the user is away from their seat, the identification unit 543 determines (identifies) the reason for absence as being temporarily away. In addition, in response to a received seat list request, the identification unit 543 reads the seat management information 512 from the storage unit 510 and generates a seat list screen.

[0059] The transmitting unit 544 transmits the seat list screen generated in response to the received seat list request to the requesting PC 601 or the like via the network 300.

[0060] The update unit 545 generates seat management information 512 (first seat management information) according to the received seating status information and registers or updates it in the storage unit 510. Specifically, the update unit 545 extracts the seat location and seating status from the received seating status information. Then, the update unit 545 generates and updates seat management information 512 by associating the extracted seat location and seating status. Furthermore, if the received seating status information includes a user ID, the update unit 545 generates and updates seat management information 512 by associating the user ID, seat location, and seating status. On the other hand, if the seating status is seated but does not include a user ID, the update unit 545 leaves the user information 5122 blank and generates and updates seat management information 512 by associating the seat location and seating status. Furthermore, if the reason for absence or the planned return date is identified, the update unit 545 generates and updates seat management information 512 by associating the seat location, occupancy status, reason for absence, and planned return date. In other words, when the update unit 545 receives notification of schedule information from the schedule management server 400, it updates the first seat management information, including the reason for absence based on that schedule information. Also, when the update unit 545 receives notification of information indicating a temporary absence from the schedule management server 400, or when no schedule information is received within a predetermined time, it updates the first seat management information, including the temporary absence as the reason for absence. Furthermore, if current schedule information is already registered, the update unit 545 derives the planned return date information based on that schedule information and updates the seat management information, further including that planned return date information.

[0061] Returning to Figure 3, we continue the explanation. PC601 to 60m is an example of an information processing terminal operated by a user. PC601 and other terminals send a seat list request to the seat management server 500 via network 300 in response to user operations. PC601 then receives the seat list screen from the seat management server 500 via network 300 and displays it on the screen. This allows the user to easily understand the occupancy status of each seat, the reason for absence, and the expected return date.

[0062] The seat management unit 700 is a collective term for the management terminal 200, network 300, schedule management server 400, and seat management server 500, and may be considered an example of the seat management device 1. Alternatively, the seat management unit 700 may be called a seat management system. The seat management unit 700 can also be considered to include the storage unit 11, reception unit 12, and update unit 13 described above.

[0063] Figure 11 is a flowchart showing the flow of the presence / absence detection process according to this embodiment 2. The detection unit 10112 of the presence / absence detection sensor 1011 detects presence or absence in response to a detection instruction from the timer 10111 (S201). The detection unit 10112 determines whether the detection result is presence (seated) or not (S202). If it is determined that the person is present, the notification unit 10113 notifies the personal identification sensor 1012 of the presence status (S203). If it is determined in step S202 that the person is not present, the detection unit 10112 determines whether the detection result is absent or not (S204). If it is determined that the person is absent, the notification unit 10113 notifies the personal identification sensor 1012 of the presence status (S205). If NO is determined in step S204, after step S203 or S205, the presence / absence detection sensor 1011 waits for a certain period of time according to the timer 10111 (S206). After the period of time has elapsed, the timer 10111 outputs a detection instruction to the detection unit 10112, and the detection unit 10112 executes step S201 again.

[0064] Figure 12 is a flowchart showing the flow of personal identification processing according to this embodiment 2. First, the receiving unit 10121 of the personal identification sensor 1012 receives the presence / absence status from the presence / absence detection sensor 1011 (S211). Next, the personal identification unit 10122 performs personal identification processing for the user of seat 101 (S212). Then, the personal identification unit 10122 determines whether or not the user ID has been identified through the personal identification processing (S213). If the user ID has been identified, the notification unit 10123 generates presence status information including the identified user ID, the received presence status, and the seat location of seat 101. Then, the notification unit 10123 notifies the management terminal 200 of the presence status information (S214). If the user ID could not be identified in step S213, the notification unit 10123 generates presence status information including the received presence status and the seat location of seat 101. The notification unit 10123 then notifies the management terminal 200 of the presence status information (S215).

[0065] Figure 13 is a flowchart showing the processing flow of the management terminal 200 according to this embodiment 2. First, the receiving unit 241 of the management terminal 200 receives presence status information from the personal identification sensor 1012 via the network 300 (S221). Next, the determination unit 242 determines whether the presence status included in the received presence status information indicates presence (S222). If the determination in step S222 is NO, the determination unit 242 determines whether the presence status included in the received presence status information indicates absence (away) (S223). If the determination in step S223 is NO, no processing is performed and the process returns to step S221.

[0066] If step S223 determines YES (occupancy status is absent, away from seat), the identification unit 243 refers to the seat management information 212 and attempts to identify the user information 2122 (user ID) associated with the seat location 2121 included in the received occupancy status information (S224). If the user ID is identified, the transmission unit 244 sends a query for current schedule information corresponding to the identified user ID to the schedule management server 400 via the network 300 (S225). Specifically, the transmission unit 244 sends a query for schedule information including the identified user ID.

[0067] If the answer is YES in step S222, NO in S224, or after step S225, the transmission unit 244 transmits the received occupancy status information to the seat management server 500 via the network 300 (S226).

[0068] Figure 14 is a flowchart showing the processing flow of the schedule management server 400 according to this second embodiment. First, the receiving unit 441 of the schedule management server 400 receives the inquiry described in step S225 from the management terminal 200 via the network 300 (S231). That is, the receiving unit 441 receives an inquiry for current schedule information corresponding to the absent person (user ID).

[0069] Next, the determination unit 442 determines whether the current schedule information corresponding to the user information 4121 (user ID) included in the query is already registered in the schedule management information 412 (S232). Specifically, the determination unit 442 determines whether the data corresponding to the pair of the year, month, and day 4122 and time zone 4123 corresponding to the current time, and the user information 4121 including the user ID included in the query, is already registered in the schedule management information 412.

[0070] If the result in step S232 is determined to be YES, the identification unit 443 obtains the date 4122, time zone 4123, content 4124, and location 4125, which are associated with the user information 4121 included in the query, from the schedule management information 412 as schedule information (S233). Then, the transmission unit 444 transmits the obtained schedule information to the seat management server 500 via the network 300 (S234). At this time, the transmission unit 444 may also transmit the user ID included in the query along with the schedule information.

[0071] If the result in step S232 is determined to be YES, the transmission unit 444 sends a message to the seat management server 500 via the network 300 indicating that there is no corresponding scheduled information (S235).

[0072] Figure 15 is a flowchart showing the flow of the seat management information update process according to this embodiment 2. First, the receiving unit 541 of the seat management server 500 receives occupancy status information from the management terminal 200 via the network 300 (S241). Next, the determination unit 542 determines whether the occupancy status included in the received occupancy status information indicates that the seat is occupied (S242). If the occupancy status indicates that the seat is occupied, the determination unit 542 determines whether the received occupancy status information includes a user ID (S243). If a user ID is included, the update unit 545 extracts the seat location, user ID, and occupancy status from the received occupancy status information. Then, the update unit 545 generates and updates seat management information 512 by associating the extracted seat location 5121, user ID (user information 5122), and occupancy status 5123 (occupied) (S244).

[0073] If NO is determined in step S243, the update unit 545 leaves the user information 5122 blank, associates the seat location 5121 and occupancy status 5123 (occupied), generates seat management information 512, and updates it (S245).

[0074] If the result in step S242 is NO, the determination unit 542 determines whether or not schedule information has been received from the schedule management server 400 within a predetermined time (S246). If schedule information has been received, the identification unit 543 identifies the reason for absence and the return date based on the schedule information, as described above (S247). Then, the update unit 545 generates and updates seat management information 512 by associating the seat location 5121, presence status 5123 (absent), reason for absence 5124, and return date 5125 (S248). At this time, the updated seat management information 512 will retain the registered user information 5122.

[0075] If the result in step S246 is NO, the identification unit 543 determines (identifies) the reason for absence as temporary absence (S249). Then, the update unit 545 generates and updates seat management information 512 by associating the seat location 5121, occupancy status 5123 (not occupied), and reason for absence 5124 (S250). At this time, the updated seat management information 512 will retain the registered user information 5122.

[0076] Figure 16 is a sequence diagram showing the flow of the seat management information update process when presence is detected according to this embodiment 2. First, the presence / absence detection sensor 1011 detects presence (seated) (S261). Then, the presence / absence detection sensor 1011 notifies the personal identification sensor 1012 of the presence status indicating presence (S262). Subsequently, the personal identification sensor 1012 performs personal identification processing in response to the presence status notification (S263). Here, it is assumed that the user ID has been identified. The personal identification sensor 1012 then notifies the management terminal 200 of the presence status information, including the identified user ID, the received presence status, and the seat location of seat 101 (S264). In response, the management terminal 200, because the received presence status information indicates presence, transmits the presence status information to the seat management server 500 (S265). Subsequently, the seat management server 500 updates the seat management information 512 according to the received seating status information (S266).

[0077] Figure 17 is a sequence diagram showing the flow of the seat management information update process when absence is detected according to this second embodiment. First, the presence / absence detection sensor 1011 detects that the user has left their seat (S271). The presence / absence detection sensor 1011 then notifies the personal identification sensor 1012 of the presence status indicating that the user is not present (S272). Subsequently, the personal identification sensor 1012 performs personal identification processing in response to the presence status notification (S273). Here, since the user is absent, the user ID cannot be identified. Therefore, the personal identification sensor 1012 notifies the management terminal 200 of the presence status information, including the received presence status and the seat location of seat 101 (S274).

[0078] In response, the management terminal 200, seeing that the received occupancy status information indicates no occupancy, refers to the internal seat management information 212 and identifies the user ID associated with the seat location indicated by the received occupancy status information (S275). In other words, it identifies the user ID that was seated immediately before. Here, we assume that the user ID has been identified. The management terminal 200 then sends a request for schedule information, including the user ID, to the schedule management server 400 (S276). At the same time, the management terminal 200 sends the received occupancy status information to the seat management server 500 (S277).

[0079] The schedule management server 400 determines whether current schedule information corresponding to the user ID included in the inquiry from the management terminal 200 is registered. In the example in Figure 8, if the current time is 10:00 on day X of 2020, users C and D will have their schedule information registered for the current time. On the other hand, users E and other users will not have their schedule information registered for the current time. Here, we will assume that the schedule information is already registered. Therefore, the schedule management server 400 obtains the schedule information for the current time period, which is associated with the user ID, from the schedule management information 412 (S278). Then, the schedule management server 400 sends the obtained schedule information to the seat management server 500 (S279).

[0080] The seat management server 500 receives occupancy status information and schedule information. Then, as described above, the seat management server 500 identifies the reason for absence and the expected return date (S280). In the example in Figure 8, since user C's schedule information is "out of the office" and the scheduled end time of the time slot is 14:00, the identification unit 543 identifies the reason for absence as "out of the office" and the expected return date as "14:00". Similarly, since user D's schedule information is "meeting" and the scheduled end time of the time slot is 10:30, the identification unit 543 identifies the reason for absence as "in a meeting" and the expected return date as "10:30". Subsequently, the seat management server 500 updates the seat management information 512 based on the occupancy status information and the identified reasons for absence and expected return dates (S281). In the example in Figure 10, the reasons for absence and expected return dates for user C at seat ST006 and user D at seat ST009 are updated accordingly.

[0081] Figure 18 is a sequence diagram showing the flow of the seat list display process according to this second embodiment. First, PC 601 sends a seat list request to the seat management server 500 via the network 300 in response to an operation by a predetermined user (S291). The seat list request may specify, for example, a particular floor. When the seat management server 500 receives the seat list request, it generates a seat list screen based on the occupancy management information (S292). For example, the seat management server 500 may generate a seat list screen for seats corresponding to the floor specified in the seat list request. In other words, the seat management server 500 obtains user information 5122, reason for absence 5124, and expected return date 5125 associated with the seat location corresponding to the specified floor from the seat management information 512. Then, it applies the obtained information to the occupancy layout data of the specified floor to generate a seat list screen. After that, the seat management server 500 returns the generated seat list screen to PC 601 via the network 300 (S293). Then, PC601 displays the received seat list screen on its display (S294).

[0082] Figure 19 is a diagram illustrating the concept of user location and movement within the floor according to this second embodiment. It is assumed that floor F1 contains a management terminal 200, the first conference room R1, the first conference room R2, and seats ST001 to ST012. User A is seated at seat ST001, and User B is seated at seat ST003. User C was initially seated at seat ST006, but is currently out of the room, and this outing is registered in the schedule management information 412 in Figure 8. User D was initially seated at seat ST009, but is currently in a meeting in the first conference room R1 on floor F1, and this meeting is registered in the schedule management information 412 in Figure 8. Furthermore, although seat ST012 was initially occupied by user E, user E is currently vacant, and the schedule management information 412 in Figure 8 does not contain any schedule information for the current time of 10:00.

[0083] Figure 20 shows an example of a floor seating list display according to this second embodiment. Here, the current time is assumed to be 10:00 (Month X, Day Y, 2020). Seats ST001 and ST003 show that Mr. A and Mr. B are present, respectively. On the other hand, seats ST006, ST009, and ST012 show that Mr. C, Mr. D, and Mr. E are absent. Specifically, seat ST006 shows that "Mr. C" is "out of the office" as the reason for absence and is expected to return at "14:00". Seat ST009 shows that "Mr. D" is "in a meeting" as the reason for absence and is expected to return at "10:30". Seat ST012 shows that "Mr. E" is "temporarily absent" as the reason for absence.

[0084] As mentioned above, while a free-address system is being adopted, in reality, some people remain seated in the same seats for extended periods, or leave their belongings unattended for long periods during meetings, etc. As a result, many people are unable to sit in the seats they want. Therefore, it is desirable to be able to understand the reasons why users are away from their seats. For example, some reasons for users leaving their seats include meetings or business trips to clients (going out), for which the schedule information is registered in the schedule management system. On the other hand, reasons for leaving a seat may also include temporary absences or moving to other seats, which are not part of the schedule. Therefore, by linking with the schedule management server using this embodiment, it is possible to easily identify not only who is using each seat, but also the reasons for their absence. For example, if it is not a temporary absence, it is possible to contact the absent person separately and make arrangements such as obtaining permission to use the seat temporarily. Furthermore, in this embodiment, the display of expected return dates makes it easy to understand how long the absence will last.

[0085] Furthermore, the seat management server 500 may display a list of seats on a display or digital signage installed near the entrance of the floor. In this case, the seat management server 500 may update the displayed seat list periodically or whenever the seat management information 512 is updated.

[0086] <Embodiment 3> This third embodiment is a modification of the second embodiment described above. In this third embodiment, the seat management unit 700 is consolidated into a single server or cloud system. Figure 21 is a block diagram showing the overall configuration of the seat management system 1000a according to this third embodiment. In the seat management system 1000a, the presence / absence detection sensors 1011a to 10n1a and the personal identification sensors 1012a to 10n2a, which are installed on seats 101 etc., each become IoT (Internet of Things) devices and are connected to the network 300. In addition, in the seat management system 1000a, the management terminal 200, schedule management server 400 and seat management server 500 described above are replaced by a seat management server 500a. The other configurations are the same as in the second embodiment, so definitions, redundant explanations and illustrations are omitted.

[0087] Figure 22 is a block diagram showing the configuration of the seat management server 500a according to this third embodiment. Compared to the seat management server 500, the seat management server 500a has changes to the program 511a, the receiving unit 541a, and the update unit 545a, and the addition of schedule management information 513. Note that the schedule management information 513 is not mandatory, and schedule management information 412 stored in the schedule management server 400 connected to the network 300 may be used instead.

[0088] Program 511a is a computer program that implements the processing of the seat management method according to this embodiment 3.

[0089] The receiving unit 541a is an example of the reception unit 12 described above. The receiving unit 541a receives information from personal identification sensors 1012, etc. (or presence / absence detection sensors 1011, etc.) via the network 300. For example, the receiving unit 541a receives presence status information from personal identification sensors 1012a, etc. The receiving unit 541a also receives a seat list request from a PC 601, etc. via the network 300.

[0090] The determination unit 542a performs the same determination processing as the determination units 242, 442, and 542 described above. That is, the determination unit 542a determines whether the presence status included in the received presence status information indicates presence. If the presence status indicates presence, the determination unit 542a determines whether the received presence status information includes a user ID. If the presence status indicates absence, the determination unit 542a refers to the seat management information 512 and determines whether user information 5122 (user ID) associated with the seat location 5121 included in the received presence status information exists. Then, the determination unit 542a refers to the schedule management information 513 and determines whether the current schedule information corresponding to the user information 5122 (user ID) is registered.

[0091] The identification unit 543a performs the same identification processing as the identification units 243, 443, and 543 described above. That is, if the presence status indicates no presence, the identification unit 543a refers to the seat management information 512 and attempts to identify the user information 5122 (user ID) associated with the seat location 5121 included in the received presence status information. If the identification unit 543a determines that the current schedule information is already registered, it obtains (identifies) the schedule information corresponding to the identified user from the schedule management information 513. The identification unit 543a also identifies the reason for absence and the expected return date based on the schedule information received while the user is away from their seat. In addition, in response to a received seat list request, the identification unit 543a reads the seat management information 512 from the storage unit 510 and generates a seat list screen.

[0092] Furthermore, the determination unit 542a and the identification unit 543a can also be called the schedule processing unit. That is, if the presence status included in the presence status information indicates no presence, the schedule processing unit identifies the user identification information associated with the seat location included in the presence status information from the seat management information, and queries the current schedule information of the user corresponding to the identified identification information. Here, the schedule processing unit may query the schedule management information 513 in the seat management server 500a. Alternatively, the schedule processing unit may query the schedule management information 412 of the schedule management server 400 outside the seat management server 500a.

[0093] The transmitting unit 544a transmits the seat list screen generated in response to the received seat list request to the requesting PC 601 or the like via the network 300.

[0094] The update unit 545a, similar to the update unit 545 described above, generates seat management information 512 (first seat management information) according to the received seating status information and registers or updates it in the storage unit 510.

[0095] Figure 23 is a flowchart showing the flow of the seat management information update process according to this embodiment 3. Steps S301 to S305 are the same as steps S241 to S245 in Figure 15.

[0096] If the result in step S302 is NO, the identification unit 243a refers to the seat management information 512 and attempts to identify the user information 5122 (user ID) associated with the seat position 5121 included in the received occupancy status information (S306). If the user ID is identified, the determination unit 542a refers to the schedule management information 513 and determines whether or not the current schedule information corresponding to the identified user ID is registered (exists) (S307). If the result in step S307 is YES, steps S308 and S309 are processed in the same way as steps S247 and S248 in Figure 15. If the result in step S307 is NO, steps S310 and S311 are processed in the same way as steps S249 and S250 in Figure 15. If NO is determined in step S306, the update unit 545a leaves the user information 5122 blank, associates the seat location 5121 and occupancy status 5123 (not occupied), generates seat management information 512, and updates it (S312). After these steps, the process ends.

[0097] Thus, this third embodiment can achieve the same effects as the third embodiment described above.

[0098] <Other Embodiments> Furthermore, this embodiment may be improved as follows. For example, the scheduling processing unit may, at a predetermined timing, identify multiple users who are scheduled to attend the same meeting in the scheduling information, identify seating locations within a predetermined range of these identified users from the seating management information, and notify each user of the identified seating locations. This makes it possible to support smooth communication among attendees of the same meeting, even in a free-address system. It also helps prevent delays in gathering at the meeting room.

[0099] Furthermore, the update unit may update the seat management information to reflect the occupancy status associated with a specific seat location as a reserved seat. This makes it easier for attendees of the same meeting to work within a predetermined scope.

[0100] Furthermore, the occupancy status information may also include luggage status, which indicates the presence or absence of luggage near the corresponding seat. For example, a luggage hook pressure sensor may be installed on the seat. In this case, the pressure sensor may detect the presence or absence of luggage from the pressure of the hook, include it in the occupancy status information as luggage status, and notify the management terminal 200 or the seat management server 500a. Alternatively, the presence or absence of luggage may be detected by a camera installed on the seat. The update unit then updates the seat management information, including the reason for leaving the seat as temporary absence, if the occupancy status included in the occupancy status information indicates no occupancy and the luggage status indicates luggage present. This makes the determination of temporary absence more accurate.

[0101] Although the above embodiments were described as hardware configurations, the invention is not limited thereto. This disclosure can also be implemented by having the CPU execute computer programs to perform any desired processing.

[0102] In the above example, the program can be stored and supplied to the computer using various types of non-transitory computer-readable medium. Non-transitory computer-readable medium includes various types of tangible storage medium. Examples of non-transitory computer-readable medium include magnetic storage media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical storage media (e.g., magneto-optical disks), CD-ROMs (Read Only Memory), CD-Rs, CD-R / Ws, DVDs (Digital Versatile Discs), and semiconductor memory (e.g., mask ROMs, PROMs (Programmable ROMs), EPROMs (Erasable PROMs), flash ROMs, RAMs (Random Access Memory)). Alternatively, the program may be supplied to the computer by various types of transient computer-readable medium. Examples of transient computer-readable medium include electrical signals, optical signals, and electromagnetic waves. Transitory computer-readable medium can be supplied to the computer via wired communication channels such as electric wires and optical fibers, or via wireless communication channels.

[0103] This disclosure is not limited to the embodiments described above, and may be modified as appropriate without departing from its spirit. Furthermore, this disclosure may be implemented by combining the respective embodiments as appropriate.

[0104] Some or all of the above embodiments may also be described as follows, but are not limited to the following: (Note A1) A storage unit that stores seat management information, including the occupancy status of users at each of multiple seats, A reception unit receives occupancy status information, including the occupancy status (indicating whether or not a seat is occupied) and the seat location, as detected by sensors installed at each seat. An update unit that updates the seat management information according to the aforementioned occupancy status information, Equipped with, The aforementioned update unit is If the occupancy status indicates that the person is occupying, and the occupancy status information includes user identification information detected by the sensor, the seat management information is updated by associating the seat location, the identification information, and the occupancy status included in the occupancy status information. If the aforementioned occupancy status indicates no occupancy, the seat management information is updated by associating the seat location and the occupancy status included in the occupancy status information. Seat management system. (Appendix A2) If the presence status included in the presence status information indicates no presence, the system further includes a scheduling processing unit that identifies the user's identification information associated with the seat location included in the presence status information from the seat management information, and queries the current schedule information of the user corresponding to the identified identification information. The aforementioned update unit is If the current schedule information is already registered, the seat management information will be updated, including the reason for leaving the seat based on that schedule information. If the current schedule information is not registered, update the seat management information to include temporary absence as the reason for absence. The seat management device described in Appendix A1. (Note A3) The aforementioned update unit is If the current schedule information is already registered, the return-to-seat schedule information is derived based on that schedule information, and the seat management information is updated to include that return-to-seat schedule information. The seat management device described in Appendix A2. (Note A4) The aforementioned planned processing unit is, At a predetermined time, the schedule information identifies multiple users who are scheduled to attend the same meeting, From the aforementioned seat management information, the seat locations within a predetermined range of the identified users are determined. The identified seat location will be notified to each user. The seat management device described in Appendix A2 or A3. (Note A5) The aforementioned update unit is The seat management information is updated to reflect the seating status associated with the identified seat location as a reserved seat. The seat management device described in Appendix A4. (Note A6) The aforementioned seating status information further includes luggage status indicating the presence or absence of luggage near the corresponding seat, The aforementioned update unit is If the seating status included in the seating status information indicates "not seated" and the luggage status indicates "with luggage," the seating management information is updated to include the reason for leaving the seat as "temporarily away." A seat management device as described in any one of the items A2 to A5 in the appendix. (Note B1) A storage device that stores first seat management information, including the occupancy status of users at each of multiple seats, Multiple sensors installed in each of the aforementioned multiple seats, Equipped with a seat management device, The aforementioned seat management device is, A reception unit that receives occupancy status information including the occupancy status, which indicates whether or not someone is present, and the seat location, as detected by each of the aforementioned multiple sensors, An update unit updates the first seat management information according to the aforementioned seating status information, Equipped with, The aforementioned update unit is If the occupancy status indicates that the seat is occupied, and the occupancy status information includes user identification information detected by the sensor, the first seat management information is updated by associating the seat location, the identification information, and the occupancy status included in the occupancy status information. If the seating status indicates no seating, the first seating management information is updated by associating the seating location and seating status included in the seating status information. Seat management system. (Note B2) The aforementioned seat management system is A management terminal connected to each of the aforementioned multiple sensors, A schedule management server that manages the schedule information of multiple users, Furthermore, The aforementioned management terminal is When the occupancy status information is received from the multiple sensors, the occupancy status information is transmitted to the seat management device, and second seat management information is registered internally according to the occupancy status information. If the presence status included in the presence status information indicates no presence, the user identification information associated with the seat location included in the presence status information is identified from the second seat management information, and the current schedule information of the user corresponding to the identified identification information is queried from the schedule management server. The aforementioned schedule management server is If the user's current schedule information in the aforementioned inquiry is already registered, the schedule information is notified to the seat management device. If the user's current schedule information in the aforementioned inquiry is not registered, information indicating temporary absence will be sent to the seat management device. The update unit of the seat management device is When the schedule information is notified from the schedule management server, the first seat management information is updated, including the reason for leaving the seat based on the schedule information. When the aforementioned schedule management server notifies information indicating temporary absence, the first seat management information is updated to include the temporary absence as the reason for absence. The seat management system described in Appendix B1. (Note C1) A computer equipped with a storage unit that stores seat management information, including the occupancy status of users at each of multiple seats, The system receives occupancy status information, including the occupancy status (indicating whether or not a seat is occupied) and the seat location, as detected by sensors installed at each seat. If the occupancy status indicates that the person is occupying, and the occupancy status information includes user identification information detected by the sensor, the seat management information is updated by associating the seat location, the identification information, and the occupancy status included in the occupancy status information. If the aforementioned occupancy status indicates no occupancy, the seat management information is updated by associating the seat location and the occupancy status included in the occupancy status information. Seating management method. (Note D1) A computer equipped with a storage unit that stores seat management information, including the occupancy status of users at each of multiple seats, A process that receives occupancy status information, including the occupancy status (indicating whether or not a seat is occupied) and the seat location, as detected by sensors installed at each seat. If the occupancy status indicates that the user is present, and the occupancy status information includes user identification information detected by the sensor, the process of updating the seat management information by associating the seat location, the identification information, and the occupancy status included in the occupancy status information, If the aforementioned occupancy status indicates no occupancy, the process of updating the seat management information by associating the seat location and said occupancy status included in the occupancy status information, A seat management program that executes this process.

[0105] Although the present invention has been described above with reference to embodiments (and examples), the present invention is not limited to the above embodiments (and examples). Various modifications to the structure and details of the present invention can be made, which can be understood by those skilled in the art within the scope of the present invention. [Explanation of Symbols]

[0106] 1. Seat management device 11 Storage section 111 Seat Management Information 12 Reception Department 13 Update section 1000 Seat Management System 1000a Seat Management System 101 seats 1011 Presence / Absence Detection Sensor 10111 Timer 10112 Detection unit 10113 Notification Department 1012 Personal Identification Sensor 10121 Receiver 10122 Personal identification section 10123 Notification Department 1011a Presence / Absence Detection Sensor 1012a Personal identification sensor 10n seat 10n1 Presence / Absence Detection Sensor 10n2 Personal Identification Sensor 10n1a Presence / Absence Detection Sensor 10n2a Personal Identification Sensor 200 management terminals 210 Storage section 211 Programs 212 Seat Management Information 2121 Seat location 2122 User Information 2123 Presence status 220 memory 230 Communications Department 240 Control Unit 241 Receiving Unit 242 Judgment section 243 Specific part 244 Transmitter 245 Update Department 300 Networks 400 Schedule Management Server 410 Storage section 411 Programs 412 Schedule Management Information 4121 User Information 4122 year, month, day 4123 time slot 4124 Contents 4125 Location 420 memory 430 Communications Department 440 Control Unit 441 Receiving Unit 442 Judgment section 443 Specific part 444 Transmitter 445 Update Department 500 seat management server 510 Storage section 511 Programs 512 Seat Management Information 5121 Seat location 5122 User Information 5123 Presence status 5124 Reason for leaving seat 5125 Scheduled to return to seat 520 memory 530 Communications Department 540 Control Unit 541 Receiving Unit 542 Judgment section 543 Specific part 544 Transmitter 545 Update Department 500a Seat Management Server 511a Program 513 Schedule Management Information 5131 User Information 5132 year, month, day 5133 time slot 5134 Contents 5135 Location 541a Receiving Unit 542a Judgment part 543a Specific part 544a Transmitter 545a Update Department 601 PC 60m PC 700 Seating Management Department F1 Floor R1 Conference Room 1 R2 Conference Room 1 ST001 Seat ST002 Seat ST003 Seat ST004 Seat ST005 Seat ST006 Seat ST007 Seat ST008 Seat ST009 Seat ST010 Seat ST011 Seat ST012 Seat

Claims

1. A storage unit that stores seat management information, including the occupancy status of users at each of multiple seats, A reception unit receives occupancy status information, including the occupancy status (indicating whether or not a seat is occupied) and the seat location, as detected by sensors installed at each seat. An update unit updates the seat management information according to the occupancy status information, and if the occupancy status indicates that the seat is occupied and the occupancy status information includes user identification information detected by the sensor, it updates the seat management information by associating the seat location, the identification information, and the occupancy status included in the occupancy status information. If the presence status included in the presence status information indicates no presence, the schedule processing unit identifies the user's identification information associated with the seat location included in the presence status information from the seat management information and queries the current schedule information of the user corresponding to the identified identification information. Equipped with, The aforementioned update unit is In the seat list displayed on the display device installed near the aforementioned multiple seats, the user identification information and the occupancy status display included in the seat management information are updated at the seat location where the identification information is identified. If the occupancy status indicates that the seat is occupied, and the occupancy status information includes user identification information detected by the sensor, the display content of the seat list is updated to display the identification information and the occupancy status at the seat location included in the occupancy status information. If the aforementioned seating status indicates no seating, the display content of the seating list is updated to display the aforementioned seating status in the seating location included in the seating status information. If the current schedule information is already registered, the display content of the seat list will be updated to include the reason for leaving the seat based on the schedule information, in the seat location included in the seating status information. If the current schedule information is already registered, the return-to-seat information is derived based on that schedule information, and the display content of the seat list is updated to further display the return-to-seat information along with the reason for leaving the seat at the seat location included in the occupancy status information. If the current schedule information is not registered, the display content of the seat list will be updated to include "temporarily away from seat" as the reason for absence in the seat location included in the occupancy status information. Seat management system.

2. The aforementioned planned processing unit is, At a predetermined time, the schedule information identifies multiple users who are scheduled to attend the same meeting, From the aforementioned seat management information, the seat locations within a predetermined range of the identified users are determined. The identified seat location will be notified to each user. The seat management device according to claim 1.

3. The aforementioned update unit is The seat management information is updated to reflect the seating status associated with the identified seat location as a reserved seat. The seat management device according to claim 2.

4. The aforementioned seating status information further includes luggage status indicating the presence or absence of luggage near the corresponding seat, The aforementioned update unit is If the seating status included in the seating status information indicates "not seated" and the luggage status indicates "with luggage," the seating management information is updated to include the reason for leaving the seat as "temporarily away." The seat management device according to any one of claims 2 to 3.

5. A storage device that stores first seat management information, including the occupancy status of users at each of multiple seats, Multiple sensors installed in each of the aforementioned multiple seats, A display device installed near the aforementioned multiple seats, A management terminal connected to each of the aforementioned multiple sensors, A schedule management server that manages the schedule information of multiple users, A seat management device, Equipped with, The aforementioned management terminal is When the system receives occupancy status information from each of the multiple sensors, including the occupancy status indicating whether or not a seat is occupied and the seat location, it transmits the occupancy status information to the seat management device and registers second seat management information internally according to the occupancy status information. If the occupancy status indicates that the seat is occupied, and the occupancy status information includes user identification information detected by the sensor, the second seat management information is updated by associating the seat location, the identification information, and the occupancy status included in the occupancy status information. If the presence status included in the presence status information indicates no presence, the user identification information associated with the seat location included in the presence status information is identified from the second seat management information, and the current schedule information of the user corresponding to the identified identification information is queried from the schedule management server. The aforementioned schedule management server is If the user's current schedule information in the aforementioned inquiry is already registered, the schedule information is notified to the seat management device. If the user's current schedule information in the aforementioned inquiry is not registered, information indicating temporary absence will be sent to the seat management device. The aforementioned seat management device is, A reception unit that receives the presence status information from the management terminal, An update unit updates the first seat management information according to the occupancy status information, and if the occupancy status indicates that the seat is occupied and the occupancy status information includes user identification information detected by the sensor, it updates the first seat management information by associating the seat location, the identification information, and the occupancy status included in the occupancy status information. Equipped with, The aforementioned update unit is In the seat list displayed on the display device, the user identification information and the occupancy status display included in the first seat management information are updated at the seat location where the identification information has been identified. If the occupancy status indicates that the seat is occupied, and the occupancy status information includes user identification information detected by the sensor, the display content of the seat list is updated to display the identification information and the occupancy status at the seat location included in the occupancy status information. If the aforementioned seating status indicates no seating, the display content of the seating list is updated to display the aforementioned seating status in the seating location included in the seating status information. When the schedule information is notified from the schedule management server, the display content of the seat list is updated to include the reason for leaving the seat based on the schedule information, in addition to the seat location included in the occupancy status information. When the schedule information is notified from the schedule management server, the return-to-seat information is derived based on the schedule information, and the display content of the seat list is updated to further display the return-to-seat information along with the reason for leaving the seat at the seat location included in the occupancy status information. When the aforementioned schedule management server notifies information indicating temporary absence, the display content of the seat list is updated to include the temporary absence as the reason for absence in the seat location included in the occupancy status information. Seat management system.

6. A computer equipped with a storage unit that stores seat management information, including the occupancy status of users at each of multiple seats, The system receives occupancy status information, including the occupancy status (indicating whether or not a seat is occupied) and the seat location, as detected by sensors installed at each seat. The seat management information is updated according to the aforementioned occupancy status information. If the occupancy status indicates that the person is occupying, and the occupancy status information includes user identification information detected by the sensor, the seat management information is updated by associating the seat location, the identification information, and the occupancy status included in the occupancy status information. In the seat list displayed on the display device installed near the aforementioned multiple seats, the user identification information and the occupancy status display included in the seat management information are updated at the seat location where the identification information is identified. If the occupancy status indicates that the seat is occupied, and the occupancy status information includes user identification information detected by the sensor, the display content of the seat list is updated to display the identification information and the occupancy status at the seat location included in the occupancy status information. If the aforementioned seating status indicates no seating, the display content of the seating list is updated to display the aforementioned seating status in the seating location included in the seating status information. If the presence status included in the presence status information indicates no presence, the user identification information associated with the seat location included in the presence status information is identified from the seat management information, and the current schedule information of the user corresponding to the identified identification information is queried. If the current schedule information is already registered, the display content of the seat list will be updated to include the reason for leaving the seat based on the schedule information, in the seat location included in the seating status information. If the current schedule information is already registered, the return-to-seat information is derived based on that schedule information, and the display content of the seat list is updated to further display the return-to-seat information along with the reason for leaving the seat at the seat location included in the occupancy status information. If the current schedule information is not registered, the display content of the seat list will be updated to include "temporarily away from seat" as the reason for absence in the seat location included in the occupancy status information. Seating management method.

7. A computer equipped with a storage unit that stores seat management information, including the occupancy status of users at each of multiple seats, A process that receives occupancy status information, including the occupancy status (indicating whether or not a seat is occupied) and the seat location, as detected by sensors installed at each seat. A process to update the seat management information according to the aforementioned occupancy status information, If the occupancy status indicates that the user is present, and the occupancy status information includes user identification information detected by the sensor, the process of updating the seat management information by associating the seat location, the identification information, and the occupancy status included in the occupancy status information, In the seat list displayed on the display device installed near the aforementioned multiple seats, the process of updating the user identification information and the occupancy status display included in the seat management information at the seat location where the identification information has been identified, If the occupancy status indicates that the seat is occupied, and the occupancy status information includes user identification information detected by the sensor, the process of updating the display content of the seat list to display the seat location, the identification information, and the occupancy status included in the occupancy status information, If the aforementioned occupancy status indicates no occupancy, the process updates the display content of the seat list to display the seat location and the said occupancy status included in the occupancy status information. If the presence status included in the presence status information indicates no presence, the process involves identifying the user's identification information associated with the seat location included in the presence status information from the seat management information, and querying the current schedule information of the user corresponding to the identified identification information. If the current schedule information is already registered, the process updates the display content of the seat list so that the seat location included in the occupancy status information also includes the reason for leaving the seat based on the schedule information. If the current schedule information is already registered, the process involves deriving the return-to-seat schedule information based on that schedule information, and updating the display content of the seat list so that the return-to-seat schedule information is further displayed along with the reason for leaving the seat at the seat location included in the occupancy status information. If the current schedule information is not registered, the process updates the display content of the seat list so that the seat location included in the seating status information includes "temporarily away from seat" as the reason for absence. A seat management program that executes this process.

Images