Intermediation server, remote control system, intermediation method, and program

Abstract

To provide an intermediation server, a remote control system, an intermediation method and a program that prevent processing of a reservation party (user) from becoming complicated.SOLUTION: In a remote control system 1, where a PC 2, a smartphone 3, a reservation management server 5, an intermediation server 6, a drive control server 7, and a smart lock 9 are capable of communicating with each other via a communication network 100 such as the Internet, the intermediation server 6 mediates between the reservation management server 5, which manages resource reservation received from the PC 2 that registers reservation, and the drive control server 7, which remotely controls the smart lock 9 for unlocking the resource, and thereby provides authentication information required for unlocking the smart lock 9 to unlock a reserved resource or the like.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to an intermediation server, a remote control system, an intermediation method, and a program. [Background technology]

[0002] In recent years, a system has been provided that remotely unlocks (or locks) a smart lock by remotely controlling the smart lock from a smartphone via a server (see Prior Art Document 1). By using such a smart lock, it is possible to not only unlock (or lock) the door of a dedicated resource such as a private home or apartment, but also to unlock (or lock) the door of a shared resource such as a company conference room or a car-sharing vehicle. Summary of the Invention [Problem to be solved by the invention]

[0003] However, when a resource is shared, reservations for the resource may be registered and managed in advance in a reservation management service (system) or the like so that multiple users can use it efficiently, but the reservation management service does not necessarily remotely control smart locks, etc. Therefore, when using a reserved resource, if it is necessary to unlock or lock the lock using electronic information of a smart lock or the like related to the resource, the user must reserve the resource while separately obtaining authentication information such as a passcode required to unlock the lock related to the reserved resource from a system that remotely controls the smart lock, etc. This creates an issue in that the user's processing becomes complicated. [Means for solving the problem]

[0004] The invention of claim 1 is an intermediary server comprising a receiving means for receiving resource identification information for identifying a resource, which is sent by a reservation management server that manages resource reservations accepted from a registration terminal that registers the reservation, and a transmitting means for transmitting drive unit identification information for identifying the drive unit corresponding to the resource identification information to a drive control server that remotely controls a drive unit for unlocking a key related to the resource, wherein the receiving means receives authentication information required to unlock the key using the drive unit indicated by the drive unit identification information, which is sent by the drive control server, and the transmitting means transmits the authentication information so as to be received by the registration terminal. Effect of the Invention

[0005] As described above, according to the present invention, the intermediary server mediates between the reservation management server that manages the reservation of the resource accepted from the registration terminal that registers the reservation, and the drive control server that remotely controls the drive device for unlocking the resource, and can provide the registration terminal with authentication information required to unlock the drive device for unlocking the reserved resource. This has the effect of preventing the process for the person who makes the reservation (user) from becoming complicated. [Brief description of the drawings]

[0006] [Figure 1] 1 is a schematic diagram of a remote control system according to an embodiment of the present invention. [Diagram 2] This is a hardware configuration diagram of a PC, a reservation management server, an intermediary server, and a drive control server. [Diagram 3] FIG. 1 is a hardware configuration diagram of a smartphone. [Figure 4] FIG. 1 is a hardware configuration diagram of a smart lock. [Diagram 5] 2 is a functional block diagram of each device constituting the remote control system. FIG. [Figure 6] FIG. 4 is a conceptual diagram showing a reservation information management table. [Figure 7]1A is a conceptual diagram of a user information management table, FIG. 1B is a conceptual diagram of an event management table, and FIG. 1C is a conceptual diagram of a drive method management table. [Figure 8] FIG. 4 is a conceptual diagram of a drive unit management table. [Figure 9] FIG. 11 is a sequence diagram showing a reservation registration process. [Figure 10] FIG. 13 is a diagram showing an example of a schedule input screen. [Figure 11] FIG. 13 is a sequence diagram showing a process when a user is not a valid user. [Figure 12] 13 is a flowchart showing a process of determining the type of key performed by the intermediary server in the case of a valid user. [Figure 13] FIG. 13 is a sequence diagram showing a process for sending a message when the key type is an “electronic key.” [Figure 14] This is an example of the screen displayed on a PC when the key type is "electronic key." [Figure 15] FIG. 11 is a sequence diagram showing a process of sending a message when the type of key is a "physical key." [Figure 16] This is an example of the screen displayed on a PC when the key type is "physical key." [Figure 17] FIG. 13 is a sequence diagram showing a process of sending a message when the key type is "none." [Figure 18] This is an example of the screen displayed on a PC when the key type is "None." [Figure 19] FIG. 11 is a sequence diagram showing a remote unlocking process when the key type is an "electronic key." [Figure 20] FIG. 11 is a sequence diagram showing a remote unlocking process when the key type is an "electronic key." [Figure 21] FIG. 11 is a sequence diagram showing a remote unlocking process when the key type is an "electronic key." [Figure 22] 13 is an example of a smartphone screen when starting a meeting. [Figure 23] FIG. 11 is a sequence diagram showing a remote locking process when the key type is an "electronic key." [Figure 24]FIG. 11 is a sequence diagram showing a remote locking process when the key type is an "electronic key." DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] The present embodiment will be described in detail below with reference to the drawings.

[0008] [System Overview] First, an overview of the remote control system 1 will be described. Fig. 1 is a schematic diagram of the remote control system according to the present embodiment. Here, a case will be described in which a smartphone 3 remotely unlocks and locks a smart lock 9 installed on the outside of a door 8 of a resource such as a conference room A (on the outside side of the conference room A).

[0009] 1, the remote control system 1 is constructed by a PC 2, a smartphone 3, a reservation management server 5, an intermediary server 6, a drive control server 7, and a smart lock 9. These can communicate with each other via a communication network 100 such as the Internet. Note that the communication network 100 may include not only wired communication, but also wireless communication networks such as mobile communication systems (4G, 5G, 6G, etc.) and WiMAX (Worldwide Interoperability for Microwave Access).

[0010] Of these, PC 2, smartphone 3, and smart lock 9 belong to the same business (organization), such as a company. Conference rooms A, B, and C are installed in the building of this business. Conference room A is shown in FIG. 1. A sticker with a QR code printed on it is affixed to the outside of door 8 of conference room A (on the outside side of conference room A). Resource identification information (e.g., resource ID) and access destination information for identifying conference room A are embedded in this QR code.

[0011] The PC 2 is, for example, a notebook PC used by the user a, and is an example of a registration terminal for the user a to register his / her schedule and resource reservations in the reservation management server 5.

[0012] The smartphone 3 is an example of a (mobile) communication terminal carried by the user a.

[0013] The smart lock 9 is installed in the lock of the door 8 and has a mechanism for locking and unlocking the door. In addition, a QR code (registered trademark) 10 such as a barcode is displayed on the door 8. The QR code 10 is printed on a sticker to be affixed to the door 8. A resource ID for identifying a resource such as a conference room in which the door 8 is installed, and access destination information (such as a URL) for the intermediary server 6 are embedded in the QR code 10. The sticker showing the QR code 10 is attached to part of a resource such as the door 8, thereby linking the QR code to the resource. The smartphone 3 obtains information about the QR code using an installed QR code scanner application.

