JP7740726B2 - Processing System - Google Patents

Description

Article 30, Paragraph 2 of the Patent Act applies. Published by PR TIMES Co., Ltd. on October 12, 2022 at hppts://prtimes.jp/main/html/rd/p/000000113.000040203.html

Article 30, Paragraph 2 of the Patent Act applies. Published by Bitkey Co., Ltd. on October 12, 2022 at https://bitkey.co.jp/newsroom/20221012/

Article 30, Paragraph 2 of the Patent Act applies. Published by Nikkan Kogyo Shimbun Ltd. on October 13, 2022 at https://www.nikkan.co.jp/releases/view/145085

Article 30, Paragraph 2 of the Patent Act applies. Published by ONE COMPATH Co., Ltd. on October 13, 2022 at https://www.mapion.co.jp/news/release/000000113.000040203/

Article 30, Paragraph 2 of the Patent Act applies. Published by Excite Inc. on October 13, 2022 at https://www.excite.co.jp/news/article/Purtimes_2022-10-13-40203-113/

Article 30, Paragraph 2 of the Patent Act applies. Published by Asahi Interactive Inc. on October 13, 2022 at https://japan.zdnet.com/release/30790790/

Article 30, Paragraph 2 of the Patent Act applies. Published by Asahi Interactive Inc. on October 13, 2022 at https://japan.cnet.com/release/30790790/

Article 30, Paragraph 2 of the Patent Act applies. Published by CST Entertainment Inc. on October 13, 2022 at https://otakei.otakuma.net/prtimes/10132213878.html

Article 30, Paragraph 2 of the Patent Act applies. Published by Shogakukan Inc. on October 13, 2022 at https://dime.jp/company_news/detail/?pr=1255463

Article 30, Paragraph 2 of the Patent Act applies. Published by Blast Holdings Co., Ltd. on October 13, 2022 at https://www.seotools.jp/news/id_000000113.000040203.html

Article 30, Paragraph 2 of the Patent Act applies. Published by JORUDAN Co., Ltd. on October 12, 2022 at https://news.jorudan.co.jp/docs/news/detail.cgi?newsid=PT000113A000040203

Article 30, Paragraph 2 of the Patent Act applies. Published by Dwango Co., Ltd. on October 12, 2022 at https://news.nicovideo.jp/watch/nw11552074

Article 30, Paragraph 2 of the Patent Act applies. Published by Zaikei Shimbun Co., Ltd. on October 12, 2022 at https://www.zaikei.co.jp/releases/1823024/

Article 30, Paragraph 2 of the Patent Act applies. Published by THE BRIDGE Co., Ltd. on October 12, 2022 at https://thebridge.jp/prtimes/458202

Article 30, Paragraph 2 of the Patent Act applies. Published by Cytoscope Co., Ltd. on October 12, 2022 at https://news.toremaga.com/release/others/2409754.html

Article 30, Paragraph 2 of the Patent Act applies. Published on October 12, 2022 by the Yomiuri Shimbun Tokyo Headquarters, the Yomiuri Shimbun Osaka Headquarters, and the Yomiuri Shimbun Western Headquarters at https://yab.yomiuri.co.jp/adv/feature/release/detail/000000113000040203.html

Article 30, Paragraph 2 of the Patent Act applies. Published by Biglobe Inc. on October 12, 2022 at https://news.biglobe.ne.jp/economy/1012/prt_221012_9596551733.html

Article 30, Paragraph 2 of the Patent Act applies. Published by Scalar Communications Inc. on October 12, 2022 at https://news.fresheye.com/prtimes/article/pr-000000113.000040203.html

Article 30, Paragraph 2 of the Patent Act applies. Published by Nifty Corporation on October 12, 2022 at https://business.nifty.com/cs/catalog/business_release/catalog_prt000000113000040203_1.htm

Article 30, Paragraph 2 of the Patent Act applies. Published by Jiji Press, Inc. on October 12, 2022 at https://www.jiji.com/err/index.php

Article 30, Paragraph 2 of the Patent Act applies. Published by OSDN Co., Ltd. on October 13, 2022 at https://mag.osdn.jp/pr/22/10/12/130020OSDN

Article 30, Paragraph 2 of the Patent Act applies. Published by Excite Inc. on October 12, 2022 at https://www.excite.co.jp/news/article/Purtimes_2022-10-12-40203-113/

Article 30, Paragraph 2 of the Patent Act applies. Published by IID Co., Ltd. on October 12, 2022 at https://www.newscafe.ne.jp/release/Purtimes2/20221012/1139489.html

Article 30, Paragraph 2 of the Patent Act applies. Published by Rakuten Group, Inc. on October 13, 2022 at https://news.infoseek.co.jp/article/prtimes_000000113_000040203/

Article 30, Paragraph 2 of the Patent Act applies. Published by Panasonic Holdings Corporation on October 12, 2022 at https://news.panasonic.com/jp/press/jn221012-1

Patent Act Article 30, Paragraph 2 applies. Published by Jutaku Shinpo Co., Ltd. on October 12, 2022 at https://www.jutaku-s.com/newsp/id/0000053421

Article 30, Paragraph 2 of the Patent Act applies. Published by KDDI Corporation on October 18, 2022 at https://mugenlabo-magazine.kddi.com/list/bitkey-panasonic/

Article 30, Paragraph 2 of the Patent Act applies. Published by Dempa Shimbun Co., Ltd. on October 13, 2022 at https://dempa-digital.com/article/361646

Article 30, Paragraph 2 of the Patent Act applies. Published by Rgene Co., Ltd. on October 12, 2022 at https://iotnews.jp/smart-building/206606/

Article 30, Paragraph 2 of the Patent Act applies. Published by Impress Corporation on October 12, 2022 at https://www.watch.impress.co.jp/docs/news/1446839.html

This disclosure relates to a processing system used to authenticate a user.

Patent Document 1 (Patent Document 1) has been known to date, describing a ticket gate management system that controls the opening and closing of ticket gates to manage entry and exit to a facility, comprising: a contactless information recording medium carried by a person entering or exiting the facility and storing management information necessary for entering or exiting through the ticket gate; a reader that reads the management information stored on the contactless information recording medium; a ticket gate device that opens the ticket gate when the contactless information recording medium is authenticated; and a control device that performs an authentication determination based on the management information read by the reader and controls the opening and closing of the ticket gate, wherein the control device determines whether the person is an individual entering or exiting the facility or a group entering or exiting with a reservation based on the management information read by the reader, and changes the processing procedures related to the authentication determination and the opening and closing control of the ticket gate based on the determination result.

JP 2010-86479 A

Based on the above technologies, the present disclosure aims to provide a processing system that enables more efficient user authentication through various embodiments.

One aspect of the present disclosure provides a processing device including: "a first communication interface configured to communicatively connect with a first authentication device installed in equipment whose use by a user is restricted in order to determine whether to allow the user to use the equipment by authenticating the user using a first authentication method that uses first authentication information; a second communication interface configured to receive, from a second authentication device different from the first authentication device, permission information used to allow the user to use the equipment by authenticating the user using a second authentication method different from the first authentication method; and a processor configured to execute processing to transmit the permission information to the first authentication device upon receiving the permission information from the second authentication device."

One aspect of the present disclosure provides a processing device including: a first communication interface configured to communicatively connect with a first authentication device installed in equipment whose use by a user is restricted in order to determine whether to allow the user to use the equipment by authenticating the user using a first authentication method that uses first authentication information; a second communication interface configured to receive, from a second authentication device different from the first authentication device, permission information used to allow the user to use the equipment by authenticating the user using a second authentication method different from the first authentication method; and at least one processor; and a processing program that causes the at least one processor to execute a process for transmitting the permission information to the first authentication device upon receiving the permission information from the second authentication device.

One aspect of the present disclosure provides a processing method executed by at least one processor in a processing device including: a first communication interface configured to communicatively connect with a first authentication device installed in equipment whose use by a user is restricted in order to determine whether to allow the user to use the equipment by authenticating the user using a first authentication method using first authentication information; a second communication interface configured to receive, from a second authentication device different from the first authentication device, acceptance information used to allow the user to use the equipment by authenticating the user using a second authentication method different from the first authentication method; and at least one processor, the processing method including a step of transmitting the acceptance information to the first authentication device upon receiving the acceptance information from the second authentication device.

One aspect of the present disclosure provides a server device including at least one processor, the server device being configured to execute the following processes: receive first log information indicating that a user has been authenticated from a first authentication device installed in a facility where user access is restricted, the first log information being received from the first authentication device, the first authentication device being installed to authenticate the user using a first authentication method and determine whether or not to allow the user to use the facility, upon receipt of an authentication request from the user using first authentication information; receive second log information indicating that the user has been authenticated from the first authentication device upon receipt by the first authentication device of allowance information generated by authenticating the user using a second authentication method different from the first authentication method; and store the first log information and the second log information.

According to one aspect of the present disclosure, there is provided a program that causes a computer having at least one processor to execute processing to receive, from a first authentication device installed in a facility where user access is restricted, first log information indicating that the user has been authenticated, the first log information indicating that the user has been authenticated, the first log information being received from the first authentication device, the first authentication device being installed to authenticate the user using a first authentication method and determine whether or not to allow the user to use the facility, upon receipt of an authentication request from the user using first authentication information from the user, and second log information indicating that the user has been authenticated upon receipt by the first authentication device of allowance information generated by authenticating the user using a second authentication method different from the first authentication method, and storing the first log information and the second log information.

One aspect of the present disclosure provides a method executed by at least one processor in a computer having the at least one processor, the method including: receiving first log information indicating that the user has been authenticated from a first authentication device installed in a facility where user access is restricted, the first log information being received when the facility receives an authentication request from the user using first authentication information, the first log information being received from the first authentication device, the first log information being received when the facility receives acceptance information generated by authenticating the user using a second authentication method different from the first authentication method, and the second log information being received from the first authentication device.

According to one aspect of the present disclosure, there is provided a processing system including a server device and a processing device, configured to execute the following processing: upon receiving an authentication request from a user using first authentication information in a facility where user use is restricted, the server device receives first log information indicating that the user has been authenticated from a first authentication device installed to authenticate the user using a first authentication method and determine whether to allow the user to use the facility; the server device outputs acceptance information generated by authenticating the user using a second authentication method different from the first authentication method to provide to the processing device; upon receiving the acceptance information output from the server device, the processing device transmits the acceptance information to the first authentication device; upon receiving the acceptance information from the first authentication device, the server device receives second log information indicating that the user has been authenticated from the first authentication device; and the server device stores the first log information and the second log information.

