JP7673402B2 - RESOURCE MANAGEMENT DEVICE, RESOURCE MANAGEMENT SYSTEM, PROGRAM, AND RESOURCE MANAGEMENT METHOD - Google Patents

Description

The present invention relates to a resource management device, a resource management system, a program, and a resource management method.

There is a known technology in which an information processing terminal installed or used in a conference room displays information regarding reservations for resources (managed resources) such as conference rooms. With such technology, when a user starts using the conference room, the user inputs the necessary information into the information processing terminal, allowing the user to use the conference room.

For example, when reserving resources such as a conference room, if an administrator sets a configuration file in a conference room terminal, the administrator can access a server within the terminal by capturing an image code containing connection destination information on the conference room terminal (see, for example, Patent Document 1).

However, while conventional technology can manage users, such as administrators or participants who plan to use resources such as conference rooms, it is difficult to identify users who have actually used the resources.

The present invention has been made in consideration of the above, and aims to facilitate the management of users when using resources.

In order to solve the above-mentioned problems and achieve the object, the present invention provides a resource management device comprising: a communication information storage unit that stores communication information including information indicating the date and time when multiple communication terminals communicated; a resource information storage unit that stores usage information including information indicating the date and time when a resource that is a managed resource was used; an identification unit that identifies a user of a second communication terminal who is using the same resource as a user of a first communication terminal when the user of a first communication terminal uses the resource based on the resource usage information and the communication information; and a registration unit that registers the communication information between the identified user of the second communication terminal and the user of the first communication terminal in association with the resource usage information, wherein the identification unit identifies the user of the second communication terminal as using the same resource as the user of the first communication terminal when a difference between the date and time when the first communication terminal and the second communication terminal communicated and the date and time when the resource was used is within a predetermined range, and user identification information of the second communication terminal that communicated with the first communication terminal is included in the usage information of the resource used by the user of the first communication terminal.

As described above, the present invention has the effect of facilitating the management of users in the use of resources.

FIG. 1 is a diagram illustrating an example of an overall configuration of a resource management system according to a first embodiment. FIG. 2 is a diagram illustrating an example of the hardware configuration of the resource management device, the reservation management device, and the PC according to the embodiment. FIG. 3 is a diagram illustrating an example of a hardware configuration of a communication terminal and a resource terminal according to the embodiment. FIG. 4 is a diagram illustrating an example of a functional configuration of a resource management system according to an embodiment. FIG. 5A is a conceptual diagram showing an example of a login management table according to the embodiment, and FIG. 5B is a conceptual diagram showing an example of an infected person management table according to the embodiment. FIG. 6 is a conceptual diagram showing an example of a resource state information table according to the embodiment. FIG. 7A is a conceptual diagram showing an example of a communication information management table according to the embodiment, and FIG. 7B is a conceptual diagram showing an example of a user information management table according to the embodiment. FIG. 8 is a conceptual diagram illustrating an example of a reservation information management table according to the embodiment. FIG. 9 is a sequence diagram illustrating an example of an authentication process according to the embodiment. FIG. 10 is a diagram showing an example of an authentication screen according to the embodiment. FIG. 11 is a sequence diagram illustrating an example of a check-in process using a QR code according to the embodiment. FIG. 12 is a diagram showing an example of a check-in possible screen on a resource terminal according to the embodiment. FIG. 13 is a diagram illustrating an example of a QR code photographing screen according to the embodiment. FIG. 14 is a diagram showing an example of a check-in available screen (vacant room) on a resource terminal according to the embodiment. FIG. 15 is a flowchart showing an example of a management report creation process according to the embodiment. FIG. 16 is a sequence diagram illustrating an example of a process for registering an infected person according to the embodiment. FIG. 17 is a diagram illustrating an example of an infected person registration screen according to the embodiment. FIG. 18 is a sequence diagram illustrating an example of a process of notifying a contact person according to the embodiment. FIG. 19 is a diagram illustrating an example of a contact confirmation screen according to the embodiment. FIG. 20 is a diagram illustrating another example of the contact confirmation screen according to the embodiment. FIG. 21 is a sequence diagram illustrating an example of a process of determining a contact person and a process of notifying the contact person according to the second embodiment. FIG. 22 is a flowchart illustrating an example of a contactor determination process according to the second embodiment. FIG. 23 is a diagram illustrating an example of a warning screen according to the second embodiment. FIG. 24 is a flowchart illustrating an example of a contact search process according to the third embodiment. FIG. 25(A) is a diagram showing an example of a contact search screen according to the third embodiment, and FIG. 25(B) is a diagram showing an example of a contact search result screen according to the third embodiment.

Below, the mode for implementing the invention will be explained with reference to the drawings. Note that in the explanation of the drawings, the same elements are given the same reference numerals, and duplicate explanations will be omitted.

(First embodiment)
<System configuration example>
FIG. 1 is a diagram showing an example of the overall configuration of a resource management system according to a first embodiment. In this embodiment, the resource management system 1 is composed of a resource management device 2, a reservation management device 3, a communication terminal 4, a resource terminal 5, and a PC 6. The resource management device 2 manages the usage status of a conference room, which is a resource (resource to be managed). The reservation management device 3 manages the reservation status of the resource. The communication terminal 4, the resource terminal 5, and the PC 6 are connected to each other through a communication network 100 such as an in-house network inside a firewall 105. In addition, the resource management device 2 and the reservation management device 3 are connected to each other through a communication network 110 outside the firewall 105. The communication network 110 is a network through which an unspecified number of communications are transmitted, and is constructed by the Internet, a mobile communication network, a LAN (Local Area Network), or the like. In other words, the resource management device 2 can communicate with the reservation management device 3 through the communication network 110. The resource management device 2 can communicate with the communication terminal 4, the resource terminal 5, and the PC 6 via the communication network 110, the firewall 105, and the communication network 100. The reservation management device 3 can communicate with the communication terminal 4, the resource terminal 5, and the PC 6 via the communication network 110, the firewall 105, and the communication network 100. The communication terminal 4 can communicate with the resource terminal 5 via the communication network 100.

In addition, the communication network 110 may include not only wired communication but also wireless communication networks such as 3G ( ^3rd Generation), 4G ( ^4th Generation), 5G ( ^5th Generation), WiMAX (Worldwide Interoperability for Microwave Access), or LTE (Long Term Evolution).

<<Reservation management device>>
The reservation management device 3 is realized by one or more information processing devices (computer systems) equipped with a general server OS or the like. A system related to the reservation of resources and management of users' reservations or schedules provided by the reservation management device 3 is referred to as a reservation management system here. The reservation management device 3 has a calendar system and provides a Web application that manages various schedules of users. For example, the reservation management device 3 has the following functions.
- Accepts user reservations or schedule registrations, and users can check their reservation status or schedule anytime, anywhere

- Notify users by email at a set date and time, such as 30 minutes before the event. - One person can manage reservations or events on multiple calendars (work, home, etc.). - Share calendars with people in the same group.

The reservation management device 3 manages users with accounts. An account is a right that a user has to use a service. In many systems, users log into the system using an account. For this reason, the account has a function that allows the system to uniquely identify the user (identification information function). In this embodiment, the reservation management device 3 transmits reservation information of a pre-registered account (domain) to the resource management device 2 that manages conference rooms, etc. Alternatively, the resource management device 2 may specify an account of the reservation management device 3 and request the reservation information, so that the resource management device 2 can obtain the reservation information of the conference room from the reservation management device 3. Note that there are no particular restrictions on the account, as long as it is information that can uniquely identify the user, such as an email address, ID, or telephone number.

In this embodiment, the reservation management device 3 can manage reservation information for reserving various resources including free spaces and conference rooms, and user schedules. Note that, although G Suite (registered trademark), Office365 (registered trademark), etc. are well-known reservation management systems, any reservation management system having the functions described in this embodiment will suffice.

In addition, in this embodiment, information regarding the various resources reserved by each user and the schedule of each user is pre-registered in the reservation management device 3. That is, the web application of the reservation management device 3 is customized according to the reservation user account, resource ID, resource name, start date and time, end date and time, participant identification information, etc. in the internal network of the company using the resource management system 1. Therefore, the reservation information is linked to resources including each conference room of the company using the resource management system 1. Note that in this embodiment, the reservation management device 3 functions as an example of a reservation management device.

<<Resource management device>>
The resource management device 2 is realized by one or more information processing devices (computer systems) equipped with a general server OS or the like. The resource management device 2 acquires reservation information of each resource and expected participant identification information set in the reservation information from the reservation management device 3 as processing related to the communication network 110. This expected participant identification information is information for identifying expected participants who are planning to participate in the reserved resource. For example, an email address is used as the expected participant identification information. Furthermore, as processing related to the communication network 100, the resource management device 2 manages check-in and check-out to each conference room, and communicates with the resource terminals 5 provided in each conference room based on the reservation information of each conference room acquired from the reservation management device 3. Note that in this embodiment, the resource management device 2 functions as an example of a resource management device.

The communication network 100 includes, for example, each conference room within the floor space, work areas of prospective participants, etc. Planned participants of an event held in a specific conference room can access the communication network 110 from various locations via the communication network 100 and a firewall 105. The communication network 100 is, for example, a LAN (Local Area Network). However, each conference room and the work areas of prospective participants do not have to be a LAN within the same company.

In addition, the information shared by the resource management device 2 may include information that is not limited to text information, such as images, videos, and audio. However, for the sake of convenience, this embodiment will be described assuming that text information is mainly used for notifications.

The resource management device 2, like the reservation management device 3, can manage users with an account different from the account of the reservation management device 3. However, in principle, the above-mentioned resource management device 2 does not need to be aware of the account of the resource management device 2. The resource management device 2 can specify any account of the resource management device 2 and notify.

