Patent Description:
Conventionally, authentication of users has been performed in various money handling systems. For example, a user of a money handling apparatus is requested to input user information such as a user ID and a password, the inputted user information is checked with user information registered in advance, and when the inputted user information matches the registered user information, the user is authenticated to be an authorized user. Authentication using biometric information or two-factor authentication may be performed in order to enhance security related to user authentication.

For example, <CIT> discloses a conventional system. The conventional system may perform two-factor authentication, i.e., password authentication and voiceprint authentication, when a user dispenses cash from an ATM (Automatic Teller Machine) by using a cash card. In a first authentication process, information obtained from the cash card is used as a user ID and the user inputs a password of the user ID. The user, who has been authenticated in the first authentication process, is subjected to a second authentication process that uses voice. A secret question for the second authentication, an answer to the question, and the voice of the user uttering the answer, are prepared in advance in an authentication server. In the second authentication process, the secret question is given to the user, the user utters the answer, and an obtained voice is compared with the voice in the authentication server, thereby identifying the user.

<CIT> discloses an authentication device. The devise may receive a request from a first user device to access a protected device. The device may verify a user identity of a user of the first device based on user credentials and determine that an authentication code is needed to authenticate the request to access the protected device. The device may dynamically generate multiple codes and transmit the multiple codes to a second user device associated with the user identity of the user of the first device. A first code, of the multiple codes, may correspond to a correct authentication code needed to authenticate the request to access the protected device. The device may transmit a message including an instruction for identifying the correct authentication code from among the multiple codes, receive a second code from the first device, compare the second code and the first code, and selectively authenticate the request to access the protected device.

<CIT> and <CIT> are further examples of prior art related with the application.

In the conventional art, however, after the user inputted the user ID and the password, and authenticated based on the inputted information, the user further needs to check the question and utter the answer, which is troublesome for the user. Additionally, since the user is not authenticated if the answer to the question is wrong, the user needs to memorize the question and the answer in addition to the password. Therefore, the conventional authentication method may not be a user-friendly method.

The present disclosure is made in view of the above problem of the conventional art. The present disclosure addresses the problem, as discussed herein, with a money handling system and a money handling method that can ensure security related to money handling by using a user-friendly authentication method.

Further embodiments are specified in the dependent claims.

In an exemplary implementation of the present disclosure, a money handling system comprises: a money handling apparatus to perform money handling; an input terminal configured to receive an input of authentication information for authenticating a user of the money handling apparatus, and transmit the authentication information to an authentication server which performs a first authentication process for the user based on the authentication information; and a control device including processing circuitry configured to receive user information of the user from the authentication server based on a result of the first authentication process, and perform a second authentication process for the user based on the user information.

The inventors of the present disclosure have recognized that with conventional devices, after a user has input a user ID and password, and the user has been authenticated based on the inputted information, the user further needs to check a question and input an answer, which is troublesome for the user. Additionally, since the user is not authenticated if the answer to the question is wrong, the user needs to memorize the question and the answer in addition to the password. Therefore, conventional authentication systems and methods are not user-friendly.

The inventors have developed the present disclosure to address issues with the conventional systems and methods. The present disclosure addresses problems, as discussed herein, with a money handling system and a money handling method that can ensure security related to money handling by using a user-friendly authentication method.

A money handling system according to one aspect of the present disclosure includes: a money handling apparatus configured to perform money handling; an input terminal configured to receive an input of authentication information for authenticating a user of the money handling apparatus; and a control device configured to receive user information of the user from an authentication server. The authentication server is a device that receives the authentication information of the user from the input terminal, and performs a first authentication process for the user, based on the authentication information. The control device performs a second authentication process for the user, based on the user information received from the authentication device.

Hereinafter, an embodiment of a money handling system and a money handling method according to the present disclosure will be described with reference to the accompanying drawings. <FIG> illustrates a money handling system according to the present embodiment. The money handling system includes an authentication server <NUM>, a money handling server <NUM>, and an operation terminal <NUM>. The authentication server <NUM> is communicably connected to the money handling server <NUM> and the operation terminal <NUM>. The money handling server <NUM> is communicably connected to the operation terminal <NUM>.

An installation location and a user of the money handling system are not particularly limited. The description will be continued for a case where the money handling system is used in a retail store that sells items to customers. Although the configuration shown in <FIG> is regarded as a money handling system in the description below, since a money handling system in each store may be constituted by using the money handling server <NUM>, the system of each store including the money handling server <NUM> may be regarded as a first money handling system, and the configuration shown in <FIG> may be regarded as a second money handling system including the first money handling system.

The authentication server <NUM> may be a cloud server. The authentication server <NUM> stores various kinds of information therein, receives operations through a network such as the Internet, and performs various kinds of processes corresponding to the operations. The money handling server <NUM> may be a computer device that provides functions related to money handling performed in the store. The authentication server <NUM> and the money handling server <NUM> may be implemented in any way as long as the servers can perform processes described below. For example, both the authentication server <NUM> and the money handling server <NUM> may be cloud servers, or may be computer devices.

