JP7790739B2 - Processing device, processing program, and processing method - Google Patents

Description

This disclosure relates to a processing device, processing program, and processing method for managing user access to an object.

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-mentioned technologies, the present disclosure aims to provide, through various embodiments, a processing device, processing program, and processing method that enable more efficient management of user usage.

One aspect of the present disclosure provides a processing device that includes at least one processor and is communicatively connected to a first authentication device configured to acquire first acquired information for authenticating a user using a first authentication method for a first object usable by the user, wherein the at least one processor pre-stores the first acquired information of the user used in the first authentication method and behavioral information indicating an action taken by the user in relation to the first object or an object other than the first object, in association with user identification information for identifying the user, and that, when the first acquired information of the user is acquired by the first authentication device, executes processing to determine whether or not to permit use of the first object based on the behavioral information pre-stored in association with the user identification information.

One aspect of the present disclosure provides a processing program that causes a computer having at least one processor and communicatively connected to a first authentication device configured to acquire first acquired information for authenticating a user using a first authentication method for a first object usable by the user to pre-store the first acquired information of the user used in the first authentication method and behavioral information indicating an action taken by the user in relation to the first object or an object other than the first object, in association with user identification information for identifying the user, and that, when the first acquired information of the user is acquired by the first authentication device, executes a process to determine whether or not to permit use of the first object based on the behavioral information pre-stored in association with the user identification information.

One aspect of the present disclosure provides a processing method executed by at least one processor on a computer communicatively connected to a first authentication device configured to acquire first acquired information for authenticating a user using a first authentication method for a first object usable by the user, the processing method including: a step of pre-storing the first acquired information of the user used in the first authentication method and behavioral information indicating an action taken by the user in relation to the first object or an object other than the first object in association with user identification information for identifying the user; and a step of determining, when the first acquired information of the user is acquired by the first authentication device, whether to allow use of the first object based on the behavioral information pre-stored in association with the user identification information.

This disclosure provides a processing device, processing program, and processing method that enable more efficient management of user usage.

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 the management device 100 according to an embodiment of the present disclosure. FIG. 2B is a block diagram showing a configuration of the authentication device 200 according to an embodiment of the present disclosure. FIG. 3A is a diagram conceptually illustrating a user management table stored in the management device 100 according to an embodiment of the present disclosure. FIG. 3B is a diagram conceptually illustrating a log management table stored in the management device 100 according to an embodiment of the present disclosure. FIG. 3C is a diagram conceptually illustrating an authority management table stored in the management device 100 according to an embodiment of the present disclosure. FIG. 3D is a diagram conceptually illustrating an authentication device management table stored in the management device 100 according to an embodiment of the present disclosure. FIG. 4 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 diagram showing a processing flow executed in the management device 100 according to an embodiment of the present disclosure. FIG. 6A is a diagram conceptually illustrating a method for detecting entrance and exit according to an embodiment of the present disclosure. FIG. 6B is a diagram conceptually illustrating a method for detecting entrance and exit according to an embodiment of the present disclosure. FIG. 7 is a diagram conceptually illustrating a user management table stored in the management device 100 according to an embodiment of the present disclosure. FIG. 8 is a diagram conceptually illustrating a fraud detection method according to an embodiment of the present disclosure. FIG. 9A is a diagram conceptually illustrating an authentication device management table stored in the management device 100 according to an embodiment of the present disclosure. FIG. 9B is a diagram conceptually illustrating an authority management table stored in the management device 100 according to an embodiment of the present disclosure. FIG. 10 is a diagram illustrating a processing flow executed in the management device 100 according to an embodiment of the present disclosure.

1. Overview of the Processing System 1 For example, authentication methods using card readers are used to authenticate users at building gates, which are subject to user restrictions. However, such authentication methods pose a risk of so-called "tailgating." Tailgating occurs when, for example, after employee A authenticates with a card, a person other than employee A passes through the gate together with employee A when the gate opens and is authorized for passage. Employee A may allow guests, such as visitors, to pass through the gate to guide them into the building. However, if unauthorized individuals enter without authorization, there is a risk of information leakage or unauthorized system manipulation. Physical methods for preventing tailgating include monitoring using cameras and reducing the number of seconds required for flapper gates to open, as well as managing entry and exit logs on the control panel that controls the building's systems. Specifically, tailgating is prevented by anti-passback, which monitors the alternating occurrence of "entrance logs" and "exit logs" associated with the card used for authentication.

Anti-passback is also performed by registering location information as the current location using an ID card pre-registered in a database in the local environment as a function of the control panel that controls the building's systems. In this case, when a pre-registered ID card is used to enter, an "entry log" indicating entry for each ID card is recorded. With this method, it is possible to bypass anti-passback if multiple ID cards are in possession. Furthermore, if an ID card is used to enter, it must also be used to exit, and since only one authentication method is supported, greater convenience is needed.

Furthermore, if the anti-passback system detects fraud as described above, a process is executed to prohibit passage through the gate. As a result, if a user attempts to exit even though there is no entry log on the ID card, the user who owns the ID card will not be able to pass through the gate and will be trapped inside. Conversely, if a user attempts to enter even though there is no exit log, the user who owns the ID card will not be able to pass through the gate. In other words, if the ID card is not read properly or if the user happens to pass through the gate at the same time as another user who has passed through before them, trapping or being locked out will occur frequently.

In the processing system 1 disclosed herein, the processing device pre-stores behavioral information (e.g., "entrance log") indicating actions taken by a user in relation to a first object, etc., the use of which is restricted by the user, in association with user identification information for identifying the user. When the first authentication device acquires the user's first acquired information, it determines whether or not to allow the user to use the first object based on the behavioral information pre-stored in association with the user identification information. In other words, the processing device communicatively connected to the first authentication device manages the user's behavioral information online for each user identification, rather than for each ID card, etc. This eliminates the need for authentication using the same first authentication device for entry and exit, and allows for flexible anti-passback control for authentications using devices other than the first authentication device, improving convenience.

Furthermore, the processing device outputs a notification according to attribute information indicating the attributes of the user based on the results of the above judgment. In other words, even if fraud is detected, it does not necessarily restrict use of the first object (for example, prohibiting passage through a gate), and various controls can be implemented according to the attributes (for example, "sounding an alarm" or "sending a notification to a specific person such as an administrator or security guard" when fraud is detected).

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 the following:
A locking/unlocking device 300-1 for locking/unlocking a gate installed in a first object 20-1 (e.g., a building) whose use by a user can be restricted, and a first authentication device 200-1 configured to acquire information (e.g., facial features) for authenticating a user.
A locking/unlocking device 300-2 for locking/unlocking a door installed in a second object 20-2 (for example, an office area) whose use by a user can be restricted, and a second authentication device 200-2 configured to acquire information (for example, an identification code stored in an ID card) for authenticating a user.
A locking/unlocking device 300-3 for locking/unlocking a door installed in a third object 20-3 (e.g., a conference room) whose use by a user can be restricted, and a third authentication device 200-3 configured to acquire information (e.g., a QR code) for authenticating a user.
A management device 100 communicably connected to the first authentication device 200-1, the second authentication device 200-2, and the third authentication device 200-3.