[0014] The smart lock 9 is an example of a drive device provided to the organization (business) to which the user a belongs by the business that operates the drive control server 7. In the case of a smart lock for a door, the smart lock 9 is attached to the thumb turn of the door 8, and the smart lock 9 remotely turns the thumb turn to lock or unlock the door.

[0015] Next, the reservation management server 5, the intermediary server 6, and the drive control server 7 are each managed by different businesses. The reservation management server 5 is, for example, a server such as Microsoft (registered trademark) 365. The intermediary server 6 is, for example, a server managed by a business that provides a service that combines a service including reservation management such as Microsoft (registered trademark) 365 with a remote unlocking (or locking) service for a smart lock 9. The drive control server 7 is a server managed by a business that sells smart locks 9 and provides a remote unlocking (or locking) service.

[0016] Since the reservation management server 5 and the drive control server 7 are managed by different businesses, in this embodiment, the intermediation server 6 mediates the processing between the reservation management server 5 and the drive control server 7.

[0017] 〔Hardware Configuration〕 Next, with reference to FIGS. 2 to 4, the hardware configuration of each device constituting the remote control system will be described.

[0018] <Hardware Configuration of PC and Each Server> FIG. 2 is a hardware configuration diagram of a PC, a reservation management server, an intermediary server, and a drive control server. The hardware configuration of PC2 is indicated by reference numerals in the 200s. Since the hardware configurations of the reservation management server 5, the intermediary server 6, and the drive control server 7 are the same as that of PC2, they are respectively assigned reference numerals in the 500s, 600s, and 700s, and the descriptions thereof are omitted.

[0019] PC2 is constructed by a computer and, as shown in FIG. 2, includes a CPU 201, a ROM 202, a RAM 203, an HD 204, an HDD (Hard Disk Drive) controller 205, a display 208, a network I / F 209, a data bus 210, a keyboard 211, a mouse 212, a media I / F 207, and a DVD-RW (Digital Versatile Disk Rewritable) drive 214.

[0020] Among these, the CPU 201 controls the overall operation of PC2. The ROM 202 stores programs used for driving 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 to / from the HD 204 according to the control of the CPU 201. The display 208 displays various information such as a cursor, a menu, a window, characters, or images. The network I / F 209 is an interface for data communication using the communication network 100. The bus line 210 is an address bus, a data bus, etc. for electrically connecting the components such as the CPU 201 shown in FIG. 2.

[0021] The keyboard 211 is a type of input means having a plurality of keys for inputting characters, numbers, various instructions, etc. The mouse 212 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, etc. The media I / F 207 controls reading and writing (storing) data from and to a recording medium 206 such as a flash memory. The DVD-RW drive 214 controls reading and writing of various data from and to a DVD-RW 213 as an example of a removable recording medium. Note that the medium is not limited to a DVD-RW, and may be a DVD-R, a Blu-ray Disc, etc.

[0022] <Hardware configuration of smartphone> 3 is a hardware configuration diagram of the smartphone 3. As shown in FIG. 3, the smartphone 3 includes a CPU 301, a ROM 302, a RAM 303, an EEPROM 304, a CMOS sensor 305, an image sensor I / F 306, an acceleration / direction sensor 307, a media I / F 309, and a GPS receiver 311.

[0023] Among these, the CPU 301 controls the operation of the entire smartphone 3. The ROM 302 stores programs used to drive the CPU 301, such as the CPU 301 and the IPL. The RAM 303 is used as a work area for the CPU 301. The EEPROM 304 reads or writes various data, such as smartphone programs, under the control of the CPU 301. The CMOS (Complementary Metal Oxide Semiconductor) sensor 305 is a type of built-in imaging means that captures an image of a subject (mainly a self-portrait) under the control of the CPU 301 to obtain image data. Note that the imaging means may be a CCD (Charge Coupled Device) sensor or other type instead of a CMOS sensor. The imaging element I / F 306 is a circuit that controls the driving of the CMOS sensor 305. The acceleration / direction sensor 307 is various sensors, such as an electronic magnetic compass or gyrocompass that detects geomagnetism, and an acceleration sensor. The media I / F 309 controls the reading or writing (storing) of data from or to a recording medium 308, such as a flash memory. The GPS receiver 311 receives GPS signals from GPS satellites.

[0024] The smartphone 3 also includes a long-distance communication circuit 312, an antenna 312a of the long-distance communication circuit 312, a CMOS sensor 313, an image sensor I / F 314, a microphone 315, a speaker 316, an audio input / output I / F 317, a display 318, an external device connection I / F (Interface) 319, a short-distance communication circuit 320, an antenna 320a of the short-distance communication circuit 320, and a touch panel 321.

[0025] Among these, the long-distance communication circuit 312 is a circuit that communicates with other devices via the communication network 100. The CMOS sensor 313 is a type of built-in imaging means that captures an image of a subject under the control of the CPU 301 to obtain image data. The imaging element I / F 314 is a circuit that controls the driving of the CMOS sensor 313. The microphone 315 is a built-in circuit that converts sound into an electric signal. The speaker 316 is a built-in circuit that converts an electric signal into physical vibration to generate sound such as music or voice. The sound input / output I / F 317 is a circuit that processes input and output of sound signals between the microphone 315 and the speaker 316 under the control of the CPU 301. The display 318 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 319 is an interface for connecting various external devices. The short-distance communication circuit 320 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The touch panel 321 is a type of input means that allows the user to operate the smartphone 3 by pressing the display 318.

[0026] The smartphone 3 also includes a bus line 310. The bus line 310 is an address bus, a data bus, or the like for electrically connecting the components such as the CPU 301 shown in FIG.

[0027] <Smart lock hardware configuration> Fig. 4 is a hardware configuration diagram of a smart lock. The smart lock 9 is equipped with a computer, and as shown in Fig. 4, includes a CPU 901, a ROM 902, a RAM 903, an NVRAM 904, an opening / closing mechanism 905, an operation unit 907, a long-distance communication circuit 909, an antenna 909a of the long-distance communication circuit 909, and a bus line 910.

[0028] Among these, the CPU 901 controls the operation of the entire smart lock 9. The ROM 902 stores programs used for driving the CPU 901 such as the IPL. The RAM 903 is used as a work area for the CPU 901. The NVRAM (Non-Volatile RAM) 904 is a non-volatile memory that stores and reads various data such as programs.

[0029] The opening / closing mechanism 905 is attached to the thumb turn of the door 8 and is a mechanism that unlocks or locks by rotating the thumb turn through remote operation. The operation unit 907 is a part that the user operates such as a switch. The long-distance communication circuit 909 is a communication circuit for data communication with the drive control server 7 via a communication network. The bus line 910 is an address bus, a data bus, etc. for electrically connecting each component such as the CPU 901 shown in FIG. 4.