The operation terminal <NUM> is used by a user <NUM> who uses the money handling server <NUM>. The operation terminal <NUM> serves as an input terminal to which the user <NUM> inputs various kinds of information. For example, a smartphone, a tablet computer, or the like wirelessly communicable with the money handling server <NUM> is used as the operation terminal <NUM>. The operation terminal <NUM> may be a computer device communicably connected to the money handling server <NUM> wirelessly or via wires. The money handling server <NUM> may include an operation unit and a display unit, and these units may be used as the operation terminal <NUM>. The operation terminal <NUM> may be a terminal that is used with or included in a money handling apparatus connected to the money handling server <NUM>, which will be described later.

Although <FIG> shows one money handling server <NUM> and one operation terminal <NUM>, the authentication server <NUM> may be shared by a plurality of money handling servers <NUM> and/or a plurality of operation terminals <NUM>. For example, each of a plurality of stores has a money handling server <NUM> installed therein, and staff members of the store, such as a store manager, a sub manager, and a cashier, are users <NUM> who use the operation terminal <NUM>.

When using the money handling server <NUM>, the user <NUM> operates the operation terminal <NUM> to request the money handling server <NUM> to perform a log-in process (step S1). The money handling server <NUM> requests the authentication server <NUM> to perform an authentication process for the user <NUM> who requested the log-in process (step S2).

The authentication server <NUM> performs the authentication process for the user <NUM> who wants to log into the money handling server <NUM>. In the authentication server <NUM>, profile data, in which information on a plurality of users <NUM> has been registered, is prepared in advance. <FIG> shows an example of the profile data. Information on a plurality of staff members belonging to each of a plurality of stores, is registered in the profile data.

The profile data includes user IDs and passwords to be used for log-in of the respective users <NUM>. The profile data further includes information on the respective users <NUM> provided from each store. For example, personnel information in each store is registered in the profile data. In the example shown in <FIG>, job position, authority, age, terminal ID (identification information such as IMEI of each terminal), etc., obtained from the personnel data have been registered in the profile data. In the profile data shown in <FIG>, the same kinds of information are registered for a store A and a store B, but different kinds of information may be registered for the store A and the store B. The profile data shown in <FIG> is an example. The profile data may include some or all of the information shown in <FIG>, e.g., age, and may or may not include information not shown in <FIG>, e.g., gender.

As shown in <FIG>, the authentication server <NUM> performs the authentication process for the user <NUM>, based on authentication information <NUM> (step S3). The authentication process is performed by using the user ID and the password of the user <NUM> registered in the profile data in advance.

Specifically, when the user <NUM> inputs the user ID and the password by operating the operation terminal <NUM> (step S4), the authentication information <NUM> including the user ID and the password is transmitted from the operation terminal <NUM> to the authentication server <NUM>. The authentication server <NUM> authenticates the user <NUM>, based on that the user ID and the password included in the authentication information <NUM> match the user ID and the password registered in the profile data in advance. If the combination of the user ID and the password inputted to the operation terminal <NUM> is not present in the profile data, the user <NUM> is not authenticated and therefore cannot use the money handling server <NUM>.

The authentication server <NUM> can specify the store to which the authenticated user <NUM> belongs, the job position of the user <NUM>, and the like by referring to the information registered in the profile data. The authentication server <NUM> generates user information <NUM> from one or more pieces of information registered in the profile data (step S5). The user information <NUM> is generated based on setting prepared in advance. The setting for generating the user information <NUM> may be different among stores.

For example, when the user <NUM> of the store A, for which setting is prepared to generate user information <NUM> by combining the store name and the job position, is authenticated and identified to be the user <NUM> having the user ID of "A0001" shown in <FIG>, user information <NUM> indicating "A, store manager" is generated by combining the store name "A" and the job position "store manager". If the store A is set to generate user information <NUM> by combining the store name, the job position, and the authority, user information <NUM> indicating "A, store manager, <NUM>" is generated. However, the form of "A, store manager" or the like is an example. The form of the user information <NUM> generated by the authentication server <NUM> is not particularly limited as long as the money handling server <NUM> can acquire the pieces of information included in the user information <NUM>.

The authentication server <NUM> transmits the user information <NUM> generated for the authenticated user <NUM>, to the money handling server <NUM> that has requested the authentication process of the user <NUM> (<FIG>, step S6). The money handling server <NUM> performs the authentication process for the user <NUM>, based on the user information <NUM> received from the authentication server <NUM> (step S7). That is, while the authentication server <NUM> performs a first authentication process of authenticating the user <NUM> based on the authentication information <NUM> inputted to the operation terminal <NUM> serving as an input terminal, the money handling server <NUM> serving as a control device in the store performs a second authentication process of authenticating the user <NUM> based on the user information <NUM> generated by the authentication server <NUM>. In the authentication process by the money handling server <NUM>, a determination process is performed to confirm that the pieces of information included in the user information <NUM> indicate a staff member having an authority to use the money handling server <NUM>. In the determination process, the money handling server <NUM> determines whether or not the pieces of information included in the user information <NUM> match the pieces of information managed by the money handling server <NUM>.