In the present disclosure, an "object" may be anything that can be restricted from being used by a user. Typical examples include buildings, office areas, and conference rooms, as described above. The object may be anything that can be restricted from being used by a user, and is not limited to specific objects. However, examples include the following:
・Buildings, hotels, apartment complexes, houses, event facilities, or specific areas or rooms (conference rooms, conference booths, residences) within buildings or apartment complexes that provide space; ・Gates, doors, and other devices that divide the space; ・Items with restricted use, such as electronic devices such as printers and computers, home equipment such as elevators and delivery boxes, or vehicles such as bicycles and cars.

For ease of explanation, an example will be given here in which a building is used as the first object 20-1, an office area as the second object 20-2, and a conference room as the third object 20-3, but of course this is not limited to this. Furthermore, for ease of explanation, an example will be given here in which a processing system 1 including first object 20-1 to third object 20-3 is used, but the processing system 1 does not necessarily have to include three objects; it could of course include one, two, or four or more objects.

In addition, in this disclosure, "administrator" simply means a person who manages the first object 20-1 to the third object 20-3 or the management device 100. 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 first object 20-1 (e.g., a building) and the management device 100 may be different from the administrator who manages the second object 20-2 (e.g., an office area) and the third object 20-3 (e.g., a conference room).

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 to third authentication methods, first to third authentication devices 200-1 to 200-3, first to third authentication information, and first to third acquired information are used in this disclosure, they can include any of the methods, devices, and information used to perform the authentication exemplified above.

For the sake of convenience, the following case will be described here. However, it is not limited to this. Furthermore, the authentication information, authentication methods, and authentication devices do not need to be different from one another and may be the same type.
First authentication information (first acquired information), first authentication method, and first authentication device 200-1: facial feature amount of a user, face authentication method, and face authentication device. Second authentication information (second acquired information), second authentication method, and second authentication device 200-2: identification code (6-digit number) assigned to each user, method for determining whether an identification code stored in the user's smartphone matches or does not match, beacon device. Third authentication information (third acquired information), third authentication method, and third authentication device 200-3: QR code, method for determining whether an identification code recorded in the QR code matches or does not match, QR code reader device.

In addition, in this disclosure, a "user" may be any person who uses an object. Examples of such users include employees of an institution occupying the building, building security guards, residents of an apartment complex, and guests or service providers who are temporarily permitted to use the object by employees or residents.

In addition, in the present disclosure, "behavioral information" refers to information indicating a user's behavior in relation to a specific object or an object other than the specific object. The behavioral information may be any information indicating the user's behavior and is not limited to specific information, but examples include the following:
- Information indicating whether the user is currently using the object (for example, "entrance log" or "exit log")
Information indicating the user's plans to use the object or other objects (e.g., user's schedule information)
Location information indicating the user's location (e.g., the user's location information 30 minutes ago)

Furthermore, in this disclosure, the "processing device" may be any of the management device 100, the first authentication device 200-1, the second authentication device 200-2, the third authentication device 200-3, and other devices. In other words, when referring to a processing device, it means any of the above devices and is not limited to any one device unless specifically stated. For ease of explanation, the management device 100 will be used here as a specific example of a processing device.

In addition, although terms such as "first" through "third" may be used in this disclosure, unless otherwise specified, these are merely designations used for the convenience of explaining both elements. Therefore, even if terms such as "first" through "third" are used, this does not mean that the elements are limited to only those elements to which they are attached. Naturally, the processing system 1 may include at least one of the "first" through "third" elements, or may include multiple elements such as "fourth," "fifth," and more.

2. Configuration of the Management Device 100 FIG. 2A is a block diagram showing the configuration of the management device 100 according to an embodiment of the present disclosure. The management device 100 does not need to include all of the components shown in FIG. 2A ; it is possible to omit some components, or to add other components. The management device 100 may be a device pre-installed in a facility such as a building, or may be a server device connected online via a network. Furthermore, the management device 100 does not need to include the components shown in FIG. 2A in a single housing; the components and processes of the management device 100 may be distributed across multiple devices, such as on-premise servers or cloud servers.

As shown in FIG. 2A, the management device 100 includes a processor 111 consisting of a CPU or the like, memory 112 including RAM, ROM, non-volatile memory, and an HDD or the like, and a communication interface 113. 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 and programs for executing the OS from the memory 112. Specifically, the processor 111 executes the following processes based on the programs stored in the memory 112: "a process for pre-storing the first authentication information of a user used in the first authentication method and behavioral information indicating the user's behavior in relation to the first object or objects other than the first object, in association with user identification information for identifying the user"; and "a process for determining whether or not to permit use of the first object, based on the behavioral information pre-stored in association with the user identification information, when the first authentication device acquires the user's first acquired information." The processor 111 is primarily composed of one or more CPUs, but may also be combined with a GPU, FPGA, or the like as appropriate.

Memory 112 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 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 retained even after the execution of the programs has ended. Specifically, memory 112 stores programs that allow processor 111 to execute the above-mentioned processes, etc. Memory 112 also stores various types of information, such as a user management table (Figure 3A), a log management table (Figure 3B), an authority management table (Figure 3C), and an authentication device management table (Figure 3D). If necessary, this information may be stored in a database device communicatively connected to management device 100 (in which case, the database may also be included as part of memory 112).

The communication interface 113 functions as a communication unit that transmits and receives information to and from other devices, such as the first authentication device 200-1 to the third authentication device 200-3, which are installed remotely, 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 or a contactless wireless communication method such as a wireless LAN such as IEEE 802.11 or Bluetooth (registered trademark). Wired communication can also be used instead of or in addition to wireless communication.

3. Configuration of Authentication Device 200 FIG. 2B is a block diagram showing the configuration of authentication device 200 according to an embodiment of the present disclosure. Authentication device 200 does not need to include all of the components shown in FIG. 2B ; it is possible to omit some components, or to add other components. Furthermore, authentication device 200 is described as an example of first authentication device 200-1 to third authentication device 200-3, but first authentication device 200-1 to third authentication device 200-3 do not need to have exactly the same configuration as authentication device 200; each authentication device may have a different configuration.

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

The processor 211 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 212. The processor 211 reads and executes programs for executing applications related to the present disclosure and programs for executing the OS from the memory 212. Specifically, the processor 211 performs the following processes based on the programs stored in the memory 212: "accepting acquired information via the input interface 214 and storing it in the memory 212 to acquire the acquired information," "sending the acquired acquired information to the management device 100 via the communication interface 213," "receiving a determination result notification indicating the result of the determination made by the management device 100 from the management device 100 via the communication interface," and "outputting a control signal via an output interface (not shown) based on information that may be included in the determination result notification." The processor 211 is primarily composed of one or more CPUs, but may also be combined with a GPU, FPGA, or the like as appropriate.

Memory 212 includes RAM, ROM, or non-volatile memory, and functions as a storage unit. ROM stores instructions and commands for executing the 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 retained even after execution of the programs has ended. Specifically, memory 212 stores programs that allow processor 211 to execute the above-mentioned processes, etc.