According to one aspect of the present disclosure, there is provided a processing program that causes a processing system including a server device and a processing device to function as follows: upon receiving an authentication request from a user using first authentication information in a facility where user use is restricted, the server device receives first log information indicating that the user has been authenticated from a first authentication device installed to authenticate the user using a first authentication method and determine whether to allow the user to use the facility; the server device outputs acceptance information generated by authenticating the user using a second authentication method different from the first authentication method to provide to the processing device; upon receiving the acceptance information output from the server device, the processing device transmits the acceptance information to the first authentication device; upon receiving the acceptance information from the first authentication device, the server device receives second log information from the first authentication device indicating that the user has been authenticated; and the server device stores the first log information and the second log information.

According to one aspect of the present disclosure, there is provided a processing method executed in a processing system including a server device and a processing device, the processing method including: a step in which, upon receiving an authentication request from a user using first authentication information in a facility where user use is restricted, the server device receives first log information indicating that the user has been authenticated from a first authentication device installed to authenticate the user using a first authentication method and determine whether or not to allow the user to use the facility; a step in which the server device outputs acceptance information generated by authenticating the user using a second authentication method different from the first authentication method to provide to the processing device; a step in which the processing device transmits the acceptance information output from the server device to the first authentication device upon receiving the acceptance information; a step in which the server device receives second log information from the first authentication device indicating that the user has been authenticated upon acceptance by the first authentication device; and a step in which the server device stores the first log information and the second log information.

This disclosure provides a processing system method that enables more efficient user authentication.

The above effects are merely illustrative for the sake of convenience and are not limiting. In addition to or instead of the above effects, any effect described in this disclosure or any effect that would be obvious to one skilled in the art may be achieved.

FIG. 1 is a block diagram showing the configuration of a processing system 1 according to an embodiment of the present disclosure. FIG. 2A is a block diagram showing the configuration of a processing device 100 according to an embodiment of the present disclosure. FIG. 2B is a block diagram showing the configuration of the server device 200 according to an embodiment of the present disclosure. FIG. 3A is a diagram conceptually illustrating a user management table stored in the second server device 200-2 according to an embodiment of the present disclosure. FIG. 3B is a diagram conceptually illustrating a log management table stored in the second server device 200-2 according to an embodiment of the present disclosure. FIG. 3C is a diagram conceptually illustrating authority information according to an embodiment of the present disclosure. FIG. 4A is a diagram showing a processing sequence executed by the processing system 1 according to an embodiment of the present disclosure. FIG. 4B is a diagram showing a processing sequence executed by the processing system 1 according to an embodiment of the present disclosure. FIG. 4C is a diagram showing a processing sequence executed by the processing system 1 according to an embodiment of the present disclosure. FIG. 4D is a diagram showing a processing sequence executed by the processing system 1 according to an embodiment of the present disclosure. FIG. 4E is a diagram showing a processing sequence executed by the processing system 1 according to an embodiment of the present disclosure. FIG. 5 is a block diagram showing the configuration of a processing system 1000 according to an embodiment of the present disclosure. FIG. 6 is a diagram conceptually illustrating a user management table stored in the second server device 200-2 according to an embodiment of the present disclosure. FIG. 7A is a diagram showing a processing sequence executed by the processing system 1000 according to an embodiment of the present disclosure. FIG. 7B is a diagram showing a processing sequence executed by the processing system 1000 according to an embodiment of the present disclosure.

1. Overview of Processing System 1 In conventional buildings, for example, when a building gate uses a card reader for authentication, a user cannot enter or exit the gate unless they physically have a card. Therefore, if a user forgets their card, they are unable to enter or exit the building, and may need to go to a distant reception desk to report that they have forgotten their card and receive a spare card, resulting in inconvenient procedures. Furthermore, even if an authentication method different from the first authentication method is introduced to a building or a gate installed in the building, the introduction costs are high, and the administrator is burdened with additional wiring work and other issues. The processing system 1 disclosed herein is capable of authenticating users using a first authentication method via a first authentication device 300-1 in a facility with restricted user access. In addition, the second authentication device 300-2 can authenticate users using various authentication methods as a second authentication method via a processing device 100. This allows for easy expansion of authentication methods by retrofitting the processing device 100 without incurring significant introduction costs. Furthermore, by using biometric authentication such as face recognition as the second authentication method, it becomes unnecessary to carry a card, thereby improving convenience. Furthermore, it is possible to combine multiple methods, such as face recognition and device authentication or QR code recognition, as the second authentication method, further improving convenience.

Furthermore, the processing system 1 according to the present disclosure not only expands the authentication method, but also expands the authentication conditions. Conventional building control panels do not allow for flexible assignment of entry/exit conditions to a single user ID. For example, when controlling authorization based on reservation times, it may not be possible to set multiple dates or times in advance as conditions for entry/exit, or there may be an upper limit on the number of times that can be set for entry/exit. In addition, maintenance management of the building's control panel is performed by the building manager, so employees of companies occupying the building communicate directly with the building manager via email, etc., and authorization is only reflected in the control panel after a certain number of work days have passed. This creates the problem of not being able to flexibly set conditions for reservation times and entry/exit, and even if authorization conditions are changed, the changed conditions cannot be quickly reflected in the control panel.

The second server device 200-1 in the processing system 1 according to the present disclosure cooperates with the first server device 200-1 to which the building's control panel is connected, allowing the second server device 200-1 to flexibly set the dates and times for entry and exit conditions. Furthermore, by coordinating with the first server device 200-1 to which the building's control panel is connected, for example via an API, the second server device 200-1 can timely update the entry and exit conditions set on the second server device 200-1 in the control panel, making it possible to grant limited privileges to visitors at the time they check in at the building entrance based on the schedule information registered in advance by employees of the occupying company.