The money handling server <NUM> can determine whether or not the store name included in the user information <NUM> matches the store name of the store in which the money handling server <NUM> is installed. For example, when the money handling server <NUM> of the store A has received the user information <NUM> including the store name of the store B, the money handling server <NUM> determines that the user information <NUM> does not indicate a staff member who is permitted to use the money handling server <NUM>, and does not permit the user <NUM> to use the money handling server <NUM>. Even when the user <NUM> has been authenticated by the authentication server <NUM>, the user <NUM> cannot use the money handling server <NUM> unless the user <NUM> is authenticated by the money handling server <NUM>.

The money handling server <NUM> can determine whether or not the job position included in the user information <NUM> matches the job position in the store in which the money handling server <NUM> is installed. If the job position included in the user information <NUM> is different from a job position having an authority to use the money handling server <NUM>, the money handling server <NUM> determines that the user information <NUM> does not indicate a staff member who is permitted to use the money handling server <NUM>, and does not permit the user <NUM> to use the money handling server <NUM>. Similarly, in a case where the user information <NUM> includes information other than the store name and the job position, the money handling server <NUM> can perform a similar determination process with respect to each piece of the information.

As described above, in the money handling system, as for the user <NUM> who requests to use the money handling server <NUM>, after the first authentication process based on the user ID and the password of the user <NUM> has been performed by the authentication server <NUM>, the second authentication process based on the user information <NUM> is further performed by the money handling server <NUM>. The money handling server <NUM> does not receive the user ID and the password from the operation terminal <NUM>, but receives the user information <NUM> from the authentication server <NUM> to perform the authentication process. The user information <NUM> is generated from one or more pieces of other information that are already stored in the profile data in association with the user ID and the password. Since both the authentication process by the authentication server <NUM> based on the authentication information <NUM> and the authentication process by the money handling server <NUM> based on the user information <NUM> are performed, security related to use of the money handling server <NUM> can be enhanced.

In the money handling server <NUM>, mapping data indicating the correspondence between the pieces of information to be included in the user information <NUM>, and information on processes to be performed by the money handling server <NUM>, may be stored in advance. Using the mapping data, the money handling server <NUM> converts the pieces of information included in the user information <NUM> into information to be used by the money handling server <NUM>, and performs the processes based on the converted information.

<FIG> shows an example of the mapping data. In the mapping data, the pieces of information included in the user information <NUM> are associated with pieces of information used by the money handling server <NUM>. The mapping data shown in <FIG> indicates that the job positions, such as "store manager", "sub manager", etc., included in the user information <NUM> correspond to "R01", "R02", etc., indicating the job positions used by the money handling server <NUM>.

The mapping data may associate information included in the user information <NUM> with information of a kind different from the information in the user information <NUM>. For example, as shown in <FIG>, in addition to the correspondence between "job position" in the user information <NUM> and "job position" used by the money handling server <NUM>, the correspondence between "job position" in the user information <NUM> and other information, such as "authority", used by the money handling server <NUM>, may be registered in the mapping data.

If the authentication server <NUM> is set to generate user information <NUM> including authority information registered in the profile data in the authentication server <NUM>, the money handling server <NUM> can determine whether or not the authority information included in the user information <NUM> received from the authentication server <NUM> matches the authority, of the user <NUM>, managed in the money handling server <NUM>.

For example, in the authentication process for the user <NUM> who is a cashier, the authentication server <NUM> generates user information <NUM> indicating "cashier, <NUM>" that is a combination of the job position "cashier" and the cashier's authority "<NUM>" registered in the profile data. Upon receiving the user information <NUM>, the money handling server <NUM> determines whether or not the user information <NUM> matches the authority information registered in the mapping data.

If the money handling server <NUM> is subjected to a malicious attack and thereby the cashier's authority set as "<NUM>" in <FIG> is rewritten to "<NUM>" that is the store manager's authority, the information of the cashier in the money handling server <NUM> corresponding to the user information <NUM> consisting of the job position and the authority becomes "cashier, <NUM>". In this case, the money handling server <NUM> can determine that the user information <NUM> indicating "cashier, <NUM>" received from the authentication server <NUM> does not match the information indicating "cashier, <NUM>" in the money handling server <NUM>, and does not permit the user <NUM> to use the money handling server <NUM>. This prevents the user <NUM> authenticated as a cashier by the authentication server <NUM> from using the money handling server <NUM> with the same authority as the store manager.

The money handling server <NUM> can perform a notification process on the result of the authentication process performed based on the user information <NUM>. For example, if the store name included in the user information <NUM> does not match the name of the store in which the money handling server <NUM> is installed, the money handling server <NUM> displays predetermined information on the operation terminal <NUM> to notify the user <NUM> of the determination result.

Notification by the money handling server <NUM> may be performed by a predetermined terminal device such as another operation terminal <NUM> used by the store manager. For example, if the determination result indicates that the authority information of the user <NUM> included in the user information <NUM> does not match the authority of the user <NUM> managed in the money handling server <NUM>, this determination result is notified to the store manager through the predetermined operation terminal <NUM>, so that the store manager can investigate issues on an attack to the money handling server <NUM>, for example.