<<Communication terminal>>
The communication terminal 4 is realized by one or more information processing devices (computer systems) equipped with a general server OS or the like. The communication terminal 4 is a communication terminal for a user to perform various settings when using a resource (conference room) via a web page provided by the resource management device 2 and after using the resource. The communication terminal 4 is capable of both wired and wireless communication and can perform wireless communication with other communication terminals. The communication terminal 4 is also used as a display terminal that displays the user's name when the user starts using a resource such as a conference room that the user has reserved. Furthermore, the communication terminal 4 may have a function of communicating using browser software and displaying a web page.

The communication terminal 4 may be, for example, a communication terminal having a communication function, such as a smartphone, a tablet terminal, a PDA (Personal Digital Assistant), or a wearable PC (sunglasses type, wristwatch type, etc.). In other words, a terminal capable of running software such as browser software is used as the communication terminal. In this embodiment, the communication terminal 4 functions as an example of a communication terminal. Furthermore, in this embodiment, the communication terminal 4 includes communication terminals owned by users including a reservation person who has reserved a resource described below, a user who has used a specific resource within a specified time period in which the same resource was used, an infected person who has been found to be infected with or tested positive for a specific infectious disease, and a contact person who has come into contact with an infected person.

<<Resource terminal>>
The resource terminal 5 is a communication terminal equipped with a general OS, etc. Instead of the resource terminal 5, a communication terminal having a communication function, such as a tablet terminal, a PC (Personal Computer), a PDA (Personal Digital Assistant), a wearable PC (sunglasses type, wristwatch type, etc.), etc., may be used. In other words, the communication terminal is a terminal capable of operating software such as browser software.

In addition, as described below, the resource terminal 5 has a function of generating and displaying code symbols, such as a barcode as an example of a one-dimensional code or a QR code (registered trademark, hereafter omitted) as an example of a two-dimensional code, based on reservation identification information related to the resource in which the resource terminal 5 is placed and installed, and allowing the user using the communication terminal 4 to read the code symbols.

Furthermore, in this embodiment, the resource terminal 5 may include a resource management device 2 for operating dedicated application software (hereinafter referred to as a conference app) related to a specific event such as a conference held in the resource management system 1. Note that the above-mentioned application may be substituted with browser software. Note that in this embodiment, the resource terminal 5 functions as an example of a resource terminal.

<<PC>>
Furthermore, an administrator who manages the schedules of users can use a PC 6 that can be connected to the communication network 100 inside the firewall 105. The PC 6 is a communication terminal that allows the administrator to perform various settings related to resources (conference rooms) via a web page provided by the resource management device 2. One of these settings is an initial setting. For the initial setting, a terminal device such as a smartphone owned by the administrator may be used. The PC 6 is capable of communication both wired and wirelessly. A chat application is installed in the PC 6. The PC 6 is used as a display terminal for checking the reservation status of resources such as conference rooms including free spaces reserved by users by using the chat application. Furthermore, the PC 6 may have a function of communicating using browser software and displaying web pages.

In place of PC 6, for example, a communication terminal having a communication function, such as a tablet terminal, a PDA (Personal Digital Assistant), or a wearable PC (sunglasses type, wristwatch type, etc.), may be used. In other words, the communication terminal is a terminal capable of running software such as browser software. In this embodiment, PC 6 functions as an example of an administrator terminal.

○About terminology○
Resources refer to resources owned, rented, or managed by schools, companies, groups, and organizations. Examples of resources for schools, companies, groups, and organizations include conference rooms, equipment, devices, and people (reception groups) that can be used in conference rooms. In addition, free spaces with free addresses (hereinafter simply referred to as free spaces), locations such as desks, chairs, and booths, company cars, bicycles, parking lots, bicycle parking lots, remote conference systems, and printing services and mechanisms can also be resources. Resources that are difficult to move are called equipment. In this embodiment, for the sake of convenience, the term conference room is used as an example of a resource. In addition, various types of equipment can also be treated as resources, such as various types of electronic devices, locations such as rental offices and rental studios, rental bicycles, rental cars (shared cars), accommodation facilities such as hotels, event venues, and rental spaces and spaces such as lockers.

A request to use a resource may be a request to use a resource that requires resource identification information (resource ID). For example, this may be a request to start using the resource or a request to start reserving the resource.

Furthermore, the term "user" includes a person who reserves a resource such as a free space or a conference room, a participant who participates in using the resource, and an administrator who manages the resource management system 1 in this embodiment. In other words, if a person who reserves a specific resource uses or participates in that resource, the person who made the reservation becomes the user or participant. Note that a user may also be called a user.

[Hardware configuration]
<Hardware configuration of resource management device, reservation management device, and PC>
2 is a diagram showing an example of the hardware configuration of a resource management device, a reservation management device, and a PC according to the third embodiment. The resource management device 2 and the reservation management device 3 are realized, for example, by a computer system having the hardware configuration shown in FIG.

The resource management device 2 shown in FIG. 2 is constructed by a computer. The resource management device 2 includes, for example, a CPU (Central Processing Unit) 201, a ROM (Read Only Memory) 202, a RAM (Random Access Memory) 203, a HD (Hard Disk) 204, a HDD (Hard Disk Drive) controller 205, a display 206, an external device connection I/F 207 (Interface), a bus line 208, a network I/F 209, a keyboard 210, a pointing device 211, a DVD-RW (Digital Versatile Disc Rewritable) drive 213, and a media I/F 215.

Of these, the CPU 201 controls the operation of the entire computer system. The ROM 202 stores programs used to drive the CPU 201, such as IPL. The RAM 203 is used as a work area for the CPU 201. The HD 204 stores various data such as programs. The HDD controller 205 controls the reading or writing of various data from the HD 204 under the control of the CPU 201. The display 206 displays various information such as a cursor, menu, window, character, or image. The external device connection I/F 207 is an interface for connecting various external devices. In this case, the external device is, for example, a USB (Universal Serial Bus) memory or a printer. The network I/F 209 is an interface for data communication using the communication network 110. The bus line 208 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 201 shown in FIG. 2.

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

The reservation management device 3 is constructed by a computer. As shown in Fig. 2, the reservation management device 3 includes a CPU 301, a ROM 302, a RAM 303, a HD 304, a HDD (Hard Disk Drive) controller 305, a display 306, an external device connection I/F 307 (Interface), a bus line 308, a network I/F 309, a keyboard 310, a pointing device 311, a DVD-RW (Digital Versatile Disc Rewritable) drive 313, and a media I/F 315. These have the same configuration as the CPU 201, ROM 202, RAM 203, HD 204, HDD controller 205, display 206, external device connection I/F 207, bus line 208, network I/F 209, keyboard 210, pointing device 211, DVD-RW drive 213, and media I/F 215 in the resource management device 2, so their explanation will be omitted.

The PC 6 is constructed by a computer. As shown in Fig. 2, the PC 6 includes a CPU 601, a ROM 602, a RAM 603, a HD 604, a HDD (Hard Disk Drive) controller 605, a display 606, an external device connection I/F 607 (Interface), a bus line 608, a network I/F 609, a keyboard 610, a pointing device 611, a DVD-RW (Digital Versatile Disc Rewritable) drive 613, and a media I/F 615. These have the same configuration as the CPU 201, ROM 202, RAM 203, HD 204, HDD controller 205, display 206, external device connection I/F 207, bus line 208, network I/F 209, keyboard 210, pointing device 211, DVD-RW drive 213, and media I/F 215 in the resource management device 2, so their explanation will be omitted.

<Hardware configuration of communication terminal and resource terminal>
3 is a diagram showing an example of the hardware configuration of the communication terminal and the resource terminal according to the embodiment. The communication terminal 4 and the resource terminal 5 are realized by, for example, a computer system having the hardware configuration shown in FIG.

The communication terminal 4 shown in FIG. 3 is constructed by a computer. The communication terminal 4 includes, for example, a CPU 401, a ROM 402, a RAM 403, an EEPROM 404, a CMOS sensor 405, an image sensor I/F 406, an acceleration/direction sensor 407, a media I/F 409, and a GPS receiver 411.

Of these, the CPU 401 controls the overall operation of the communication terminal 4. The ROM 402 stores programs used to drive the CPU 401, such as the CPU 401 and the IPL. The RAM 403 is used as a work area for the CPU 401. The EEPROM 404 reads or writes various data, such as a user authentication application and an infected person registration application, under the control of the CPU 401. The CMOS (Complementary Metal Oxide Semiconductor) sensor 405 is a type of built-in imaging means that captures an image of a subject under the control of the CPU 401 to obtain image data or video data. The imaging means may be an imaging means such as a CCD (Charge Coupled Device) sensor instead of a CMOS sensor. The imaging element I/F 406 is a circuit that controls the driving of the CMOS sensor 405. The acceleration/direction sensor 407 is various sensors, such as an electronic magnetic compass or gyrocompass that detects geomagnetism, and an acceleration sensor. The media I/F 409 controls the reading and writing (storage) of data from and to a recording medium 408 such as a flash memory. The GPS receiver 411 receives GPS signals from GPS satellites.

Furthermore, the communication terminal 4 includes, for example, a long-distance communication circuit 412, an antenna 412a of the long-distance communication circuit 412, a CMOS sensor 413, an image sensor I/F 414, a microphone 415, a speaker 416, an audio input/output I/F 417, a display 418, an external device connection I/F (Interface) 419, a short-distance communication circuit 420, an antenna 420a of the short-distance communication circuit 420, and a touch panel 421.