[0030] 〔Functional Configuration〕 Subsequently, with reference to FIGS. 5 to 8, the functional configurations of the devices and the like for constructing the remote control system 1 will be described. FIG. 5 is a functional block diagram of the devices and the like that make up the remote control system 1.

[0031] <Functional Configuration of PC> As shown in FIG. 5, the PC 2 has a transmission / reception unit 21, a reception unit 22, a display control unit 24, and a storage / reading processing unit 29. Each of these units is a function or means realized by any of the components shown in FIG. 2 operating according to an instruction from the CPU 201 according to a program for the PC developed from the ROM 202 onto the RAM 203.

[0032] Also, the PC 2 has a storage unit 2000 constructed by the ROM 202, the RAM 203, and the HD 204 shown in FIG. 2.

[0033] (Functional Configurations of PC) The transmission / reception unit 21 of the PC 2 is realized by the processing of the CPU 201 for the network I / F 209, and transmits and receives various data (or information) to and from other devices via the communication network 100.

[0034] The reception unit 22 is realized mainly by the processing of the CPU 201 on the keyboard 211 and mouse 212, and receives various selections or inputs from the user.

[0035] The display control unit 24 is realized mainly by the processing of the CPU 201, and causes the display 208 to display various images.

[0036] The storage / reading processing unit 29 is realized mainly by the processing of the CPU 201 , and stores various data (or information) in the storage unit 2000 and reads various data (or information) from the storage unit 2000 .

[0037] <Smartphone functional configuration> 5, the smartphone 3 has a transmission / reception unit 31, a reception unit 32, an acquisition unit 33, a display control unit 34, and a storage / readout processing unit 39. Each of these units is a function or means realized by any of the components shown in FIG. 5 operating in response to an instruction from a CPU 301 in accordance with a smartphone program loaded from an EEPROM 304 onto a RAM 303.

[0038] The smartphone 3 also has a storage unit 3000 that is configured by the ROM 302, the RAM 303, and the EEPROM 304 shown in FIG.

[0039] (Smartphone functional configuration) The transmission / reception unit 31 of the smartphone 3 is mainly realized by the processing of the CPU 301 for the long-distance communication circuit 312, and transmits and receives various data (or information) to and from other devices via the communication network 100.

[0040] The reception unit 32 is mainly realized by the processing of the CPU 301 on the touch panel 321, and receives various selections or inputs from the user.

[0041] The acquisition unit 33 is realized mainly by processing by the CPU 301 for the image sensor I / F 314 and processing by the CPU, causes the CMOS 313 to capture an image of a QR code, and acquires data embedded in the QR code from the captured image.

[0042] The display control unit 34 is realized mainly by the processing of the CPU 301, and causes the display 318 to display various images.

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

[0044] <Functional configuration of reservation management server> 5, the reservation management server 5 has a transmission / reception unit 51, and a storage / readout processing unit 59. 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 501 in accordance with the program for the reservation management server loaded from the HD 504 onto the RAM 503.

[0045] The reservation management server 5 also has a storage unit 5000 constructed by the ROM 502 and HD 504 shown in FIG.

[0046] (Reservation management table) Fig. 6 is a conceptual diagram showing a reservation management table. The reservation management table is a table for managing the schedule of each user and resource reservations such as conference rooms. A reservation management DB 5001 configured with a reservation management table as shown in Fig. 6 is constructed in the storage unit 5000. In this reservation management table, a reservation ID, a reservation account, an event name, a resource ID, a start date and time, an end date and time, and an account of a prospective participant are associated and managed.

[0047] Of these, the reservation ID is an example of reservation identification information for identifying a specific reservation. The reservation account is the account of a reservationr (user) who has reserved the use of a resource such as a conference room, and in the record for reservation ID "R001", the email address of user a is shown as the account of user a. The reservation account is an example of reservation identification information. The event name indicates the name of a conference held using a resource such as a conference room, etc. The resource ID is an example of resource identification information for identifying a resource such as a conference room. The start date and time is the scheduled start date and time of the event. The end date and time is the scheduled end date and time of the event. The prospective participant account is the account of a user who will participate in the event, and here, like the reservation account, the email address of the prospective participant is shown. The prospective participant account is an example of prospective participant identification information.

[0048] The event name, resource ID, start date and time, and end date and time make up reservation information.

[0049] (Functional configuration of reservation management server) The transmission / reception unit 51 of the reservation management server 5 is realized by processing of the CPU 501 for the network I / F 509, and transmits and receives various data (or information) to and from other devices and the like via the communication network 100.

[0050] The storage / readout processing unit 59 is realized mainly by the processing of the CPU 501 , and stores various data (or information) in the storage unit 5000 and reads various data (or information) from the storage unit 5000 .

[0051] <Functional configuration of the intermediary server> 5, the intermediation server 6 has a transmission / reception unit 61, an authentication unit 62, a creation unit 63, and a storage / readout processing unit 69. Each of these 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 601 in accordance with the program for the intermediation server loaded from the HD 604 onto the RAM 603.

[0052] The intermediation server 6 also has a storage unit 6000 constructed by the ROM 602 and HD 604 shown in FIG.

[0053] (User management table) Fig. 7(a) is a conceptual diagram showing a user management table. The user management table is a table for managing personal information of users. A user management DB 6001 configured with a user management table as shown in Fig. 7(a) is constructed in the storage unit 6000. In this user management table, organization IDs, user accounts, and user names are managed in association with each other.

[0054] Of these, the organization ID is an example of organization identification information for identifying the organization (business) to which the user belongs. The user account is an example of user identification information for identifying the user. Here, the user's email address is shown as the user's account. If the user is a reserving party, the user account is managed as a reserving party account in the reservation information management table described above. If the user is a prospective participant, the user account is managed as a prospective participant account in the reservation information management table described above. The user name is the name of the user.

[0055] (Event management table) FIG. 7(b) is a conceptual diagram showing an event management table. The event management table is a table for managing detailed information of events such as conferences. An event management DB 6002 configured with an event management table as shown in FIG. 7(b) is constructed in the storage unit 6000. In this event management table, in addition to each piece of information managed in the above-mentioned reservation management table (reservation ID, reservation account, event name, resource ID, start date and time, end date and time, and prospective attendee accounts), event status information is associated and managed. Note that a description of the same information as each piece of information managed in the above-mentioned reservation management table will be omitted. The event status is information that mainly indicates the status of an event such as a conference.

[0056] (Key type management table) Fig. 7(c) is a conceptual diagram showing a key type management table. The key type management table is a table for managing the types of keys for unlocking and locking a driving device such as a smart lock. A key type management DB 6003 configured by the key type management table as shown in Fig. 7(c) is constructed in the storage unit 6000. In this key type management table, an organization ID, a resource name, a resource ID, a key type, a driving device ID, and access location information are associated and managed.

[0057] Among these, the organization ID and resource ID are the same as the organization ID in the user information management table and the resource ID in the event management table described above, so their explanation will be omitted. Also, the resource name is the name of the resource such as a conference room.