The money handling server <NUM>, which has authenticated the user <NUM> based on the user information <NUM>, can perform money handling corresponding to the authenticated user <NUM> (<FIG>, step S8). For example, the money handling server <NUM>, which has recognized that the user <NUM> is the store manager based on the user information <NUM>, displays a handling menu for the store manager on the operation terminal <NUM>, and performs a process related to money handling selected by the user <NUM> thorough the operation terminal <NUM>. Also, when the user <NUM> is a sub manager or a cashier, a handling menu according to the job position is presented to the user <NUM>, and a process based on the selection of the user <NUM> is performed. That is, the content of the process to be performed by the money handling server <NUM> can be limited based on the user information <NUM>. As for a handling menu changing method, only the kinds of money handling that the user <NUM> can perform may be displayed on the handling menu, or all the kinds of money handling may be displayed on the handling menu such that the user <NUM> cannot select some of them.

<FIG> each show an example of setting contents when the money handling server <NUM> performs money handling. For example, as shown in <FIG>, setting indicating the correspondence between the authority of the user <NUM> and the money handling menu is prepared in the money handling server <NUM> in advance. For example, the money handling server <NUM> specifies the authority of the authenticated user <NUM>, based on the user information <NUM> received from the authentication server <NUM> and on the mapping data shown in <FIG>. After specifying the authority of the user <NUM>, the money handling server <NUM> displays the handling menu corresponding to the authority of the user <NUM> on the operation terminal <NUM>, based on the setting shown in <FIG>.

For another example, as shown in <FIG>, setting indicating the correspondence between the authority of the user <NUM> and kinds of the money handling is prepared in the money handling server <NUM> in advance. The money handling server <NUM>, which has specified the authority of the user <NUM> based on the user information <NUM> and the mapping data, recognizes the money handling corresponding the specified authority in the store, based on the setting shown in <FIG>. The money handling server <NUM> performs various processes for the money handling that can be performed by the user <NUM>.

A specific example of processes that the money handling server <NUM> performs in the store will be described. <FIG> illustrate examples of processes performed in the store. As shown in <FIG>, the money handling server <NUM> is communicably connected to one or more money handling apparatuses <NUM> installed in the store. The money handling server <NUM> can manage each money handling apparatus <NUM>. For example, the money handling server <NUM> can manage the denomination, quantity, amount, etc., of money stored in each money handling apparatus <NUM>, and can limit the kind and content of money handling performed by each money handling apparatus <NUM>. For example, the money handling apparatuses <NUM> include an apparatus installed at a checkout counter of the store and used for performing checkout for transactions with customers, and an apparatus installed in a back office of the store and used for managing money of the store. Since the money handling server <NUM> and the one or more money handling apparatuses <NUM> shown in <FIG> constitute a money handling system for each store, the money handling server <NUM> shown in <FIG> can be regarded as an apparatus of a money handling system of each store.

As shown in <FIG>, the user <NUM>, who wants to use the money handling apparatus <NUM>, inputs authentication information <NUM> by operating the operation terminal <NUM>. The operation terminal <NUM> may be a communication terminal such as a smartphone independent from the money handling apparatus <NUM>, or a terminal connected to the money handling apparatus <NUM>. An operation unit and a display unit included in the money handling apparatus <NUM> may be used as the operation terminal <NUM>. In the case where the operation terminal <NUM> connected to the money handling apparatus <NUM> is used or where the operation unit and the display unit of the money handling apparatus <NUM> are used as the operation terminal <NUM>, address information of the authentication server <NUM> may be acquired in advance from the money handling server <NUM> into the money handling apparatus <NUM>, and the authentication information <NUM> and the user information <NUM> may be transmitted/received between the operation terminal <NUM> and the authentication server <NUM> by using the address information.

Based on the authentication information <NUM> inputted to the operation terminal <NUM> by the user <NUM>, the authentication server <NUM> performs the authentication process for the user <NUM> and generates the user information <NUM>, as described above. As shown in <FIG>, the money handling server <NUM> may receive the user information <NUM> from the authentication server <NUM> and control the money handling apparatus <NUM>. As shown in <FIG>, the money handling apparatus <NUM> may receive the user information <NUM> directly from the authentication server <NUM> and perform money handling based on the user information <NUM>. As shown in <FIG>, the operation terminal <NUM> communicably connected to the money handling apparatus <NUM> wirelessly or via wires may receive the user information <NUM> from the authentication server <NUM>, and the money handling apparatus <NUM> may perform money handling based on the user information <NUM> received in the operation terminal <NUM>. Hereinafter, the example shown in <FIG> will be firstly described, and thereafter the examples shown in <FIG> will be described in order.

In the example shown in <FIG>, the money handling server <NUM>, which has received the user information <NUM> from the authentication server <NUM>, performs the authentication process for the user <NUM> based on the user information <NUM> and specifies the authority of the user <NUM>, as described above.

In the money handling server <NUM>, as shown in <FIG>, it is possible to set: the authorities; the apparatus IDs of one or more money handling apparatuses <NUM> that the user <NUM> having each authority can use; the kinds of money handling that each money handling apparatus <NUM> can perform; and limitation regarding the content of each money handling. In the example shown in <FIG>, as the limitation regarding the contents of the money handling, an upper-limit amount of money is set in order to limit the amount of money that can be handled at the time of money handling.