Among these, the long-distance communication circuit 412 is a circuit that communicates with other devices via the communication network 100. The CMOS sensor 413 is a type of built-in imaging means that captures an image of a subject and obtains image data under the control of the CPU 401. The image sensor I/F 414 is a circuit that controls the drive of the CMOS sensor 413. The microphone 415 is a built-in circuit that converts sound into an electrical signal, and obtains information using the electrical signal by acquiring voice or sound waves emitted from an external speaker or the like. The speaker 416 is a built-in circuit that converts an electrical signal into physical vibrations to generate sounds such as music and voice. The sound input/output I/F 417 is a circuit that processes the input and output of sound signals between the microphone 415 and the speaker 416 under the control of the CPU 401. The display 418 is a type of display means such as a liquid crystal or organic EL (Electro Luminescence) that displays an image of a subject, various icons, etc. The external device connection I/F 419 is an interface for connecting various external devices. The short-range communication circuit 420 is a communication circuit for short-range wireless communication such as NFC (Near Field Communication) or Bluetooth (registered trademark). The touch panel 421 is a type of input means for operating the communication terminal 4 by the user pressing, clicking, tapping, or other operations on the display 418. Note that the imaging means such as the CMOS sensor 413, the short-range communication means such as the short-range communication circuit 420, the audio input means such as the microphone 415, and the like are information acquisition means for acquiring resource identification information, for example, by an image such as an image code, wireless communication, or sound waves, respectively.

The communication terminal 4 also includes a bus line 410. The bus line 410 is an address bus, a data bus, etc., for electrically connecting each component such as the CPU 401 shown in FIG. 3.

On the other hand, the resource terminal 5 is constructed by a computer. As shown in FIG. 3, the resource terminal 5 includes, for example, a CPU 501, a ROM 502, a RAM 503, an EEPROM 504, a CMOS sensor 505, an image sensor I/F 506, an acceleration/direction sensor 507, a media I/F 509, a bus line 510, and a GPS receiver 511.

Furthermore, the resource terminal 5 is equipped with, for example, a long-distance communication circuit 512, an antenna 512a of the long-distance communication circuit 512, a CMOS sensor 513, an image sensor I/F 514, a microphone 515, a speaker 516, an audio input/output I/F 517, a display 518, an external device connection I/F (Interface) 519, a short-distance communication circuit 520, an antenna 520a of the short-distance communication circuit 520, and a touch panel 521. These have the same configuration as the CPU 401, ROM 402, RAM 403, EEPROM 404, CMOS sensor 405, image sensor I/F 406, acceleration and direction sensor 407, media I/F 409, bus line 510, GPS receiver 411, long-distance communication circuit 412, antenna 412a of long-distance communication circuit 412, CMOS sensor 413, image sensor I/F 414, microphone 415, speaker 416, sound input/output I/F 417, display 418, external device connection I/F 419, short-distance communication circuit 420, antenna 420a of short-distance communication circuit 420, and touch panel 421 in communication terminal 4, and therefore will not be described.

The above programs may be distributed by recording them on a computer-readable recording medium in the form of an installable or executable file. Examples of recording media include CD-Rs (Compact Disc Recordable), DVDs (Digital Versatile Discs), Blu-ray (registered trademark) Discs, SD cards, and USB memories. The recording media may be provided domestically or internationally as a program product.

The above programs may also be configured to be stored on a computer connected to a network such as the Internet and provided by downloading them via the network. The above programs may also be configured to be provided or distributed via a network such as the Internet.

For example, the resource management device 2 and the communication terminal 4 realize the resource management method according to the present invention by executing the program according to the present invention.

[Functional configuration of the resource management system]
Next, a functional configuration of the present embodiment will be described below. Fig. 4 is a diagram showing an example of the functional configuration of the resource management system according to the embodiment.

<Functional configuration of the resource management device>
As shown in Fig. 4, the resource management device 2 has a transmission/reception unit 21, an acquisition unit 22, a clock unit 23, an identification unit 25, an authentication unit 26, a registration unit 28, and a storage/readout processing unit 29. Each of these functional units is a function or means realized by any of the components shown in Fig. 2 operating in response to an instruction from the CPU 201 in accordance with a program for the resource management device 2 expanded from at least one of the ROM 202 and the HD 204 to the RAM 203. The resource management device 2 also has a storage unit 2000 constructed in the ROM 202 or the HD 204 shown in Fig. 2. The storage unit 2000 has a login management table 2001, an infected person management table 2002, a resource status management table 2003, a communication information management table 2004, and a user information management table 2005.

The transmitting/receiving unit 21, the acquiring unit 22, the clock unit 23, the identifying unit 25, the authenticating unit 26, the registering unit 28, and the storing/reading processing unit 29 shown in FIG. 4 are realized by a program for the resource management device 2. However, all or part of these may be realized by hardware such as an integrated circuit (IC).

●Login management table●
Fig. 5(A) is a conceptual diagram showing an example of a login management table according to an embodiment. A login management table 2001 as shown in Fig. 5(A) is constructed in the storage unit 2000. In this login management table 2001, user identification information, a password, and a user name are associated with each customer ID and stored and managed. Of these, the customer ID is identification information associated with a customer such as a company.

The user identification information stores and manages the email address, etc., of each user managed by customer ID. For example, when a user successfully authenticates the resource management device 2, the resource management device 2 considers the input user account to be correct. This user identification information indicates the same as the identification information of the person who reserved the resource or the participant of various events held on the resource. Therefore, the resource management device 2 can use the input user identification information to identify reservation information in which the user who input the user identification information is the reservation or the participant.

The login password is identification information associated with the user identification information at the time of logging in when using the resource management system 1, and is set by the user at the time of initial startup (login), etc.

The user name represents the name of each user to whom user identification information is given. This user name may be written in kanji, hiragana, katakana, roman letters, numbers, or a combination of these.

●Infected Person Management Table●
Fig. 5(B) is a conceptual diagram showing an example of an infected person management table according to the third embodiment. An infected person management table 2002 as shown in Fig. 5(B) is constructed in the storage unit 2000. In this infected person management table 2002, user identification information, user name, whether or not the user is infected, and the date and time when the infection was discovered are associated with each customer ID and stored and managed.

Among these, the infection status is managed as infection status information that manages whether or not a person has been infected with or tested positive for an infectious disease (Class 1 to 5 infectious diseases, new influenza and other infectious diseases, designated infectious diseases, new infectious diseases, etc.) as classified by the Ministry of Health, Labor and Welfare, and includes items such as "positive," "under testing," and "negative."

The date and time when infection was discovered is managed as information on the date and time when infection with the specific infectious disease described above or a positive test result was discovered.

●Resource status management table●
Fig. 6 is a conceptual diagram showing an example of a resource status management table according to an embodiment. A resource status management table 2003 as a resource information storage unit as shown in Fig. 6 is constructed in the storage unit 2000. In this resource status management table 2003, for each reservation identification information for identifying a reservation person, reservation user identification information, resource ID, resource name, start date and time, end date and time, expected participant identification information, user identification information, and resource usage status are associated with each other and stored and managed as resource usage information.

Of these, the reservation identification information is identification information for identifying one record of reservation information. The same applies to identification information other than the reservation identification information below. The reservation identification information is information for checking in to a resource such as a conference room where a specific event will be held, and is a uniquely assigned letter, a multi-digit number, or a combination of these. Checking in means starting to use a resource. The reservation identification information is also called a reservation ID (Identification). An ID is a name, code, character string, number, or a combination of one or more of these that is used to uniquely distinguish a specific object from multiple objects.

The reservation identification information is given, for example, as the account (e.g., email address) of the reservation person who reserved each resource in the floor space within the resource management system 1, and is stored and managed as Taro.r@xxxxx, etc.

The resource ID is identification information for identifying each resource (such as a conference room) in the company network. The resource name is the name of the resource associated with the resource ID, and is assigned names such as "Conference Room A," "Conference Room B," and "Reception Room 1."

The start date and time is the date and time when a specific event (such as a meeting, entertainment, lecture, or special event) to be performed using the reserved resource will start. The end date and time is the date and time when the specific event to be performed using the reserved resource will end. The start date and time and end date and time are updated and managed as the start date and time and end date and time when the resource was actually used. In other words, the start date and time and end date and time managed in the reservation information management table 3001 described below are updated in accordance with the check-in process, check-out process, etc. of the user who uses the reserved resource.

The participant identification information is the identification information of the participants who plan to attend the conference, and is indicated by, for example, the email address of each participant.

The user identification information is the identification information of a user who participates in an event held at a specified resource, and among the participant identification information, the email addresses, etc. of users who actually participated in the event held at the specified resource described above are stored and managed. Note that the reservation identification information, participant identification information, and user identification information in Figure 6 are all identification information issued by the reservation management device 3.

The user identification information is added to the resource status management table 2003 by the report creation process described below, using the communication information management table 2004 in FIG. 7(A) and the resource status management table 2003 in FIG. 6.

The resource usage status indicates the current state of the target resource. If the resource is a space such as a conference room, the resource usage status may be, for example, "In use," "In use (checked in)," "Waiting to enter," "Reserved," etc. The resource usage status may be associated with the reservation status of the resource. For example, the status of each resource reservation such as notified, confirmed use, waiting for check-in, checked in, checked out, or canceled (cancelled) may be registered. These usage statuses may be changed in association with the relationship between the current time and the start date and time, and the end date and time, as well as with a specific operation by the user (check-in process, check-out process, etc.).