[0058] Additionally, the type of key indicates the type of method for unlocking and locking. Here, examples of key types include "electronic key," "physical key," and "none." "Electronic key" indicates a method in which a driving device such as a smart lock 9 unlocks and locks the door using electronic information such as authentication information via remote control. "Physical key" indicates a method in which a user inserts a physical key such as a metal key into a keyhole to unlock and lock the door without using a driving device such as a smart lock 9. "None" indicates a case in which no key is required to open or close the door.

[0059] The driving device ID is an example of driving device identification information for identifying a driving device such as the smart lock 9. The access location information indicates information on the location of the access destination, which differs depending on the type of key.

[0060] The location to be accessed when the key type is "electronic key" indicates information about the location to be accessed by the intermediary server 6 via the communication network 100. Here, the URL of the drive control server 7 is indicated as information about the location to be accessed.

[0061] When the key type is "physical key," the access location indicates the location the user is accessing. In this example, the access location information shows the 1st floor security room where the physical key is managed.

[0062] If the key type is "none," no key is required to open or close the door, so there is no information about the location to be accessed.

[0063] (Functional configuration of the intermediary server) The transmission / reception unit 61 of the intermediation server 6 is realized by processing of the CPU 601 for the network I / F 609, and transmits and receives various data (or information) to and from other devices via the communication network 100.

[0064] The authentication unit 62 is mainly realized by the processing of the CPU 601, and performs authentication as to whether or not the person making the reservation is a person authorized to reserve a resource such as a conference room.

[0065] The creation unit 63 is mainly realized by the processing of the CPU 601, and creates a predetermined message using information read from each of the DBs 6001, 6002, and 6003.

[0066] The storage / readout processing unit 69 is realized mainly by the processing of the CPU 601 , and stores various data (or information) in the storage unit 6000 and reads various data (or information) from the storage unit 6000 .

[0067] <Functional configuration of the drive control server> 7, the drive control server 7 has a transmission / reception unit 71, an issuing unit 72, a determination unit 75, and a storage / readout processing unit 79. Each of these units is a function or means realized by any of the components shown in FIG. 2 operating in response to an instruction from a CPU 701 in accordance with a program for the drive control server loaded from the HD 704 onto the RAM 703.

[0068] The drive control server 7 also has a storage unit 7000 constructed by the ROM 702 and HD 704 shown in FIG.

[0069] (Drive management table) Fig. 8 is a conceptual diagram showing a drive management table. The drive management table is a table for managing information about drives such as the smart lock 9. A drive management DB 7001 configured by a drive management table such as that shown in Fig. 8 is constructed in the storage unit 7000. In this drive management table, the drive ID, destination information of the drive, authentication information, the validity period of the authentication information, and the state of the drive are associated and managed.

[0070] Among these, the drive ID is the same as the drive ID managed in the above-mentioned key type management table. This drive ID allows the intermediary server 6 and the drive control server 7 to perform cooperative processing.

[0071] The destination information of the driving device indicates the destination of the driving device, such as the smart lock 9, on the communication network 100. The destination information is, for example, an IP address or a MAC address.

[0072] The authentication information is information required for authentication when a driving device such as the smart lock 9 performs unlocking or locking. The authentication information is, for example, a passcode or a password.

[0073] The validity period of the authentication information indicates a period during which the authentication information can be effectively used by the drive control server 7. As a result, as shown in Fig. 8, even if the same drive (drive ID "d001") is used, the authentication information and the validity period of the authentication information are different, and therefore the smart lock 9 cannot be unlocked or locked outside the period reserved by the reservation user, even if the resource is the same, such as the same conference room.

[0074] The state of the driving device indicates the unlocked or locked state by a driving device such as a smart lock 9.

[0075] (Functional configuration of the drive control server) The transmission / reception unit 71 of the drive control server 7 is realized by processing of the CPU 701 for the network I / F 709, and transmits and receives various data (or information) to and from other devices via the communication network 100.

[0076] The issuing unit 72 is realized mainly by the processing of the CPU 701, and issues authentication information.

[0077] The determination unit 75 performs various determinations and is mainly realized by the processing of the CPU 701. For example, the determination unit 75 determines the validity of authentication information.

[0078] The storage / read processing unit 79 is realized mainly by the processing of the CPU 701 , and stores various data (or information) in the storage unit 7000 and reads various data (or information) from the storage unit 7000 .

[0079] <Smart lock function configuration> As shown in Fig. 5, the smart lock 9 has a transceiver unit 91 and a drive control unit 92. Each of these units is a function or means realized by any of the components shown in Fig. 4 operating in response to an instruction from the CPU 901 in accordance with the program for the smart lock loaded from the NVRAM 904 onto the RAM 903.

[0080] (Smart lock functional configuration) The transmitter / receiver unit 91 of the smart lock 9 is mainly realized by the processing of the CPU 901 for the long-distance communication circuit 909, and transmits and receives various data (or information) to and from other devices via the communication network 100.

[0081] The drive control unit 92 is realized mainly by the processing of the CPU 901, and drives the opening / closing mechanism 905 to perform unlocking or locking.

[0082] [Processing and Operation of the Embodiment] Next, the processing or operation of this embodiment will be described with reference to FIGS.

[0083] <Reservation registration process> First, with reference to Fig. 9 to Fig. 12, a case will be described in which a user a uses a PC 2 to reserve a conference room A, which is an example of a resource, in the reservation management server 5. Fig. 9 is a sequence diagram showing a reservation registration process. Fig. 10 is a diagram showing an example of a schedule input screen.

[0084] The user a uses the PC 2 to input reservation information (event name, resource, event start time, event end time) and expected participants to a schedule input screen 1560 as shown in Fig. 10, and the reception unit 22 accepts the input or selection of the reservation information and expected participants (S21). This schedule input screen 1560 includes an input field 1561 for inputting the event name, an input field 1562 for inputting the resource name, an input field 1563 for inputting the expected start date and time of the event, an input field 1564 for inputting the expected end date and time of the event, a display area 1565 for displaying the name of the person who made the reservation (the account of the person who made the reservation), and a selection field 1566 for selecting the names of expected participants (the accounts of the people who made the reservation) of people who made the reservation. Note that, here, the accounts of the person who made the reservation and the people who made the reservation are their respective e-mail addresses.

[0085] Next, the transmitting / receiving unit 21 of PC2 transmits each piece of information (reservator account, participant account, reservation information) entered or selected in step S21 to the reservation management server 5 (S22). As a result, the transmitting / receiving unit 51 of the reservation management server 5 receives each piece of information. Note that step S22 may be executed after the reserving person (user a) obtains approval to make a reservation from the PC of an approver such as a superior via the communication network 100.

[0086] Next, in the reservation management server 5, the storage / read processing unit 79 assigns a reservation ID to each piece of information received in the reservation step S22, and stores and manages the information in the reservation management DB 5001 (S23). Then, the transmitting / receiving unit 51 transmits a completion notification to PC2 indicating that the reservation has been completed (S24). As a result, the transmitting / receiving unit 21 of PC2 receives the completion notification.