For example, the money handling server <NUM> recognizes that the user <NUM> has the authority to use the money handling apparatus <NUM> whose apparatus ID is "M01", based on the setting shown in <FIG> and on the authority of the user <NUM> specified based on the user information <NUM> and the mapping data. Then, the money handling server <NUM> controls the money handling apparatus <NUM> to set the money handling apparatus <NUM> in the money handling executable state such that the money handling apparatus <NUM> can start money handling. If there are a plurality of money handling apparatuses <NUM> for which the user <NUM> have use authorities, the money handling server <NUM> allows the user <NUM> to select a money handling apparatus <NUM> through the operation terminal <NUM>. For example, a handling menu indicating the kinds of money handling that the user <NUM> can perform is displayed on the display unit of the money handling apparatus <NUM>, so that the user <NUM> can select and start money handling with the money handling apparatus <NUM>.

Based on the setting shown in <FIG>, the money handling server <NUM> can limit the kinds of money handling that the user <NUM> can perform by using the money handling apparatus <NUM>, and can limit the content of each money handling.

For example, the user <NUM> is a cashier, and the money handling apparatus <NUM> is a change machine connected to a cash register operated by the cashier. The cashier operates the cash register to dispense change from the money handling apparatus <NUM>. In this case, the money handling server <NUM> can limit the amount of money that the cashier can dispense per dispensing process or per day, based on the setting shown in <FIG>. For another example, if the user <NUM> is a staff member of a cash-in-transit (CIT) company that replenishes the money handling apparatus <NUM> with money, the money handling server <NUM> can limit the money handling apparatus <NUM> that can be replenished with money by the user <NUM> of the CIT. The money handling server <NUM> may limit the kinds of money handling to depositing process or replenishment process that can be performed in the money handling apparatus <NUM> by the CIT.

As shown in <FIG>, when the money handling apparatus <NUM> receives the user information <NUM> directly from the authentication server <NUM>, the money handling apparatus <NUM> acquires the mapping data shown in <FIG> and the setting data shown in <FIG> from the money handling server <NUM>, and operates similarly to the money handling server <NUM> as described above. That is, while the authentication server <NUM> performs the first authentication process based on the authentication information <NUM>, the money handling apparatus <NUM> serves as a control device for performing the second authentication process based on the user information <NUM>.

Specifically, the money handling apparatus <NUM>, which has received the user information <NUM> from the authentication server <NUM>, performs the authentication process for the user <NUM> and specifies the authority of the authenticated user <NUM>, based on the user information <NUM> and the mapping data. The money handling apparatus <NUM>, which has confirmed that the user <NUM> has the authority to use the money handling apparatus <NUM> based on the specified authority of the user <NUM> and the setting shown in <FIG>, becomes able to perform money handling. For example, on the display unit of the money handling apparatus <NUM>, a handling menu showing the kinds of money handling that the user <NUM> can perform is displayed, so that the user <NUM> can select and start money handling by using the money handling apparatus <NUM>.

In the example shown in <FIG>, as in the example shown in <FIG>, the money handling apparatus <NUM> can limit the kinds of money handling that the user <NUM> can perform, and can limit the content of each money handling, based on the setting shown in <FIG>. When the money handling apparatus <NUM> performs money handling based on the user information <NUM> without intervention of the money handling server <NUM> as shown in <FIG>, information on the handling performed by the money handling apparatus <NUM> is transmitted to the money handling server <NUM>, and the money handling server <NUM> manages handling history information.

As shown in <FIG>, when the operation terminal <NUM> communicably connected to the money handling apparatus <NUM> receives the user information <NUM> from the authentication server <NUM>, the operation terminal <NUM> acquires the mapping data shown in <FIG> and the setting data shown in <FIG> from the money handling server <NUM>, and operates similarly to the money handling server <NUM> as described above. That is, while the authentication server <NUM> performs the first authentication process based on the authentication information <NUM>, the operation terminal <NUM> serves as a control device for performing the second authentication process based on the user information <NUM>.

Specifically, the operation terminal <NUM>, which has received the user information <NUM> from the authentication server <NUM>, performs the authentication process for the user <NUM> and specifies the authority of the authenticated user <NUM>, based on the user information <NUM> and the mapping data. The operation terminal <NUM>, which has confirmed that the user <NUM> has the authority to use the money handling apparatus <NUM> based on the specified authority of the user <NUM> and the setting shown in <FIG>, controls the money handling apparatus <NUM> to set the money handling apparatus <NUM> in the money handling executable state. For example, on the display unit of the operation terminal <NUM>, a handling menu showing the kinds of money handling that the user <NUM> can perform is displayed, so that the user <NUM> can select and start money handling by using the money handling apparatus <NUM>.

In the example shown in <FIG>, as in the examples shown in <FIG>, the operation terminal <NUM> can limit the kinds of money handling that the user <NUM> can perform, and can limit the content of each money handling, based on the setting shown in <FIG>. When the operation terminal <NUM> performs handling based on the user information <NUM> without intervention of the money handling server <NUM> as shown in <FIG>, information on the handling performed by the money handling apparatus <NUM> is transmitted to the money handling server <NUM>, and the money handling server <NUM> manages handling history information.