Furthermore, in conventional buildings, when a company or other entity occupying a building has already implemented an access control system, when a user authenticates at facilities other than the gate (such as the user's office), a different authentication method (e.g., facial recognition, etc.) may be set than the authentication method at the building gate (e.g., an authentication method using a card reader). In this case, while facial recognition or other authentication methods are possible at facilities other than the gate, a physical card must be used at the building gate, making it difficult to improve convenience. With the processing system 1 disclosed herein, the authentication method at the building gate can also be easily expanded by retrofitting the processing device 100 without incurring huge implementation costs. Using biometric authentication such as facial recognition as the second authentication method eliminates the need to carry a card, improving convenience throughout the entire building's access control system.

Furthermore, in conventional buildings, the building manager and the companies occupying the building manage different objects, making it difficult to manage access to the entire building in a unified manner. In other words, only the building manager can view the building's access control system; it is not intended for companies actually occupying the building. Therefore, when managing the access to an employee of a company actually occupying the building, there is a problem in that the access control for the employee's entry and exit at the building entrance is separated from the access control for the company's office. For example, when a user is authenticated by an authentication device installed at the building's gate, the time of authentication and the user are simply recorded, and the management company that manages the building manages this recorded information. Furthermore, when a user is authenticated by another authentication device installed in another facility (such as a conference room, conference booth, or office floor) within the building's gate, the time of authentication and the user are similarly recorded, and another company (e.g., a company occupying the building) that manages the other facility manages this recorded information. In other words, it is difficult to share information authenticated at the building gate and information authenticated at other facilities across businesses. With the processing system 1 disclosed herein, if both the building manager and a company located in building 10 use the same second server device 200-1 for privilege management, necessary information, such as employee information that can pass through and log information indicating authentication, can be shared between the two parties, while unnecessary information is kept confidential, allowing for more flexible expansion of authentication methods even between organizations. Furthermore, by collecting log information that includes not only the time and user of authentication but also information about the facility where the authentication was performed, it becomes possible to manage more detailed information, such as when, who, and where the authentication was performed.

Furthermore, the second server device 200-1 in the processing system 1 according to the present disclosure can assign a user-friendly name (e.g., "Gate in front of the elevator on the third floor of Building A" indicating the facility or location) to each authentication device installed at each door, pass-through point, and other facility on the management screen, and display the name and location together with a floor map. In addition to device management, it can also manage location information such as building information, floor information, conference room information, and seating information, and manage people information related to employees, external businesses, guests, and other people inside and outside the company. This allows for highly visible display of access history logs on the management screen, indicating who accessed the system, when, and where, providing a system that is easy for administrators to manage. By linking the second server device 200-1 with the first server device 200-1, the log information managed by the first server device 200-1 can be displayed with high visibility on the management screen connected to the second server device 200-1, making management easier for system administrators.

In other words, the processing system 1 according to the present disclosure is a system that, in a facility where user use is restricted, enables a first authentication device 300-1 to authenticate a user using a first authentication method, and a second authentication device 300-2 to authenticate a user using a second authentication method via a processing device. Typically, the first authentication device 300-1 has, for example, a card reader function, and acquires first authentication information when the user's ID card 500-1 is brought close to the first authentication device 300-1. The first authentication device 300-1 then authenticates the user using the acquired first authentication information. Once the user is authenticated, the first authentication device 300-1 transmits an unlock signal to the locking/unlocking device 400 connected via a communications network to lift the restrictions on use of the facility. This unlocks the gate connected to the locking/unlocking device 400, allowing the user to use the facility. In addition, the first authentication device 300-1 transmits permission log information, including information that restrictions on the user's use have been lifted and that the user's use has been permitted, as well as the time, in response to a request from the first server device 200-1. This allows the first server device 200-1 to manage the user's usage status.

Here, processing system 1, which performs such authentication processing, is typically used as equipment in buildings or gates installed in buildings.

FIG. 1 is a block diagram showing the configuration of a processing system 1 according to an embodiment of the present disclosure. According to FIG. 1, the processing system 1 includes a building 10, which is an example of a facility, in which a first authentication device 300-1 and a locking/unlocking device 400 are communicatively connected to each other via a communication network. Although not specifically shown, a gate installed in the building 10 is electrically connected to the locking/unlocking device 400. The gate opens and closes when the gate receives an unlock signal from the first authentication device 300-1 via the locking/unlocking device 400. The processing system 1 also includes a first server device 200-1 that is communicatively connected to the first authentication device 300-1 via a gateway 600 and a communication network. The first server device 200-1 transmits an identification code as first authentication information to the first authentication device 300-1 and receives user authorization log information from the first authentication device 300-1.

In this disclosure, a processing system 1 that already includes a first authentication device 300-1 and the like includes a processing device 100 that is communicatively connected to the first authentication device 300-1 via a communications network, a second authentication device 300-2 that is communicatively connected to the processing device 100 via a communications network, and a second server device 200-2 that is communicatively connected to the second authentication device 300-2 and the first server device 200-1 via a communications network. These processing devices 100 and second authentication devices 300-2 can be retrofitted to a building 10 that already has the first authentication device 300-1 and the like installed. Therefore, in addition to the first authentication method performed by the already installed first authentication device 300-1, authentication using the second authentication method can also be performed, allowing for flexible expansion of authentication methods and management of authentication information.

In this disclosure, "facility" typically refers to a building or a gate installed in a building, as described above. However, the facility may be any object subject to usage restrictions, the usage of which is restricted by users. Examples of such facility include the following:
-Providing space such as buildings, hotels, apartment complexes, houses, event facilities, or rooms (conference rooms, conference booths, residences) within buildings or apartment complexes,
- Gates and doors installed in the space that restrict the use of the space,
- Items with restricted use, such as electronic devices such as printers and computers, home appliances such as elevators and delivery boxes, or vehicles such as bicycles and cars

For ease of explanation, we will use an example where a building is used as the facility, but of course this is not limited to this.

In addition, in this disclosure, "administrator" simply means a person who manages each facility or each server device. Therefore, the administrator may be an individual or an organization such as a company or business. Furthermore, the entire processing system 1 does not need to be managed by the same administrator; the administrator who manages the building 10 and the first server device 200-1 and the administrator who manages the second server device 200-2 may be different individuals.

Furthermore, in this disclosure, "authentication" may be performed by any authentication method that is capable of authenticating a user. For example, depending on how the information used for authentication is held, examples of authentication include knowledge-based (e.g., memorization by the user), possession-based (e.g., ID card, smartphone, QR code, license, or token), biometric-based (e.g., fingerprint, voice, iris, or face), or a combination of these. Therefore, while terms such as first authentication method and second authentication method, first authentication device and second authentication device, and first authentication information and second authentication information are used in this disclosure, they can include any of the methods, devices, and information used to perform the authentication exemplified above.

For ease of explanation, the following description will be given assuming that the first authentication information, first authentication method, and first authentication device are an identification code (e.g., a six-digit number) that is unique information assigned to each user, a method in the first authentication device for determining whether the identification code matches or does not match, and a card reader for obtaining the identification code via near-field wireless communication from an ID card on which the identification code is stored. Similarly, the following description will be given assuming that the second authentication information, second authentication method, and second authentication device are usage certificate information, a method for authenticating a user based on a usage certificate, and a reader for reading usage certificate information from a user terminal device. However, this is not necessarily limited to this. Furthermore, the authentication information, authentication methods, and authentication devices do not need to be different from each other and may be the same type.

In addition, in this disclosure, a "user" may be any person who uses the facility. Examples of such users include employees of institutions occupying the building, residents of apartment complexes, and guests or service providers temporarily permitted to use the facility by employees or residents.

In addition, although terms such as "first" and "second" may be used in this disclosure, unless otherwise specified, these are merely names used for the convenience of explaining the two. Therefore, even if terms such as "first" and "second" are used, this does not mean that the elements are limited to those to which they are attached. Naturally, multiple elements such as "third," "fourth," "fifth," and more may also be included.

2. Configuration of the Processing Device 100 FIG. 2A is a block diagram showing the configuration of the processing device 100 according to one embodiment of the present disclosure. The processing device 100 does not need to include all of the components shown in FIG. 2A ; it may omit some components or add other components. Although not specifically shown, the processing device 100 is used to relay communications between the first authentication device 300-1 and the second authentication device 300-2. Typically, the processing device 100 is retrofitted and connected to the first authentication device 300-1 already installed in the building 10 so as to be communicable via a communication network. Therefore, the processing device 100 may take any form as long as it can perform this function, and may be a chip or substrate on which each of the components illustrated in FIG. 2A is mounted, or a device composed of these.

As shown in FIG. 2, the processing device 100 includes a processor 111 consisting of a CPU or the like, a memory 112 including RAM, ROM, non-volatile memory, an HDD, etc., a first communication interface 113, and a second communication interface 114. These components are electrically connected to each other via control lines and data lines.

The processor 111 is composed of a CPU (microcomputer) and functions as a control unit for controlling other connected components based on various programs stored in the memory 112. The processor 111 reads and executes programs for executing applications related to the present disclosure and programs for executing the OS from the memory 112. Specifically, upon receiving permission information from the second authentication device 300-2, the processor 111 executes processing for transmitting the permission information to the first authentication device 300-1 based on the programs stored in the memory 112. The processor 111 is primarily composed of one or more CPUs, but may also be combined with a GPU, FPGA, etc. as appropriate.

Memory 112 includes RAM, ROM, or non-volatile memory and functions as a storage unit. ROM stores instructions and commands for executing applications and OSs related to the present disclosure as programs. Such programs are loaded and executed by processor 111. RAM is used to write and read data while the programs stored in ROM are being processed by processor 111. Non-volatile memory is memory into which data is written and read as the programs are executed, and data written therein is saved even after execution of the programs has ended. Specifically, memory 112 stores a program that causes processor 111 to execute processes such as transmitting acceptance information to first authentication device 300-1 upon receiving the acceptance information from second authentication device 300-2.

The first communication interface 113 functions as a first communication unit that sends and receives information to and from the electrically connected first authentication device 300-1 via a communication processing circuit. The first communication interface 113 sends to the first authentication device 300-1 acceptance information generated when a user is authenticated using the second authentication method. Such a first communication interface 113 is preferably configured using serial communication such as RS-485, RS-422, or USB, a wired LAN, or a combination of these. However, the first communication interface 113 is not limited to the above-mentioned wired communication, and may also be configured using a communication circuit for communication via wireless communication such as short-range wireless communication.

The second communication interface 114 functions as a second communication unit that transmits and receives information to and from the second authentication device 300-2 via a communication processing circuit and an antenna. The second communication interface 114 receives, from the second authentication device 300-2, permission information generated when a user is authenticated using the second authentication method. This second communication interface 114 is preferably configured using a wireless LAN such as IEEE 802.11, a short-range wireless communication method such as Bluetooth (registered trademark), BLE (Bluetooth Low Energy), NFC, or RFID, a wideband wireless communication method such as LTE, or a combination of these. However, the second communication interface 114 is not limited to the above wireless communication methods, and may also be configured using a wired communication method such as serial communication.

3. Configuration of Server Device 200 FIG. 2B is a block diagram showing the configuration of a server device 200 according to an embodiment of the present disclosure. The server device 200 does not need to include all of the components shown in FIG. 2B ; it is possible to omit some components or add other components. Furthermore, the server device 200 does not need to include the components shown in FIG. 2B in a single housing; the components and processes of the server device 200 can be distributed to multiple processing devices, such as on-premise server devices and cloud server devices. While the present disclosure includes a first server device 200-1 and a second server device 200-2, the server devices can have similar or different configurations. Here, the configuration and functions of the second server device 200-2 will be mainly described.

As shown in FIG. 2B, the server device 200 includes a processor 211 consisting of a CPU or the like, memory 212 including RAM, ROM, non-volatile memory, and an HDD, and a communication interface 213. These components are electrically connected to each other via control lines and data lines.

The processor 211 is comprised of a CPU (microcomputer) and functions as a control unit for controlling other connected components based on various programs stored in the memory 212. The processor 211 reads and executes from the memory 212 programs for executing applications related to the present disclosure and programs for executing the OS. Specifically, the processor 111 performs the following functions: "generating acceptance information by authenticating a user in a second authentication device 300-2 configured to be able to authenticate the user in a second authentication method using second authentication information different from the first authentication information, for equipment where whether or not to allow the user to use the equipment is determined by a first authentication device 300-1 configured to be able to authenticate the user in a first authentication method using first authentication information," "outputting acceptance information via a communication interface in order to provide the acceptance information to a processing device 100 communicably connected to the first authentication device 300-1," and "processing for providing acceptance information to a user in equipment where the user's use is restricted." The processor 211 executes, based on a program stored in the memory 212, the following operations: receiving first log information indicating that a user has been authenticated from a first authentication device 300-1, which is installed to authenticate the user using the first authentication method and determine whether or not to allow the user to use the system, upon receiving an authentication request using first authentication information from the first authentication device 300-1; receiving second log information indicating that a user has been authenticated from the first authentication device 300-1 upon receiving acceptance information generated by authenticating the user using a second authentication method different from the first authentication method; and storing the first log information and the second log information. The processor 211 is primarily composed of one or more CPUs, but may also be combined with a GPU, FPGA, etc. as appropriate.

Memory 212 includes RAM, ROM, non-volatile memory, and HDD, and functions as a storage unit. ROM stores instructions and commands for executing applications and OS related to the present disclosure as programs. Such programs are loaded and executed by processor 211. RAM is used to write and read data while the programs stored in ROM are being processed by processor 211. Non-volatile memory is memory into which data is written and read as the programs are executed, and data written therein is saved even after the execution of the programs has ended. Specifically, memory 212 stores programs that allow processor 211 to execute the above-mentioned processes, etc. Memory 212 also stores various types of information, such as a user management table (Figure 3A) and a log management table (Figure 3B). If necessary, this information may be stored in a database device communicatively connected to server device 200 (in which case, the database may also be included as part of memory 212).

The communication interface 213 functions as a communication unit that transmits and receives information to and from other remotely installed server devices, such as the first server device 200-1, and other devices, such as the second authentication device 300-2, via a communication processing circuit and antenna. The communication processing circuit processes programs used in the processing system 1 and various information to transmit and receive information as processing progresses. The communication processing circuit processes based on a wideband wireless communication method, such as the LTE method, but it is also possible to process based on a narrowband wireless communication method, such as a wireless LAN, such as IEEE 802.11, or Bluetooth (registered trademark), or a contactless wireless communication method. Wired communication can also be used instead of or in addition to wireless communication.

The second server device 200-2 mainly functions as an authority management unit, a permission information management unit, and an authentication unit when a program is processed by the processor 211. In FIG. 2B, the second server device 200-2 is described as performing each of these functions on its own. However, this is not limiting, and the second server device 200-2 may include multiple server devices, each of which may execute each of these functional units.

As described above, the processing system 1 includes the first authentication device 300-1, the second authentication device 300-2, the locking/unlocking device 400, and the gateway 600. Although the specific configuration of these devices is not particularly illustrated, they include components necessary for executing each process, such as a processor, memory, and a communication interface, and each component is electrically connected to each other via a control line and a data line.

As an example, the first authentication device 300-1 is installed for authentication at the gate of building 10 and includes a control panel or control device connected by wire to the locking/unlocking device 400 and gateway 600, and an authentication unit (e.g., a card reader) communicatively connected to the control panel or control device. As an example, the second authentication device 3000-2 is a terminal device such as a smartphone that includes a control unit communicatively connected to the second server device 200-2 and a camera or sensor for user facial authentication. However, these are merely examples, and other forms may naturally be used. As for the gateway 600, any device may be used as long as it is communicatively connected to the first server device 300-1 and can relay communication between the first authentication device 300-1 and the first server device 300-1. As an example, for a first authentication device 300-1 that only has a wired communication environment, a gateway 600 that is wirelessly connected to the first server device 300-1 relays communication, thereby enabling communication between the first authentication device 300 and the first server device 300-1.

5. Information Stored in the Second Server Device 200-2 Figure 3A is a diagram conceptually illustrating a user management table stored in the second server device 200-2 according to an embodiment of the present disclosure. The information stored in the user management table is updated and stored as needed in accordance with the progress of processing by the processor 211 of the second server device 200-2.

As shown in FIG. 3A, the user management table stores attribute information, first authentication information, authority information, second authentication information, and the like, in association with user ID information. "User ID information" is information unique to each user and is used to identify each user. This user ID information is generated in the second server device 200-2, for example, when a user or administrator sends a new registration request for a service provided by the processing system 1. "Attribute information" is information related to the attributes of each user. Examples of such attribute information include the user's name (first and last name), title, nickname, career history, contact information such as telephone number and email address, company address and name, and department name. This information is stored as needed based on instructions entered by the user or administrator.

The "first authentication information" is information used to authenticate a user when the first authentication method is executed by the first authentication device 300-1. The first authentication information may be any of the authentication information corresponding to the knowledge-based, possession-based, or biometric authentication methods. Here, an example is described in which an identification code, which is unique information assigned to each user, is used as the first authentication information (for example, an identification code may be a six-digit number, but the same identification code may be used for each user). The "authority information" is information indicating the authority of each user to use the equipment. The authority information is, for example, information indicating the times when each user can use the equipment (for example, a combination of days and times, such as 9:00 to 17:00 on Mondays) and the locations where the equipment can be used. This is specifically described in Figure 3C.

The "second authentication information" is information used to authenticate a user when the second authentication method is executed in the second authentication device 300-2. The second authentication information may be any of authentication information corresponding to a knowledge-based, possession-based, or biometric authentication method. Here, an example is described in which license information granted to each user is used as the second authentication information. Note that while authentication information different from the first authentication information is exemplified as the second authentication information here, it may also be the same authentication information as the first authentication information. Naturally, multiple pieces of authentication information may be additionally stored in addition to the second authentication information, such as third authentication information used to authenticate a user when the third authentication method is executed in the third authentication device, and fourth authentication information used to authenticate a user when the fourth authentication method is executed in the fourth authentication device.

Although not specifically shown, in relation to the second authentication information in Figure 3A, information used for signature verification of each private key, each public key, common key, etc. used when issuing a usage certificate, etc., is also stored in memory 212.

Figure 3B is a diagram conceptually illustrating a log management table stored in the second server device 200-2 according to an embodiment of the present disclosure. The information stored in the log management table is updated and stored as needed in accordance with the progress of processing by the processor 211 of the second server device 200-2.

As shown in Figure 3B, the log management table stores restricted ID information, unlocking time information, and entry/exit information in association with user ID information. "User ID information" is information unique to each user and is used to identify each user. In other words, when a user is authenticated via any authentication device, such as the first authentication device 300-1, the user ID information is stored to identify the user.

"Lock/unlock ID information" is information specific to a lock/unlock device for locking and unlocking restricted objects such as facilities whose use by users is restricted, and is information for identifying each lock/unlock device. Here, restricted objects include, as described above, buildings, hotels, apartment buildings, houses, event facilities, or rooms (conference rooms, conference booths, residences) installed in buildings or apartment buildings that provide space,
- Gates and doors installed in the space that restrict the use of the space,
Examples of restricted use items include electronic devices such as printers and personal computers, home appliances such as elevators and delivery boxes, and vehicles such as bicycles and cars. A locking/unlocking device is provided for each of these items of equipment. Therefore, each item of equipment can be identified using the locking/unlocking ID information. In many cases, an authentication device is installed for each of the above-mentioned items of equipment or each locking/unlocking device. Therefore, authentication device ID information that identifies each authentication device or equipment ID information that identifies each item of equipment can also be used as the locking/unlocking ID information. In this embodiment, by using the locking/unlocking device ID information, it is possible to identify the equipment that is a restricted object that the user is permitted to use and the locking/unlocking device provided for that equipment.

"Unlocking time information" is information related to the time when an unlocking signal is transmitted from the first authentication device 300-1 to the locking/unlocking device 400 upon authentication of a user via the first authentication device 300-1. The unlocking time information may directly indicate the time when the unlocking signal was transmitted, the time when the unlocking signal was received by the locking/unlocking device 400, or the time when authentication was performed to transmit the unlocking signal. In other words, the unlocking time information may be any information indicating the time when any process related to the transmission of the unlocking signal was performed. "Entry/exit information" is information indicating whether each user is currently entering or exiting the building 10. For example, when the first authentication device 300-1 first authenticates a user and generates an unlocking signal, "enter" is stored as the entry/exit information. Thereafter, each time the user is authenticated and an unlocking signal is generated, the entry/exit information is alternately stored as either "exit" or "enter."

Figure 3C is a conceptual diagram illustrating permission information according to one embodiment of the present disclosure. This information is updated and stored as needed, for example, in response to a request from one of the administrators.

The authority information shown in Figure 3C is generated for each user's user ID information. In other words, by referencing this authority information, it is possible to determine whether the user associated with the user ID information has the authority to use each piece of equipment. Figure 3C shows the authority information of a user with user ID information "A1." According to Figure 3C, restriction target information and time information are stored in association with locking/unlocking ID information. As explained in Figure 3B, locking/unlocking ID information is information unique to the locking/unlocking device used to lock and unlock restricted objects, such as equipment whose use by users is restricted, and is information for identifying each locking/unlocking device. Each locking/unlocking device is provided for each piece of equipment, and each locking/unlocking device is connected to an authentication device that authenticates users. However, it is also possible to use equipment ID information that identifies each piece of equipment or authentication device ID information that identifies each authentication device as locking/unlocking ID information.

"Restriction target information" is information that indicates the facility, which is a restricted object and in which a locking/unlocking device is installed. Examples include information that indicates the name of the facility, such as "Building 10," and information that indicates the location of each facility. "Time information" is information that indicates the time that each user is permitted to use the facility, which is a restricted object and in which a locking/unlocking device is installed. Note that the time information may be in units of year, month, week, day, hour, minute, or second. Furthermore, the time information does not necessarily have to be a fixed, continuous period, but may be a period specified each time.

In the case of the above-mentioned authority information shown in Figure 3C, for example, a user with user ID information "A1" can use the building (gate) where a locking/unlocking device with locking/unlocking ID information "G1" is installed between 9:00 and 22:00 on weekdays, and can use Room C where a locking/unlocking device with locking/unlocking ID information "G4" is installed between 12:00 and 13:00 on weekdays.

6. Processing Sequence Executed by Processing System 1 (A) Pre-Registration Processing of First Authentication Information Fig. 4A is a diagram showing a processing sequence executed by the processing system 1 according to an embodiment of the present disclosure. Specifically, Fig. 4A shows a processing sequence executed between the first authentication device 300-1, the first server device 200-1, and the second server device 200-2 to register, in the first authentication device 300-1, first authentication information used in the first authentication device 300-1 to authenticate a user using the first authentication method. The processing in each device is executed by a processor processing a program stored in the memory of each device.

As shown in FIG. 4A, the processor 211 of the second server device 200-2 receives a user registration request for a new user via the communication interface 213 from an administrator terminal device available to the administrator. The user registration request includes attribute information and permission information for the new user who wishes to register. Examples of attribute information include the user's name (first and last name), title, nickname, career history, contact information such as telephone number and email address, the address of the company to which the user belongs, the name of that company, and the name of the department to which the user belongs. The permission information also includes information indicating the available times and facilities (FIG. 3C) that has been set in advance for the user by the administrator.

When the processor 211 of the second server device 200-2 receives a user registration request, it generates new user ID information (S11). The processor 211 of the second server device 200-2 then associates the generated user ID information with the received attribute information and authority information and stores them in the user management table (S12). The processor 211 of the second server device 200-2 also generates an identification code, which is information unique to the user, as first authentication information for authenticating the new user, and stores this in the user management table in association with the user ID information (S13). At a predetermined timing, the processor 211 of the second server device 200-2 transmits, via the communication interface 213 to the first server device 200-1, each piece of user ID information stored in the user management table, as well as the first authentication information (T11) and authority information associated with each user ID information.

When the processor 211 of the first server device 200-1 receives each piece of user ID information and the first authentication information and authority information associated with each piece of user ID information from the second server device 200-2 via the communication interface 213, it stores the received information in the memory 212 (S14). Then, at a predetermined timing, the processor 211 of the first server device 200-1 transmits each piece of user ID information and the first authentication information (T12) and authority information associated with each piece of user ID information to the first authentication device 300-1 via the communication interface 213.

When the processor of the first authentication device 300-1 receives each piece of user ID information and the first authentication information and authority information associated with each piece of user ID information from the first server device 200-1 via the communication interface, it stores the received information in memory (S14). This received information is used when authentication is performed by the first authentication device using the first authentication method. This completes the pre-registration process for the first authentication information.

The first authentication information, first authentication method, and first authentication device may be, for example, an identification code, which is unique information assigned to each user; a method for determining whether an identification code matches or does not match in the first authentication device; and a card reader for acquiring the identification code via near-field wireless communication from an ID card on which the identification code is stored. In other words, in such a case, the user must possess an ID card 500-1 (Figure 1) on which an identification code readable by a card reader is stored in advance. Therefore, although not specifically shown, an ID card is prepared in advance by an administrator, and first authentication information (identification code) associated with user ID information is stored on the ID card by an administrator terminal device or the like from the second server device 200-2. The ID card on which the first authentication information (identification code) is stored is then given to the user in advance by the administrator.

(B) Pre-registration Process of Second Authentication Information Fig. 4B is a diagram showing a processing sequence executed in the processing system 1 according to an embodiment of the present disclosure. Specifically, Fig. 4B shows a processing sequence executed between the second authentication device 300-2 and the second server device 200-2 to generate second authentication information used in the second authentication device 300-2 to authenticate a user using the second authentication method. The processing in each device is executed by a processor running a program stored in the memory of each device.

(B-1) Registration Process of Second Authentication Information The registration process of second authentication information is performed when new second authentication information used for user authentication is registered in the second server device 200-2. According to FIG. 4B , the processor 211 of the second server device 200-2 receives a registration request for second authentication information via the communication interface 213 from an administrator terminal device available to the administrator. Note that, in transmitting the registration request, the administrator retrofits the processing device 100 to the first authentication device 300-1, and installs the second authentication device 300-2 in the building 10 so that it can communicate with the processing device 100. The registration request also includes attribute information of the user who wishes to newly register, second authentication information used for authentication by the second authentication device 300-2 (e.g., facial features of the user if a facial authentication method is used), and authority information. Examples of attribute information include the user's name, title, nickname, career history, contact information such as a telephone number and email address, the address of the company to which the user belongs, the name of the company, and the name of the department to which the user belongs. The authority information also includes information (FIG. 3C) indicating the time and facilities that can be used, which is set in advance by an administrator for the user.

When the processor 211 of the second server device 200-2 receives a registration request via the communication interface 213, it generates new user ID information (S21). The processor 211 then uses its authority management unit (access control) to associate the received attribute information and authority information with the generated user ID information and store them in the user management table (S22). The processor 211 also uses its permission information management unit (which references and reads the identification code (first authentication information) as permission information) to generate an identification code unique to the user as first authentication information for authenticating the user, and stores this in the user management table in association with the user ID information (S23). The processor 211 also uses its authentication management unit (which manages facial features, information used for biometric authentication, etc.) to associate the second authentication information included in the received registration request with the generated user ID information and store it in the user management table (S24). This completes the second authentication information registration process.

In the above, the processed authority information, first authentication information, and second authentication information are each stored in the memory 212 of the second server device 200-2. This information is used for processes such as authentication using the second authentication method shown in FIG. 4D, authorization information confirmation, and permission information reference, but the second authentication information and authorization information may be frequently updated. In such cases, the information can be easily updated to the latest information, and authentication and other processes can be performed using the updated information. On the other hand, the processed authority information, first authentication information, and second authentication information may be transmitted to the second authentication device 300-2 in advance. Transmitting this information in advance in this way enables the second authentication device 300-2 to perform processes such as authentication using the second authentication method, authorization information confirmation, and permission information generation, enabling more flexible response to problems such as a deterioration in the communication environment.

(B-2) Hole Data Setting Process The hole data setting process is performed when a new processing device 100 is retrofitted to the first authentication device 300-1 and new hole data is set for the processing device 100. As shown in FIG. 4B, upon the administrator's retrofitting of the processing device 100 to the first authentication device 300-1, the processor 211 of the second server device 200-2 receives a hole data setting request for the processing device 100 via the communication interface 213, for example, from an administrator terminal device available to the administrator. Upon receiving the registration request via the communication interface 213, the processor 211 of the second server device 200-2 generates a pair of a private key A and a public key A unique to the newly generated hole data in accordance with public key cryptography (S31). The hole data includes processing device ID information, which is information unique to the processing device 100 and is used to identify the processing device 100.

Next, the processor 211 of the second server device 200-2 generates a common key A for the hole data using the generated private key A for the hole data and public key A for the hole data according to the common key cryptosystem (S32). The processor 211 of the second server device 200-2 stores the private key A for the hole data and the common key A for the hole data in its own memory 213 (S33), and transmits the public key A for the hole data and the common key A for the hole data (T31) to the processing device 100 via the administrator's terminal device. When the processor 111 of the processing device 100 receives the public key A for the hole data and the common key A for the hole data via the communication interface 113, it stores the received public key A for the hole data and the common key A for the hole data in memory 112 (S34). This completes the hole data setting process.

(B-3) Administrator Setup Process The administrator setup process is a process for generating a private key, etc., used to verify that an account is authorized to generate a digital key for the processing device 100 in the processing system 1 including the second server device 200-2 and the processing device 100 via the second authentication device 300-2. According to FIG. 4B , the processor of the second authentication device 300-2 receives an administrator setup request via a communication interface, for example, from an administrator terminal device available to the administrator. Upon receiving the registration request via the communication interface, the processor of the second authentication device 300-2 generates a pair of private key B and public key B unique to the administrator according to a public key cryptosystem (S35). The processor of the second authentication device 300-2 then stores the administrator private key B of the generated administrator private key B and administrator public key B in its own memory (S36) and transmits the administrator public key B (T31) to the second server device 200-1. When the processor 211 of the second server device 200-2 receives the administrator's public key B via the communication interface 213, it stores the received administrator's public key B in the memory 212 (S37). This completes the administrator setting process.

(B-4) Digital Key Issuance Process The digital key generation process is a process for issuing a digital key used to authenticate the connection source between the second authentication device 300-2 and the processing device 100. According to FIG. 4B , the processor of the second authentication device 300-2 detects an operation input by the administrator via an input interface, for example, and accepts the selection of hole data for which the digital key to be generated is to be used (S41). The processor of the second authentication device 300-2 then transmits a digital key issuance request (T41) for the hole data to the second server device 200-2 via the communication interface. The issuance request includes administrator ID information for the administrator's public key B and hole data ID information for specifying the hole data.

When the processor 211 of the second server device 200-2 receives the issuance request via the communication interface 213, it generates a digital key containing predetermined digital data unique to that digital key (S42). The processor 211 of the second server device 200-2 then encrypts the digital key using the common key A of the hole data generated in S32 (S43), and generates a signature A for the digital key using the private key A of the hole data generated in S31 (S44). The processor 211 of the second server device 200-2 then transmits the generated digital key and signature A to the second authentication device 300-2 via the communication interface 213.

When the processor of the second authentication device 300-2 receives the digital key and signature A via the communication interface, it generates signature B for the received digital key and signature A using the administrator's private key B generated in S35 (S45). The processor of the second authentication device 300-2 then stores the digital key in memory along with signature A generated using the hall data's private key A and signature B generated using the administrator's private key B (S46). This completes the digital key issuance process.

The digital key issued in Figure 4B includes information indicating the unlocking conditions, such as the validity period, usable time, and number of times the digital key can be used, as well as the administrator's public key B generated in S35.

(C) Authentication Processing in First Authentication Device 300-1 Figure 4C is a diagram showing a processing sequence executed in the processing system 1 according to an embodiment of the present disclosure. Specifically, Figure 4C shows a processing sequence executed between the first authentication device 300-1, the first server device 200-1, and the second server device 200-2 in order to authenticate a user by the first authentication method using the first authentication information in the first authentication device 300-1. The processing in each device is executed by a processor processing a program stored in the memory of each device.

As shown in FIG. 4C, the card reader of the first authentication device 300-1 includes a communication interface capable of communicating via a short-range wireless communication method such as NFC. When an ID card 500-1 (FIG. 1) storing first authentication information (identification code) previously assigned to a user is brought close to the card reader of the first authentication device 300-1 (when the ID card 500-1 is located within the communication range of short-range wireless communication), the first authentication device 300-1 acquires the first authentication information from the ID card 500-1 via the card reader (S51). Note that, since the ID card 500-1 is used here, the first authentication information is acquired via a communication interface capable of communicating via short-range wireless communication. However, the acquisition method may be changed as appropriate depending on the type of first authentication information. For example, in the case of knowledge-based authentication (e.g., user memorization), the first authentication information may be acquired via an input interface such as a numeric keypad or keyboard. Furthermore, in the case of possession-based authentication (e.g., ID card, smartphone, QR code, license, token, etc.), the first authentication information may be acquired via a communication interface such as a short-range wireless communication method or a wideband wireless communication method, a camera, or a sensor. Furthermore, in the case of biometric authentication (e.g., fingerprint, voice, iris, face, etc.), the first authentication information may be acquired via a camera or sensor.

The processor of the first authentication device 300-1 references the first authentication information previously stored in memory during the first authentication information pre-registration process of FIG. 4A and verifies whether there is any first authentication information that matches the first authentication information obtained from the ID card 500-1. If any of the first authentication information previously stored in memory matches the first authentication information obtained from the ID card 500-1, the processor of the first authentication device 300-1 authenticates the user by reading out the user ID information stored in memory in association with the matching first authentication information (S52).

Next, the processor of the first authentication device 300-1 references the authorization information (Figures 3A and 3C) associated with the read user ID information. Specifically, the processor of the first authentication device 300-1 obtains the time at which the first authentication information was obtained from the ID card 500-1 from the timer of the first authentication device 300-1. The processor of the first authentication device 300-1 then compares the obtained time with the time information for the facility (building 10) stored as authorization information, and determines whether the obtained time satisfies the available hours (e.g., 9:00 to 22:00 on weekdays, based on a combination of day and time). If the obtained time satisfies the available hours, the processor of the first authentication device 300-1 determines that authentication was successful and that the facility is available for use, and generates an unlock signal to send to the locking/unlocking device 400. The processor of the first authentication device 300-1 transmits the unlock signal to the locking/unlocking device 400 via the communication interface. Although not shown in the figure, upon receiving the unlock signal, the locking/unlocking device 400 sends an unlock signal to the gate connected to the locking/unlocking device 400, which opens the gate and allows the user to enter the facility. In other words, the restrictions on the user's use of the facility are lifted.

The processor of the first authentication device 300-1 also generates an authorization log (first log) containing locking/unlocking ID information for identifying the locking/unlocking device 400, user ID information of the authenticated user, information indicating that use of the equipment was permitted, and unlocking time information, which is the time related to the unlocking signal, and stores this in memory (S53). In this way, whereas previously it was only possible to manage "who (the user identified by user ID information) was authenticated on a certain day (information in days as time information)," it is now possible to obtain and manage information on the equipment or its location that is permitted for use from the locking/unlocking ID information, the user who is authenticated and permitted for use from the user ID information, and the detailed time that use was permitted from the unlocking time information.

Next, the processor 211 of the first server device 200-1 periodically transmits a request (T51) to the first authentication device 300-1 to send the allowed log (first log) stored in memory via the communication interface 213. Upon receiving the request to send the allowed log (first log), the processor of the first authentication device 300-1 reads the allowed log (T52: first log) stored in memory and transmits it to the first server device 200-1 via the communication interface. Upon receiving the allowed log via the communication interface 213, the processor 211 of the first server device 200-1 stores the received allowed log (first log) in the memory 212 (S54). The period for transmitting the request to send the allowed log (first log) may be on a yearly, monthly, weekly, daily, hourly, minutely, or secondly basis, and does not necessarily have to be set at a fixed interval. For example, the log may be sent once a day, or once every 12 hours on weekdays, and once a day on holidays. The intervals can be changed as desired by the administrator or other appropriate person. A request to send the allowed log (first log) is not necessarily required; the allowed log (first log) may be sent each time a new log is stored in the first authentication device 300-1, or the allowed log (first log) may be sent each time a predetermined amount of allowed logs (first logs) are stored in the first authentication device 300-1, or at predetermined intervals.

Furthermore, the processor 211 of the second server device 200-2 periodically transmits a transmission request (T53) for the permitted log (first log) stored in memory to each server device, including the first server device 200-1 to which the first authentication device 300-1 is connected, via the communication interface 213. Upon receiving the transmission request for the permitted log (first log), the processor 211 of the first server device 200-1 reads the permitted log (T54) stored in the memory 212 and transmits it to the second server device 200-2 via the communication interface 213. Upon receiving the permitted log (first log) via the communication interface 213, the processor 211 of the second server device 200-2 identifies the log management table corresponding to the locking/unlocking device 400 based on the locking/unlocking ID information included in the received permitted log (first log), stores the unlocking time information in association with the user ID information also included in the permitted log (first log), and updates the entry/exit information (S55). The interval for sending the request to send the allowed log (first log) may be yearly, monthly, weekly, daily, hourly, minutely, or second-by-second intervals, and does not necessarily have to be set at a fixed interval. For example, the request may be sent once a day, or once every 12 hours on weekdays, and once a day on holidays. The interval can also be changed as desired by an administrator or other appropriate person. A request to send the allowed log (first log) is not necessarily required; the allowed log (first log) may be sent each time a new log is stored in the first server device 200-1, or every time a predetermined amount of allowed logs (first logs) are stored in the first server device 200-1, or at predetermined intervals. This completes the authentication process in the first authentication device 300-1.

(D) Authentication Processing in Second Authentication Device 300-2 Figures 4D and 4E are diagrams showing a processing sequence executed in the processing system 1 according to an embodiment of the present disclosure. Specifically, Figures 4D and 4E show a processing sequence executed mainly between the second server device 200-2, the second authentication device 300-2, and the processing device 100 in order to authenticate a user by the second authentication method using second authentication information in the second authentication device 300-2. The processing in each device is executed by a processor processing a program stored in the memory of each device.

(D-1) Authentication Process Using Second Authentication Information According to FIG. 4D, the second authentication device 300-2 includes a sensor (camera) for acquiring the user's facial features. The processor of the second authentication device 300-2 activates the camera by detecting a user's operational input via, for example, an input interface. When the processor of the second authentication device 300-2 detects the user's face within the camera's field of view, it acquires a facial image of the user as second authentication information used in the second authentication method (S61). While facial features are used for the second authentication information, these features may be calculated by the second authentication device 300-2 or the second server device 200-2. In this embodiment, the second authentication information includes not only facial features but also the facial image itself and data after image processing to calculate the facial features. Although the above description uses a sensor (camera) to acquire a facial image or facial features as the second authentication information, the acquisition method may be adapted to suit the type of second authentication information. For example, in the case of knowledge-based authentication (e.g., user memorization), the second authentication information may be acquired via an input interface such as a numeric keypad or keyboard. Also, in the case of possession-based authentication (e.g., ID card, smartphone, QR code, license, token, etc.), the second authentication information may be acquired via a communication interface such as a short-range wireless communication method or a wideband wireless communication method, a camera, or a sensor. Also, in the case of biometric-based authentication (e.g., fingerprint, voice, iris, face, etc.), the second authentication information may be acquired via a camera or a sensor.

When the processor of the second authentication device 300-2 acquires the second authentication information, it transmits the acquired second authentication information (S61) to the second server device 200-2 via the communication interface. When the processor 211 of the second server device 200-2 receives the second authentication information via the communication interface 213, it accesses the authentication management unit's database and performs authentication using the second authentication method by checking whether the corresponding second authentication information is included (S62). Specifically, the processor 211 of the second server device 200-2 references the second authentication information previously stored in the user management table by processing such as S24 in FIG. 4B, and checks whether there is user ID information that matches the second authentication information received from the second authentication device 300-2. If there is no match, the processor 211 of the second server device 200-2 considers the authentication to be unsuccessful and cancels subsequent processing.

On the other hand, if a match is found, the processor 211 of the second server device 200-2 accesses the database of the authority management unit and references the authority information (FIGS. 3A and 3C) previously stored in the user management table by processing such as S22 of FIG. 4B to determine whether the corresponding user ID information is included (S63). Specifically, the processor 212 of the second server device 200-2 identifies the user ID information associated with the matching second authentication information and references the authority information associated with the user ID information in the user management table. The processor 212 of the second server device 200-2 compares the current time acquired from the timer with the time information for the facility (building 10) stored as the authority information, and determines whether the acquired time satisfies the available hours (for example, 9:00 to 22:00 on weekdays, based on a combination of day and time). If the acquired time satisfies the available hours, the processor 212 of the second server device 200-2 determines that the facility (building 10) is available for use.

When the processor 212 of the second server device 200-2 determines based on the authorization information that the facility (building 10) is permitted to be used, it accesses the database of the permission information management unit and references the permission information (FIGS. 3A and 3C) previously stored in the user management table by processing such as S22 of FIG. 4B (S64). Specifically, the processor 212 of the second server device 200-2 reads the permission information including the first authentication information (identification code) associated with the user ID information associated with the matching second authentication information.

The processor 212 of the second server device 200-2 transmits the allowable information (T61) read from the allowable information management unit to the second authentication device 300-2 via the communication interface 213. Upon receiving the allowable information via the communication interface, the processor of the second authentication device 300-2 stores the allowable information in its own memory (S65). This completes the authentication process using the second authentication information. Note that, as shown in T91 in Figure 4E, the allowable information is transmitted from the second authentication device 300-2 to the processing device 100, and therefore only needs to be stored at least temporarily for this transmission.

In FIG. 4D, the above processes are executed by the authentication unit, the authority management unit, and the permission information management unit in the second server device 200-2. However, for example, the second server device 200-2 can be configured with server devices that each execute a separate function, and each function can be distributed and executed among these.

In the above, the second server device 200-2 receives the authority information, first authentication information, and second authentication information from the second authentication device 300-2 in advance, and the second server device 200-2 executes each function. Of the information used when executing each function, the second authentication information and authority information in particular may be frequently updated. In such cases, when executing each function on the second server device 200-2, the information can be easily updated to the latest information, and authentication and other processes can be performed using the updated information. On the other hand, the authority information, first authentication information, and second authentication information can also be stored in the second authentication device 300-2, and the above functions can be executed by the second authentication device 300-2. In such cases, there is less need to communicate with the second server device 200-2, allowing for more flexible responses to problems such as a deterioration in the communication environment.

(D-2) Encryption Processing of Near Field Communication The encryption processing of near field communication is a process of performing encryption to establish more secure near field communication between the second authentication device 300-2 and the processing device 100. One example of this is the Diffie-Hellman key sharing method, in which the second authentication device 300-2 and the processing device 100 exchange public keys generated by each other to generate a common shared key. As shown in FIG. 4D, the processor of the second authentication device 300-2 detects the processing device 100 by receiving a signal transmitted at a predetermined interval from the processing device 100 to which it is to connect (S71). Upon detecting the processing device 100, the processor of the second authentication device 300-2 transmits a connection request (T71) to the processing device 100 via the communication interface.

When the processor 111 of the processing device 100 receives a connection request via the second communication interface 114, it authorizes connection with the second authentication device 300-2 (S72). Then, the processor 111 of the processing device 100 generates a private key C and a public key C of the processing device 100 that are unique for communication with the second authentication device 300-2 in accordance with a public encryption method (S73). The processor 111 of the processing device 100 stores the generated private key C of the processing device 100 in the memory 112 (S74), and transmits the public key C (T72) of the processing device 100 to the second authentication device 300-2 via the second communication interface 214 (at this time, it also transmits a message indicating that the connection is authorized). When the processor of the second authentication device 300-2 receives the public key C of the processing device 100 via the communication interface, it stores the public key C of the processing device 100 in its own memory (S75).

Next, the processor of the second authentication device 300-2 generates a private key D of the second authentication device 300-2 and a public key D of the second authentication device 300-2 that are unique for communication with the processing device 100 in accordance with a public encryption method (S76). The processor of the second authentication device 300-2 generates a common key C using the generated private key D of the second authentication device 300-2 and the public key C of the processing device 100 received from the processing device 100 (S77). The processor of the second authentication device 300-2 stores the generated private key D of the second authentication device 300-2 and the common key C generated by the second authentication device 300-2 in its own memory (S78). The processor of the second authentication device 300-2 encrypts arbitrary information with the common key C (S79) and transmits the encrypted information and the public key D (T73) of the second authentication device 300-2 to the processing device 100 via the communication interface. When the processor 111 of the processing device 100 receives the public key D of the second authentication device 300-2 via the second communication interface 114, it stores the received public key D in the memory 112 (S80).

Next, the processor 111 of the processing device 100 generates a common key C using the private key C of the processing device 100 generated in S73 and the public key D of the second authentication device 300-2 received from the second authentication device 300-2 (S81). The processor 111 of the processing device 100 decrypts the encrypted information received from the second authentication device 300-2 using the common key C generated by the processing device 100 (S82). If the encrypted information can be decrypted using the common key C generated by the processing device 100, the processor 111 of the processing device 100 generates decryption result information indicating that the common keys C generated by the second authentication device 300-2 and the processing device 100 are the same (i.e., shared), and that the decryption was successful. The processor 111 of the processing device 100 encrypts the decryption result information using the common key C generated by the processing device 100, and then transmits the encrypted decryption result information to the second authentication device 300-2 via the second communication interface 114. This makes it possible to encrypt all information sent and received in communication between the second processing device 300-2 and the processing device 100 using the common key C, improving the security of communications. This completes the encryption process.

(D-3) Digital Key Authentication Processing The digital key authentication processing is processing for authenticating the connection source between the second authentication device 300-2 and the processing device 100. According to FIG. 4E, when the second authentication device 300-2 receives the decryption result information in FIG. 4D, it reads out the digital key stored in S46 of FIG. 4B together with signature A based on private key A of the hall data and signature B based on private key B of the administrator in order to transmit the digital key to the processing device 100 (S91). Then, the processor of the second authentication device 300-2 transmits the read digital key, signature A based on private key A of the hall data, and signature B based on private key B of the administrator (T91) to the processing device 100 via the communication interface. Note that the digital key was encrypted with common key A of the hall data in S43 of FIG. 4B.

When the processor 111 of the processing device 100 receives the digital key, signature A based on the hole data private key A, and signature B based on the administrator's private key B via the second communication interface 114, it decrypts the digital key using the common key A of the processing device 100 stored in S34 of FIG. 4B (S92). Once the digital key is decrypted, the processor 111 of the processing device 100 verifies signature A based on the hole data private key A using the hole data public key A that was previously set in the hole data of the processing device 100 and stored in S34 of FIG. 4B. If the signature verification is successful, the processor 111 of the processing device 100 verifies signature B using the administrator's private key B using the administrator's public key B that was previously set for the administrator and obtained from within the digital key (S94). When the verification of each signature is successful, the processor 111 of the processing device 100 generates authentication result information indicating that signature verification has ended and that authentication of the digital key has been successful, and sends the authentication result information (T92) encrypted with the common key C generated by the processing device 100 to the second authentication device 300-2 via the second communication interface 114. Here, if authentication of the digital key is successful, the processor 111 of the processing device 100 becomes ready to accept commands from the second authentication device 300-2.

When the processor of the second authentication device 300-2 receives the authentication result information via the communication interface, it encrypts the allowable information received in S65 of FIG. 4D using the common key C generated by the second authentication device 300-2 (S95) and transmits the encrypted allowable information (T93) via the communication interface to the processing device 100 as an unlock request. When the processor 111 of the processing device 100 receives the encrypted allowable information via the second communication interface 114, it decrypts the allowable information using the common key C generated by the processing device 100. Then, the processor 111 of the processing device 100 transmits the decrypted allowable information to the first authentication device 300-1 via the first communication interface 113.

When the processor of the first authentication device 300-1 receives the acceptance information from the processing device 100, it acquires an identification code (first authentication information) that may be included in the acceptance information. Subsequent processing, although not shown, is executed in the same manner as in FIG. 4C. Specifically, the processor of the first authentication device 300-1 references the first authentication information previously stored in memory during the first authentication information pre-registration processing of FIG. 4A and verifies whether there is any first authentication information that matches the first authentication information acquired from the processing device 100. Then, if any of the first authentication information previously stored in memory matches the first authentication information acquired from the processing device 100, the processor of the first authentication device 300-1 authenticates the user by reading out the user ID information stored in memory in association with the matching first authentication information.

Next, the processor of the first authentication device 300-1 references the authorization information (Figures 3A and 3C) associated with the read user ID information. Specifically, the processor of the first authentication device 300-1 obtains the time at which the first authentication information was obtained from the processing device 100 from the timer of the first authentication device 300-1. The processor of the first authentication device 300-1 then compares the obtained time with the time information for the facility (building 10) stored as authorization information, and determines whether the obtained time satisfies the available time (e.g., a combination of day of the week and time, such as 9:00 to 22:00 on weekdays). If the obtained time satisfies the available time, the processor of the first authentication device 300-1 determines that authentication was successful and that the facility is available for use, and generates an unlock signal to be sent to the locking/unlocking device 400. The processor of the first authentication device 300-1 sends the unlock signal to the locking/unlocking device 400 via the communication interface. Although not specifically shown, the operation of the locking/unlocking device 400 upon receiving the unlock signal is the same as that described in Figure 4C.

The processor of the first authentication device 300-1 also generates and stores in memory an authorization log (second log) containing locking/unlocking ID information for identifying the locking/unlocking device 400, user ID information for the authenticated user, information indicating that use of the facility is permitted, and unlocking time information, which is the time related to the unlocking signal. After the authorization log (second log) is stored, it is sent to the first server device 200-1 and the second server device 200-2, and the operations when the authorization log is acquired and managed by the first server device 200-1 and the second server device 200-2 are the same as those described in FIG. 4C.

In addition, in Figures 4D and 4E, the identification code (first authentication information) itself is read out and transmitted to the processing device 100 as the acceptance information upon authentication by the second authentication device 300-2, but it is not necessary to use the identification code. For example, the acceptance information may include the user ID information of the user authenticated by the second authentication device 300-2 and information indicating that authentication of the user was successful, and be transmitted to the processing device 100. This allows the first authentication device 300-1 to perform authentication using the first authentication method based on whether or not the user ID information has been stored in advance.

7. Example Use Cases of the Processing System 1 The processing system 1 that performs the processing described above is typically used in the following use cases: However, the use cases shown below are merely examples, and are not limited to the following.

(A) Case of authenticating an employee It is assumed that an administrator of a company located in a building 10 with restricted use or an administrator of the building 10 registers an employee of the company as a user. In this case, an identification code is stored as first authentication information on an employee ID card (ID card) and distributed to the employee in advance. Then, when the employee brings the employee ID card close to a card reader, which is the first authentication device, authentication using the identification code is performed, and the employee is authenticated. If the employee is successfully authenticated, a gate installed at the entrance to the building 10 opens, and the employee is permitted to enter the building 10 (i.e., is permitted to use the building 10).

In addition, to provide the employee with a variety of authentication methods, the administrator issues a usage permit to the employee in advance as the employee's second authentication information. Specifically, the usage permit is stored in a user terminal device (smartphone) that the employee can use. When the employee brings the smartphone close to the second authentication device, authentication using the usage permit is performed, and the employee is authenticated. If the employee is successfully authenticated, an identification code (first authentication information) previously associated with the employee is provided to the first authentication device via the processing device 100. Then, authentication using the identification code is performed, and the employee is authenticated. If the employee is successfully authenticated, the gate installed at the entrance to building 10 opens, and the employee is permitted to enter building 10 (i.e., is permitted to use building 10).

Although not specifically described, the processing system 1 can be used not only with the building 10 and its employees, but also with an apartment building and its residents, an event facility and its users, or a car and its users, etc.

(B) Case of authenticating a service provider It is assumed that a resident of an apartment complex with restricted use registers, for example, a parcel delivery person as a user to temporarily allow them to use the service. In this case, a PIN to be entered into the numeric keypad of an auto-lock device (first authentication device) of the apartment complex is provided to the delivery person in advance as first authentication information. Then, when the delivery person enters the PIN into the auto-lock device, which is the first authentication device, authentication using the PIN is performed, and the delivery person is authenticated. If the authentication of the delivery person is successful, the entrance door of the apartment complex opens, and the delivery person is allowed to enter the apartment complex (i.e., is allowed to use the apartment complex).

In addition, to provide the deliverer with a variety of authentication methods, the resident issues a usage permit to the deliverer in advance as the deliverer's second authentication information. Specifically, the usage permit is stored in a user terminal device (smartphone) that the deliverer can use. When the deliverer brings the smartphone close to the second authentication device, authentication is performed using the usage permit, and the deliverer is authenticated. If authentication of the deliverer is successful, a PIN number (first authentication information) previously associated with the deliverer is provided to the first authentication device via the processing device 100. Then, authentication is performed using the PIN number, and the deliverer is authenticated. If authentication of the deliverer is successful, the entrance door to the apartment complex opens, and the deliverer is allowed to enter the apartment complex (i.e., is allowed to use the apartment complex).

Although not specifically described, the processing system 1 can be used not only for combinations of apartment buildings and delivery people, but also for visitors who have been registered as visiting the building 10 and its employees.

As described above, this embodiment provides a processing device, processing program, and processing method that enable more efficient user authentication. In particular, by retrofitting a second authentication device 300-2, etc., that performs authentication using a second authentication method, in addition to the pre-installed first authentication device 300-1, via the processing device 100, more flexible equipment expansion is possible. Furthermore, users can also use a second authentication method other than the first authentication method, enabling more flexible authentication. Furthermore, when acquiring an acceptance log on the first authentication device 300-1, it is typically difficult to reflect the results of authentication on a different authentication device, such as the second authentication device 300-2. However, by having the second server device 200-2 acquire the acceptance log via the first server device 200-1, it is possible for the second server device 200-2 to centrally manage acceptance logs for not only the first authentication device 300-1 but also the second authentication device 300-2, etc. Furthermore, by collecting log information that does not simply include the time and user information of authentication, but also information about the equipment on which the authentication was performed, it becomes possible to manage more detailed information such as when, who, and where authentication was performed. Furthermore, when authentication is performed using second authentication information, authentication is performed by the first authentication device 300-1 in addition to authentication by the second authentication device 300-2, which makes it possible to further improve security, authenticity of authentication, and confidentiality. In other words, by going through multiple authentication rounds, it is possible to improve the authenticity of "who can enter and exit where," and multiple authentication methods can further increase confidentiality for high-security areas.

8. Others In the above embodiment, a case has been described in which only the locking/unlocking device 400 is controlled via the first authentication device 300-1. However, the object to be controlled is not limited to the locking/unlocking device 400, and it is also possible to control a wider variety of devices. FIG. 5 is a block diagram showing the configuration of a processing system 1000 according to an embodiment of the present disclosure. Specifically, FIG. 5 shows the configuration of the processing system 1000 including an elevator 400-2 and a gateway 600 in addition to the locking/unlocking device 400-1.

As shown in FIG. 5, as described above, the processing system 1000 includes the elevator 400-2 in addition to the locking/unlocking device 400-1. The elevator 400-2 is communicatively connected to the first server device 200-1 via a communication network. Note that the other components are the same as those of the processing system 1 in FIG. 1.

Figure 6 is a conceptual diagram of a user management table stored in the second server device 200-2 according to an embodiment of the present disclosure. In addition to the information stored in the user management table shown in Figure 3A, the user management table stores control information associated with user ID information. The "control information" is information for controlling elevator 400-2. For example, for a user with user ID information "A1," call information for calling the elevator hall nearest to the gate for an elevator capable of transporting to the 8th floor of building 10, and destination information indicating the "8th floor," which is the elevator's usual destination, are stored. Such control information is stored, for example, by receiving it from an administrator terminal device available to the administrator together with a user registration request. Note that other information is the same as in Figure 3A.

Figure 7A is a diagram showing a processing sequence executed in a processing system 1000 according to an embodiment of the present disclosure. Specifically, Figure 7A shows a processing sequence executed between the first authentication device 300-1, the first server device 200-1, and the second server device 200-2 in order to register, in the first authentication device 300-1, first authentication information used in the first authentication device 300-1 to authenticate a user using the first authentication method. The processing in each device is executed by a processor running a program stored in the memory of each device.

According to FIG. 7A, the processor 211 of the second server device 200-2 receives a user registration request for a new user via the communication interface 213 from an administrator terminal device available to the administrator. The user registration request includes attribute information, authority information, and control information for the user wishing to register. The attribute information includes, for example, the user's name (first and last name), title, nickname, career history, contact information such as telephone number and email address, the address of the company to which the user belongs, the name of the company, and the name of the department to which the user belongs. The authority information also includes information set in advance by the administrator for the user indicating the times and locations at which the equipment can be used. The control information also includes information for controlling elevator 400-2, such as call information for calling an elevator capable of transporting a user to a specified floor in building 10 to the elevator hall nearest to the gate, and destination information indicating the floor to which the elevator normally transports users.

When the processor 211 of the second server device 200-2 receives a user registration request, it generates new user ID information (S71). The processor 211 of the second server device 200-2 then associates the received attribute information and authority information with the generated user ID information and stores them in the user management table (S72), and also stores the received control information associated with the user ID information in the user management table (S73). The processor 211 of the second server device 200-2 also generates an identification code, which is information unique to the user, as first authentication information for authenticating the new user, and associates it with the user ID information and stores it in the user management table (S74). At a predetermined timing, the processor 211 of the second server device 200-2 transmits each user ID information stored in the user management table, along with the first authentication information (T71), authority information, and control information associated with each user ID information, to the first server device 200-1 via the communication interface 213.

When the processor 211 of the first server device 200-1 receives each piece of user ID information and the first authentication information, authority information, and control information associated with each piece of user ID information from the second server device 200-2 via the communication interface 213, it stores the received information in the memory 212 (S75). Then, at a predetermined timing, the processor 211 of the first server device 200-1 transmits each piece of user ID information and the first authentication information (T72) and authority information associated with each piece of user ID information to the first authentication device 300-1 via the communication interface 213.

When the processor of the first authentication device 300-1 receives each piece of user ID information and the first authentication information and authority information associated with each piece of user ID information from the first server device 200-1 via the communication interface, it stores the received information in memory (S76). This received information is used when authentication is performed by the first authentication device using the first authentication method. This completes the pre-registration process for the first authentication information.

Figure 7B is a diagram showing a processing sequence executed in a processing system 1000 according to an embodiment of the present disclosure. Specifically, Figure 7B shows a processing sequence executed between the first authentication device 300-1, the first server device 200-1, and the second server device 200-2 in order to authenticate a user by the first authentication method using first authentication information in the first authentication device 300-1. The processing in each device is executed by a processor running a program stored in the memory of each device.

As shown in FIG. 7B, the process shown in FIG. 4C or 4D acquires first identification information (identification code) from the ID card 500-1 or authorization information including the identification code, which is the first identification information, from the processing device 100 (S81). The processor of the first authentication device 300-1 references the first authentication information previously stored in memory during the first authentication information pre-registration process of FIG. 7A and verifies whether there is any first authentication information that matches the first authentication information acquired from the ID card 500-1 or the processing device 100. Then, if any of the first authentication information previously stored in memory matches the first authentication information acquired from the ID card 500-1 or the processing device 100, the processor of the first authentication device 300-1 authenticates the user by reading the user ID information stored in memory in association with the matching first authentication information (S82).

Next, the processor of the first authentication device 300-1 references the authority information associated with the read user ID information. The specific processing is similar to that shown in Figure 4C. Once the processor of the first authentication device 300-1 has confirmed the authority, it generates an unlock signal to be sent to the locking/unlocking device 400-1. The processor of the first authentication device 300-1 sends the unlock signal to the locking/unlocking device 400-1 via a communication interface. Although not specifically shown, upon receiving the unlock signal, the locking/unlocking device 400-1 sends the unlock signal to the gate connected to the locking/unlocking device 400-1, which opens the gate and allows the user to enter the facility. In other words, the restrictions on the user's use of the facility are lifted.

The processor of the first authentication device 300-1 also generates an authorization log containing locking/unlocking ID information for identifying the locking/unlocking device 400-1, the user ID information of the authenticated user, and information indicating that use of the facility is authorized and unlocking time information, which is the time related to the unlocking signal, and stores this in memory (S83).

Next, the processor 211 of the first server device 200-1 periodically transmits a request (T81) to the first authentication device 300-1 to send the tolerance log stored in memory via the communication interface 213. Upon receiving the request, the processor of the first authentication device 300-1 reads the tolerance log (T82) stored in memory and transmits it to the first server device 200-1 via the communication interface. Upon receiving the tolerance log via the communication interface 213, the processor 211 of the first server device 200-1 stores the received tolerance log in the memory 212 (S84). The period for transmitting the tolerance log transmission request and whether or not a tolerance log transmission request is sent are the same as those in FIG. 4C.

Furthermore, after storing the permission log in S84, the processor 211 of the first server device 200-1 reads the control information stored in S75 of FIG. 7A based on the user ID information included in the received permission information. The processor 211 of the first server device 200-1 then transmits the control information read via the communication interface 213 to the elevator 400-2, the device to be controlled, via the gateway 600. Upon receiving the control information, the elevator 400-2 calls an elevator capable of transporting the user to a specified floor in building 10 to the elevator hall nearest to the gate based on the received control information, and pre-sets the floor number that is the normal destination for that elevator. Specifically, for example, in the case of a user with user ID information "A1," an elevator capable of transporting the user to the 8th floor of building 10 is called to the elevator hall nearest to the gate, and pre-sets the "8th floor" as the normal destination for that elevator.

The processor 211 of the second server device 200-2 periodically transmits a request (T83) for transmitting the permission log stored in memory to each server device, including the first server device 200-1 to which the first authentication device 300-1 is connected, via the communication interface 213. Upon receiving the request for transmitting the permission log, the processor 211 of the first server device 200-1 reads the permission log (T84) stored in the memory 212 and transmits it to the second server device 200-2 via the communication interface 213. Upon receiving the permission log via the communication interface 213, the processor 211 of the second server device 200-2 identifies the log management table corresponding to the locking/unlocking device 400 based on the locking/unlocking ID information contained in the received permission log, stores the unlocking time information in association with the user ID information also contained in the permission log, and updates the entry/exit information (S85). The period for transmitting the request for transmitting the permission log and whether or not a request for transmitting the permission log is issued are the same as those shown in FIG. 4C.

Although not specifically shown, the pre-registration process of the second authentication information and the authentication process in the second authentication device 300-2 are performed in the same manner as in Figures 4B and 4D.

Furthermore, while Figures 5 to 7B show elevator 400-2 as an example of a device to be controlled, it is of course possible to add other devices as well. For example, other automatic doors, gates, air conditioning equipment, lighting equipment, etc. inside building 10 can also be processed in the same way.

As described above, this embodiment provides a processing device, processing program, and processing method that enable more efficient user authentication. In particular, by retrofitting a second authentication device 300-2, etc., that performs authentication using a second authentication method, in addition to the pre-installed first authentication device 300-1, via the processing device 100, more flexible equipment expansion is possible. Furthermore, users can also use a second authentication method other than the first authentication method, enabling more flexible authentication. Furthermore, when acquiring an acceptance log on the first authentication device 300-1, it is typically difficult to reflect the results of authentication on a different authentication device, such as the second authentication device 300-2. However, by having the second server device 200-2 acquire the acceptance log via the first server device 200-1, it is possible for the second server device 200-2 to centrally manage acceptance logs for not only the first authentication device 300-1 but also the second authentication device 300-2, etc. Furthermore, by collecting log information that does not simply include the time of authentication and user information, but also information about the equipment that was authenticated, it becomes possible to manage more detailed information such as when, who, and where authentication occurred. Furthermore, when authentication is performed using second authentication information, authentication is performed by first authentication device 300-1 in addition to authentication by second authentication device 300-2, which makes it possible to further improve safety and authentication accuracy. Furthermore, by authenticating the user in addition to these, it becomes possible to control in advance the equipment that is expected to be used next (e.g., elevator 400-2), allowing the user to use each equipment more efficiently.

The processes and procedures described in this specification can be realized not only by those explicitly described in the embodiments, but also by software, hardware, or a combination of these. Specifically, the processes and procedures described in this specification are realized by implementing logic corresponding to the processes in media such as integrated circuits, volatile memory, non-volatile memory, magnetic disks, and optical storage. Furthermore, the processes and procedures described in this specification can be implemented as computer programs and executed by various computers, including processing devices and server devices.

Even if the processes and procedures described herein are described as being performed by a single device, software, component, or module, such processes or procedures may be performed by multiple devices, multiple software, multiple components, and/or multiple modules. Furthermore, even if various information described herein is described as being stored in a single memory or storage unit, such information may be stored in multiple memories within a single device or in multiple memories distributed across multiple devices. Furthermore, the software and hardware elements described herein may be realized by integrating them into fewer components or by breaking them down into more components.

1 Processing system 10 Building 100 Processing device 200 Server device 200-1 First server device 200-2 Second server device 300-1 First authentication device 300-2 Second authentication device 400 Locking/unlocking device 500-1 ID card 500-2 User terminal device 1000 Processing system 400-1 Locking/unlocking device 400-2 Elevator 600 Gateway

Claims (16)

A processing system including a server device and a processing device,
the server device receives first log information indicating that the user has been authenticated from a first authentication device that is installed in a facility where user use is restricted and that executes a process of authenticating the user by a first authentication method using the first authentication information upon receiving an authentication request from the user using the first authentication information in order to determine whether or not the user is permitted to use the facility;
a second authentication device different from the first authentication device outputs, to the processing device, allowance information generated by authenticating the user by a second authentication method different from the first authentication method;
When the processing device receives the permission information output from the second authentication device, the processing device transmits the permission information to the first authentication device;
the server device receives second log information from the first authentication device, the second log information indicating that the user has been authenticated due to the first authentication device accepting the permission information;
the server device stores the first log information and the second log information;
a processing system configured to perform processing for The processing system of claim 1, wherein the permission information is the same as the first authentication information. The processing system described in claim 1, wherein the permission information is unique information assigned to the user in advance. The processing system described in claim 1, wherein the permission information is transmitted in advance to the second authentication device from a second server device connected to the second authentication device via a communication network, and is also transmitted in advance to the first authentication device via a first server device different from the second server device. The processing system described in claim 1, wherein the second authentication method uses second authentication information different from the first authentication information. the processing device includes a first communication interface configured to communicatively couple with the first authentication device and a second communication interface configured to receive the acceptance information from the second authentication device;
The processing system according to claim 1 , wherein the second communication interface uses a communication method different from the communication method used by the first communication interface. The processing system of claim 6, wherein the second communication interface communicates via short-range wireless communication. The processing system of claim 7, wherein the short-range wireless communication in the second communication interface includes encryption processing. The processing system described in claim 1, wherein the first authentication device authorizes the user to use the system based on receipt of the authorization information. The processing system described in claim 1, wherein the processing device is installed in the facility as a retrofit to the first authentication device already installed in the facility. The processing system of claim 6, wherein the first authentication device is connected via serial communication via the first communication interface. The processing system described in claim 1, wherein the first log information and the second log information are transmitted from the first authentication device to the server device via another server device that is communicatively connected to the first authentication device and different from the server device. the server device and the other server device are managed by different administrators,
The processing system according to claim 12 , wherein the first log information and the second log information are transmitted from the first authentication device to the server device via the other server device in response to a request from an administrator who manages the server device. The processing system of claim 12, wherein the first log information and the second log information include at least one of information indicating the equipment that the user is permitted to use and information indicating the time that the user is permitted to use the equipment. a processing system including a server device and a processing device,
the server device receives first log information indicating that the user has been authenticated from a first authentication device that is installed in a facility where user use is restricted and that executes a process of authenticating the user by a first authentication method using the first authentication information upon receiving an authentication request from the user using the first authentication information in order to determine whether or not the user is permitted to use the facility;
a second authentication device different from the first authentication device outputs, to the processing device, allowance information generated by authenticating the user by a second authentication method different from the first authentication method;
When the processing device receives the permission information output from the second authentication device, the processing device transmits the permission information to the first authentication device;
the server device receives second log information from the first authentication device, the second log information indicating that the user has been authenticated due to the first authentication device accepting the permission information;
the server device stores the first log information and the second log information;
A processing program that functions to perform processing for the purpose. A processing method executed in a processing system including a server device and a processing device,
a step in which the server device receives first log information indicating that the user has been authenticated from a first authentication device that is installed in a facility where user use is restricted and that executes a process of authenticating the user by a first authentication method using the first authentication information upon receiving an authentication request from the user using the first authentication information in order to determine whether or not the user is permitted to use the facility;
outputting, by a second authentication device different from the first authentication device, acceptance information generated by authenticating the user by a second authentication method different from the first authentication method, for providing to the processing device;
a step of transmitting the permission information to the first authentication device by the processing device upon receiving the permission information output from the second authentication device;
receiving, by the server device, second log information from the first authentication device, which indicates that the user has been authenticated due to the first authentication device accepting the permission information;
storing the first log information and the second log information in the server device;
A processing method comprising: