Intermediary server, remote control system, intermediary 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 intermediary server, a remote control system, an intermediary method, and a program.

Background Art

[0002] In recent years, a system has been provided that remotely locks (or unlocks) 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, not only can the door of a dedicated resource such as an individual's house or condominium be locked (or unlocked), but also the key of a shared resource such as a company conference room or a car-sharing vehicle can be locked (or unlocked).

Summary of the Invention

Problems to be Solved by the Invention

[0003] However, when the resource is a shared item, in order for multiple users to use it efficiently, it may be necessary to register and manage the reservation of the resource in a reservation management service (system) in advance. However, the smart lock etc. is not necessarily remotely controlled by the reservation management service. Therefore, when using the reserved resource, if it is necessary to lock or unlock the key using electronic information such as a smart lock related to the resource, the user must separately obtain authentication information such as a passcode necessary for unlocking the key related to the reserved resource from a system that remotely controls the smart lock etc. This causes a problem that the user's processing becomes complicated.

Means for Solving the Problems

[0004] The invention according to claim 1 is a mediation server comprising: receiving means for receiving resource identification information for identifying the resource, which is transmitted by a reservation management server that manages reservations of resources received from a registration terminal that performs reservation registration; and transmitting means for transmitting drive device identification information for identifying the drive device corresponding to the resource identification information to a drive control server that remotely controls a drive device for unlocking a key related to the resource, wherein the receiving means receives authentication information necessary for unlocking the key by the drive device indicated by the drive device identification information transmitted 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 mediation server mediates between a reservation management server that manages reservations of resources received from a registration terminal that performs reservation registration and a drive control server that remotely controls a drive device for unlocking a resource, so that it is possible to provide the registration terminal with authentication information necessary for unlocking the drive device for unlocking the reserved resource. Thereby, it is possible to suppress the complication of the processing of the reserver (user).

Brief Description of the Drawings

[0006]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Embodiments for Carrying Out the Invention

[0007] Hereinafter, this embodiment will be described in detail with reference to the drawings.

[0008] 〔Outline of the System〕 First, the outline of the remote control system 1 will be described. FIG. 1 is a schematic diagram of the remote control system according to this embodiment. Here, the case where the smartphone 3 remotely unlocks and locks the smart lock 9 installed outside the door 8 of a resource such as Conference Room A (the outside of Conference Room A) will be described.

[0009] As shown in FIG. 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 via a communication network 100 such as the Internet. Note that the communication network 100 may include not only wired communication but also networks by wireless communication such as a mobile communication system (4G, 5G, 6G, etc.) and WiMAX (Worldwide Interoperability for Microwave Access).

[0010] Among these, the PC 2, the smartphone 3, and the smart lock 9 belong to the same operator (organization) such as the same company. Conference Rooms A, B, and C are installed in the building of this operator. In FIG. 1, Conference Room A is shown. Outside the door 8 of Conference Room A (the outside of Conference Room A), a seal with a QR code printed on it is pasted. Resource identification information (for example, resource ID) for identifying Conference Room A and access destination information 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 user a.

[0013] The smart lock 9 is installed in the key part of the door 8 and has a mechanism capable of unlocking and locking the door. In addition, a QR code (registered trademark) 10 such as a barcode is shown on the door 8. The QR code 10 is printed on a sticker for attaching to the door 8. The QR code 10 embeds a resource ID for identifying a resource such as a conference room where the door 8 is installed, and access destination information (URL, etc.) to the mediation server 6. The sticker with the QR code 10 shown is attached to a part of a resource such as the door 8, so that the QR code and the resource are linked. The smartphone 3 acquires the information of the QR code by an installed QR code scanner application.

[0014] The smart lock 9 is an example of a driving device provided by the operator operating the drive control server 7 to the organization (operator) to which user a belongs. 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 rotates the thumb turn by remote operation to unlock or lock the door.

[0015] Next, the reservation management server 5, the mediation server 6, and the drive control server 7 are each managed by different operators. The reservation management server 5 is, for example, a server such as Microsoft (registered trademark) 365. The mediation server 6 is a server managed by an operator that provides a service that links a service including reservation management such as Microsoft (registered trademark) 365 and a remote unlocking (or locking) service of the smart lock 9. The drive control server 7 is a server of an operator that sells the smart lock 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 operators, in this embodiment, the mediation 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 and 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 an image. 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] Also, the keyboard 211 is a type of input means having a plurality of keys for inputting characters, numerical values, 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 the reading or writing (storage) of data to / from the recording medium 206 such as a flash memory. The DVD-RW drive 214 controls the reading or writing of various data to / from the DVD-RW 213 as an example of a removable recording medium. Note that it is not limited to DVD-RW, and it may be DVD-R, Blu-ray Disc, etc.