The communication interface 213 functions as a communication unit that transmits and receives information to and from the electrically connected locking/unlocking devices 300 (each of locking/unlocking devices 300-1 to 300-3) and management device 100 via a communication processing circuit. Such a communication processing circuit can also process data based on serial communication such as RS-485, RS-422, or USB; wideband wireless communication methods such as wired LAN and LTE; narrowband wireless communication methods such as wireless LAN and Bluetooth (registered trademark) such as IEEE 802.11; contactless wireless communication methods; or a combination of these.

The input interface 214 functions as an input unit for acquiring authentication information used to authenticate a user. Examples of the input interface 214 include a camera, various sensors such as infrared sensors, and readers for reading information from ID cards, smartphones, etc. via short-range wireless communication or contactless wireless communication. In this embodiment, the input interface includes the most appropriate input interface depending on the authentication method used by each authentication device. For example, if face authentication is used as the first authentication method, a camera is included as the input interface 214; if a method of determining whether an identification code stored in the user's smartphone matches or does not match is used as the second authentication method, a card reader is included; and if a method of determining whether an identification code recorded in a QR code matches or does not match is used as the third authentication method, a QR code reader (camera) is included.

As described above, the processing system 1 includes the locking/unlocking devices 300 (locking/unlocking devices 300-1 to 300-2), etc. Although the specific configurations of these are not particularly illustrated, they include components necessary for executing each process, such as a processor, memory, and communication interface, and each component is electrically connected to each other via control lines and data lines.

3A is a diagram conceptually illustrating a user management table stored in the management device 100 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 management device 100.

As shown in FIG. 3A, the user management table stores attribute information, authority information, first authentication information, second authentication information, nth authentication information, etc., 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 management device 100 when a user or administrator sends a new registration request for a service provided by the processing system 1, for example. "Attribute information" is information related to the attributes of each user. Examples of such attribute information include user name (first and last name), title, position (employee, security guard, guest, resident, etc.), 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.

"Permission information" is information indicating whether each user has permission to use an object. Permission information is information indicating, for example, the times when each user can use the facility (e.g., a combination of days and times, such as Mondays from 9:00 to 17:00) and the locations where the facility can be used. Details of this permission information are explained in Figure 3C.

The "first authentication information" is information used to authenticate a user when the first authentication method is executed in the first authentication device 200-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 facial recognition information of each user (e.g., a facial image or features obtained from the image) is used as the first authentication information. The "second authentication information" is information used to authenticate a user when the second authentication method is executed in the second authentication device 200-2. The second 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 (for example, an identification code may be a six-digit number, but the same identification code may be used for each user). While the example shows authentication information different from the first authentication information as the second authentication information, it may also be the same authentication information as the first authentication information.

Although only the first authentication information and second authentication information have been described above, it is natural that each authentication information is stored corresponding to the installed authentication device, such as third authentication information (e.g., an identification code recorded in a QR code) used to authenticate a user when the third authentication method is executed on the third authentication device. Similarly, fourth authentication information through nth authentication information used on the fourth authentication device through nth authentication device may also be stored, respectively.

Figure 3B is a conceptual diagram illustrating a log management table stored in a management device 100 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 management device 100.

As shown in Figure 3B, the log management table is a table provided for each locking/unlocking device 300. As an example, Figure 3B shows a log management table provided for locking/unlocking device 300-1. Each log management table stores unlocking time information and entry/exit information as behavior information, associated 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 the first authentication device 200-1 installed in correspondence with locking/unlocking device 300-1, user ID information is stored to identify the user.

"Unlocking time information" is information related to the time when an unlocking signal is transmitted from the first authentication device 200-1 to the locking/unlocking device 300-1 as a result of a user being authenticated via the first authentication device 200-1, and is a type of behavioral information. The unlocking time information may directly indicate the time when the unlocking signal was transmitted, may indicate the time when the unlocking signal was received by the locking/unlocking device 300-1, or may indicate the time when authentication was performed to transmit the unlocking signal. In other words, the unlocking time information may be any information that indicates the time when any processing related to the transmission of the unlocking signal was performed.

"Entry/Exit Information" is information indicating whether each user is currently entering or exiting building 10, and is a type of behavioral information. For example, when the first authentication device 200-1 authenticates a user for the first time and generates an unlock signal, "Entry" is stored as the entry/exit information. Thereafter, each time the user is authenticated and entry or exit is detected, "Exit" or "Entry" is stored alternately.

Figure 3C is a conceptual diagram illustrating an authority management table stored in the management device 100 according to an 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 management table shown in Figure 3C is generated for each user's user ID information. In other words, by referencing this authority management table, it is possible to determine whether the user associated with the user ID information has the authority to use each object. Figure 3C shows the authority information of a user with user ID information "A1." According to Figure 3C, time information is stored in association with authentication device ID information for identifying the authentication device installed on each object. "Authentication device ID information" is information unique to the authentication device used to authenticate whether or not a user is permitted to use an object whose use can be restricted, and is information for identifying each authentication device. Note that instead of authentication device ID information, object ID information for identifying each object or locking/unlocking device ID information for identifying each locking/unlocking device can also be used.

"Time information" is information that indicates the content of use that each user is permitted to make of each object. 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; it may be a period specified on a case-by-case basis. In the case of the above-mentioned authority information shown in Figure 3C, for example, it indicates that a user with user ID information "A1" can use a building in which an authentication device with authentication device ID information "G1" is installed between 9:00 and 22:00 on weekdays, and can use a conference room in which an authentication device with authentication device ID information "G4" is installed between 12:00 and 13:00 on weekdays.

Figure 3D is a conceptual diagram illustrating an authentication device management table stored in a management device 100 according to an embodiment of the present disclosure. The information stored in the authentication device management table is updated and stored as necessary according to the progress of processing by the processor 211 of the management device 100.

As shown in Figure 3D, the authentication device management table stores location information and the like in association with authentication device ID information. As described above, "authentication device ID information" is information specific to each authentication device used to authenticate whether or not a user is permitted to use an object whose use can be restricted, and is information used to identify each authentication device. The authentication ID information is information generated in the management device 100, for example, when a new authentication device 200 is installed in association with an object and receives a request from an administrator, etc.

"Location information" is information used to identify the location where each authentication device is installed. Examples of this location information include information that conceptually indicates the installation location, such as a "building" or "office area," but it can also be any information such as coordinate information, an address, or a base station acquired by each authentication device via wireless communication. Furthermore, location information does not simply indicate the location of a "building," but can also include information such as "outside the building" or "inside the building." This type of location information makes it possible to more appropriately determine whether a user has entered or exited.

In addition to this information, although not specifically shown, in some cases, usage information indicating whether each authentication device is used for entry or exit may be stored in association with each authentication device ID information. For example, if there are a pair of authentication devices installed at the gate of a building, one authentication device may be stored as being for entry in association with the authentication device ID information, and the other authentication device may be stored as being for exit in association with the authentication device ID information. This makes it possible to determine whether a user passing through the gate is attempting to enter or exit.