As described above, in the authentication process by the authentication server <NUM>, the user <NUM> of the money handling system inputs the authentication information <NUM> such as the user ID, the password, etc., by operating the operation terminal <NUM>, whereby the user <NUM> can perform money handling by using the money handling apparatus <NUM>. The user ID and the password are not stored in the money handling server <NUM> and the money handling apparatus <NUM> installed in the store, but are stored and managed in the authentication server <NUM> being a cloud server. The user ID and the password of the user <NUM> are not included in the user information <NUM> transmitted/received between the authentication server <NUM>, the money handling server <NUM>, the operation terminal <NUM> and the money handling apparatus <NUM>. Thus, security related to the authentication process using the user ID and the password can be enhanced.

In addition to the above, other countermeasures for security enhancement are taken in the money handling system. For example, each user <NUM> cannot be subjected to authentication by the authentication server <NUM> unless the user <NUM> installs dedicated application software on his/her own operation terminal <NUM> such as a smartphone and registers a user ID and a password. The authentication server <NUM> acquires, from the operation terminal <NUM> on which the dedicated application software is installed, identification information such as IMEI for identifying the operation terminal <NUM>, and associates the identification information with the user ID as shown in <FIG> to manage them. In this case, the authentication server <NUM> does not perform authentication if the user ID is inputted to another operation terminal <NUM> whose IMEI is different from that of the operation terminal <NUM> associated with the inputted user ID.

The authentication information <NUM> transmitted/received between the authentication server <NUM> and the operation terminal <NUM>, and the user information <NUM> transmitted/received between the authentication server <NUM> and any of the money handling server <NUM>, the money handling apparatus <NUM>, and the operation terminal <NUM>, are encrypted. For example, in order to enhance security, the encryption method is changed according to the date when the information is transmitted/received.

The data shown in <FIG> and <FIG> prepared in the money handling server <NUM> are also encrypted so that the contents thereof cannot be understood. As described with reference to <FIG>, in the case where the money handling apparatus <NUM> acquires these data from the money handling server <NUM> to use them, the data acquired and used by the money handling apparatus <NUM> are deleted after the use. Likewise, as described with reference to <FIG>, in the case where the operation terminal <NUM> uses these data acquired from the money handling server <NUM> to use them, the data acquired and used by the operation terminal <NUM> are deleted after the use.

In the present embodiment, the user information <NUM> includes the store name, the job position, and the like. However, the user information <NUM> may include a user ID and a password different from those for the authentication information <NUM>. Specifically, a first user ID and a first password to be used for the authentication process in the authentication server <NUM> and a second user ID and a second password to be used for the authentication process in the money handling server <NUM> may be registered in the profile data, and the user information <NUM> may include the second user ID and the second password. In this case, as described above, the authentication server <NUM> can perform the authentication process based on the first user ID and the first password inputted to the operation terminal <NUM> by the user <NUM>, and the money handling server <NUM> can perform the authentication process based on the second user ID and the second password included in the user information <NUM> generated by the authentication server <NUM>.

In the present embodiment, the profile data is stored in the authentication server <NUM>, and the mapping data is stored in the money handling server <NUM>. However, the data storage places are not particularly limited as long as the money handling system can perform the above-described processes. For example, the profile data may be managed in a storage device or a server other than the authentication server <NUM>, and the mapping data may be managed in a storage device or a server other than the money handling server <NUM>.

In examples of the present embodiment, the kind of money handling that the money handling apparatus <NUM> can perform, and the upper-limit of the amount of money that can be handled in the money handling are changed based on the user information <NUM>, the mapping data, and the setting data, i.e., based on the authority of the user <NUM>. However, the targets to be changed based on the authority of the user <NUM> are not limited to those described above.

For example, handling of data regarding the money handling apparatus <NUM> may be limited according to the authority of the user <NUM>. Specifically, browsing of data, copying/transfer of data, and editing of data may be restricted based on the authority of the user <NUM>. Examples of data whose handling is limited may include: transaction data indicating the content of money handling performed by the money handling apparatus <NUM>; log data indicating the content of operation of the money handling apparatus <NUM>, such as an error generated in the money handling apparatus <NUM>; and inventory amount data indicating the kind and the quantity of money present inside the money handling apparatus <NUM>.

For another example, the operation and processing related to setting of the money handling apparatus <NUM> may be limited according to the authority of the user <NUM>. Examples of the setting to be limited may include: setting of denominations that the user <NUM> can handle in the money handling apparatus <NUM>; setting of storage units in the money handling apparatus <NUM> that the user <NUM> can use for the money handling, among a plurality of money storage units included in the money handling apparatus <NUM>; and setting related to locking/unlocking of a door from which one or more money storage units are exposed to the outside of the apparatus. The setting to be limited may be setting related to at least one of the user ID, password, job position, and authority of the user <NUM>.

In the present embodiment, the example of the money handling system used in a retail store has been described. However, the money handling system may be used in a branch of a financial institution. The money handling system in the present embodiment is configured to include the authentication server <NUM>, the money handling server <NUM>, and the operation terminal <NUM>, but this configuration is conceptually functional, and the money handling system is not physically limited to the configuration. For example, the authentication server <NUM> may implement a part of the function and operation of the money handling server <NUM>, or the money handling server <NUM> may implement a part of the function and operation of the authentication server <NUM>. The operation terminal <NUM> may implement a part of the function and operation of the authentication server <NUM>. The distributed or integrated forms of each device are not limited to the forms described above, and all or some of the forms may be distributed or integrated functionally or physically in any unit depending on various loads, use statuses, or the like.