[0087] Furthermore, in the reservation management server 5, the transmitting / receiving unit 51 transmits the various pieces of information stored in step S23 (reservation ID, reservation user account, participant accounts, reservation information) to the intermediary server (S25). As a result, the transmitting / receiving unit 61 of the intermediary server 6 receives the various pieces of information. Note that step S25 may be executed as a response to a periodic inquiry from the intermediary server 6 to the reservation management server 5 by polling.

[0088] Next, the intermediary server 6 authenticates the user based on whether or not the subscriber account received in step S25 is managed as a user account in the user management DB 6001 (S26).

[0089] (If you are not a legitimate user) Next, a case where user a is found not to be a legitimate user as a result of user authentication in step S26 will be described with reference to Fig. 11. Fig. 11 is a sequence diagram showing the process when the user is not a legitimate user.

[0090] 11, the transmitting / receiving unit 61 of the intermediary server 6 transmits a reservation cancellation request to the reservation management server 5 (S31). This reservation cancellation request includes the specific reservation ID received in step S25. As a result, the transmitting / receiving unit 51 of the reservation management server 5 receives the reservation cancellation request.

[0091] Next, in reservation management server 5, storage / read processing unit 59 in step S23 deletes the specific reservation ID and each piece of information stored together with this reservation ID (S32).

[0092] Furthermore, the creation unit 63 of the intermediary server 6 creates a reservation-prohibited message for PC2 indicating that the reservation could not be made (S33). Then, the transmission / reception unit 61 sends the reservation-prohibited message created in step S33 to PC2 (S34). In this case, the reservation account received by the transmission / reception unit 61 of the intermediary server 6 in step S25 is an email address, so the transmission / reception unit 61 sends the reservation-prohibited message to this email address. As a result, the transmission / reception unit 21 of PC2 receives the reservation-prohibited message. Then, in PC2, the display control unit 24 displays the reservation-prohibited message on the display 208 (S35).

[0093] (For legitimate users) Next, a case where user a is found to be a valid user through user authentication in step S26 will be described with reference to Fig. 12. Fig. 12 is a flowchart showing the key type determination process performed by the intermediary server when the user is a valid user.

[0094] First, the storage / read processing unit 69 associates the various pieces of information received in step S25 (reservation ID, reserving account, participant accounts, and reservation information) and stores and manages them as a new record in the event management DB 6002 (S41). At this point, the "event status" column in the new record is not managed.

[0095] Next, the storage / readout processing unit 69 searches the key type management DB 6003 using the resource ID in the reservation information stored in step S41 as a search key, thereby reading out the corresponding key type information (S42). Then, if the key type is an "electronic key", the processes from step S61 onwards, which will be described later, are executed. If the key type is a "physical key", the processes from step S81 onwards, which will be described later, are executed. Furthermore, if the key type is "none", that is, if there is no key, the processes from step S101 onwards are executed. Therefore, the processes for each type will be explained below.

[0096] (If the key type is electronic key) First, the case where the key type is an "electronic key" will be described with reference to Fig. 13 and Fig. 14. Fig. 13 is a sequence diagram showing the process of sending a message when the key type is an "electronic key." Fig. 14 is an example of a screen displayed on a PC when the key type is an "electronic key."

[0097] 13, the storage / read processing unit 69 of the intermediation server 6 searches the key type management DB 6003 using the resource ID in the reservation information received in step S25 as a search key to read out the corresponding drive device ID and access location information (S61). Then, the transmission / reception unit 61 transmits a request for authentication information to the access location of the drive control server 7 (S62). This request includes the drive device ID read out in step S61. As a result, the transmission / reception unit 71 of the drive control server 7 receives the request for authentication information.

[0098] Next, in the drive control server 7, the issuing unit 72 issues unique authentication information (S63). Then, the storage / reading processing unit 79 associates the authentication information issued in step S63 with the record of the drive unit ID that is the same as the drive unit ID received in step S62 in the drive unit management DB 7001, stores the information, and manages the information (S64).

[0099] Next, the transmitting / receiving unit 71 transmits the authentication information issued in step S63 to the intermediation server 6 (S65). As a result, the transmitting / receiving unit 61 of the intermediation server 6 receives the authentication information.

[0100] Next, in the intermediary server 6, the storage / read processing unit 69 reads out the corresponding user name from the user management DB 6001 using the reserving user (user a) account received in step S25 as a search key (S66).

[0101] Next, the storage / read processing unit 69 searches the key type management DB 6003 using the resource ID in the reservation information received in step S41 as a search key, thereby reading out the corresponding resource name (S67).

[0102] Next, the event management DB 6002 is searched using the reserving user account received in step S41 as a search key to read out corresponding reservation information (S68). Then, the creation unit 63 uses the authentication information received in step S65 and the information read out in steps S66 to S68 (reservation name (name of the user who made the reservation), resource name, reservation information) to create a message to convey information that the reservation has been completed together with the authentication information, as shown in Fig. 14 (S69).

[0103] Next, the transmitting / receiving unit 61 of the intermediary server 6 transmits to the PC2 a message to inform the PC2 that the reservation has been completed together with the authentication information created in step S69 (S70). As a result, the transmitting / receiving unit 21 of the PC2 receives this message.

[0104] The authentication information may always be the same. In this case, the drive control server 7 does not execute the process of step S63, but adjusts the timing of sending the authentication information in step S70. For example, the intermediary server 6 sends the authentication information 10 minutes before the start of the conference. Also, in step S70, the intermediary server 6 may send a reservation completion message not only to the PC 2 of the person who made the reservation (user a), but also to the PCs of some or all of the people who plan to attend the same conference.

[0105] Next, the storage / read processing unit 69 manages the "event status" column of the record of the subscriber account read in step S68 in the event management DB 6002 as "authentication information notified" (S71). As a result, the "event status" column that was not managed in step S41 above is managed with new information.

[0106] Next, in the PC 2, the display control unit 24 causes the display 208 to display a message screen as shown in Fig. 14. This allows the reserving person (user a) to input or select reservation information, etc. in the above step S21, and to obtain information that the reservation has been completed together with authentication information required to unlock the resource in step S72.

[0107] (If the key type is a physical key) Next, the case where the key type is a "physical key" will be described with reference to Fig. 15 and Fig. 16. Fig. 15 is a sequence diagram showing the process of sending a message when the key type is a "physical key". Fig. 16 is an example of a screen displayed on a PC when the key type is a "physical key".

[0108] 15, the storage / readout processing unit 69 of the intermediary server 6 searches the key type management DB 6003 using the resource ID in the reservation information received in step S25 as a search key to read out the corresponding drive device ID and access location information (S81). Since there is no process (S62-S65) for acquiring authentication information from the drive control server 7 as in the case of the "electronic key" described above, the storage / readout processing unit 69 reads out the corresponding user name from the user management DB 6001 using the reservation user (user a) account received in step S25 as a search key (S82).

[0109] Next, the storage / read processing unit 69 searches the key type management DB 6003 using the resource ID in the reservation information received in step S41 as a search key, thereby reading out the corresponding resource name (S83).