6. Processing Sequence Executed by Processing System 1 FIG. 4 is a diagram illustrating a processing sequence executed by the processing system 1 according to an embodiment of the present disclosure. Specifically, FIG. 4 illustrates a processing sequence executed between the management device 100, the first authentication device 200-1, and the first locking/unlocking device 300-1 for an authentication device registration process for registering a newly installed authentication device in the management device 100, a user registration process for acquiring a new user in the management device 100, and an authentication process for authenticating a user using information acquired by the authentication device. The processing in each device is executed by a processor running a program stored in the memory of each device. Note that the following description focuses on the case where the first authentication device 200-1 is newly installed. Furthermore, although the second authentication device 200-2 and the second locking/unlocking device 300-2, and the third authentication device 200-3 and the third locking/unlocking device 300-3 are not specifically described, they execute processing in the same manner as the first authentication device 200-1 and the first locking/unlocking device 300-1.

(A) Authentication Device Registration Process According to FIG. 4, the processor 111 of the management device 100 receives a registration request for a new first authentication device 200-1 from an administrator terminal device available to the administrator via the communication interface 113. The registration request includes at least location information for the first authentication device 200-1 newly installed relative to the target object and information indicating the communication destination of the first authentication device 200-1 (e.g., an IP address). Upon receiving the registration request, the processor 111 generates new authentication device ID information (S11). After generating the authentication device ID information, the processor 111 stores the generated authentication device ID information in the authentication device management table, and also stores the location information included in the registration request in association with the authentication information ID information (S12). This completes the authentication device registration process.

Although not specifically shown, when a new first authentication device 200-1 is registered, the processor 111 of the management device 100 sends the generated authentication device ID information along with a notice of the new registration to the first authentication device 200-1 via the communication interface 113. The processor 211 of the first authentication device 200-1 then stores the received authentication device ID information as its own authentication device ID information.

Also, although not specifically shown, if usage information is stored in the authentication device management table, the usage information for each authentication device included in the registration request (information indicating whether it is an entry authentication device or an exit authentication device) is stored in association with the authentication device ID information.

(B) User Registration Processing According to FIG. 4, the processor 111 of the management device 100 receives a user registration request for a new user via the communication interface 113 from an administrator terminal device available to the administrator. The user registration request includes attribute information, authority information, and first authentication information of the user who wishes to newly register. Examples of the attribute information include the user's name (first 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 (FIG. 3C) indicating the available times and facilities, which have been set for the user by the administrator in advance.

When the processor 111 of the management device 100 receives a user registration request, it generates new user ID information (S21). Then, the processor 111 of the management device 100 associates the received attribute information and authority information with the generated user ID information and stores them in the user management table and authority management table (S22). The processor 111 of the management device 100 also associates facial image data with the user ID information and stores it in the user management table as first authentication information for newly authenticating the user (S23). This completes the user registration process.

The facial image data stored as the first authentication information may be the image data of the facial image itself, image data after image processing has been performed on the image data, or feature data extracted from the image data.

(C) Authentication Process As shown in FIG. 4, the first authentication device 200-1 includes a sensor (camera) as an input interface 214 for acquiring a user's facial image. The processor 211 of the first authentication device 200-1 activates the input interface 214 by detecting a user's operational input via, for example, an operational input interface. When the processor 211 detects the user's face within the camera's field of view, it acquires the user's facial image as first acquired information corresponding to the first authentication information used in the first authentication method (S31). Note that, although a facial image is used as the first acquired information, feature quantities calculated from the facial image may be used instead. Furthermore, although a sensor (camera) is used as the input interface 214 and a facial image is acquired as the first acquired information in the above example, the acquisition method may be changed as appropriate depending on the type of first acquired information. For example, in the case of knowledge-based authentication (e.g., user memory), the first acquired information may be acquired via an input interface such as a numeric keypad or keyboard. In addition, in the case of possession-type authentication (e.g., ID card, smartphone, QR code, license, token, etc.), the first acquired 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. In addition, in the case of biometric-type authentication (e.g., fingerprint, voice, iris, face, etc.), the first acquired information may be acquired via a camera or a sensor.

At this time, the processor 211 of the first authentication device 200-1 determines whether the user from whom the first acquired information was acquired is attempting to enter or exit the building, which is the target object. Details of this determination will be explained in Figures 6A and 6B, etc.

When the processor 211 of the first authentication device 200-1 acquires the first acquisition information, it transmits an authentication request (T31) to the management device 100 via the communication interface 213. The authentication request includes at least the following information:
- Acquired first acquired information - Information indicating whether the person is attempting to enter or exit - Authentication device ID information of the first authentication device

Next, when the processor 111 of the management device 100 receives the first acquired information via the communication interface 113, it references the user management table. Specifically, the processor 111 references the user management table and determines whether the first authentication information corresponding to the authentication ID information of the first authentication device matches the first acquired information, thereby authenticating the user (S32).

Next, if matching first authentication information is found, the processor 111 of the management device 100 identifies the user ID information corresponding to that first authentication information and references the authority information associated with that user ID information (S33). Specifically, the processor 111 obtains the time at which the first acquisition information was received from the first authentication device 200-1 from a timer (not shown) of the management device 100. The processor 111 then compares the obtained time with the time information stored in association with the authentication device ID information of the first authentication device 200-1, and determines whether the obtained time satisfies the available time (for example, a combination of day of the week and time, such as 9:00 to 22:00 on weekdays).

Next, if the acquired time satisfies the available time, the processor 111 of the management device 100 performs an entry/exit determination (S34). Specifically, the processor 111 references the log management table based on the identified user ID information and reads out the entry/exit information, which is one type of behavior information. The processor 111 then compares the information indicating entry or exit contained in the authentication request with the read entry/exit information to determine whether the use of the object is unauthorized, and determines whether entry or exit is permitted based on the result. The processor 111 transmits determination result information (T32) generated based on the determination result to the first authentication device 200-1 that sent the authentication request via the communication interface 113. The determination result information includes notification information for outputting the determination result in the first authentication device 200-1, information indicating whether it is OK to send an unlocking signal to the locking/unlocking device 300-1, and so on.

Note that, although the determination result information is sent only to the first authentication device 200-1 here, it may of course also be sent to other devices. For example, depending on the circumstances, it may be sent to an administrator terminal device available to the administrator or a security guard terminal device available to the security guard. Details of this will be explained in Figure 9B, etc.

When the processor 211 of the first authentication device 200-1 receives the judgment result information, it displays the received judgment result information on a display or the like via an output interface (not shown in Figure 2) (S35), and, depending on the result, sends an unlocking signal (T33) via the communication interface 213 to the correspondingly installed locking/unlocking device 300-1. The locking/unlocking device 300-1 unlocks the gate on which the locking/unlocking device 300-1 is installed, allowing the user to use the object. This completes the authentication process.

7. Processing Flow of the Management Device 100 in the Authentication Process Fig. 5 is a diagram showing a processing flow executed by the management device 100 according to an embodiment of the present disclosure. Specifically, Fig. 5 is a diagram showing the flow of the authentication processing performed by the management device 100 in S32 to S34 of Fig. 4. This processing flow is mainly performed by the processor 111 of the management device 100 reading and executing a program stored in the memory 112.

5, the processor 111 receives an authentication request from the first authentication device 200-1 via the communication interface 113 (S111). As described above, the authentication request includes at least the following information:
- Acquired first acquired information - Authentication device ID information of the first authentication device