As described above, the user of the money handling system is authenticated by inputting only the user ID and the password into the operation terminal, and is allowed to log into the money handling server, and perform money handling with the money handling apparatus connected to the money handling server. The user is authenticated a plurality of times by using the authentication server and the money handling server. When the user, who wants to perform money handling, inputs the user ID and the password only one time, the user is authenticated a plurality of times by the different devices. Thus, it is possible to ensure security related to money handling while realizing the user-friendly authentication method.

<FIG> is a block diagram of processing circuitry that performs computer-based operations in accordance with the present disclosure. <FIG> illustrates processing circuitry <NUM> of authentication server <NUM>, money handling server <NUM>, operation terminal <NUM> and/or money handling apparatus <NUM>.

Processing circuitry <NUM> is used to control any computer-based and cloud-based control processes, descriptions or blocks in flowcharts can be understood as representing modules, segments or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process, and alternate implementations are included within the scope of the exemplary embodiments of the present advancements in which functions can be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending upon the functionality involved, as would be understood by those skilled in the art. The functionality of the elements disclosed herein may be implemented using circuitry or processing circuitry which may include general purpose processors, special purpose processors, integrated circuits, ASICs ("Application Specific Integrated Circuits"), conventional circuitry and/or combinations thereof which are configured or programmed to perform the disclosed functionality. Processors are processing circuitry or circuitry as they include transistors and other circuitry therein. The processor may be a programmed processor which executes a program stored in a memory. In the disclosure, the processing circuitry, units, or means are hardware that carry out or are programmed to perform the recited functionality. The hardware may be any hardware disclosed herein or otherwise known which is programmed or configured to carry out the recited functionality.

In <FIG>, the processing circuitry <NUM> includes a CPU <NUM> which performs one or more of the control processes discussed in this disclosure. The process data and instructions may be stored in memory <NUM>. These processes and instructions may also be stored on a storage medium disk <NUM> such as a hard drive (HDD) or portable storage medium or may be stored remotely. Further, the claimed advancements are not limited by the form of the computer-readable media on which the instructions of the inventive process are stored. For example, the instructions may be stored on CDs, DVDs, in FLASH memory, RAM, ROM, PROM, EPROM, EEPROM, hard disk or any other non-transitory computer readable medium of an information processing device with which the processing circuitry <NUM> communicates, such as a server or computer. The processes may also be stored in network based storage, cloud-based storage or other mobile accessible storage and executable by processing circuitry <NUM>.

Further, the claimed advancements may be provided as a utility application, background daemon, or component of an operating system, or combination thereof, executing in conjunction with CPU <NUM> and an operating system such as Microsoft Windows, UNIX, Solaris, LINUX, Apple MAC-OS, Apple iOS and other systems known to those skilled in the art.

The hardware elements in order to achieve the processing circuitry <NUM> may be realized by various circuitry elements. Further, each of the functions of the above described embodiments may be implemented by circuitry, which includes one or more processing circuits. A processing circuit includes a particularly programmed processor, for example, processor (CPU) <NUM>, as shown in <FIG>. A processing circuit also includes devices such as an application specific integrated circuit (ASIC) and conventional circuit components arranged to perform the recited functions.

In <FIG>, the processing circuitry <NUM> may be a computer or a particular, special-purpose machine. Processing circuitry <NUM> is programmed to execute processing to control processing circuitry <NUM> of authentication server <NUM>, money handling server <NUM> which serves as a control device, operation terminal <NUM> which serves as a control device and/or money handling apparatus <NUM> which serves as a control device.

Alternatively, or additionally, the CPU <NUM> may be implemented on an FPGA, ASIC, PLD or using discrete logic circuits, as one of ordinary skill in the art would recognize. Further, CPU <NUM> may be implemented as multiple processors cooperatively working in parallel to perform the instructions of the inventive processes described above.

The processing circuitry <NUM> in <FIG> also includes a network controller <NUM>, such as an Ethernet PRO network interface card, for interfacing with network <NUM>. As can be appreciated, the network <NUM> can be a public network, such as the Internet, or a private network such as a local area network (LAN) or wide area network (WAN), or any combination thereof and can also include Public Switched Telephone Network (PSTN) or Integrated Services Digital Network (ISDN) sub-networks. The network <NUM> can also be wired, such as an Ethernet network, universal serial bus (USB) cable, or can be wireless such as a cellular network including EDGE, <NUM> and <NUM> wireless cellular systems. The wireless network can also be Wi-Fi, wireless LAN, Bluetooth, or any other wireless form of communication that is known. Additionally, network controller <NUM> may be compliant with other direct communication standards, such as Bluetooth, a near field communication (NFC), infrared ray or other.