[0110] Next, the event management DB 6002 is searched using the reserving user account received in step S41 as a search key to read out corresponding reservation information (S84). Then, the creation unit 63 uses each piece of information read out in steps S81 to S84 (access location information, reservation name (name of the user who made the reservation), resource name, and reservation information) to create a message to convey information that the reservation has been completed together with access location information, as shown in Fig. 16 (S85). In this case, the type of key is a "physical key", so the location where the physical key is managed (for example, the 1st floor security room) is shown, as shown in Fig. 16.

[0111] Next, the transmitting / receiving unit 61 of the intermediary server 6 transmits to PC2 a message conveying information that the reservation has been completed together with the access location information created in step S85 (S86). As a result, the transmitting / receiving unit 21 of PC2 receives this message. Then, the storage / reading processing unit 69 manages the "event status" column of the record of the subscriber account read in step S84 in the event management DB 6002 as "access location information notified" (S87). As a result, the "event status" column that was not managed in step S41 above is managed with new information.

[0112] Next, in PC2, the display control unit 24 causes the display 208 to display a message screen as shown in Fig. 16 (S88). This allows the reserving person (user a) to input or select reservation information, etc. in step S21 above, and to obtain information that the reservation has been completed, together with information on the physical access location required to unlock the resource, in step S88.