When processor 111 receives an authentication request, it refers to the user management table and authenticates the user (S112). Specifically, processor 111 refers to the user management table and determines whether the first authentication information corresponding to the authentication ID information of the first authentication device contains first authentication information that matches the first acquired information included in the authentication request. If the first authentication information matches any of the first authentication information, processor 111 reads the user ID information associated with the matching first authentication device and proceeds to the next process, assuming that the user is a legitimate user.

Next, the processor 111 reads the authority information (Figure 3C) from the user management table based on the read user ID information, and makes a judgment based on the authority information (S113). Specifically, the processor 111 obtains the time at which the first acquisition information was received from the first authentication device 200-1 from a timer (not shown) in the management device 100. The processor 111 then compares the obtained time with the time information stored in association with the authentication device ID information of the first authentication device 200-1, and determines whether the obtained time satisfies the available time (for example, a combination of day of the week and time, such as 9:00 to 22:00 on weekdays).

Next, if the acquired time satisfies the available time, processor 111 determines whether the user is entering or leaving based on the entry/exit information, which is behavior information (S114). Specifically, processor 111 references the authentication device management table and reads the location information or usage information stored in association with the authentication device ID information of the first authentication device. Then, processor 111 determines whether the user's behavior is entering or leaving based on the location information or usage information.

Figures 6A and 6B are conceptual diagrams illustrating a method for detecting entry and exit according to an embodiment of the present disclosure. Of these, Figure 6A illustrates an example of detecting entry and exit using a pair of an entry first authentication device 200-1a and an exit first authentication device 200-1b, while Figure 6B illustrates an example of detection using a beacon signal in a second authentication device 200-2.

Figure 6A shows a side view of the locking/unlocking device 300-1 installed at the entrance of a building. As shown in Figure 6A, the locking/unlocking device 300-1 is equipped with an entry first authentication device 200-1a for acquiring the user's first acquired information upon entry, and an exit first authentication device 200-1b for acquiring the user's first acquired information upon exit. When the locking/unlocking device 300-1 acquires the first acquired information in either device and receives determination result information from the management device 100, it unlocks the gate 311 based on the received determination result information.

At this time, when the entry first authentication device 200-1a and the exit first authentication device 200-1b are installed, the entry first authentication device 200-1a stores the location information "outside the building," and the exit first authentication device 200-1b stores the location information "inside the building." Therefore, when an authentication request including the authentication device ID information of the entry first authentication device 200-1a is received from the entry first authentication device 200-1a, it is determined that the user has entered because the authentication device is installed outside the building. Similarly, when an authentication request including the authentication device ID information of the exit first authentication device 200-1b is received from the exit first authentication device 200-1b, it is determined that the user has exited because the authentication device is installed inside the building.

Furthermore, when the entrance first authentication device 200-1a and the exit first authentication device 200-1b are installed, the entrance first authentication device 200-1a may store "entrance" as its usage information, and the exit first authentication device 200-1b may store "exit." In such a case, when an authentication request including the authentication device ID information of the entrance first authentication device 200-1a is received from the entrance first authentication device 200-1a, it can be determined that the user has entered, and when an authentication request including the authentication device ID information of the exit first authentication device 200-1b is received from the exit first authentication device 200-1b, it can be determined that the user has exited.

In this way, a pair of first authentication devices, 200-1a for entry and 200-1b for exit, is provided for the locking/unlocking device 300-1, making it possible to detect the entry and exit of a user based on their location information or application information.

Note that Figure 6A illustrates a case in which a pair of first authentication devices, entrance 200-1a and exit 200-1b, are installed. However, it is not necessary for these authentication devices to be installed in the same space (for example, a specific entrance to a building). For example, an authentication device could be installed at a gate dedicated to entrances to a building, and another authentication device could be installed at a gate dedicated to exits, and each authentication device could be associated with and stored with location information such as "entrance gate" or "exit gate," or purpose information such as "entrance" or "exit." This also makes it possible to detect user entry and exit, just as in the case of Figure 6A.

In addition, multiple authentication devices are often installed depending on the object. For example, if the object is a building, there may be multiple gates for entering and exiting the building, each with an authentication device installed. In such cases, by registering location information and purpose information for each authentication device in advance as described above, it is possible to freely set the gates used for entry and exit.

In the above description, location information and usage information are stored in advance in the authentication device management table, and a pair of authentication devices such as the one shown in Figure 6A is used. However, this is not limited to this. For example, it is also possible to include "information indicating whether a user is attempting to enter or exit" in the authentication request, and detect whether a user is entering or exiting based on this information.

As an example of such a case, FIG. 6B shows a door 312 at the entrance to an office area that restricts entry and exit. The door 312 is equipped with a locking/unlocking device 300-2 and a second authentication device 200-2 for acquiring the user's second authentication information. When the second authentication device 200-2 acquires the second acquired information and receives the judgment result information from the management device 100, the locking/unlocking device 300-2 unlocks the door 312 based on the received judgment result information. At this time, the second authentication device 200-2 transmits a beacon signal at a predetermined interval to the user's smartphone (terminal device) that stores the identification code, which is the second acquired information. The signal strength of the beacon signal in the direction of the wall is attenuated by the walls of the office area, which are made of metal or other materials. Alternatively, the direction and signal strength of a directional beacon signal can be controlled. Therefore, the smartphone (terminal device) detects the location or strength of the beacon signal received to detect entry and exit. For example, when a smartphone (terminal device) is brought close to second authentication device 200-2 and an identification code is received, second authentication device 200-2 transmits a beacon signal with different signal strengths on the entry and exit sides. The smartphone (terminal device) then determines entry and exit based on the strength of the received signal (for example, a high signal strength on the exit side and a low signal strength on the entry side). The smartphone (terminal device) then transmits the result to second authentication device 200-2, which then detects entry and exit.

As another example, the second authentication device 200-2 can read identification codes via contactless communication (for example, NFC) and via BLE communication. In this case, if a user holds a smartphone (terminal device) over the second authentication device 200-2 and the identification code is read via contactless communication, it is determined that the user has left the venue, and if the identification code is read via BLE communication between the second authentication device 200-2 and the second authentication device 200-2, it is determined that the user has entered the venue, thereby making it possible to detect entry and exit.

In addition to the methods shown in Figures 6A and 6B, it is also possible to detect entry and exit using, for example, a camera provided on the first authentication device 200-1 or the second authentication device 200-2, or a camera or human sensor provided near these devices. Furthermore, for example, when a user uses an authentication device, the user can use the authentication device to select "enter" or "exit."

Returning again to FIG. 5, once processor 111 determines whether a user has entered or exited based on the information indicating entry or exit detected using the method shown in FIGS. 6A and 6B, etc., it references the log management table (S115). Specifically, processor 111 reads out the behavior information associated with the read user ID information, i.e., the entry and exit information, from the log management table. Then, processor 111 compares the information indicating entry and exit determined in S114 with the read log management table to determine whether the entry and exit conditions are met (S116).

Here, examples of entry and exit conditions include the following:
Condition 1: If "entry" is determined in S114, use is permitted only if the entry/exit information read from the log management table is "exit." Condition 2: If "exit" is determined in S114, use is permitted only if the entry/exit information read from the log management table is "entry."