●Communication information management table●
FIG. 7A is a conceptual diagram showing an example of a communication information management table according to an embodiment. In the storage unit 2000, a communication information management table 2004 as shown in FIG. 7A is constructed as a communication information storage unit. In this communication information management table 2004, user identification information, communication start date and time, communication end date and time, communication time, and communication distance are associated with each terminal ID for identifying the communication terminal 4 and stored and managed as communication information. In addition, this communication information management table 2004 is created by performing wireless communication such as Bluetooth using an application installed in the communication terminal 4. The communication terminal 4 may periodically transmit information to the resource management device 2. In addition, the communication terminal 4 may start wireless communication in response to a check-in process described later, and end wireless communication in response to a check-out process, and transmit information on the communication performed during that time to the resource management device 2. In addition, the communication terminal 4 may become a parent terminal of a resource reserver, communicate with another communication terminal 4, and transmit the collected communication information to the resource management device 2. Here, an example of a communication information management table 2004 created by communications carried out between a communication terminal 4 of a user identified by Taro.r@xxxxx and another communication terminal 4 is shown.

Of these, the terminal ID is identification information used to identify the communication terminal 4 owned by the user identified by the user identification information.

The user identification information is the same as the user identification information described above in Figure 6, so a detailed explanation will be omitted.

The communication start date and time is information indicating the date and time when communication was started between the communication terminal 4 and another communication terminal 4. For example, the communication start date and time indicates information such as 2020/9/10 14:00, which is the date and time when communication was started between the communication terminal 4 of a user identified by Taro.r@xxxxx and the communication terminal 4 of a user identified by Hanako.r@xxxxx.

The communication end date and time is information indicating the date and time when communication between the communication terminal 4 and another communication terminal 4 ended. For example, the communication end date and time indicates information such as 2020/9/10 15:00, which is the date and time when communication between the communication terminal 4 of a user identified by Taro.r@xxxxx and the communication terminal 4 of a user identified by Hanako.r@xxxxx ended.

The communication time is information indicating the time of communication between the communication terminal 4 and another communication terminal 4. For example, the communication time indicates information that the communication between the communication terminal 4 of the user identified by Taro.r@xxxxx and the communication terminal 4 of the user identified by Hanako.r@xxxxx was within 60 minutes. Here, the communication time may be generated by taking the difference between the communication start date and time and the communication end date and time.

The communication distance is information indicating the distance of communication between the communication terminal 4 and another communication terminal 4. The communication distance is derived, for example, from the communication strength. For example, the communication time indicates information that the distance during which communication was performed between the communication terminal 4 of the user identified by Taro.r@xxxxx and the communication terminal 4 of the user identified by Hanako.r@xxxxx was within 1 meter. Here, the communication distance may be calculated using information on wireless communication, such as Bluetooth communication, performed between the communication terminal 4 and another communication terminal 4.

●User information management table●
Fig. 7B is a conceptual diagram showing an example of a user information management table according to the embodiment. A user information management table 2005 as shown in Fig. 7B is constructed in the storage unit 2000. In this user information management table 2005, a resource ID, a resource name, user identification information, a conference start date and time, a conference end date and time, a communication time, and a communication distance are associated with each of the above-mentioned reservation identification information, and are stored and managed. In addition, this user information management table 2005 is created by a report creation process described later using the communication information management table 2004 in Fig. 7A and the resource status management table 2003 in Fig. 6. Here, an example of the user information management table 2005 of a user identified by Taro.r@xxxxx is shown.

Of these, the reservation identification information, resource ID, resource name, user identification information, conference start date and time, and conference end date and time are the same as those described above in Figure 6, so their explanation will be omitted.

The communication time and distance are the same as those described above in Figure 7 (A), so the explanation is omitted.

<<Functional configuration of the resource management device>>
Next, a detailed description will be given of each functional configuration of the resource management device 2. The transmission/reception unit 21 of the resource management device 2 shown in Fig. 4 is mainly realized by the processing of the CPU 201 for the external device connection I/F 207 and the network I/F 209 shown in Fig. 2, and transmits/receives various data or information to/from other devices or terminals (for example, the reservation management device 3, the communication terminal 4, and the resource terminal 5) via the communication network 100.

The transmitter/receiver 21 of the resource management device 2 functions, for example, as a notification unit that notifies a user of a specific communication terminal 4 of specific information (for example, that the user has been in contact with a user who has developed an infectious disease).

The transmitter/receiver unit 21 of the resource management device 2 also functions as a reception unit that receives, for example, a usage start request from the communication terminal 4 to start using the resource.

The acquisition unit 22 is mainly realized by the processing of the CPU 201 shown in FIG. 2, and acquires authentication information (user identification information and password, administrator ID and password) sent from the communication terminal 4, and registers it in the login management table 2001. Furthermore, the acquisition unit 22 acquires reservation information related to a specific resource from the reservation management device 3, and registers it in the resource status management table 2003.

The clock unit 23 is mainly realized by the processing of the CPU 201 shown in FIG. 2, and manages the time information within the resource management device 2.

The identification unit 25 is mainly realized by the processing of the CPU 201 shown in FIG. 2, and uses the communication information management table 2004 and the reservation information management table to identify conferences attended by a user, identify users managed in the user information management table, and identify close contacts. It also performs various judgment, determination, and search processes.

The authentication unit 26 is mainly realized by the processing of the CPU 501 shown in FIG. 2, and performs user authentication processing based on the user identification information and login password transmitted from the communication terminal 4.

The registration unit 28 uses the communication information management table 2004 and the reservation information management table to register the user information management table 2005, and registers the user identification information of users who are actually using (or have used) conference room A in the resource status management table 2003.

The storage/readout processing unit 29 is realized mainly by the processing of the CPU 201 shown in FIG. 2, and stores various data (or information) in the storage unit 2000 and reads various data (or information) from the storage unit 2000.

<Functional configuration of reservation management device>
4, the reservation management device 3 has a transmission/reception unit 31, a judgment unit 35, an authentication unit 36, a reservation information management unit 37, and a storage/readout processing unit 39. Each of these units is a function or means realized when any of the components shown in FIG. 2 operates in response to an instruction from the CPU 301 in accordance with a program for the reservation management device 3 that is loaded onto the RAM 303 from at least one of the ROM 302 and the HD 304.

The reservation management device 3 also has a memory unit 3000 constructed in the ROM 302 or HD 304 shown in FIG. 2. The memory unit 3000 has a reservation information management table 3001.

●Reservation information management table●
FIG. 8 is a conceptual diagram showing an example of a reservation information management table according to an embodiment. A reservation information management table as shown in FIG. 8 is constructed in the storage unit 3000. In this reservation information management table, reservation user identification information, resource ID, resource name, start date and time, end date and time, and expected participant identification information are stored and managed in association with each reservation identification information. Each of the above-mentioned items is the same as each of the items described in the resource status management table 2003 shown in FIG. 6, so description thereof will be omitted. However, the start date and time and the end date and time may be managed as the scheduled start date and time and the scheduled end date and time, respectively, and may be managed separately from the start date and the end date and time when actually used. Furthermore, as described in the above-mentioned resource status management table 2003, they may be updated in association with a predetermined process by the user.

<<Functional configuration of the reservation management device>>
Next, a detailed description will be given of each functional configuration of the reservation management device 3. The transmission/reception unit 31 of the reservation management device 3 shown in Fig. 4 is mainly realized by the processing of the CPU 301 for the external device connection I/F 307 and the network I/F 309 shown in Fig. 2, and transmits and receives various data (or information) to and from the resource management device 2 via the communication network 110 constructed outside the firewall 105. The transmission/reception unit 31 also receives a login authentication request and reservation settings when a free address is used in the resource terminal 5.

The judgment unit 35 is mainly realized by the processing of the CPU 301 shown in FIG. 3, and performs various judgments in the reservation management device 3.

The authentication unit 36 is mainly realized by the processing of the CPU 301 shown in FIG. 3, and authenticates the user based on the authentication information (e.g., user identification information and password) stored in the storage unit 3000. Authentication may also be performed using an IC card or biometric authentication information.

The reservation information management unit 37 is mainly realized by the processing of the CPU 301 shown in FIG. 3, and manages the reservation information registered by the user. The reservation information management unit 37 reads various reservation information from the reservation information management table 3001 via the storage/read processing unit 39 described later, and transmits it to the resource management device 2 via the transmission/reception unit 31.

The storage/readout processing unit 39 is realized mainly by the processing of the CPU 301 shown in FIG. 3, and stores various data (or information) in the storage unit 3000 and reads various data (or information) from the storage unit 3000.

<Functional configuration of communication terminal and PC>
As shown in Fig. 4, the communication terminal 4 has a transmission/reception unit 41, a reception unit 42, a clock unit 43, a display control unit 44, a photographing/acquiring unit 46, an application launch unit 47, a registration unit 48, and a storage/readout processing unit 49. Each of these functional units is a function or means realized by operating any of the components shown in Fig. 3 by an instruction from the CPU 401 according to a program for the communication terminal 4 that is loaded from at least one of the ROM 402 and the EEPROM 404 to the RAM 403. The communication terminal 4 also has a storage unit 4000 constructed in the ROM 402 or the EEPROM 404 shown in Fig. 3.

<<Functional configuration of communication terminal>>
Next, each functional configuration of the communication terminal 4 will be described in detail. The transmission/reception unit 41 of the communication terminal 4 and the PC 6 shown in Fig. 4 is mainly realized by the processing of the CPU 401 on the long-distance communication circuit 412 and the external device connection I/F 419 shown in Fig. 3, and transmits and receives various data (or information) with the resource terminal 5 via the communication network 100 constructed inside the firewall 105. Furthermore, the transmission/reception unit 41 transmits and receives various data (or information) with the resource management device 2 via the communication network 110 constructed outside the firewall 105.