[0113] (If you don't use a key) Next, the case where the key type is "None" will be described with reference to Fig. 17 and Fig. 18. Fig. 17 is a sequence diagram showing the process of sending a message when the key type is "None". Fig. 18 is an example of a screen displayed on a PC when the key type is "None". Here, the key type is "None", in other words, there is no key, so the storage / reading processing unit 69 does not need to read out information about the access location as in step S61 (S81) above.

[0114] As shown in FIG. 17, the storage / read processing unit 69 reads out the corresponding user name from the user management DB 6001 using the reserving user (user a) account received in step S25 as a search key (S101).

[0115] Next, the storage / read processing unit 69 searches the key type management DB 6003 using the resource ID in the reservation information received in step S41 as a search key, thereby reading out the corresponding resource name (S102).

[0116] Next, the event management DB 6002 is searched using the reserving user account received in step S41 as a search key to read out corresponding reservation information (S103). Then, the creation unit 63 uses each piece of information read out in steps S101 to S103 (reservation name (name of the user who made the reservation), resource name, reservation information) to create a message for notifying completion of the reservation as shown in Fig. 18 (S104).

[0117] Next, the transmitting / receiving unit 61 of the intermediary server 6 transmits the message created in step S85 to PC2 to inform the completion of the reservation (S105). As a result, the transmitting / receiving unit 21 of PC2 receives the message to inform the completion of the reservation. Then, the storage / reading processing unit 69 manages the "event status" column of the record of the subscriber account read in step S103 in the event management DB 6002 as "notification of reservation completion completed" (S106). As a result, the "event status" column that was not managed in step S41 above is managed with new information.

[0118] Next, in the PC 2, the display control unit 24 causes the display 208 to display a message screen as shown in Fig. 16. This allows the reserving person (user a) to input or select reservation information, etc. in the above step S21, and thereby obtain information that the reservation has been completed in step S107.

[0119] <Remote unlocking process when the key type is electronic key> Next, the process of remotely unlocking the smart lock 9 when the key type is an "electronic key" will be described with reference to Figs. 19 to 22. Figs. 19 to 21 are sequence diagrams showing the process of remotely unlocking when the key type is an "electronic key". Fig. 22 is an example of a screen on a smartphone when starting a conference. Here, a case will be described in which user a goes to the door 8 outside the conference room A and uses his / her smartphone 3 to unlock the smart lock in front of him / her.

[0120] First, the user a operates the smartphone 3, and the acquisition unit 33 photographs the QR code shown on the door 8 as shown in FIG. 1, thereby acquiring access destination information such as a resource ID and a URL embedded in the QR code (S121). Furthermore, the storage / readout processing unit 39 reads out the reservation account of the user a stored in the storage unit 3000 (S122). Then, the transmission / reception unit 31 of the smartphone 3 transmits a request for reservation information to the intermediation server 6 indicated by the access destination information (S123). This request for reservation information includes the resource ID acquired in step S121 and the reservation (user a) account read out in step S122. As a result, the transmission / reception unit 61 of the intermediation server 6 receives the request for reservation information (S123).

[0121] Next, in the intermediation server 6, the storage / read processing unit 69 searches the key type management DB 6003 using the resource ID received in step S123 as a search key, thereby reading out the corresponding resource name (S124).

[0122] Next, the event management DB 6002 is searched using the reservation account received in step S123 as a search key to read out all reservation IDs and reservation information for the event execution date (S125).

[0123] Next, the storage / read processing unit 69 reads out the corresponding user name from the user management DB 6001 using the reserving person (user a) account received in step S123 as a search key (S126). Then, the creation unit 63 uses each piece of information read out in steps S124 to S126 (resource name, all reservation information for the execution date, reservation name (name of the user who made the reservation)) to create a reservation content message showing the reservation content to prompt the reserving person to start the event procedure, as shown in Fig. 22(a) (S127).

[0124] Next, the transmitting / receiving unit 61 of the intermediation server 6 transmits the reservation content message created in step S127 to the smartphone 3 (S128). The reservation content message includes a reservation ID. As a result, the transmitting / receiving unit 31 of the smartphone 3 receives this message.

[0125] Next, in the smartphone 3, the display control unit 34 displays a message screen as shown in FIG. 16(a) on the display 318 (S129). This message screen displays a resource name (conference room A) display field 401, an event name (regular meeting) display field 402, a start date and end date and time display field 403, a reservation person name (user a) display field 404, and a start date and end date and time display field 407 of other events on the same day. In addition, this message screen displays a "Start" button 411 and a "Cancel" button 412. The "Start" button 411 is a button pressed by the reservation person or the like when the smart lock 9 is remotely operated to unlock and the event is started. The "Cancel" button 412 is a button pressed by the reservation person or the like when the smart lock 9 is remotely operated to unlock and the event is stopped from starting. Note that the "Start" button may be replaced with an "Unlock" button.

[0126] Here, when the person who made the reservation (user a) presses the "START" button 411, the reception unit 32 remotely operates the smart lock 9 to unlock it and receives the request to start the event (S130). As a result, the display control unit 34 pops up an authentication information input screen 450 for inputting authentication information, as shown in FIG. 22(b) (S131). As shown in FIG. 22(b), the authentication information input screen 450 displays an authentication information input field 451 for inputting authentication information, an "OK" button 452, and a "Cancel" button 453. The "OK" button 452 is a button to be pressed by the person who made the reservation (user a) when the authentication information input in the authentication information input field 451 is confirmed. The "Cancel" button 453 is a button to be pressed by the person who made the reservation (user a) when the authentication information input in the authentication information input field 451 is confirmed.

[0127] Here, when the reserving person (user a) inputs the authentication information obtained in step S72 into the authentication information input field 451 and presses the "OK" button 452, the reception unit 32 receives the input of the authentication information (S132).

[0128] 20, after the process of step S132, the transmitting / receiving unit 31 transmits a request to unlock the smart lock 9 and a request to start the event to the intermediary server 6 (S141). The unlocking request and the start request include the reservation ID received in step S128 and the authentication information accepted in step S132. As a result, the transmitting / receiving unit 61 of the intermediary server 6 receives the unlocking request and the start request.

[0129] Next, in the intermediation server 6, the storage / read processing unit 69 searches the event management DB 6002 using the reservation ID received in step S141 as a search key, and reads out the corresponding resource ID (S142).

[0130] Next, the storage / read processing unit 69 searches the key type management DB 6003 using the resource ID read in step S142 as a search key to read out the corresponding drive device ID and access location information (S143). Then, the transmission / reception unit 61 transmits a request to start remote control of the smart lock 9 to the drive control server 7 indicated by the access location information (S144). This request includes the drive device ID read in step S143 and the authentication information received in step S141. As a result, the transmission / reception unit 71 of the drive control server 7 receives the request to start remote control.

[0131] Next, in the drive control server 7, the storage / read processing unit 79 searches the drive management DB 7001 using the drive ID received in step S144 as a search key, thereby reading information on the validity period of the corresponding authentication information (S145).

[0132] Next, the determination unit 75 determines the validity of the authentication information received in step S144 based on whether the current date and time is within the validity period of the authentication information read in step S145 (S146). Here, the case where the determination unit 75 determines that the authentication information is valid because the current date and time is within the validity period will be described below.

[0133] Next, the storage / readout processing unit 79 searches the drive management DB 7001 using the drive ID received in step S144 as a search key to read out destination information (e.g., IP address) of the corresponding drive unit (S147). Then, the transmission / reception unit 71 transmits an unlocking request to the smart lock 9 indicated by the destination information of the drive unit read in step S147 (S148). As a result, the transmission / reception unit 91 of the smart lock 9 receives the unlocking request.

[0134] Next, in the smart lock 9, the drive control unit 92 drives the opening / closing mechanism 905 to unlock the lock (S149). This allows the smartphone 3 to remotely unlock the smart lock 9 via the intermediary server 6 and the drive control server 7.

[0135] 24, the transmitting / receiving unit 91 of the smart lock 9 transmits a response indicating that the unlocking has been completed to the drive control server 7 (S161). As a result, the transmitting / receiving unit 71 of the drive control server 7 receives the response.

[0136] Next, in the drive control server 7, the storage / read processing unit 79 changes the column of "drive device status" in the record of the drive device ID received in step S144 above from "locked" to "unlocked" (S162). Then, the transmitting / receiving unit 71 of the drive control server 7 transmits a response to the intermediary server 6 indicating that unlocking has been completed (S163). As a result, the transmitting / receiving unit 81 of the intermediary server 6 receives the response.

[0137] Next, in the intermediary server 6, the storage / read processing unit 69 changes the "event status" column in the record of the reservation ID received in step S141 above from "authentication information notified" to "event started" (S164). Then, the transmitting / receiving unit 61 of the intermediary server 6 transmits a response indicating that unlocking has been completed to the smartphone 3 (S165). As a result, the transmitting / receiving unit 31 of the smartphone 3 receives the response.

[0138] Next, in the smartphone 3, the display control unit 34 displays an "End" button 413 as shown in Fig. 22(c) (S166). This "End" button 413 is a button pressed by the person who made the reservation (user a) or the like when ending the event, in contrast to the "Start" button 411 in Fig. 22(a). This allows the person who made the reservation (user a) to know that the smart lock 9 has been unlocked not only by the sound made when the smart lock 9 is unlocked, but also by the display of this "End" button 413.

[0139] In FIG. 22(b), if the reservation person (user a) makes a mistake in inputting the authentication information, as shown in FIG. 22(d), the display control unit 34 pops up an authentication information re-entry screen 460 for re-entering the authentication information, as shown in FIG. 22(d). As shown in FIG. 22(d), the authentication information re-entry screen 460 displays an authentication information input field 461 for re-entering the authentication information, an "OK" button 462, and a "Cancel" button 463. The "OK" button 462 is a button to be pressed by the reservation person (user a) when the reservation person (user a) confirms the authentication information input in the authentication information re-entry field 451. The "Cancel" button 463 is a button to be pressed by the reservation person (user a) when the reservation person (user a) confirms the authentication information input in the authentication information re-entry field 461. Here, when the reserver (user a) re-enters the authentication information known in step S72 in the authentication information re-entry field 461 and presses the "OK" button 462, the acceptance unit 32 accepts the re-entry of the authentication information (S132).

[0140] <Remote locking process when the key type is electronic key> Next, the process of remotely locking the smart lock 9 when the key type is an "electronic key" will be described with reference to Fig. 23 and Fig. 24. Fig. 23 and Fig. 24 are sequence diagrams showing the process of remotely locking when the key type is an "electronic key".

[0141] First, after the event ends, the person who made the reservation and all participants leave conference room A, and the person who made the reservation (user a) presses the “End” button 413 shown in FIG. 22(c), and the reception unit 32 accepts the unlocking of the drive device and the end of the event (S181).

[0142] 23, the transmitting / receiving unit 31 transmits a request to lock the smart lock 9 and a request to end the event to the intermediary server 6 (S182). The locking request and the end request include the reservation ID received in step S182. As a result, the transmitting / receiving unit 61 of the intermediary server 6 receives the locking request and the end request.

[0143] Next, in the intermediation server 6, the storage / read processing unit 69 searches the event management DB 6002 using the reservation ID received in step S182 as a search key, and reads out the corresponding resource ID (S183).

[0144] Next, the storage / read processing unit 69 searches the key type management DB 6003 using the resource ID read in step S183 as a search key to read out the corresponding drive device ID and access location information (S184). Then, the transmission / reception unit 61 transmits a request to start remote control of the smart lock 9 to the drive control server 7 indicated by the access location information (S185). This request includes the drive device ID read in step S184. As a result, the transmission / reception unit 71 of the drive control server 7 receives the request to start remote control.

[0145] Next, in the drive control server 7, the storage / read processing unit 79 searches the drive management DB 7001 using the drive ID received in step S185 as a search key to read out destination information (e.g., IP address) of the corresponding drive (S186). Then, the transmission / reception unit 71 transmits a locking request to the smart lock 9 indicated by the destination information of the drive read in step S186 (S187). As a result, the transmission / reception unit 91 of the smart lock 9 receives the locking request.

[0146] Next, in the smart lock 9, the drive control unit 92 drives the opening / closing mechanism 905 to lock the door (S188). This allows the smartphone 3 to remotely lock the smart lock 9 via the intermediation server 6 and the drive control server 7.

[0147] 24, the transmitting / receiving unit 91 of the smart lock 9 transmits a response indicating that the locking has been completed to the drive control server 7 (S201). As a result, the transmitting / receiving unit 71 of the drive control server 7 receives the response.

[0148] Next, in the drive control server 7, the storage / read processing unit 79 changes the column of "drive device status" in the record of the drive device ID received in step S185 above from "unlocked" to "locked" (S202). Then, the transmitting / receiving unit 71 of the drive control server 7 transmits a response to the intermediary server 6 indicating that locking has been completed (S203). As a result, the transmitting / receiving unit 81 of the intermediary server 6 receives the response.

[0149] Next, in the intermediation server 6, the storage / read processing unit 69 changes the "event status" column in the record of the reservation ID received in step S182 above from "event start" to "event end" (S204). Then, the transmission / reception unit 61 of the intermediation server 6 transmits a response indicating that the locking has been completed to the smartphone 3 (S205). As a result, the transmission / reception unit 31 of the smartphone 3 receives the response.

[0150] Next, in the smartphone 3, the display control unit 34 displays a message indicating that the locking has been completed on the display 318. An "End" button 413 is displayed. This allows the reserver (user a) to know that the smart lock 9 has been unlocked by the sound of the smart lock 9 locking, and also to know that the locking has been completed by the display of the message indicating that the locking has been completed.

[0151] [Effects of the embodiment] As described above, according to this embodiment, the intermediary server 6 mediates processing between the reservation management server 5 that manages the resource reservation accepted from the PC 2 that registers the reservation, and the drive control server 7 that remotely controls the smart lock 9 for unlocking the resource, thereby providing the PC 2 with authentication information required to unlock the smart lock 9 for unlocking the reserved resource. This has the effect of preventing the process for the person who made the reservation (user) from becoming complicated.

[0152] 〔supplement〕 The QR code is an example of an information providing object. In addition to QR codes, information providing objects also include IC tags, beacon transmitters, etc.

[0153] When the information item is an IC tag, the acquisition unit 33 of the smartphone 3 is realized by the processing of the CPU 301 on the short-range communication circuit 320, not by the processing of the CPU 301 on the image sensor I / F 314, and acquires the resource ID and the access destination information from the IC tag by a short-range communication technology such as NFC (Near Field Communication) (registered trademark) or Bluetooth (registered trademark) (see S121). The IC tag is attached to a structure such as the door 8, and thus the IC tag and the resource are linked to each other.

[0154] On the other hand, when the information provided object is a beacon transmitter, the acquisition unit 33 of the smartphone 3 is realized by the processing of the CPU 301 on the short-range communication circuit 320, not the processing of the CPU 301 on the image sensor I / F 314, and when the smartphone 3 enters the radio wave area of ​​the beacon transmitter, it acquires the resource ID access destination information by the radio wave transmitted from the beacon transmitter (see S121). The beacon transmitter is attached to a structure such as a door 8, and the beacon transmitter and the resource are linked to each other.

[0155] In the above, an example was described in which a QR code sticker, an IC tag, and a beacon transmitter were attached to the door 8 of the conference room, but the present invention is not limited to this. For example, the QR code sticker, the IC tag, and the beacon transmitter may be attached to a structure other than the door of the conference room where the door 8 is installed, such as a wall part.

[0156] Furthermore, in the above, a conference room, which is a common unit, is shown as an example of a resource, but is not limited thereto. For example, another example of a resource may be a mobile object such as an aircraft, a vehicle, or a ship, which is a common unit. Also, the smart lock 9 may not be attached to the outer panel of the door, but may be part of the mechanism inside the door. For example, the mechanism of the smart lock 9 is attached inside the door of the vehicle, and the vehicle may be used for car sharing.

[0157] Although the above description has been given of the case where the remote control system remotely controls unlocking and locking, it may be possible to remotely control at least one of unlocking and locking.

[0158] Each of the components such as the CPUs 201, 301, 501, 601, 701, etc. may be a single component or a plurality of components.

[0159] Each function in the above-described embodiment can be realized by one or more processing circuits. Here, the "processing circuit" in the present embodiment 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), a DSP (digital signal processor), an FPGA (field programmable gate array), a SOC (System on a chip), a GPU, and a conventional circuit module designed to execute each of the above-described functions. [Explanation of symbols]