In other words, the processor 111 determines that the use of the object is not unauthorized and permits its use only if any of the above conditions is met. The processor 111 then generates determination result information based on the results of the above determination (S117). Note that if the determinations in S112, S113, and S116 are all satisfied, the determination result information includes notification information for outputting from the first authentication device 200-1 that the use of the object is permitted, and information indicating that an unlocking signal may be sent to the locking/unlocking device 300-1. On the other hand, if at least any of the determinations in S112, S113, and S116 are not satisfied, the determination result information includes notification information for outputting from the first authentication device 200-1 that the use of the object is not permitted. In particular, if the determination in S116 is not satisfied, the determination result information includes information indicating that the user is using the object unauthorizedly.

This concludes the processing flow of the management device 100 for authentication processing. In this way, by using the entry/exit information associated with the user ID information as behavioral information, it is possible to more accurately restrict irregular behavior (e.g., unauthorized use of an object), such as re-entering after entering without exiting, or re-exiting after exiting without entering or exiting. Furthermore, the entry/exit information is stored in the management device 100 in association with the user ID information, rather than being associated with the identification code used for authentication. Therefore, even if a user enters using the first authentication device 200-1 and exits the object using a different authentication device, it is possible to grasp the behavioral information based on the user ID information, thereby improving user convenience.

Note that while Figure 5 illustrates the case where the first acquisition information is acquired by the first authentication device 200-1, similar processing can also be performed by the second authentication device 200-2 and the third authentication device 200-3.

6, the entry/exit information stored in association with the user's user ID information is used to determine whether or not the user is permitted to use the object (S115). However , the user's schedule information can also be used in addition to or instead of the entry/exit information.

Figure 7 is a conceptual diagram of a user management table stored in the management device 100 according to an embodiment of the present disclosure. As shown in Figure 7, the user management table stores schedule information for each user in association with user ID information. "Schedule information" is information that identifies events that a user will participate in, attend, or carry out, as well as the location and time of the events, and is a type of behavioral information. Each event stored as schedule information may be held at the object where the first authentication device 200-1 is installed, or may be held at another object.

Note that the attribute information, attribute information, authority information, first authentication information, second authentication information, and nth authentication information other than schedule information are the same as those in the user management table shown in Figure 3A.

Next, we will explain a case where, instead of making a judgment based on entry/exit information, which is one type of behavior information, in steps S114 to S116 of Figure 5, a judgment is made based on schedule information, which is also one type of behavior information.

As shown in FIG. 5, when processor 111 determines that the authority information is satisfied (S113), it references the user management table shown in FIG. 7 and identifies the schedule information associated with the read-out user ID information. Based on the schedule information, processor 111 identifies events and their locations whose holding times are set to occur in the current or a specified period before or after the current time. Processor 111 also references the authentication device management table and identifies location information associated with the authentication device ID information of the first authentication device that transmitted the first authentication information. Processor 111 then compares the event location identified based on the schedule information with the location information of the first authentication device. If, as a result of the comparison, the distance between the two locations exceeds a predetermined threshold (e.g., 100 m), processor 111 restricts use of the object, but allows use of the object if the distance is within the threshold. The processing after a determination based on the behavior information is the same as that shown in FIG. 5.

In this way, by using schedule information associated with user ID information as behavioral information, a user who is in a location where they should not be according to the schedule information can be considered to be engaging in irregular behavior, and their use of the object can be restricted.

In the above, we have described a case where, instead of making a judgment based on entry/exit information, which is one type of behavior information, in S114 to S116 of FIG. 5, a judgment is made based on schedule information, which is also one type of behavior information. However, in addition to making a judgment based on entry/exit information, etc. in S114 to S116 of FIG. 5, a judgment may also be made based on schedule information. In other words, the processor 111 executes processing using the schedule information after making the judgments in S111 to S116 of FIG. 5. This ensures even higher security and user convenience.

6, the entrance/exit information stored in association with the user's user ID information is used to determine whether or not the user is permitted to use the object (S115). However, the user's location information can also be used in addition to or instead of the entrance/exit information.

Figure 8 is a diagram conceptually illustrating a fraud detection method according to an embodiment of the present disclosure. Specifically, Figure 8 shows a floor plan of the first floor of a building. According to Figure 8, a first authentication device 200-1 and a first locking/unlocking device 300-1 are installed near a gate that restricts use of building X1, which is the first object 20-1. As the user moves from the gate along arrow R1, the second authentication device 200-2 and a second locking/unlocking device 300-2 are installed near a door that restricts use of office area X2, which is the second object 20-2. Furthermore, as the user moves from the door along arrow R2, the third authentication device 200-3 and a third locking/unlocking device 300-3 are installed near a door that restricts use of conference room X7, which is the third object 20-3.

For ease of explanation, the following describes the case where the second authentication information is acquired by the second authentication device 200-2. In this case, the processor 111 is authenticated by the first authentication device 200-1 and is permitted to use building X1, which is the first object 20-1, and therefore stores, as behavioral information, time information indicating the time at which the first acquired information was received from the first authentication device 200-1 and location information at which the authentication was performed (location information of the first authentication device 200-1) in the user management table. Apart from this, the process up to the point where the processor 111 determines whether the authority information is satisfied is performed in the same manner as S111 to S113 in FIG. 5.

As shown in FIG. 5, when the processor 111 determines that the authorization information is satisfied (S113), it references the user management table shown in FIG. 7 and identifies the time information and location information, which are part of the behavioral information associated with the read user ID information. The processor 111 also obtains, from the timer, time information indicating the time at which the second acquisition information was received from the second authentication device 200-2, and obtains the location information of the second authentication device 200-2 from the authentication device management table. The processor 111 then calculates the distance between the first authentication device 200-1 and the second authentication device 200-2 from the location information of the two devices, and calculates the time required to travel between the two devices from the time information. The processor 111 calculates the user's movement speed from this calculation result, and if the movement speed exceeds a predetermined threshold, it determines that there is a possibility of fraudulent use and restricts use of the object. On the other hand, if the movement speed is equal to or less than the threshold, the processor 111 allows use of the object. The processing after a determination based on the behavioral information is the same as that shown in FIG. 5.

The third authentication device 200-3 can also perform similar processing by using the time at which each piece of authentication information was received from the first authentication device 200-1 or the second authentication device 200-2 and the location information of each authentication device as behavioral information. The first authentication device 200-1 can also perform similar processing by using behavioral information related to other authentication devices that were used for authentication earlier than the first authentication device 200-1. Furthermore, in FIG. 8, a fourth authentication device 200-4 and a fourth locking/unlocking device 300-4 are located near a door restricting use of conference room X3, which is the fourth object 20-4; a fifth authentication device 200-5 and a fifth locking/unlocking device 300-5 are located near a door restricting use of conference room X4, which is the fifth object 20-5; a sixth authentication device 200-6 and a sixth locking/unlocking device 300-6 are located near a door restricting use of conference room X5, which is the sixth object 20-6; a seventh authentication device 200-7 and a seventh locking/unlocking device 300-7 are located near a door restricting use of conference room X6, which is the seventh object 20-7; and an eighth authentication device 200-8 and an eighth locking/unlocking device 300-8 are located near a door restricting use of conference room X8, which is the eighth object 20-8. Each of these authentication devices can be handled in the same way as the first authentication device 200-1 to the third authentication device 200-3.