The reception unit 42 is mainly realized by the processing of the CPU 401 on the touch panel 421 shown in FIG. 3, and receives input from the user during authentication processing when starting to use a resource, check-in processing of a user who uses a resource, etc.

The clock unit 43 is mainly realized by the processing of the CPU 401 shown in FIG. 3, and manages the time information within the communication terminal 4.

The display control unit 44 is mainly realized by the processing of the CPU 401 on the display 418 shown in FIG. 3, and causes the display 418 to display a user authentication screen, a QR code capture screen, an infected person (positive person) registration screen, etc.

The photographing and acquiring unit 46 is mainly realized by the processing of the CPU 401 on the CMOS sensor 413 and the image sensor I/F 414 shown in FIG. 3, and photographs a subject (a one-dimensional code such as a barcode or a two-dimensional code such as a QR code) displayed on the display 518 of the resource terminal 5, and acquires the specified code information embedded in the code.

The application launch unit 47 is mainly realized by the processing of the CPU 401 shown in FIG. 3, and launches a user authentication application for performing user authentication and code photography when using a specific resource, an infected person registration application for registering an infected person when infected with a specific infectious disease, and the like, which are installed in the EEPROM 404 of the communication terminal 4.

The registration unit 48 is mainly realized by the processing of the CPU 401 shown in FIG. 3, and acquires and registers code information from the subject (a one-dimensional code such as a barcode or a two-dimensional code such as a QR code) captured by the imaging/acquisition unit 46. Furthermore, it registers the user identification information, password, etc., as authentication information transmitted by the resource management device, in the storage means.

The storage/read processing unit 49 is realized mainly by the processing of the CPU 401 shown in FIG. 3, and stores various data (or information) in the EEPROM 404 and reads various data (or information) from the EEPROM 404.

<Functional configuration of resource terminal>
4, the resource terminal 5 has a transmission/reception unit 51, a reception unit 52, a generation unit 53, a display control unit 54, a terminal authentication unit 56, and a storage/readout processing unit 59. Each of these units is a function or means realized by any of the components shown in FIG. 3 operating in response to an instruction from the CPU 501 in accordance with a program for the resource terminal 5 loaded onto the RAM 503 from at least one of the ROM 502 and the EEPROM 504.

The resource terminal 5 also has a memory unit 5000 constructed using the ROM 502 or EEPROM 504 shown in FIG. 3.

<<Functional configuration of resource terminal>>
Next, a detailed description will be given of each functional configuration of the resource terminal 5. The transmitting/receiving unit 51 of the resource terminal 5 shown in Fig. 4 is mainly realized by the processing of the CPU 501 for the long-distance communication circuit 512 and the external device connection I/F 519 shown in Fig. 3, and transmits and receives various data (or information) to and from the reservation management device 3 and the resource management device 2 via the communication network 100.

The reception unit 52 is realized mainly by the processing of the CPU 501 and the processing of the touch panel 521 shown in FIG. 3, and receives various selections or inputs from the user. In addition to the touch panel 521, operation buttons or the like may be used as other input means.

The generation unit 53 is mainly realized by the processing of the CPU 501 and the display 518 shown in FIG. 3, and generates a code including the reservation identification information transmitted by the resource management device 2. The code generated at this time is, for example, a one-dimensional code or a two-dimensional code, and specifically, various codes such as a barcode and a QR code are generated. Furthermore, the two-dimensional code may be a color code. The data represented by these codes is data encrypted by a public key encryption method or a private key encryption method. Note that the methods of generating the various codes described above are publicly known, so detailed explanations will be omitted here.

The display control unit 54 is mainly realized by the processing of the CPU 501 and the display 518 shown in FIG. 3, and performs control for displaying various images, characters, specific codes (QR codes), etc. on the display 518. In this embodiment, an entry screen, QR code, and other images at the time of checking in a specific resource are displayed on the display 518.

The terminal authentication unit 56 is mainly realized by the processing of the CPU 501 shown in FIG. 3, and authenticates login to the terminal app based on, for example, whether the entered password is correct.

The storage/read processing unit 59 is mainly realized by the processing of the CPU 501 shown in FIG. 3, and stores various data (or information) in the storage unit 5000 and reads various data (or information) from the storage unit 5000.

[Processing or Operation of the Embodiment]
Next, the processing or operation of the resource management system 1 according to the embodiment will be described.

<Authentication process>
First, the authentication process in the communication terminal 4 will be described with reference to Fig. 9. Fig. 9 is a sequence diagram showing an example of the authentication process according to the embodiment. First, the storage/read processing unit 29 of the resource management device 2 reads reservation identification information (R001, R002, ...) from the resource status management table 2003 (step S11).

Next, the transmitting/receiving unit 21 of the resource management device 2 transmits a resource information acquisition request to the reservation management device 3 (step S12). As a result, the transmitting/receiving unit 31 of the reservation management device 3 receives the resource information acquisition request transmitted by the resource management device 2. At this time, the resource information acquisition request includes a resource ID corresponding to the reservation identification information.

Then, the storage/read processing unit 39 of the reservation management device 3 searches the reservation information management table 3001 using the resource ID received by the transmission/reception unit 31 as a search key to read the reservation information of the corresponding resource (step S13).

Then, the transmitting/receiving unit 31 transmits a resource information acquisition response to the resource management device 2 in response to the resource information acquisition request (step S14). As a result, the transmitting/receiving unit 21 of the resource management device 2 receives the resource information acquisition response transmitted by the transmitting/receiving unit 31 of the reservation management device 3. This resource information acquisition response includes, for example, reservation identification information, reservation user identification information, resource ID, resource name, start date and time, end date and time, and participant identification information, which are treated as reservation information.

The acquisition unit 22 of the resource management device 2 registers the reservation information received by the transmission/reception unit 21 in the resource status management table 2003 (step S15). As a result, the reservation information related to each acquired resource is registered and managed in the resource status management table 2003. Since resource information does not change frequently, the resource management device 2 and the reservation management device 3 may execute the above-mentioned processes from steps S12 to S15 as a loop process. Specifically, the acquisition unit 22 may acquire the information infrequently, such as once a day. The acquisition unit 22 may also acquire the reservation information from the reservation management device 3 periodically or when the reservation information is updated.

In the resource management system 1 according to this embodiment, when the processing of steps S12 and S14 described above is executed, other devices may be present between the resource management device 2 (resource management device) and the reservation management device 3 (reservation management device). In other words, each piece of information transmitted and received between the resource management device 2 and the reservation management device 3 may be configured to be transmitted and received once via another device. The above-described configuration and processing method may also be applied to other subsequent processing steps.

<<App startup process>>
Next, the reception unit 42 of the communication terminal 4 receives a request to start an application operated by a reserving person who has reserved a resource or a user who uses the resource (Step S21).

As a result, the application launch unit 47 of the communication terminal 4 launches, for example, a browser (dedicated application) (step S22).

When the dedicated app is launched, the display control unit 44 causes the display 418 to display an authentication screen (step S23). FIG. 10 is a diagram showing an example of the authentication screen according to the embodiment. In FIG. 10, the display control unit 44 displays an example of a user authentication screen 451 (e.g., a "user ID" input section, a "password" input section, and a "login" button) on the display 418 of the communication terminal 4.

In response to the processing of step S23, the person making the reservation or the user (hereinafter referred to as user A) performs an operation to log in to the resource management device 2. Specifically, user A inputs a user ID and a password, and operates (presses or taps) the login button 452 to perform the login process. As a result, the reception unit 42 accepts the input of authentication information (step S31). For example, user identification information and a password are used as the authentication information. Here, it is assumed that the authentication is successful.

After accepting the input of the authentication information in step S31, the transmission/reception unit 41 transmits an authentication processing request to the resource management device 2 (step S32). As a result, the transmission/reception unit 21 of the resource management device 2 receives the authentication processing request transmitted from the communication terminal 4. The authentication processing request includes the user identification information and the password.

Then, the storage/read processing unit 29 of the resource management device 2 searches the login management table 2001 using the received user identification information or login password as a search key to read the login information, thereby reading out the corresponding user identification information, login password, and user name (step S33). As a result, the authentication unit 26 performs the user authentication process.

If the user authentication is successful, the transmission/reception unit 21 transmits an authentication processing response including the user's user identification information to the communication terminal 4 (step S34). As a result, the transmission/reception unit 41 of the communication terminal 4 receives the authentication processing response including the user's user identification information transmitted by the resource management device 2.

The communication terminal 4 that receives the authentication processing response including the user's user identification information stores the user identification information and password included in the received authentication processing response in the memory unit 4000 (step S35).

In the resource management system 1 according to this embodiment, when the processes of steps S24 and S26 described above are executed, other devices may be present between the resource management device 2 (resource management device) and the communication terminal 4 (communication terminal). In other words, each piece of information transmitted and received between the resource management device 2 and the communication terminal 4 may be configured to be transmitted and received once via another device. The above-described configuration and processing method may also be applied to other subsequent processing steps.

<<Check-in process>>
Next, the check-in process of the resource by the user A will be described. FIG. 11 is a sequence diagram showing an example of the check-in process by the QR code according to the embodiment. The transmitting/receiving unit 51 of the resource terminal 5 of the resource (e.g., a conference room) used by the user A transmits a request to acquire resource information to the resource management device 2 (step S41). As a result, the transmitting/receiving unit 21 of the resource management device 2 receives the request to acquire resource information transmitted by the resource terminal 5. At this time, the request to acquire resource information includes the resource ID of the resource to be used. Here, regarding the timing of executing step S41, a push notification may be sent from the resource management device 2 to the resource terminal 5 in response to the response of the authentication process in the above-mentioned step S34. Furthermore, the resource terminal 5 may periodically transmit the request to acquire the resource information executed in step S41 to the resource management device 2.