[0160] 1 Remote Control System 2 PC (example of a registered terminal) 3. Smart lock (an example of a communication device) 5 Reservation Management Server 6. Intermediary Server 7 Drive control server 8 Doors 9 Smart lock (an example of a drive device) 10 QR Code 10 (Example of information provided) 61 Transmitting / receiving unit (an example of a transmitting means, an example of a receiving means) 62 Authentication Section 63 Creation Department 69 Memory / read processing section 100 Communication Network 6000 storage section 6001 User management DB (an example of user management means) 6002 Event management DB (an example of event management means) 6003 Key type management DB (an example of key type management means) [Prior art documents] [Patent documents]

[0161] [Patent Document 1] Patent No. 3845948

Claims

1. a receiving means for receiving resource identification information for identifying a resource from a reservation management device that manages reservations of the resource, and for receiving authentication information for unlocking a lock by a drive control device that manages a drive device installed in the resource from the drive control device; a transmission means for transmitting a remote control start request including the authentication information to the drive control device; An intermediary device having

2. The intermediary device described in claim 1, characterized in that, depending on the type of unlocking method associated with the resource identification information received by the receiving means, the transmitting means may or may not transmit to the drive control device drive device identification information for identifying the drive device corresponding to the resource identification information.

3. the types of the unlocking method include at least an electronic key indicating a method for remotely controlling the driving device to cause the driving device to unlock the key related to the resource, and a physical key indicating a method for physically unlocking the key by a driving device different from the driving device, The intermediary device described in claim 2, characterized in that when the type of unlocking method corresponding to the resource identification information received by the receiving means is an electronic key, the transmitting means transmits the drive device identification information to the drive control device by including it in the remote control start request.

4. When the drive control device completes remote unlocking of the drive device based on the drive device identification information and the authentication information included in the remote control start request transmitted by the transmission means, the reception means receives information indicating completion of unlocking transmitted by the drive control device.

4. The intermediary device according to claim 3.

5. An intermediary device described in any one of claims 1 to 4, wherein the driving device is a smart lock.

6. A remote control system including a drive device and an intermediate device, the drive device being managed by a drive control device and installed in a resource, The drive device is a drive control means for controlling unlocking of the door in response to a request for unlocking transmitted from the drive control device based on authentication information; The intermediary device is a receiving means for receiving resource identification information for identifying a resource from a reservation management device that manages the reservation of the resource, and receiving the authentication information for unlocking the key from the drive control device; a transmission means for transmitting a remote control start request including the authentication information to the drive control device; A remote control system comprising:

7. The computer a receiving step of receiving resource identification information for identifying a resource from a reservation management device that manages reservations of the resource, and receiving authentication information for unlocking the key by the drive device from a drive control device that manages a drive device installed in the resource; a transmitting step of transmitting a remote control start request including the authentication information to the drive control device; To carry out The method comprising:

8. On the computer, a receiving step of receiving resource identification information for identifying a resource from a reservation management device that manages reservations of the resource, and receiving authentication information for unlocking the key by the drive device from a drive control device that manages a drive device installed in the resource; a transmitting step of transmitting a remote control start request including the authentication information to the drive control device; A program that executes the following.

Images