In addition, while the time and location information when acquired information was received from a previously used authentication device are used as behavioral information here, other information can also be used. For example, various information can be used as behavioral information, such as GPS or other location information on the user's smartphone (terminal device) and the time information acquired from it, time information when the user used NFC as they passed through a station and the location information of the ticket gate, time information when the user used electronic payment at a store and the location information of that store, and time information when an authentication device was used to unlock an electronic lock at the user's remote home and the location information thereof.

In addition, the threshold for movement speed in the above case can be a speed known as the typical human walking speed. However, instead of this, for example, the time it takes for other users to pass through the same section can be stored for each user, and the average of this time can be calculated at any time. This calculated value can then be used as a threshold, and a determination can be made by comparing the time required to travel between the two devices with the threshold. Furthermore, whether or not there is fraud can be determined by inputting the movement patterns between the two devices of the user performing this authentication into a trained analysis model that has been machine-learned to learn pairs of movement patterns when other users pass through the same section and labels indicating whether or not there is fraud.

In this way, by using past location information associated with user ID information as behavioral information, users who are recognized as having clearly abnormal movements can be deemed to be engaging in irregular behavior and their use of the target object can be restricted. For example, if behavioral information is detected in a hotel in Okinawa and then immediately after acquisition information used for authentication is acquired in a building in Tokyo, this is clearly abnormal, but it is possible to detect such fraudulent user behavior.

In the above, instead of making a judgment based on entry/exit information, which is one type of behavioral information, in S114 to S116 of FIG. 5, a judgment based on location information, which is one type of behavioral information, has been described. However, in addition to making a judgment based on entry/exit information, etc. in S114 to S116 of FIG. 5, a judgment may also be made based on location information, etc. Furthermore, in addition to these, schedule information, as shown in FIG. 7, may also be added to make a judgment. In other words, the processor 111 performs processing using the above-mentioned location information, etc., after making the judgments in S111 to S116 of FIG. 5. This ensures even higher security and user convenience.

5, if the conditions in S112, S113, and S116 are not satisfied, the determination result information includes information indicating that the use of the object is restricted. However, in S116, which is a determination based on behavioral information, more diverse fraud detection can be performed depending on the user's attributes, and the determination result information can be output in more diverse forms.

FIG. 9A is a diagram conceptually illustrating an authentication device management table stored in the management device 100 according to an embodiment of the present disclosure. According to FIG. 9A , fraud detection information is stored in association with authentication device ID information. The "fraud detection information" is information that defines the conditions for detecting fraudulent behavior for each user attribute. For example, for the first authentication device 200-1 (authentication device ID information is "G1") installed in a building, which is the first object 20-1, the following conditions are defined:
・If the attribute information is "employee" or "guest", it will be considered fraudulent if the entry and exit conditions are not met at both entry and exit. ・If the attribute information is "security guard", it will not be considered fraudulent even if the entry and exit conditions are not met at both entry and exit.

Furthermore, different fraud detection information may be stored for each piece of authentication device ID information. For example, the following conditions are defined for the third authentication device 200-3 (whose authentication device ID information is "G3") installed in the conference room, which is the third object 20-3:
・If the attribute information is "employee", not meeting the entry and exit conditions at both entry and exit will be considered fraudulent. ・If the attribute information is "guest", not meeting the entry and exit conditions at both entry and exit will be considered fraudulent. ・If the attribute information is "guest", not meeting the entry and exit conditions at both entry and exit will not be considered fraudulent. ・If the attribute information is "security guard", not meeting the entry and exit conditions at both entry and exit will not be considered fraudulent.

In this way, by setting various fraud detection information according to the user's attributes, it is possible to detect various frauds according to each user's attributes. Note that other information is the same as in Figure 3D.

FIG. 9B is a conceptual diagram illustrating an authority management table stored in the management device 100 according to an embodiment of the present disclosure. As described in FIG. 3C, the authority management table is a table generated for each user. Specifically, FIG. 9B illustrates authority information for a user having user ID information "A1." According to FIG. 9B, notification information is stored in association with authentication device ID information. The "notification information" is information for specifying the content to be transmitted as determination result information. For example, if the attribute information of a user having user ID information "A1" is "employee," the following notification information (notification content and transmission destination) is stored in case each authentication device determines that the user has committed fraud:
Notification information "P1": fraud detection error information output by the first authentication device 200-1 and the security guard terminal device of the security guard, audio guidance information indicating that an error has occurred output by a microphone installed at the gate, and a locking signal for the first locking/unlocking device 300-1 of the gate. Notification information "P2": fraud detection error information output by the second authentication device 200-2, the security guard terminal device of the security guard, and the manager terminal device of the manager, and a locking signal for the second door locking/unlocking device 300-2. Notification information "P3": fraud detection error information output by the third authentication device 200-3, and a locking signal for the third door locking/unlocking device 300-3.

In addition, if the attribute information of a user with user ID information "A1" is "guest," the following notification information (notification content and destination) is stored in case each authentication device determines that the user is fraudulent.
Notification information "P1": fraud detection error information output from the first authentication device 200-1 and the security guard terminal device of the security guard, audio guidance information indicating that an error has occurred output from a microphone installed at the gate, and a locking signal for the first locking/unlocking device 300-1 of the gate. Notification information "P2": fraud detection error information output from the second authentication device 200-2, the security guard terminal device of the security guard, and the employee terminal device of the employee who invited the guest, and a locking signal for the second locking/unlocking device 300-2 of the door. Notification information "P3": fraud detection error information output from the third authentication device 200-3 and the employee terminal device of the employee who invited the guest, and a locking signal for the third locking/unlocking device 300-3 of the door.

Furthermore, if the attribute information of a user with user ID information "A1" is "security guard," fraud will not be determined by each authentication device, and notification information when fraud is determined will not be stored.

In this way, by setting various notification information according to the user's attributes, it is possible to send notifications when various fraud is detected according to each user's attributes. Note that other information is the same as in Figure 3C.

Figure 10 is a diagram showing a processing flow executed by a management device 100 according to an embodiment of the present disclosure. Specifically, Figure 10 is a diagram showing a processing flow using the fraud detection information of Figure 9A and the notification information of Figure 9B in the authentication processing performed by the management device 100 in S32 to S34 of Figure 4. This processing flow is mainly performed by the processor 111 of the management device 100 reading and executing a program stored in memory 112.