The storage/read processing unit 29 of the resource management device 2 that receives the resource information acquisition request searches the resource status management table 2003 using the received resource ID as a search key to read out the corresponding reservation user identification information, resource name, start date and time, end date and time, and expected participant identification information (step S42).

Then, the transmitter/receiver unit 21 transmits the reservation identification information, resource name, start date/time, end date/time, and planned participant identification information read in step S42 to the resource terminal 5 (step S43). As a result, the transmitter/receiver unit 51 of the resource terminal 5 receives the reservation identification information, resource name, start date/time, end date/time, and planned participant identification information transmitted by the resource management device 2.

In the resource management system 1 according to this embodiment, when the processes of steps S42 and S43 described above are executed, other devices may be present between the resource management device 2 (resource management device) and the resource terminal 5 (resource terminal). In other words, each piece of information transmitted and received between the resource management device 2 and the resource terminal 5 may be configured to be transmitted and received once via another device. The above-described configuration and processing method may also be applied to other subsequent processing steps.

Next, the generation unit 53 of the resource terminal 5 generates a predetermined code (e.g., a QR code) related to the resource terminal 5 in which the received reservation user identification information is embedded (step S44). As described above, the methods of generating various codes such as barcodes and QR codes are publicly known, so detailed explanations are omitted here.

Then, the display control unit 54 displays a check-in possible screen 551 as shown in FIG. 12 (step S45). FIG. 12 is a diagram showing an example of a check-in possible screen on a resource terminal according to an embodiment. In FIG. 12, the display control unit 44 displays an example of the check-in possible screen 551 (for example, "Conference Room A", "Waiting to enter", "XX Meeting", "14:00>15:00", and "QR Code") on the display 518 of the resource terminal 5.

After confirming that the check-in possible screen 551 is displayed on the display 518 of the resource terminal 5, the user operates to start up the camera of the communication terminal 4 owned by the user. As a result, the CPU 401, which is the subject of processing of the photographing/acquisition unit 46 of the communication terminal 4, controls the CMOS 413 and the image sensor I/F 414 to start up the camera (step S46).

After starting the camera, user A approaches the check-in screen 551 and operates the QR code shooting button 454 to shoot the QR code displayed on the screen. As a result, the shooting/acquisition unit 46 borrows user A's operation to shoot the QR code and acquires the specified code information (e.g., reservation identification information) embedded in the QR code (step S47). In other words, the shooting/acquisition unit 46 acquires the code information embedded in the specified code by shooting a specified code (QR code) related to the specified reservation information displayed by the resource terminal 5 capable of communicating with the resource management device 2. At this time, the display control unit 44 displays a QR code shooting screen 453 as shown in FIG. 13 on the display 418 of the communication terminal 4. FIG. 13 is a diagram showing an example of the QR code shooting screen according to the embodiment.

After user A has photographed the QR code, the transmitter/receiver 41 transmits a check-in request to the resource management device 2 as a request to start using the reserved resource (step S48). As a result, the transmitter/receiver 21 of the resource management device 2 receives the check-in request transmitted from the communication terminal 4. At this time, the check-in request includes current time information indicating the current time.

The resource management device 2 that has received the check-in request performs check-in processing (step S49). Specifically, the storage/read processing unit 29 rewrites the usage status of the resource to be reserved that is managed in the resource status management table 2003 to "in use (checked in)". At this time, the storage/read processing unit 29 may change the start date and time to the date and time when the check-in processing was actually performed.

After executing the process of step S49, the transmitter/receiver 21 transmits a check-in response to the communication terminal 4 (step S50). As a result, the transmitter/receiver 41 of the communication terminal 4 receives the check-in response transmitted from the resource management device 2.

The check-in process is not limited to simply photographing a QR code, but can take a variety of forms, including touching an IC card, communicating via Bluetooth, or entering a code sent in advance.

In addition, in the resource management system 1 according to this embodiment, the user reserves resources in advance, and the resource information is registered in the resource status management table 2003, but the user does not need to reserve resources in advance.

In this case, the user can perform a check-in process (immediate use) to the resource by reading the QR code displayed on the resource terminal corresponding to the resource he/she wants to use. FIG. 14 shows an example of a check-in possible screen displayed on the resource terminal 5 when performing immediate use. The display control unit 54 displays a check-in possible screen 552 as shown in FIG. 14. In FIG. 14, the display control unit 44 displays an example of a check-in possible screen 551 (for example, "Conference room A", "Vacant", "No reservation", "14:00>15:00" and "QR code") on the display 518 of the resource terminal 5. The user reads the QR code displayed on the resource terminal 5 using the communication terminal 4. The QR code includes various information about the conference room to be used and a link destination to the resource management device 2, and is sent to the resource management device together with the authentication information of the user terminal 4. The resource management device uses the authentication information and various information about the conference room to update the information in the resource status management table 2003 held by the resource management device and the reservation information management table held by the reservation management device. The resource management device sends reservation information registered in the reservation management device to the resource terminal 5, and updates the status of the conference room terminal.

In the resource management system 1 according to this embodiment, when the above-mentioned processes of steps S48 and S50 and the processes of steps S62 and S65 are executed, other devices may be present between the resource management device 2 (resource management device) and the communication terminal 4 (communication terminal). In other words, each piece of information transmitted and received between the resource management device 2 and the communication terminal 4 may be configured to be transmitted and received once via another device. The above-mentioned configuration and processing method may also be applied to other subsequent processing steps.

<<Management Reporting Process>>
Next, the process of identifying users of the above-mentioned conference room A and the process of creating a management report for the identified users will be described using the communication information management table 2004 in FIG. 7 (A) and the resource status management table 2003 in FIG. 6.

FIG. 15 is a diagram showing an example of a management report creation process according to an embodiment. By creating a management report, the user identification information item in the resource status management table 2003 in FIG. 6 is registered, and the user information management table 2005 in FIG. 8 (B) is created.

First, the storage/read processing unit 29 reads the communication information management table 2004 of the user for whom the user information management table 2005 is to be created, and reads records from the resource status management table 2003 for which the user for whom the report is to be created is included in the participant identification information (step S201).

Then, the identification unit 25 judges whether the communication start date/time and communication end date/time in the read communication information management table 2004 and the conference start date/time and conference end date/time in the resource status management table 2003 are within a predetermined range, and whether the user identification information is included in the participant identification information corresponding to the identified reservation identification information (step S202). For example, whether the date/time is within the predetermined range is judged to be within the predetermined range if the difference between the communication start date/time and the conference start date/time is within a range of ±10 minutes. Furthermore, the criteria for whether the date/time is within the predetermined range may be set appropriately. Furthermore, the target reservation identification information is identified by this judgment.

Then, it is determined whether the user identification information in the communication information management table 2004 that is determined to be within the predetermined range is included in the participant identification information corresponding to the identified reservation identification information. This determination identifies the users who actually participated in the conference.

If the result of the determination in step S202 is No, the process returns to step S202, and the identification unit 25 performs a determination on the next record in the communication information management table 2004.

On the other hand, if the result of the determination in step S202 is Yes, the registration unit 28 registers the user identification information of the identified user in the user identification information field of the resource status management table 2003 (step S203).

Then, the identification unit 25 refers to the communication information management table 2004 and determines whether the communication time is within a predetermined range or more (step S204). For example, the identification unit 25 determines that the communication time is within the predetermined range or more if the communication time is 30 minutes or more. In addition, the criteria for determining whether the communication time is within the predetermined range or more may be set appropriately.

If the result of the determination in step S204 is No, the process returns to step S202, and the identification unit 25 performs a determination on the next record in the communication information management table 2004.

On the other hand, if the determination result in step S204 is Yes, the identification unit 25 refers to the communication information management table 2004 and determines whether the communication distance is within a predetermined range (step S205). For example, the communication distance is determined to be within the predetermined range if the communication distance is within 5 m. In addition, the criteria for whether the communication distance is within the predetermined range may be set appropriately.

If the result of the determination in step S205 is No, the process returns to step S202, and the identification unit 25 performs a determination on the next record in the communication information management table 2004.

On the other hand, if the determination result in step S205 is Yes, the registration unit 28 registers a record in the user information management table 2005 (step S206). As explained in FIG. 7B above, the reservation identification information, resource ID, resource name, user identification information, conference start date and time, conference end date and time, communication time, and communication distance are registered in the record.

Then, the identification unit 25 determines whether various determinations have been performed for all records in the communication information management table 2004 (step S207).

If the determination result in step S207 is No, the process returns to step S202, and the identification unit 25 performs a determination on the next record in the communication information management table 2004. If the determination result in step S207 is Yes, the identification unit 25 ends the management report creation process.

In the resource management system 1 according to this embodiment, the determination is performed in the order of steps S202, S204, and S205 described above, but the order of the determination is not limited to this.

In addition, the read process of the communication information management table 2004 and the resource status management table 2003 may include settings such as the period and range to be read.

<<Infected Person Registration Processing>>
Next, a process when a specific user among the users who used the conference room A is infected with a specific infectious disease will be described. FIG. 16 is a sequence diagram showing an example of an infected person registration process according to the embodiment. In FIG. 16, a user B (e.g., Taro Rikko, user identification information: Taro.r@xxxxx) who is an infected person (positive person) infected with a specific infectious disease performs an operation to start a specific application (infected person registration application) for infected person registration using his/her own communication terminal 4 (infected person terminal, hereinafter referred to as infected person terminal for convenience). As a result, the reception unit 42 of the infected person terminal receives the operation to start the specific application for infected person registration (step S71), and then, after the reception unit 42 receives the application start operation, the application start unit 47 starts the infected person registration application (step S72).