[0022] <Hardware Configuration of Smartphone> Figure 3 is a hardware configuration diagram of a smartphone. As shown in Figure 3, the smartphone 3 includes a CPU 301, a ROM 302, a RAM 303, an EEPROM 304, a CMOS sensor 305, an imaging device I / F 306, an acceleration / azimuth 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 for driving the CPU 301 such as the CPU 301 and 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 according to the control of the CPU 301. The CMOS (Complementary Metal Oxide Semiconductor) sensor 305 is a type of built-in imaging means that captures a subject (mainly a self-portrait) according to the control of the CPU 301 to obtain image data. Note that an imaging means such as a CCD (Charge Coupled Device) sensor may be used instead of the CMOS sensor. The imaging device I / F 306 is a circuit that controls the driving of the CMOS sensor 305. The acceleration / azimuth sensor 307 is various sensors such as an electronic magnetic compass that detects geomagnetism, a gyrocompass, and an acceleration sensor. The media I / F 309 controls the reading or writing (storage) of data to and from the recording medium 308 such as a flash memory. The GPS receiver 311 receives GPS signals from GPS satellites.

[0024] In addition, the smartphone 3 includes a long-distance communication circuit 312, an antenna 312a of the long-distance communication circuit 312, a CMOS sensor 313, an imaging device 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 a subject according to the control of the CPU 301 to obtain image data. The imaging device 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 electrical signal. The speaker 316 is a built-in circuit that converts an electrical signal into physical vibrations to produce sounds such as music and voices. The audio input / output I / F 317 is a circuit that processes the input / output of audio signals between the microphone 315 and the speaker 316 according to the control of the CPU 301. The display 318 is a type of display means such as a liquid crystal or an 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 for operating the smartphone 3 when the user presses the display 318.

[0026] Also, the smartphone 3 includes a bus line 310. The bus line 310 is an address bus, a data bus, etc. for electrically connecting each component such as the CPU 301 shown in FIG. 3.

[0027] <Hardware Configuration of Smart Lock> FIG. 4 is a hardware configuration diagram of the 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 to drive 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 locks or unlocks 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 each device and the like for constructing the remote control system 1 will be described. FIG. 5 is a functional block diagram of each device and the like that make up the remote control system 1.

[0031] <Functional Configuration of the 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 the PC) The transmission / reception unit 21 of PC2 is realized by the processing of CPU201 for network I / F209, and transmits and receives various data (or information) to and from other devices via communication network 100.

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

[0035] The display control unit 24 is mainly realized by the processing of CPU201, and causes various images to be displayed on display 208.

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

[0037] <Functional configuration of smartphone> As shown in FIG. 5, smartphone 3 has a transmission / reception unit 31, a reception unit 32, an acquisition unit 33, a display control unit 34, and a storage / reading processing unit 39. Each of these units is a function or means realized by any of the components shown in FIG. 5 operating according to instructions from CPU301 according to a program for smartphones developed from EEPROM304 onto RAM303.

[0038] Also, smartphone 3 has a storage unit 3000 constructed by ROM302, RAM303, and EEPROM304 shown in FIG. 3.

[0039] (Functional configurations of smartphone) The transmission / reception unit 31 of smartphone 3 is mainly realized by the processing of CPU301 for long-distance communication circuit 312, and transmits and receives various data (or information) to and from other devices via 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 mainly realized by the processing of the CPU 301 on the imaging element I / F 314 and the processing by the CPU, causes the CMOS 313 to capture a QR code, and acquires the data embedded in the QR code from the captured image.

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

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

[0044] <Function configuration of the reservation management server> As shown in FIG. 5, the reservation management server 5 has a transmission / reception unit 51 and a storage / reading processing unit 59. Each of these units is a function or means realized by operating any of the components shown in FIG. 2 according to an instruction from the CPU 501 according to the program for the reservation management server developed on the RAM 503 from the HD 504.

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