According to FIG. 10, steps S211 to S216 are the same as steps S111 to S116 in FIG. 5. Next, if the processor 111 determines in S216 that the entry/exit information, which is behavior information, is not met, the processor 111 proceeds to processing in S217. The processor 111 references the user management table based on the read user ID information and identifies attribute information associated with the user ID information (for example, information indicating the user's status as an employee, security guard, guest, or resident). The processor 111 then references the authentication device management table in FIG. 9A and reads out the fraud detection information set for the identified attribute information from the fraud detection information associated with the authentication device ID information of the first authentication device 200-1 that transmitted the acquired information. Based on the read fraud detection information, the processor 111 determines whether to deem the entry/exit condition to be fraudulent even if the entry/exit condition is not met (S217).

For example, if the user's attribute information is "employee" or "guest," not meeting the entry and exit conditions at both entry and exit will be considered fraudulent. Also, if the user's attribute information is "security guard," not meeting the entry and exit conditions at both entry and exit will not be considered fraudulent.

Next, the processor 111 executes a process to generate judgment result information in the same manner as S117 in FIG. 5 (S218). At this time, if the processor 111 determines that fraud has occurred based on the fraud detection information, it references the authority management table in FIG. 9B and generates notification information. Specifically, the processor 111 references the authority management table associated with the read-out user ID information and reads out notification information associated with the authentication device ID information of the first authentication device 200-1. For example, if the user's attribute information is "employee," the following notification information is read out: fraud detection error information output from the first authentication device 200-1 and the security guard terminal device of the security guard; audio guidance information output from the microphone installed at the gate indicating that an error has occurred; and a locking signal to the first locking/unlocking device 300-1 of the gate. Furthermore, if the user's attribute information is "guest," the following notification information is read out: fraud detection error information output from the first authentication device 200-1 and the security guard terminal device of the security guard; audio guidance information output from the microphone installed at the gate indicating that an error has occurred; and a locking signal sent to the gate's first locking/unlocking device 300-1.

This completes the processing flow. In this way, by setting various fraud detection information according to user attribute information, it becomes possible to detect various frauds according to each user's attributes. Furthermore, by setting various notification information according to user attributes, it becomes possible to notify various fraud detections according to each user's attributes.

As described above, this embodiment makes it possible to provide a processing device, processing program, and processing method that enable more efficient management of user usage.

4 is performed by the management device 100. However, it is also possible for any of the first authentication device 200-1 to the third authentication device 200-3 to act as a master and execute the processing .

Furthermore, S32 to S34 in Figure 4, Figures 5 and 10, etc., describe a case where the management device 100 and each authentication device are connected so that they can communicate with each other, and each process is executed in the management device 100. However, it is also possible for the processor 111 of the management device 100 to send the attribute information, authority information, and authentication information stored in the user management table to each authentication device in advance, and for the processor of each authentication device to execute the authentication process.

In this case, because each authentication device does not have the latest log management table information (entry/exit information), it is unable to access the latest entry/exit information. In particular, if the management device 100 and each authentication device go offline due to a communication failure or other reason, the latest entry/exit information cannot be accessed, as described above. In such a case, the authentication device's processor authenticates the user using previously received authentication information and skips the determination of whether the entry/exit conditions are met. In other words, if the authentication information and authorization information are met, the authentication device's processor generates determination result information indicating that it is OK to send an unlock signal. Then, once the communication failure between the management device 100 and the authentication device is resolved, the authentication device's processor obtains the latest entry/exit information and determines whether the entry/exit conditions are met, or it may send a determination request to the management device 100 and have the management device 100 determine whether the entry/exit conditions are met. The determination may subsequently detect fraud. In this case, the fraud is reported as determination result information after the fact.

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 20-1 First object 20-2 Second object 20-3 Third object 100 Management device 200 Authentication device 200-1 First authentication device 200-2 Second authentication device 200-3 Third authentication device 300 Locking/unlocking device 300-1 First locking/unlocking device 300-2 Second locking/unlocking device 300-3 Third locking/unlocking device

Claims (11)

A processing device communicatively coupled to a first authentication device configured to acquire first acquired information for authenticating a user by a first authentication method at a first object available to the user, the processing device comprising at least one processor,
The at least one processor:
the first acquired information of the user used in the first authentication method and behavior information indicating a behavior performed by the user in relation to the first object or an object other than the first object are stored in advance in a memory of the processing device in association with user identification information for identifying the user;
When the first acquired information of the user is acquired in the first authentication device, it is determined whether or not the first object is being used fraudulently based on the behavior information that is associated with the user identification information and that is pre-stored in the memory in association with the user identification information and the first acquired information .
configured to perform processing for
A processing device, wherein the behavioral information includes information indicating whether the first object is currently being used based on detection by any authentication device, including the first authentication device and another authentication device that is communicatively connected and capable of authentication using an authentication method different from that of the first authentication device. The processing device according to claim 1, wherein the at least one processor is configured to execute processing for outputting a notification according to attribute information indicating the attributes of the user based on the result of the determination. The processing device according to claim 1, wherein the at least one processor is configured to, when first acquired information of the user is acquired by the first authentication device, execute processing to determine whether the first object is being used fraudulently based on the acquired first acquired information and first authentication information pre-stored in association with the user identification information for authenticating the user, in addition to the behavior information pre-stored in association with the user identification information. the first object is a space in which at least one of entry and exit of the user is managed,
The behavior information includes information indicating whether the user is currently entering or exiting the space,
the at least one processor is configured to execute a process for not determining that the use is fraudulent if the first acquired information is acquired in the first authentication device to enter the space and behavior information indicating exit is stored;
The processing device of claim 1 . The processing device according to claim 1, wherein the behavioral information includes the user's schedule information stored in association with the venue. The processing device of claim 5, wherein the at least one processor is configured to execute a process for determining whether or not the use is fraudulent based on the venue associated with the schedule information and the user's current location information. The processing device of claim 1, wherein the behavioral information includes the user's past location information. The processing device of claim 7, wherein the at least one processor is configured to execute processing to determine whether or not use is fraudulent based on the past location information and the user's current location information. The processing device described in claim 8, wherein the past location information and the current location information are information acquired by a terminal device carried by the user, the first authentication device, and a second authentication device configured to acquire second acquired information for authenticating the user using a second authentication method at a second object whose use by the user is restricted. A computer is communicatively connected to a first authentication device configured to acquire first acquired information for authenticating a user by a first authentication method at a first object available to the user, the computer comprising at least one processor, the at least one processor comprising:
the first acquired information of the user used in the first authentication method and behavior information indicating a behavior performed by the user in relation to the first object or an object other than the first object are stored in advance in a memory of the computer in association with user identification information for identifying the user;
When the first acquired information of the user is acquired in the first authentication device, it is determined whether or not to permit use of the first object based on the behavior information that is associated with the user identification information and that is pre-stored in the memory and the first acquired information .
A processing program that functions to execute processing for
A processing program in which the behavioral information includes information indicating whether the first object is currently being used based on detection by any authentication device, including the first authentication device and another authentication device that is communicatively connected and capable of authentication using an authentication method different from that of the first authentication device. A processing method executed by at least one processor in a computer communicatively connected to a first authentication device configured to acquire first acquisition information for authenticating a user by a first authentication method at a first object available to the user, the computer comprising the at least one processor, the processing method comprising:
a step of previously storing in a memory of the computer the first acquired information of the user used in the first authentication method and behavioral information indicating a behavior performed by the user in relation to the first object or an object other than the first object, in association with user identification information for identifying the user;
a step of determining whether to permit use of the first object based on the first acquired information of the user and the behavior information previously stored in the memory in association with the user identification information when the first acquired information of the user is acquired in the first authentication device;
Including,
A processing method in which the behavioral information includes information indicating whether the first object is currently being used based on detection by any authentication device, including the first authentication device and another authentication device that is communicatively connected and capable of authentication using an authentication method different from that of the first authentication device.