Next, user B performs the authentication process from steps S81 to S85 using his/her own infected terminal. The process from steps S81 to S85 is the same as steps S31 to S35 described above, so a description of the process is omitted.

After user B executes the authentication process, the registration unit 48 of the infected person terminal performs a process of registering the infected person (positive person) (step S91). In this embodiment, an infected person (positive person) will be referred to as an "infected person" for the sake of convenience. In other words, a positive person will also be exemplified as a de facto infected person. An infected person is registered by user B inputting the "date and time when the positive test was discovered" by scrolling or selecting, etc., on an infected person registration screen 457 as shown in FIG. 17, which has been launched by the application launch unit 47, and operating the registration button 458. FIG. 17 described above is a diagram showing an example of an infected person registration screen according to an embodiment.

After user B executes the infected person registration process, the transmitter/receiver 41 transmits an infected person registration request to the resource management device 2 (step S92). As a result, the transmitter/receiver 21 of the resource management device 2 receives the infected person registration request transmitted from the infected person terminal. At this time, the infected person registration request includes the user identification information of the infected user B and the date and time when the infection was discovered (e.g., 2020/09/12).

After receiving the request to register an infected person, the registration unit 28 of the resource management device 2 registers the user name corresponding to the user identification information, whether or not the user is infected (in this case, "positive"), and the date and time when the infection was discovered in the infected person management table 2002 (step S93).

<<Contact notification processing>>
Next, a search process of other users who have come into contact with an infected person by the resource management device 2 will be described. FIG. 18 is a sequence diagram showing an example of a process of notifying a contact person according to an embodiment. As shown in FIG. 18, the identification unit 25 of the resource management device 2 retrieves user identification information that has used the same resource as user B by searching the resource status management table 2003 using the user identification information of the infected user B: Taro.r@xxxxx as a search key. Next, the identification unit 25 further retrieves reservations of resources that have been used during a predetermined period prior to the date and time of infection (e.g., 2020/09/12) from among the retrieved user identification information. In this case, the identification unit 25 searches the resource status management table 2003 based on the information in the infected person management table 2002, and determines that the users indicated by the user identification information of Hanako.r@xxxxx and Jiro.r@xxxxx who participated in the conference held on 2020/09/10 14:00-15:00 in conference room A indicated by reservation identification information: R002, are an infected person, i.e., a contact of user B (step S101).

Then, the transmitting/receiving unit 21 transmits a contact confirmation email as a contact confirmation notification shown in FIG. 19 to the communication terminal 4 (contact terminal) owned by each user determined to be a contact (close contact) (step S102). As a result, the transmitting/receiving unit 41 of the communication terminal 4 receives the contact confirmation email transmitted by the resource management device 2.

Then, the display control unit 44 displays, for example, a contact confirmation screen as shown in FIG. 19 based on the infected person (positive case) information and close contact information contained in the received contact confirmation email (step S103). Here, FIG. 19 is a diagram showing an example of a contact confirmation screen according to an embodiment. At this time, the sent contact confirmation email contains infected person (positive case) information, close contact information, and event information of an event suspected to be close contact. Note that the infected person (positive case) information, close contact information, and event information contain the email addresses and names of the infected person (positive case) and close contact, and the details of the event held on the resource used (date and time, name of the meeting, etc.).

The transmission/reception unit 21 repeats the process of step S102 for the number of contacts. At this time, the transmission/reception unit 21 uses the email address indicated in the user identification information of each contact as the destination of the communication terminal 4 owned by each contact.

However, the resource management device 2 does not apply this embodiment to events held on the same date and time for remote participants who participated remotely in an event held on the same resource. This is because the remote participants did not use the same resources at the same date and time as the infected person. However, if the remote participants later use the same resources on the same date and time different from the infected person, a separate search according to this embodiment may be performed.

Note that the processes from step S11 to step S103 are merely examples, and the content, order, etc. of each process executed in the resource management system 1 are not limited in any way as long as they do not deviate from the gist of the present invention.

It is also possible to send emails not only to users who have come into contact with a positive case, but also to users who have come into contact with a close contact. In this case, the identification unit 25 can define a user who came into contact with a user who has come into contact with an infected person on a different date, time, and place as a "close contact" and search for users who fit this description.

Specifically, the identification unit 25 first determines that each user indicated by the user identification information of Hanako.r@xxxxx and Jiro.r@xxxxx described above has come into contact with an infected person with respect to user B (Rikotaro) indicated by the user identification information of Taro.r@xxxxx. Furthermore, the identification unit 25 may determine that other users who have come into contact with at least one of the users indicated by the user identification information of Hanako.r@xxxxx and Jiro.r@xxxxx during a predetermined period (e.g., about one week before and after) before and after the date and time of infection discovery (e.g., 2020/09/12) are close contacts. In this way, when the identification unit 25 searches the resource status management table 2003 and finds a user determined to be a close contact, the transmission/reception unit 21 transmits a contact confirmation notification as shown in FIG. 20 to the communication terminal 4 owned by each user determined to be a close contact. Note that the above-mentioned predetermined period may be changed as appropriate depending on the characteristics of the infectious disease (e.g., the survival period of a virus, etc.).

In addition, a "close contact" may be a user who participated in the same conference and whose communication time was more than a certain amount and whose communication distance was less than a certain amount. In this case, the identification unit 25 refers to the user information management table 2005 and identifies a user corresponding to the user identification information who had a communication time of more than a certain amount and whose communication distance was less than a certain amount with the user identified by the user identification information of Taro.r@xxxxx as a close contact.

In addition, a close contact management table may be created to manage the close contacts identified by the identification unit 25, and the transmission/reception unit 21 may transmit a contact confirmation notification to the communication terminal 4 owned by each user who has been determined to be a close contact based on the created close contact management table.

[Main Effects of the Embodiments]
As described above, according to the first embodiment, the communication information management table 2004 storing communication information between users and the resource status management table 2003 storing the resource status are used to identify users who have actually used a resource, and to create a user information management table 2005 in which communication information between the identified user and other users is registered. This enables the resource management device 2 to centrally manage users who have used a resource in accordance with the resource usage. This makes it easier to manage users when using a resource. As a result, one of the further effects is that users can also concentrate on events such as meetings held on that resource.

In addition to making it easier to manage users when using resources, if a user uses a resource that was previously used by a person infected with a specific infectious disease (who has tested positive), a warning will be received, enabling appropriate measures to be taken afterwards.

Second Embodiment
Next, a second embodiment will be described. The second embodiment differs from the first embodiment in that a warning is received when a resource used by an infected person (who has tested positive) for a specific infectious disease is used within a predetermined period of time. In the following description of the second embodiment, the description of the same parts as in the first embodiment will be omitted, and only the differences from the first embodiment will be described.

Figure 21 is a sequence diagram showing an example of the contact determination process and contact notification process according to the second embodiment. In the second embodiment, the system configuration, hardware configuration, and each functional configuration for the application launch using a user's operation, the check-in process to a reserved resource, and the infected person registration process are the same as those for the process up to step S93 in the previously described embodiment.

In the second embodiment, the identification unit 25 executes the close contact determination process based on the flowchart shown in FIG. 22 (step S111).

Figure 22 is a flowchart showing an example of a contact determination process according to the second embodiment. First, after the infected person registration process performed in step S93 shown in Figure 16, the storage/read processing unit 29 reads the resource status management table 2003 using the user identification information of the infected person as a search key (step S121).

Then, the identification unit 25 judges whether or not the user who has the read user identification information has used the same resource as the resource used by the infected person (step S122). At this time, if the user who has the read user identification information has not used the same resource as the resource used by the infected person (step S122; No), the process ends.

On the other hand, if the same resource as that used by the infected person is used (step S122; Yes), the identification unit 25 further judges whether the date and time of use is within a predetermined time (predetermined period) of the date and time of use by the infected person (step S123). At this time, if it is outside the predetermined time (predetermined period) of the date and time of use (step S123; No), the identification unit 25 determines that there is no problem with the user having that user identification information, and terminates the process.

If it is within a specified time (specified period) from the date and time of use (step S123; Yes), the identification unit 25 determines that the user having the corresponding user identification information is an infected person, i.e., a notification target to issue a warning to user B, and terminates the process (step S124).

Returning to the sequence diagram of FIG. 20, the transmitter/receiver 21 then transmits the warning notification (email, etc.) shown in FIG. 23 to the communication terminal 4 owned by each user determined to be a notification target (step S112). As a result, the transmitter/receiver 41 of the communication terminal 4 receives the warning email transmitted by the resource management device 2. At this time, the transmitted warning email contains user information of the user who used the same resource as the infected person (positive person), such as the email address, name, and details of the event held on the resource (date and time, name of the meeting, etc.) of the user who used the resource used by the infected person (positive person).

Then, the display control unit 44 displays, for example, the warning screen shown in FIG. 23 based on the user information included in the received warning email (step S113). FIG. 23 is a diagram showing an example of a warning screen according to the second embodiment. By the resource management device 2 performing the above-mentioned process on the communication terminal 4, it becomes possible to quickly warn users who have used resources used by an infected person within a specified time (specified period). This is because even if one does not come into direct or close contact with an infected person, the risk of infection with a specific infectious disease still remains by indirectly using resources used by an infected person.