[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 schedules of each user and the reservation of resources such as conference rooms. In the storage unit 5000, a reservation management DB 5001 configured by a reservation management table as shown in FIG. 6 is constructed. In this reservation management table, a reservation ID, a reserving user account, an event name, a resource ID, a start date and time, an end date and time, and an expected participant account are managed in association with each other.

[0047] Among these, the reservation ID is an example of reservation identification information for identifying a specific reservation. The reserving user account is the account of the user (person) who reserved the use of resources such as a conference room. In the record with the reservation ID "R001", the e-mail address of user a is shown as the account of user a. The reserving user account is an example of user identification information. The event name indicates the name of a meeting or the like held using resources such as a conference room. The resource ID is an example of resource identification information for identifying resources 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 expected participant account is the account of the user who plans to participate in the event. Here, similar to the reserving user account, the e-mail address of the expected participant is shown. The expected participant account is an example of expected participant identification information.

[0048] Note that the event name, the resource ID, the start date and time, and the end date and time constitute reservation information.

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

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

[0051] <Functional Configuration of the Intermediary Server> As shown in FIG. 5, the intermediary server 6 has a transmission / reception unit 61, an authentication unit 62, a creation unit 63, and a storage / reading processing unit 69. 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 601 according to a program for the intermediary server deployed from the HD 604 onto the RAM 603.

[0052] Further, the intermediary server 6 has a storage unit 6000 constructed by the ROM 602 and the HD 604 shown in FIG. 2.

[0053] (User Management Table) FIG. 7(a) is a conceptual diagram showing the user management table. The user management table is a table for managing personal information of users. In the storage unit 6000, a user management DB 6001 configured by a user management table as shown in FIG. 7(a) is constructed. In this user management table, the organization ID, user account, and user name are managed in association with each other.

[0054] Among these, the organization ID is an example of organization identification information for identifying the organization (business operator) 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. When the user is a reserving person, the user account is managed as the reserving person's account in the above-described reservation information management table. When the user is a person scheduled to participate, the user account is managed as the person scheduled to participate's account in the above-described reservation information management table. The user name is the name of the user.

[0055] (Event Management Table) Figure 7(b) is a conceptual diagram showing an event management table. The event management table is a table for managing detailed information about events such as meetings. In the storage unit 6000, an event management DB6002 composed of an event management table as shown in Figure 7(b) is constructed. In this event management table, in addition to each piece of information (reservation ID, reserving account, event name, resource ID, start date and time, end date and time, and planned participant account) managed by the above-described reservation management table, information on the event state is associated and managed. Note that the explanation of the same information as each piece of information managed by the above-described reservation management table is omitted. The event state is information mainly indicating the state of an event such as a meeting.

[0056] (Key type management table) Figure 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. In the storage unit 6000, a key type management DB6003 composed of a key type management table as shown in Figure 7(c) is constructed. In this key type management table, the organization ID, resource name, resource ID, key type, driving device ID, and access location information are associated and managed.

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

[0058] Also, the type of key indicates the type of method for unlocking and locking. Here, as examples of the type of key, "electronic key", "physical key", and "none" are shown. "Electronic key" indicates a method of causing a drive device such as the smart lock 9 to unlock and lock using electronic information such as authentication information by remote control. "Physical key" indicates a method in which the user inserts a physical key such as metal into the keyhole to unlock and lock without using a drive device such as the smart lock 9. "None" indicates a case where a key is not required to open and close the door.

[0059] The drive device ID is an example of drive device identification information for identifying a drive device such as the smart lock 9. The access location information indicates information on the location of different access destinations depending on the type of key.

[0060] The access destination location when the key type is "electronic key" indicates information on the location accessed by the mediation server 6 via the communication network 100. Here, the URL of the drive control server 7 is shown as the information on the accessed location.

[0061] The access destination location when the key type is "physical key" indicates the location accessed by the user. Here, the 1F security room where the physical key is managed is shown as the information on the accessed location.

[0062] When the key type is "none", since a key is not required to open and close the door, there is no information on the access destination location.

[0063] (Each functional configuration of the mediation server) The transmission / reception unit 61 of the mediation server 6 is realized by the processing of the CPU 601 with respect to 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 authenticates whether the person making the reservation is a legitimate person for reserving resources 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 the information read from each of the DBs 6001, 6002, and 6003.

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

[0067] <Functional Configuration of Drive Control Server> As shown in FIG. 7, the drive control server 7 includes a transmission / reception unit 71, an issuance unit 72, a determination unit 75, and a storage / reading processing unit 79. 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 701 according to a program for the drive control server expanded 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 the HD 704 shown in FIG. 2.

[0069] (Drive Device Management Table) FIG. 8 is a conceptual diagram showing a drive device management table. The drive device management table is a table for managing information related to drive devices such as the smart lock 9. In the storage unit 7000, a drive device management DB 7001 configured by a drive device management table as shown in FIG. 8 is constructed. In this drive device management table, the drive device ID, the destination information of the drive device, the authentication information, the expiration period of the authentication information, and the state of the drive device are managed in association with each other.

[0070] Among these, the drive device ID is the same as the drive device ID managed in the above-described key type management table. With this drive device ID, the mediation server 6 and the drive control server 7 can perform cooperative processing.

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

[0072] The authentication information is information necessary for authentication when the drive device such as the smart lock 9 unlocks or locks. The authentication information is, for example, a passcode, a password, or the like.

[0073] The validity period of the authentication information indicates the period during which the drive control server 7 can effectively use the authentication information. Thus, as shown in FIG. 8, even for the same drive device (drive device ID "d001"), since the authentication information and the validity period of the authentication information are different, even for the same resource such as a conference room, the smart lock 9 cannot be unlocked and locked outside the period reserved by the reserver.

[0074] The state of the drive device indicates the state of unlocking or locking by the drive device such as the smart lock 9.

[0075] (Each functional configuration of the drive control server) The transmission / reception unit 71 of the drive control server 7 is realized by the processing of the CPU 701 with respect to 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 mainly realized by the processing of the CPU 701 and issues authentication information.

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

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

[0079] <Functional Configuration of Smart Lock> As shown in FIG. 5, the smart lock 9 has a transmission / reception 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 according to an instruction from the CPU 901 according to a program for the smart lock deployed from the NVRAM 904 onto the RAM 903.

[0080] (Functional Configurations of Smart Lock) The transmission / reception 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 mainly realized by the processing of the CPU 901, drives the opening / closing mechanism 905, and performs unlocking or locking.

[0082] [Processing and Operations of Embodiment] Subsequently, with reference to FIGS. 9 to 24, the processing or operations of this embodiment will be described.

[0083] <Reservation Registration Processing> First, with reference to FIGS. 9 to 12, the case where the user a uses the PC 2 to reserve Conference Room A, which is an example of a resource, in the reservation management server 5 will be described. FIG. 9 is a sequence diagram showing the reservation registration processing. FIG. 10 is a diagram showing an example of a scheduled input screen.

[0084] User a uses PC2 to input reservation information (event name, resource, event start time, event end time) and scheduled participants into the reservation input screen 1560 as shown in FIG. 10, and the reception unit 22 receives the input or selection of the reservation information and the scheduled participants (S21). This reservation input screen 1560 includes an input field 1561 for entering the event name, an input field 1562 for entering the resource name, an input field 1563 for entering the scheduled start date and time of the event, an input field 1564 for entering the scheduled end date and time of the event, a display area 1565 for displaying the name of the reserving person (the account of the reserving person), and a selection field 1566 for selecting the names of the scheduled participants other than the reserving person (the accounts of the scheduled participants). Here, the accounts of the reserving person and the scheduled participants use their respective email addresses.

[0085] Subsequently, the transceiver 21 of PC2 transmits each piece of information (reserving person account, participant account, reservation information) input or selected in step S22 to the reservation management server 5 (S22). Thereby, the transceiver 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 for the reservation from the PC of an approver such as a supervisor via the communication network 100.

[0086] Next, in the reservation management server 5, the storage / reading processing unit 79 attaches a reservation ID to each piece of information received in the reservation step S22 and stores and manages it in the reservation management DB5001 (S23). Then, the transceiver 51 transmits a completion notice indicating that the reservation is completed to PC2 (S24). Thereby, the transceiver 21 of PC2 receives the completion notice.

[0087] Also, in the reservation management server 5, the transmission / reception unit 51 transmits each piece of information (reservation ID, the account of the person making the reservation, the accounts of the participants, reservation information) stored in step S23 to the mediation server (S25). As a result, the transmission / reception unit 61 of the mediation server 6 receives each piece of information. Note that step S25 may be executed as this response by periodically making an inquiry to the reservation management server 5 by polling from the mediation server 6.

[0088] Next, the mediation server 6 authenticates the user based on whether the account of the person making the reservation received in step S25 is managed in the user management DB6001 as a user account (S26).

[0089] (If not a legitimate user) Subsequently, with reference to FIG. 11, the case where user a is not a legitimate user due to user authentication in step S26 will be described. FIG. 11 is a sequence diagram showing the processing in the case of not being a legitimate user.

[0090] As shown in FIG. 11, the transmission / reception unit 61 of the mediation 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 transmission / reception unit 51 of the reservation management server 5 receives the reservation cancellation request.

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

[0092] Furthermore, the creation unit 63 of the mediation server 6 creates a reservation unavailable message indicating that a reservation cannot be made for the PC 2 (S33). Then, the transmission / reception unit 61 transmits the reservation unavailable message created in step S33 to the PC 2 (S34). In this case, since the reservation account received by the transmission / reception unit 61 of the mediation server 6 in step S25 is an email address, the transmission / reception unit 61 transmits the reservation unavailable message to this email address. As a result, the transmission / reception unit 21 of the PC 2 receives the reservation unavailable message. Then, on the PC 2, the display control unit 24 displays the reservation unavailable message on the display 208 (S35).

[0093] (In the case of a legitimate user) Subsequently, with reference to FIG. 12, the case where the user a is a legitimate user through user authentication in step S26 will be described. FIG. 12 is a flowchart showing the key type determination process performed by the mediation server in the case of a legitimate user.

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

[0095] Next, the storage / read processing unit 69 reads the corresponding key type information by searching the key type management DB 6003 using the resource ID in the reservation information stored in step S41 as a search key (S42). When the key type is "electronic key", the processes after step S61 described later are executed. When the key type is "physical key", the processes after step S81 described later are executed. Furthermore, when the key type is "none", that is, when there is no key, the processes after step S101 are executed. Therefore, the processes for each type will be described below.

[0096] (When the key type is an electronic key) First, with reference to FIGS. 13 and 14, the case where the key type is an "electronic key" will be described. FIG. 13 is a sequence diagram showing the process of transmitting 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] As shown in FIG. 13, the storage / reading processing unit 69 of the mediation 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, thereby reading 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 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 and stores the authentication information issued in step S63 with the record of the same drive device ID as the drive device ID received in step S62 in the drive device management DB 7001 for management (S64).

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

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