The processing circuitry <NUM> further includes a display controller <NUM>, such as a graphics card or graphics adaptor for interfacing with display <NUM>, such as a monitor. An I/O interface <NUM> interfaces with a keyboard and/or mouse <NUM> as well as a touch screen panel <NUM> on or separate from display <NUM>. I/O interface <NUM> also connects to a variety of peripherals <NUM>.

The storage controller <NUM> connects the storage medium disk <NUM> with communication bus <NUM>, which may be an ISA, EISA, VESA, PCI, or similar, for interconnecting all of the components of the processing circuitry <NUM>. A description of the general features and functionality of the display <NUM>, keyboard and/or mouse <NUM>, as well as the display controller <NUM>, storage controller <NUM>, network controller <NUM>, and I/O interface <NUM> is omitted herein for brevity as these features are known.

The exemplary circuit elements described in the context of the present disclosure may be replaced with other elements and structured differently than the examples provided herein. Moreover, circuitry configured to perform features described herein may be implemented in multiple circuit units (e.g., chips), or the features may be combined in circuitry on a single chipset.

The functions and features described herein may also be executed by various distributed components of a system. For example, one or more processors may execute these system functions, wherein the processors are distributed across multiple components communicating in a network. The distributed components may include one or more client and server machines, which may share processing, in addition to various human interface and communication devices (e.g., display monitors, smart phones, tablets, personal digital assistants (PDAs)). The network may be a private network, such as a LAN or WAN, or may be a public network, such as the Internet. Input to the system may be received via direct user input and received remotely either in real-time or as a batch process. Additionally, some implementations may be performed on modules or hardware not identical to those described. Accordingly, other implementations are within the scope that may be claimed.

A money handling system according to the present disclosure includes: an input terminal configured to receive an input of authentication information for authenticating a user of the money handling apparatus; and a control device configured to receive user information of the user from an authentication server that receives the authentication information of the user from the input terminal and performs a first authentication process for the user based on the authentication information. The control device performs a second authentication process for the user, based on the user information generated by the authentication server.

In the above configuration, a money handling server used in a store where the money handling apparatus is installed, may serve as the control device. The money handling apparatus may serve as the control device, or the input terminal may serve as the control device.

In the above configuration, the authentication server may generate the user information from information on the user, which has been registered in profile data in advance.

In the above configuration, the profile data may include a user ID and a password.

In the above configuration, the profile data may include job position information of the user.

In the above configuration, the profile data may include information indicating a store to which the user belongs.

In the above configuration, the control device may have, stored therein, mapping data indicating the correspondence between information included in the user information, and information on handling that the money handling apparatus performs.

In the above configuration, the control device may perform the second authentication process, based on the user information, and information that has been mapped to the user information.

In the above configuration, the control device may limit handling that the user can perform with the control device, based on the user information, and information that has been mapped to the user information.

In the above configuration, owing to the limitation on the handling that the user can perform by using the control device, the display content of a handling menu indicating the kinds of handling that the user can perform with the money handling apparatus may be changed. A process related to at least one of: transaction data of the money handling apparatus; log data of the money handling apparatus; inventory amount data of the money handling apparatus; setting of the money handling apparatus; setting of a user ID; setting of a password; setting of a job position; and setting of an authority corresponding to a job position, may be changed in the handling menu.

In the above configuration, the control device may limit handling that the user can perform by using the money handling apparatus, based on the user information, and information that has been mapped to the user information.

In the above configuration, the information mapped to the user information may be stored in the control device in advance.

In the above configuration, the authentication information may include a user ID and a password.

In the above configuration, the information registered in the profile data may further include authority information indicating contents of money handling that the user can perform by using the money handling apparatus. The control device may receive the user information including the authority information from the authentication server, and may perform the second authentication process of confirming that the authority information included in the user information matches an authority that is given to the user and managed in the control device and.

In the above configuration, the user information may include the job position of the user, and/or information indicating the store to which the user belongs.

In the above configuration, the information registered in the profile data may further include job position information indicating contents of money handling that the user can perform by using the money handling apparatus. The control device may receive the user information including the job position information from the authentication server, and may perform the second authentication process of confirming that the job position information included in the user information matches job position information that is managed in the control device and is given to the user.

In the above configuration, the money handling server may perform a notification process for notifying a result of the determination through a predetermined terminal.

A money handling method according to the present disclosure includes: receiving, by a control device, user information of a user who wants to use a money handling apparatus, from an authentication server that receives authentication information of the user from an input terminal, and performs a first authentication process for the user based on the authentication information; and performing, by the control device, a second authentication process for the user based on the user information.

Claim 1:
A money handling system comprising:
a money handling apparatus (<NUM>) to perform money handling;
an input terminal (<NUM>) configured to
receive an input of authentication information for authenticating a user of the money handling apparatus (<NUM>), and
transmit the authentication information to an authentication server (<NUM>) which performs a first authentication process for the user based on the authentication information; and
a control device (<NUM>) configured to
receive user information of the user from the authentication server (<NUM>) which has generated the user information different from the authentication information, based on a result of the first authentication process,
perform a second authentication process for the user by determining whether or not information included in the user information generated by the authentication server (<NUM>) matches information which has been managed by the control device (<NUM>), and
control the money handling apparatus (<NUM>) to allow the user to use the money handling apparatus (<NUM>), based on a result of the second authentication process.