[Major Effects of the Second Embodiment]
As described above, according to the second embodiment, the identifying unit 25 of the resource management device 2 reads the resource status management table 2003 using the user identification information of the infected person as a search key, and if the read user identification information is the same as the resource used by the infected person and is within a predetermined time (predetermined period) of the date and time of use by the infected person, the transmitting/receiving unit 21 transmits a notice (email, etc.) of a warning shown in FIG. 22 to the communication terminal 4 owned by the corresponding user. This allows the resource management device 2 to centrally manage users who have used a resource in accordance with the use of the resource. Therefore, in addition to making it easier to manage users in the use of resources, if a resource used by an infected person infected with a specific infectious disease (tested positive) is used within a predetermined period, a warning can be received, making it possible to take appropriate measures thereafter.

Third Embodiment
Next, a third embodiment will be described. The third embodiment is different from the first and second embodiments in that a contact search process can be executed. In the following description of the third embodiment, the description of the same parts as the first and second embodiments will be omitted, and the differences from the first and second embodiments will be described.

Figure 24 is a flowchart showing an example of a contact search process according to the third embodiment.

First, the user uses the communication terminal 4 or PC 6 to input the user identification information of the person for whom the contact search is to be performed in the email address input field 600, and sends a request for search processing to the resource management device 2. FIG. 25 (A) is a diagram showing an example of a contact search screen according to the third embodiment. The user inputs the user for whom he or she wishes to search for a contact from this screen (step S210). At this time, it may be possible to set a search period so as to set the scope of the search, and to set the conference room for which the search is to be performed.

Then, the identification unit 25 of the resource management device 2 determines whether a record corresponding to the user identification information being searched for exists in the user information management table 2005 (step S211).

If the result of the determination in step S211 is No, a search result that has no usage history of the resource is created (step S212).

On the other hand, if the determination result in step S211 is Yes, the search result shown in FIG. 25(B) is created based on the user information management table 2005 (step S213). FIG. 25(B) is a diagram showing an example of a contact search result screen according to the third embodiment. FIG. 25(B) includes information on the conference room used and communication information with participants in the conference used.

Finally, the resource management device 2 transmits the search results to the communication terminal 4 or PC 6 of the user who performed the search, and the display control unit 44 of the communication terminal 4 or PC 6 displays the search results (step S214). As shown in FIG. 25(B), the search results are displayed for each reservation identification information, and the search results for other reservation identification information may be displayed by switching pages.

Note that the search results shown in FIG. 25(B) are just an example, and various other information managed in the memory unit of the resource management device may also be displayed.

[Major Effects of the Third Embodiment]
As described above, according to the third embodiment, the specification unit 25 of the resource management device 2 reads the user information management table 2005 using the user identification information of the search target as a search key, creates a search result indicating communication information with other users for each reservation identification information based on the read information, and transmits the search result to the communication terminal 4 or the PC 6. This makes it possible to centrally manage users who have used resources without notification. This makes it easier to manage users who use resources.

[Other application examples]
The above describes the best mode for carrying out the present invention, but the present invention is not limited to these embodiments, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention.

The resource management system 1 shown in this embodiment can also be called a Web service. Web services are various services provided by applying Internet-related technologies. For example, Web services include a conference room rental service and various rental services. A system that uses a Web service is called a user system.

The resource management system 1 shown in this embodiment can also be divided into more processing units depending on the processing content. It can also be divided so that one processing unit includes more processes.

Furthermore, each function of each of the above-mentioned embodiments can be realized by one or more processing circuits. Here, the term "processing circuit" in this specification includes a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, and devices such as an ASIC (Application Specific Integrated Circuit), DSP (Digital Signal Processor), FPGA (Field Programmable Gate Array), SOC (System on a Chip), GPU (Graphics Processing Unit), and conventional circuit modules designed to execute each of the functions described above.

Reference Signs List 1 Resource management system 2 Resource management device 3 Reservation management device 4 Communication terminal 5 Resource terminal 6 PC
21 Notification unit, reception unit 25 Identification unit 28 Registration unit 2003 Resource information storage unit 2004 Communication information storage unit

JP 2020-123072 A

Claims (11)

a communication information storage unit that stores communication information including information indicating a date and time when a plurality of communication terminals communicate with each other;
a resource information storage unit that stores usage information including information indicating a date and time when a resource that is a managed resource is used;
an identification unit that identifies a user of a second communication terminal who is using the same resource as a user of a first communication terminal when the user of the first communication terminal uses the resource based on the resource usage information and the communication information;
a registration unit that registers the communication information between the identified user of the second communication terminal and the user of the first communication terminal in association with the resource usage information;
having
the identification unit, when a difference between a date and time when the first communication terminal and the second communication terminal communicated and a date and time when the resource was used is within a predetermined range, and user identification information of the second communication terminal that communicated with the first communication terminal is included in the usage information of the resource used by the user of the first communication terminal , identifies the user of the second communication terminal as using the same resource as the user of the first communication terminal;
Resource management device. the communication information includes time information relating to a communication time during which the plurality of communication terminals communicated and distance information relating to a communication distance during which the plurality of communication terminals communicated;
the identification unit, when the user of the first communication terminal uses the resource, identifies a user of a second communication terminal who uses the same resource as the user of the first communication terminal, based on the resource usage information, the time information, and the distance information;
The resource management device according to claim 1 . the identification unit identifies the user of the second communication terminal as using the same resource as the user of the first communication terminal, if the communication time during which the first communication terminal and the second communication terminal communicated is equal to or greater than a predetermined value when the user of the first communication terminal used the resource, and the communication distance during which the first communication terminal and the second communication terminal communicated is equal to or less than a predetermined value when the user of the first communication terminal used the resource;
The resource management device according to claim 2 . The registration unit registers that a user of the communication terminal has developed a specific infectious disease,
the identification unit, when the communication time during which the first communication terminal and the second communication terminal communicated is equal to or greater than a predetermined value when the user of the first communication terminal used the resource, and the communication distance during which the first communication terminal and the second communication terminal communicated is equal to or less than a predetermined value when the user of the first communication terminal used the resource, identifies the user of the second communication terminal as a person who has come into contact with the user who has developed the infectious disease;
The resource management device according to claim 2 . and a notification unit that notifies the user of the second communication terminal identified as the person in contact that the user has come into contact with the user who has developed the infectious disease.
The resource management device according to claim 4. the usage information includes user identification information for identifying a user who uses the resource,
the identifying unit, when user identification information of the second communication terminal that has communicated with the first communication terminal is not included in the usage information of the resource used by the user of the first communication terminal, does not identify the user of the second communication terminal as using the same resource as the user of the first communication terminal;
A resource management device according to any one of the preceding claims. a reception unit that receives a usage start request for starting usage of the resource from the communication terminal,
the communication information storage unit stores the communication information between the communication terminal that has made the usage start request and another communication terminal;
A resource management device according to any one of the preceding claims. The request to start using the resource is made by reading a code symbol displayed on a resource terminal installed in the resource, or by short-distance wireless communication with the resource terminal.
The resource management device according to claim 7. A resource management system having a plurality of communication terminals and a resource management device that manages resources to be managed,
The communication terminal includes:
a transmitting unit configured to transmit communication information including information indicating a date and time of communication with another communication terminal to the resource management device;
The resource management device includes:
a communication information storage unit that stores communication information of the plurality of communication terminals transmitted from the communication terminal;
a resource information storage unit that stores usage information including information indicating a date and time when the resource was used;
an identification unit that identifies a user of a second communication terminal who is using the same resource as a user of a first communication terminal when the user of the first communication terminal uses the resource based on the resource usage information and the communication information;
a registration unit that registers the communication information between the identified user of the second communication terminal and the user of the first communication terminal in association with the resource usage information;
having
the identification unit, when a difference between a date and time when the first communication terminal and the second communication terminal communicated and a date and time when the resource was used is within a predetermined range, and user identification information of the second communication terminal that communicated with the first communication terminal is included in the usage information of the resource used by the user of the first communication terminal , identifies the user of the second communication terminal as using the same resource as the user of the first communication terminal;
Resource management system. On the computer,
a communication information storage step of storing communication information including information indicating a date and time when a plurality of communication terminals communicate with each other;
a resource information storage step of storing usage information including information indicating a date and time when a resource that is a managed resource is used;
a step of identifying a user of a second communication terminal who is using the same resource as a user of a first communication terminal when the user of the first communication terminal uses the resource based on the resource usage information and the communication information;
a registration step of registering the communication information between the identified user of the second communication terminal and the user of the first communication terminal in association with the resource usage information;
Run the command,
The identification step identifies the user of the second communication terminal as using the same resource as the user of the first communication terminal when a difference between a date and time when the first communication terminal and the second communication terminal communicated and a date and time when the resource was used is within a predetermined range, and user identification information of the second communication terminal that communicated with the first communication terminal is included in the usage information of the resource used by the user of the first communication terminal.
program. A resource management method using a resource management system having a plurality of communication terminals and a resource management device that manages resources to be managed, comprising the steps of:
a communication information storage step of storing communication information including information indicating a date and time when a plurality of communication terminals communicate with each other;
a resource information storage step of storing usage information including information indicating a date and time when a resource that is a managed resource is used;
a step of identifying a user of a second communication terminal who is using the same resource as a user of a first communication terminal when the user of the first communication terminal uses the resource based on the resource usage information and the communication information;
a registration step of registering the communication information between the identified user of the second communication terminal and the user of the first communication terminal in association with the resource usage information;
Including,
The identification step identifies the user of the second communication terminal as using the same resource as the user of the first communication terminal when a difference between a date and time when the first communication terminal and the second communication terminal communicated and a date and time when the resource was used is within a predetermined range, and user identification information of the second communication terminal that communicated with the first communication terminal is included in the usage information of the resource used by the user of the first communication terminal.
Resource management methods.

Images