[0101] Next, the storage / reading 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, by searching the event management DB6002 using the reserved person account received in step S41 as a search key, the corresponding reservation information is read out (S68). Then, the creation unit 63 uses the authentication information received in step S65 and the respective information read out in steps S66 to S68 (reservation name (name of the reserved user), resource name, reservation information) to create, as shown in FIG. 14, a message for conveying information indicating that the reservation has been completed together with the authentication information (S69).

[0103] Next, the transmission / reception unit 61 of the mediation server 6 transmits, to the PC2, a message for conveying information indicating that the reservation has been completed together with the authentication information created in step S69 (S70). As a result, the transmission / reception unit 21 of the PC2 receives this message.

[0104] Note that the authentication information may always have the same content. In this case, the drive control server 7 does not execute the process of step S63, but adjusts the timing of transmitting the authentication information in step S70. For example, the mediation server 6 transmits the authentication information 10 minutes before the start of the meeting. Also, in step S70, the mediation server 6 may transmit the reservation completion message not only to the PC2 of the reserved person (user a) but also to the PCs of some or all of the participants who are scheduled to participate in the same meeting.

[0105] Next, the storage / read processing unit 69 manages the "event status" column of the record of the reserved person account read out in step S68 in the event management DB6002 as "notification of authentication information completed" (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 PC2, the display control unit 24 causes the display 208 to display a message screen as shown in FIG. 14. As a result, the reserved person (user a) can, by inputting or selecting reservation information or the like in step S21 above, obtain information indicating that the reservation has been completed together with the authentication information necessary for unlocking the resource in step S72.

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

[0108] As shown in FIG. 15, the storage / reading processing unit 69 of the mediation server 6 searches the key type management DB6003 using the resource ID in the reservation information received in step S25 as a search key, and reads out the corresponding drive device ID and access location information (S81). Here, unlike the case of the "electronic key" described above, since there is no process of obtaining authentication information from the drive control server 7 (S62 to S65), the storage / reading processing unit 69 searches the user management DB6001 using the reservationist (user a) account received in step S25 as a search key, and reads out the corresponding user name (S82).

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

[0110] Next, the event management DB6002 is searched using the reservationist account received in step S41 as a search key, and the corresponding reservation information is read out (S84). Then, the creation unit 63 uses each piece of information read out in steps S81 to S84 (access location information, reservation name (reserved user name), resource name, reservation information) to create a message for transmitting information indicating that the reservation has been completed together with the access location information as shown in FIG. 16 (S85). Here, since the key type is a "physical key", as shown in FIG. 16, the location where the physical key is managed (for example, the 1F security room) is shown.

[0111] Next, the transmission / reception unit 61 of the mediation server 6 transmits a message to the PC 2 to convey the information indicating that the reservation is completed together with the information on the access location created in step S85 (S86). As a result, the transmission / reception unit 21 of the PC 2 receives this message. Then, the storage / read processing unit 69 manages the "event status" column of the record of the reservation account read in step S84 as "notified of access location information" in the event management DB 6002 (S87). As a result, the "event status" column that was not managed in step S41 is managed with new information.

[0112] Next, in the PC 2, the display control unit 24 causes the display 208 to display a message screen as shown in FIG. 16 (S88). As a result, the reserving person (user a) can obtain, in step S88, the information indicating that the reservation is completed together with the information on the physical access location necessary for unlocking the resource by inputting or selecting reservation information or the like in step S21.

[0113] (When not using a key) Subsequently, with reference to FIGS. 17 and 18, the case where the type of key is "none" will be described. FIG. 17 is a sequence diagram showing the process of transmitting a message in the case where the type of key is "none". FIG. 18 is an example of a screen displayed on the PC when the type of key is "none". Here, since the type of key is "none", that is, there is no key itself, the storage / read processing unit 69 does not need to read the access location information as in step S61 (S81).

[0114] As shown in FIG. 17, the storage / read processing unit 69 reads out the corresponding user name using the reservation account of the reserving person (user a) received in step S25 as a search key for the user management DB 6001 (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, and reads out the corresponding resource name (S102).

[0116] Next, by searching the event management DB6002 using the reserved person account received in step S41 as a search key, the corresponding reservation information is read out (S103). Then, the creation unit 63 creates a message for notifying reservation completion as shown in FIG. 18 using each piece of information read in steps S101 to S103 (reservation name (name of the user who made the reservation), resource name, reservation information) (S104).

[0117] Next, the transmission / reception unit 61 of the mediation server 6 transmits a message for notifying reservation completion created in step S85 to the PC2 (S105). As a result, the transmission / reception unit 21 of the PC2 receives the message for notifying reservation completion. Then, the storage / reading processing unit 69 manages the "event status" column of the record of the reserved person account read in step S103 as "notified of reservation completion" in the event management DB6002 (S106). As a result, the "event status" column that was not managed in step S41 is managed with new information.

[0118] Next, on the PC2, the display control unit 24 causes the display 208 to display a message screen as shown in FIG. 16. As a result, the reserved person (user a) can obtain information indicating that the reservation has been completed in step S107 by inputting or selecting reservation information or the like in step S21.

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

[0120] First, user a operates the smartphone 3, and the acquisition unit 33 captures the QR code shown by the door 8 as shown in FIG. 1, thereby acquiring access destination information such as the resource ID and URL incorporated in the QR code (S121). Further, the storage / read processing unit 39 reads out the reservation account as 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 mediation 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 account (user a) read out in step S122. As a result, the transmission / reception unit 61 of the mediation server 6 receives the request for reservation information (S123).

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

[0122] Next, by searching the event management DB6002 using the reservation account received in step S123 as a search key, all reservation IDs and reservation information on the event execution date are read out (S125).

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

[0124] Next, the transmission / reception unit 61 of the mediation server 6 transmits the reservation content message created in step S127 to the smartphone 3 (S128). This reservation content message incorporates a reservation ID. As a result, the transmission / reception unit 31 of the smartphone 3 receives this message.

[0125] Next, on the smartphone 3, the display control unit 34 causes the display 318 to display a message screen as shown in Fig. 16(a) (S129). This message screen has a resource name (Conference Room A) display column 401, an event name (Regular Meeting) display column 402, start date / time and end date / time display columns 403, a reserved person name (User a) display column 404, and start date / time and end date / time display columns 407 of other events on the same day. Also, on this message screen, a "Start" button 411 and a "Cancel" button 412 are displayed. The "Start" button 411 is a button pressed by the reserved person or the like when remotely operating the smart lock 9 to unlock it and start the event. The "Cancel" button 412 is a button pressed by the reserved person or the like when remotely operating the smart lock 9 to unlock it and stop starting the event. Note that it may be an "Unlock" button instead of the "Start" button.

[0126] Here, when the reserved person (User a) presses the "Start" button 411, the reception unit 32 receives the operation of remotely operating the smart lock 9 to unlock it and start the event (S130). As a result, the display control unit 34 pops up and displays 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 has an authentication information input column 451 for inputting authentication information, an "OK" button 452, and a "Cancel" button 453. The "OK" button 452 is a button for pressing when the reserved person (User a) confirms the authentication information input in the authentication information input column 451. The "Cancel" button 453 is a button for pressing when the reserved person (User a) cancels the authentication information input in the authentication information input column 451.

[0127] Here, when the reserving user (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] Subsequently, after the process of step S132, as shown in FIG. 20, the transmission / reception unit 31 transmits a unlocking request for the smart lock 9 and a start request for the event to the mediation server 6 (S141). This unlocking request and start request include the reservation ID received in step S128 and the authentication information received in step S132. Accordingly, the transmission / reception unit 61 of the mediation server 6 receives the unlocking request and start request.

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

[0130] Next, the storage / reading processing unit 69 searches the key type management DB6003 using the resource ID read out in step S142 as a search key, and reads out the corresponding drive device ID and access location information (S143). Then, the transmission / reception unit 61 transmits a start request for 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 out in step S143 and the authentication information received in step S141. Accordingly, the transmission / reception unit 71 of the drive control server 7 receives the start request for remote control.

[0131] Next, in the drive control server 7, the storage / reading processing unit 79 searches the drive device management DB7001 using the drive device ID received in step S144 as a search key, and reads out the information on the valid 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, in 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, a continuous explanation will be given.

[0133] Next, the storage / read processing unit 79 searches the drive device management DB7001 using the drive device ID received in step S144 as a search key, and reads out the destination information (e.g., IP address) of the corresponding drive device (S147). Then, the transmission / reception unit 71 transmits a unlocking request to the smart lock 9 indicated by the destination information of the drive device 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 perform unlocking (S149). As a result, the smartphone 3 can perform remote unlocking of the smart lock 9 via the mediation server 6 and the drive control server 7.

[0135] Subsequently, as shown in FIG. 24, the transmission / reception 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 transmission / reception 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 "status of the drive device" column in the record of the drive device ID received in step S144 from "locked" to "unlocked" (S162). Then, the transmission / reception unit 71 of the drive control server 7 transmits a response indicating that the unlocking has been completed to the mediation server 6 (S163). As a result, the transmission / reception unit 81 of the mediation server 6 receives the response.

[0137] Next, in the mediation server 6, the memory / read processing unit 69 changes the "event state" column in the record of the reservation ID received in step S141 from "notification of authentication information completed" to "event start" (S164). Then, the transmission / reception unit 61 of the mediation server 6 transmits a response indicating that the unlocking has been completed to the smartphone 3 (S165). As a result, the transmission / reception unit 31 of the smartphone 3 receives the response.

[0138] Next, in the smartphone 3, as shown in FIG. 22(c), the display control unit 34 displays an "End" button 413 (S166). This "End" button 413 is a button that is pressed by the reservation maker (user a) or the like when ending the event, contrary to the "Start" button 411 in FIG. 22(a). Thereby, the reservation maker (user a) can not only recognize that the unlocking has been performed by the sound when the smart lock 9 is unlocked, but also can recognize that the unlocking has been performed by the display of this "End" button 413.

[0139] In addition, in FIG. 22(b), if the reservation maker (user a) makes a mistake in inputting the authentication information, as shown in FIG. 22(d), the display control unit 34 pops up and displays an authentication information re-input screen 460 for re-inputting the authentication information. As shown in FIG. 22(d), on the authentication information re-input screen 460, an authentication information input field 461 for re-inputting the authentication information, an "OK" button 462, and a "Cancel" button 463 are displayed. The "OK" button 462 is a button to be pressed when the reservation maker (user a) confirms the authentication information input in the authentication information input field 451. The "Cancel" button 463 is a button to be pressed when the reservation maker (user a) cancels the authentication information input in the authentication information input field 461. Here, when the reservation maker (user a) re-inputs the authentication information obtained in step S72 in the authentication information input field 461 and presses the "OK" button 462, the reception unit 32 accepts the re-input of the authentication information (S132).

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

[0141] First, after the event ends and all of the reserving person and participants leave Conference Room A, when the reserving person (user a) presses the "End" button 413 shown in FIG. 22(c), the reception unit 32 receives the unlocking of the drive device and the end of the event (S181).

[0142] Next, as shown in FIG. 23, the transmission / reception unit 31 transmits a locking request for the smart lock 9 and an event end request to the mediation server 6 (S182). This locking request and end request include the reservation ID received in step S182. As a result, the transmission / reception unit 61 of the mediation server 6 receives the locking request and end request.

[0143] Next, in the mediation server 6, the storage / read processing unit 69 searches the event management DB6002 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 DB6003 using the resource ID read in step S183 as a search key, and reads out the corresponding drive device ID and access location information (S184). Then, the transmission / reception unit 61 transmits a request to start remote control for 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 device management DB7001 using the drive device ID received in step S185 as a search key, and reads out the destination information (e.g., IP address) of the corresponding drive device (S186). Then, the transmission / reception unit 71 transmits a locking request to the smart lock 9 indicated by the destination information of the drive device 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 perform locking (S188). As a result, the smartphone 3 can perform remote locking on the smart lock 9 via the mediation server 6 and the drive control server 7.

[0147] Subsequently, as shown in FIG. 24, the transmission / reception 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 transmission / reception 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 "drive device status" column in the record of the drive device ID received in step S185 from "unlocking" to "locking" (S202). Then, the transmission / reception unit 71 of the drive control server 7 transmits a response indicating that the locking has been completed to the mediation server 6 (S203). As a result, the transmission / reception unit 81 of the mediation server 6 receives the response.

[0149] Next, in the mediation server 6, the storage / read processing unit 69 changes the "event status" column in the record of the reservation ID received in step S182 from "event start" to "event end" (S204). Then, the transmission / reception unit 61 of the mediation 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, on the smartphone 3, the display control unit 34 causes a message indicating that the locking has been completed to be displayed on the display 318. The "End" button 413 is also displayed. As a result, the reserving person (user a) can not only recognize that the unlocking was done by the sound when the smart lock 9 locks, but also recognize 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 mediation server 6 mediates the processing between the reservation management server 5 that manages the reservation of the resource received from the PC 2 that makes the reservation registration, and the drive control server 7 that remotely controls the smart lock 9 for unlocking the resource, thereby providing the PC 2 with the authentication information necessary for unlocking the smart lock 9 for unlocking the reserved resource. As a result, it is possible to suppress the complication of the processing of the reserving person (user).

[0152] 〔Supplementary Explanation〕 The above QR code is an example of the information providing object. The information providing object includes, in addition to the QR code, an IC tag, a beacon transmitter, and the like.

[0153] When the information providing object is an IC tag, the acquisition unit 33 of the smartphone 3 is realized by the processing of the CPU 301 for the short-range communication circuit 320, rather than the processing of the CPU 301 for the image pickup device 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), Bluetooth (registered trademark) (see S121). Since the IC tag is attached to a structure such as the door 8, the IC tag is associated with the resource.

[0154] On the other hand, when the information provider is a beacon transmitter, the acquisition unit 33 of the smartphone 3 is realized by the processing of the CPU 301 for the short-range communication circuit 320 instead of the processing of the CPU 301 for the imaging device I / F 314. When the smartphone 3 enters the radio wave area of the beacon transmitter, the smartphone 3 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 the door 8, etc., so that the beacon transmitter is linked to the resource.

[0155] Also, in the above, an example in which a QR code sticker, an IC tag, and a beacon transmitter are attached to the door 8 of the conference room, etc. has been described, but it is not limited to this. For example, instead of the door 8, it may be attached to a structure such as a wall portion other than the door of the conference room where the door 8 is installed.

[0156] Furthermore, in the above, a conference room which is a shared resource is shown as an example of the resource, but it is not limited to this. For example, as another example of the resource, a moving body such as an aircraft, a vehicle, or a ship which is a shared resource may be used. Also, the smart lock 9 may not be attached to the outer plate of the door, but may be a 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 can be used for car sharing of the vehicle.

[0157] Also, in the above, the case where the remote control system remotely controls unlocking and locking has been described, but at least one of unlocking and locking may be remotely controlled.

[0158] Each component such as each CPU 201, 301, 501, 601, 701, etc. may be single or plural.

[0159] In addition, each function in the above-described embodiments 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 like a processor implemented by an electronic circuit, an ASIC (Application Specific Integrated Circuit) designed to execute each of the above-described functions, a DSP (digital signal processor), an FPGA (field programmable gate array), an SOC (System on a chip), a GPU, and devices such as conventional circuit modules.

Explanation of Signs

[0160] 1 Remote control system 2 PC (an example of a registration terminal) 3 Smart lock (an example of a communication terminal) 5 Reservation management server 6 Mediation server 7 Drive control server 8 Door 9 Smart lock (an example of a driving device) 10 QR code 10 (an example of an information provider) 61 Transmission / reception unit (an example of transmission means, an example of reception means) 62 Authentication unit 63 Creation unit 69 Storage / reading processing unit 100 Communication network 6000 Storage unit 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

Claims

1. a receiving means for receiving resource identification information for identifying the resource from a reservation management device that manages the reservation of the resource; a transmission means for transmitting a request for authentication information for unlocking the lock by a drive device associated with the received resource identification information to a drive control device that manages the drive device; having The receiving means receives the authentication information from the drive control device, The transmission means transmits a remote control start request including the authentication information to the drive control device.

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. The intermediary device according to any one of claims 1 to 4, wherein the driving device is a smart lock.

6. A receiving means for receiving resource identification information for identifying a resource from a reservation management device that manages reservations for the resource, and for receiving authentication information for unlocking a key by a drive control device that manages a drive device installed on the resource from a drive control device that manages the drive device; a transmission means for transmitting a remote control start request including the authentication information to the drive control device; having An intermediary device 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.

7. 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 the resource from a reservation management device that manages the reservation of the resource; a transmission means for transmitting a request for authentication information for unlocking the lock by a drive device associated with the received resource identification information to a drive control device that manages the drive device; having The receiving means receives the authentication information from the drive control device, The transmission means transmits a remote control start request including the authentication information to the drive control device.

8. The computer a receiving step of receiving resource identification information for identifying the resource from a reservation management device that manages the reservation of the resource; a transmission step of transmitting a request for authentication information for unlocking the lock by a drive device that is installed in the resource and associated with the received resource identification information to a drive control device that manages the drive device; a receiving step of receiving the authentication information from the drive control device; 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:

9. On the computer, a receiving step of receiving resource identification information for identifying the resource from a reservation management device that manages the reservation of the resource; a transmission step of transmitting a request for authentication information for unlocking the lock by a drive device that is installed in the resource and associated with the received resource identification information to a drive control device that manages the drive device; a receiving step of receiving the authentication information from the drive control device; 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