ACTION CONTROL SYSTEM, ACTION CONTROL SERVER, AND ACTION CONTROL METHOD

Abstract

To prevent an action from being executed fraudulently by a person not present at a placement site of a tag.SOLUTION: A tag 20 placed at a site where a user should be present when an action subjected to control is executed transmits, in accordance with an access from a portable terminal 30 by short-range wireless communication, an encrypted code obtained by performing encryption processing on a verification code having a value changing access by access. The portable terminal 30 transmits the encrypted code obtained from the tag 20 to a verification server 40. The verification server 40 and a device control server 50 that operates in conjunction therewith perform decryption processing on the encrypted code received from the portable terminal 30. Consequently, when the decryption processing is successful, and when the verification code obtained by the present decryption processing differs from the verification code obtained by the past decryption processing so far, a command to execute an action corresponding to the tag 20 is given.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an action control system for controlling the execution of an action. [Background technology]

[0002] Tags that transmit unique identifiers in response to access from external devices through short-range wireless communication (e.g., NFC tags) have been used in various systems. In addition, the number of mobile terminals (e.g., smartphones) equipped with tag reading functions has been increasing, making the use of tags more familiar.

[0003] In recent years, systems that execute a predetermined action when a tag is accessed have been considered. For example, Patent Document 1 discloses a system in which a tag is attached to a door surface or a predetermined portion around the door, and when an identifier (tag ID) is read from the tag with a mobile terminal, the system unlocks or locks the electric lock of the door that is associated with the identifier on a one-to-one basis. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2014-139385 A Summary of the Invention [Problem to be solved by the invention]

[0005] In the above system, it is possible for an identifier read from an installed tag to be written to another tag (tag duplication) or for that identifier to be stored in a mobile terminal, which may result in unauthorized actions being performed by a person who is not present at the tag installation location.

[0006] The present invention has been made in consideration of the conventional circumstances described above, and aims to propose technology that can prevent unauthorized actions from being performed by people who are not at the location where the tag is installed. [Means for solving the problem]

[0007] In order to achieve the above object, an action control system, an action control server, and an action control method according to the present invention are configured as follows. (1) An action control system for controlling the execution of an action includes a tag installed at a location where a user is to be when the action to be controlled is executed, a mobile terminal carried by the user and capable of accessing the tag via short-range wireless communication, and a server accessed by the mobile terminal via a network, wherein the tag sends out an encrypted code obtained by encrypting a verification code whose value changes with each access in response to access from the mobile terminal, the mobile terminal transmits the encrypted code obtained from the tag to the server, and the server performs a decryption process on the encrypted code received from the mobile terminal, and as a result, if the decryption process is successful and the verification code obtained in this decryption process is different from the verification codes obtained in the previous decryption processes, instructs the execution of the action corresponding to the tag.

[0008] (2) In the action control system described in (1) above, the verification code is a code whose value increases each time the tag is accessed, and the server instructs the execution of an action corresponding to the tag if the decryption process is successful and the verification code obtained in the current decryption process is larger than the verification code obtained in the previous decryption process.

[0009] (3) In the action control system described in (1) or (2) above, the server requests the mobile terminal to perform user authentication before instructing the mobile terminal to execute the action corresponding to the tag, and when a response is obtained from the mobile terminal indicating that the user authentication was successful, instructs the mobile terminal to execute the action corresponding to the tag.

[0010] (4) In the action control system described in any one of (1) to (3) above, the server, before instructing the execution of the action corresponding to the tag, displays a screen on the mobile terminal that accepts an instruction operation to execute the action corresponding to the tag from the user, and when the execution operation is performed, instructs the execution of the action corresponding to the tag.

[0011] (5) An action control server that controls the execution of actions includes a memory unit that stores data indicating a correspondence between an action to be controlled and a tag installed at a location where a user is to be when the action is executed, a communication unit that receives, via a mobile terminal carried by the user, an encrypted code obtained by encrypting a verification code whose value changes with each access to the tag, the verification code being sent from the tag in response to access to the tag by short-range wireless communication from the mobile terminal carried by the user, a verification unit that performs a decryption process on the encrypted code received from the mobile terminal by the communication unit, and determines whether or not the decryption process is successful and the verification code obtained in this decryption process is different from the verification codes obtained in previous decryption processes, and an execution instruction unit that instructs the execution of an action corresponding to the tag in accordance with the data stored in the memory unit when the verification unit determines that the condition is satisfied.

[0012] (6) An action control method for controlling the execution of an action, wherein a mobile terminal carried by a user accesses via short-range wireless communication a tag installed at a location where the user is to be when the action to be controlled is to be executed, and the tag sends an encrypted code obtained by encrypting a verification code whose value changes with each access in response to the access from the mobile terminal, the mobile terminal transmits the encrypted code obtained from the tag to the server, and the server decrypts the encrypted code received from the mobile terminal, and if the decryption is successful and the verification code obtained in this decryption process is different from the verification codes obtained in the previous decryption processes, the server instructs the execution of the action corresponding to the tag. Effect of the Invention

[0013] According to the present invention, it is possible to prevent unauthorized execution of actions by persons who are not present at the location where the tag is installed. [Brief description of the drawings]

[0014] [Figure 1] 1 is a diagram illustrating a schematic configuration example of an action control system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram illustrating an example of a processing sequence of the action control system according to the first embodiment. [Diagram 3] FIG. 11 is a diagram illustrating an example of a processing sequence of an action control system according to a second embodiment. [Figure 4] FIG. 11 is a diagram illustrating an example of a processing sequence of an action control system according to a third embodiment. [Diagram 5] FIG. 13 is a diagram illustrating an example of a processing sequence of an action control system according to a fourth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] An embodiment of the present invention will be described with reference to the drawings. 1 shows a schematic configuration example of an action control system according to an embodiment of the present invention. The action control system of this example includes a device 10, a tag 20, a mobile terminal 30, a verification server 40, and a device control server 50.

[0016] The device 10 executes an action to be controlled according to instructions from the device control server 50. An example of the device 10 is an electronic lock installed on a door, locker, desk, safe, etc. of an accommodation facility. Other examples include vending machines, exit payment machines at paid parking lots, lighting fixtures, air conditioners, and other home electrical appliances. These devices are merely examples, and various types of devices can be used.

[0017] The tag 20 is placed at a location where the user should be when the action is performed by the device 10. In this example, it is assumed that the tag 20 is placed near the device 10, but the tag 20 may be placed at a location away from the device 10 as long as the correspondence between the device 10 and the tag 20 can be visually recognized.

[0018] Various types of tags capable of short-range wireless communication with external devices, such as an NFC tag, can be used as the tag 20. The tag 20 transmits tag data in response to access from the mobile terminal 30.

[0019] The tag data includes address information indicating the location of the verification server 40 on the network, a tag ID which is an identifier unique to the tag, and an encrypted code obtained by encrypting a verification code which changes with each access. The address information may be described in, for example, a Uniform Resource Identifier (URI) format, and the tag ID and the encrypted code may be set as parameters.

[0020] The encrypted code included in the tag data is generated by the IC chip built into the tag 20 in response to access from an external device. That is, when the IC chip is accessed by an external device, it obtains a verification code that is different from any verification code that has been used up until now, and performs encryption processing on this code using a specific encryption key to generate an encrypted code.

[0021] The verification code may be different for each access from an external device, and may be of various formats, such as a randomly changing code, a sequentially increasing code, or a code indicating the elapsed time from a reference time.

[0022] The encryption key used in the encryption process may be a common key in a common key cryptosystem or a server public key in a public key cryptosystem, and the format does not matter. Although the same encryption key may be used for multiple tags, it is preferable to use a different encryption key for each tag, as this is more secure.

[0023] The mobile terminal 30 is held by a user who has authority to cause the device 10 to execute an action. The mobile terminal 30 has a communication unit 31, a tag reading unit 32, and a user authentication unit 33. The communication unit 31 communicates with other devices (the verification server 40 and the device control server 50) via a network. The tag reading unit 32 accesses the tag 20 by short-range wireless communication to acquire tag data. The user authentication unit 33 accepts input such as a password from the user and performs user authentication.

[0024] When the mobile terminal 30 accesses the tag 20 by short-range wireless communication and receives the tag data, it accesses the validation server 40 via the network according to the address information contained therein. As a result, the tag data read from the tag 20 is transmitted from the mobile terminal 30 to the validation server 40. The mobile terminal 30 may be any mobile communication terminal equipped with the above-mentioned functional units 31 to 33, and various terminals such as a mobile phone, a smartphone, an iPhone (registered trademark), a tablet PC, etc. may be used. In order to further improve the security of the present system, it is preferable that the user authentication unit 33 has a biometric authentication function.

[0025] The verification server 40 is a server that verifies tag access and verifies users. The verification server 40 has a communication unit 41, a data storage unit 42, a tag verification unit 43, and a user verification unit 44. The communication unit 41 communicates with other devices (the mobile terminal 30 and the device control server 50) via a network. The data storage unit 42 stores data used for processing by the tag verification unit 43 and the user verification unit 44. The data storage unit 42 stores at least data indicating the correspondence between the action to be controlled and the tag 20 installed at the location where the user should be when the action is executed. The tag verification unit 43 verifies the tag access based on the tag ID and the encryption code included in the tag data received from the mobile terminal 30. The user verification unit 44 verifies the user who performed the tag access.

[0026] The operation of the tag verification unit 43 will now be described in detail. First, the tag verification unit 43 performs a decryption process on the encrypted code using an encryption key (a common key or a server private key) corresponding to the tag ID. If the decryption process of the encrypted code fails, it determines that the tag access is unauthorized. On the other hand, if the decryption process of the encrypted code is successful, it verifies the verification code obtained by this decryption process.

[0027] If the verification code obtained in the current decryption process is the same as the verification code obtained in the previous decryption process, it is determined that the tag access is unauthorized. On the other hand, if the verification code obtained in the current decryption process is different from the verification codes obtained in the previous decryption processes, it is determined that the tag access is genuine.

[0028] Here, the method of verifying the verification code differs depending on the format of the verification code. When using a randomly changing code as the verification code, each time the verification code is decoded it is stored as a history in data storage unit 42, and it is then checked whether the verification code obtained in the current decryption process is different from all the verification codes obtained in the previous decryption processes. When using a sequentially increasing code or a code indicating the elapsed time from a reference time as the verification code, the previously decoded verification code can be stored in data storage unit 42, and it can be checked whether the verification code obtained in the current decryption process is larger than the immediately previous verification code. In addition, when a code indicating the elapsed time from a reference time is used as the verification code, the difference with the execution time of the decryption process may be taken, and an additional determination may be made as to whether the time difference is less than or equal to a predetermined threshold value (a threshold value that takes communication delays into account).

[0029] The operation of the user verification unit 44 will now be described in detail. The tag verification unit 43 judges whether the user of the mobile terminal 30 who has performed the tag access has the authority to execute the action. The relationship between the user and the authority to execute the action is assumed to be stored in advance in the data storage unit 42. In addition, the tag verification unit 43 requests the mobile terminal 30 to authenticate the user.

[0030] If, as a result of these processes, the user of the mobile terminal 30 that has made the tag access does not have the authority to execute the action, or if user authentication by the mobile terminal 30 has failed, the user is determined to be an unauthorized user. On the other hand, if the user of the mobile terminal 30 that has made the tag access has the authority to execute the action and user authentication by the mobile terminal 30 has been successful, the user is determined to be a legitimate user. Note that, in the case of access from a pre-registered mobile terminal 30, these processes may be omitted and the user may be determined to be a legitimate user.

[0031] If the verification server 40 determines that the tag access is unauthorized or that the user is unauthorized, it decides not to permit the device 10 to execute the action. On the other hand, if the verification server 40 determines that the tag access is genuine and that the user is valid, it decides to permit the device 10 to execute the action, and transmits permission for the device 10 to execute the action to the device control server 50.

[0032] The device control server 50 is a server that instructs the device 10 to execute an action via a network. The device control server 50 has a communication unit 51 and an execution instruction unit 52. The communication unit 51 communicates with other devices (the device 10 and the validation server 40) via the network. When the execution instruction unit 52 receives permission for the device 10 to execute an action from the validation server 40, it transmits a command to execute the action to the device 10.

[0033] The specific operation of the action control system of this embodiment will be described below based on an embodiment.

[0034] (First embodiment) FIG. 2 shows an example of a processing sequence of the action control system according to the first embodiment. A user who wishes to cause the device 10 to execute a predetermined action brings the mobile terminal 30 close to the tag 20 corresponding to the device 10. This causes the mobile terminal 30 to access the tag 20 via short-range wireless communication (step S11). In response to the access from the mobile terminal 30, the tag 20 transmits tag data including an encrypted code obtained by encrypting a verification code that changes with each access (step S12).

[0035] The mobile terminal 30 accesses the verification server 40 based on the tag data received from the tag 20 (step S13). In response to this, the tag ID and the encryption code are transmitted from the mobile terminal 30 to the verification server 40.

[0036] When the verification server 40 receives the tag ID and the encrypted code from the mobile terminal 30, the verification server 40 performs a decryption process on the encrypted code using the encryption key corresponding to the tag ID. If the decryption process is successful, the verification server 40 verifies whether the verification code obtained in this decryption process is different from the verification codes obtained in the previous decryption processes (step S14).

[0037] If the decryption process fails or if the verification of the verification code fails, the verification server 40 determines that the tag access is unauthorized and instructs the mobile terminal 30 to output an error (step S15). As a result, an error screen is displayed on the mobile terminal 30 and no action is executed by the device 10. On the other hand, if the decryption process is successful and the verification of the verification code is successful, the verification server 40 determines that the tag access is genuine and permits the device control server 50 to execute the action by the device 10 (step S16). (In this embodiment, user verification is omitted.)

[0038] If the execution of the action by the device 10 is permitted, the device control server 50 transmits an action execution command to the device 10 (step S17). The device 10 executes the action according to the execution command received from the device control server 50 (step S18).

[0039] Through the above-described processing, an action is executed by the device 10 only when a user who has authority to execute an action by the device 10 reads the tag 20 with the mobile terminal 30 in a location where the user should be when the action is executed. This makes it possible to prevent an action from being executed illegally by a person who is not at the location where the tag 20 is installed.

[0040] (Second Example) Fig. 3 shows an example of a processing sequence of an action control system according to the second embodiment. The second embodiment is an extension of the first embodiment, and is configured to perform user verification after tag access verification. The process up to tag access verification is the same as the first embodiment, and the process thereafter will be described.

[0041] When the validation server 40 determines that the tag access is genuine, it verifies that the user of the mobile terminal 30 has the authority to execute the action, and then requests the mobile terminal 30 to perform biometric authentication of the user (step S21). The mobile terminal 30 performs biometric authentication of the user in accordance with the request from the validation server 40 (step S22). That is, the mobile terminal 30 performs identity verification using physical characteristics unique to each individual, such as a fingerprint, iris, or face. Note that the physical characteristic data used for identity verification is registered in advance in the mobile terminal 30. The mobile terminal 30 transmits the result of the user's biometric authentication to the validation server 40 (step S23).

[0042] If the result of the biometric authentication of the user by the mobile terminal 30 is authentication failure, the validation server 40 instructs the mobile terminal 30 to output an error (step S24). As a result, an error screen is displayed on the mobile terminal 30, and the action by the device 10 is not executed. On the other hand, if the result of the biometric authentication of the user by the mobile terminal 30 is authentication success, the validation server 40 permits the device control server 50 to execute the action by the device 10 (step S16). As a result, the device control server 50 transmits an action execution command to the device 10 (step S17), and the action is executed by the device 10 (step S18).

[0043] The above-described processing ensures that the user who reads the tag 20 with the mobile terminal 30 is the actual user with authority to execute the action, making it possible to prevent the execution of actions by unauthorized users.

[0044] In the first and second embodiments, a predetermined amount (cost of executing the action) may be charged to the user, and when the payment (settlement) is confirmed, the device control server 50 may transmit a command to execute the action to the device 10. This is effective for devices that require payment when executing an action, such as vending machines and exit payment machines at paid parking lots. In this case, when electronic payment by the mobile terminal 30 that has accessed the tag is completed, the user of the mobile terminal 30 may be considered to have authority to execute the action. It is preferable to perform electronic payment using the mobile terminal 30 after user authentication (e.g., biometric authentication) on the mobile terminal 30, but electronic payment may be performed before user authentication. In addition, in the case of small-amount payments, user authentication may be omitted.

[0045] (Third Example) 4 shows an example of a processing sequence of the action control system according to the third embodiment. The third embodiment is an extension of the first embodiment, and is configured so that an action of the device 10 is started by operating the mobile terminal 30. The process up to the verification of tag access is the same as the first embodiment, and the process thereafter will be described.

[0046] When the validation server 40 determines that the tag access is genuine, the validation server 40 causes the mobile terminal 30 to display an operation screen for accepting a selection operation of an action to be executed by the device 10 (step S31). One or more actions that can be executed by the device 10 are displayed on the operation screen.

[0047] When the mobile terminal 30 accepts the selection of an action from the user via the operation screen, it transmits the selection result to the verification server 40 (step S32). The verification server 40 transmits an instruction to execute the selected action to the device control server 50 in accordance with the selection result received from the mobile terminal 30 (step S33). As a result, an execution command for the selected action is transmitted from the device control server 50 to the device 10 (step S17), and the selected action is executed by the device 10 (step S18).

[0048] By the above-described process, when there is a device 10 capable of executing a plurality of actions, it becomes possible to selectively control the execution of the actions using one tag 20. Therefore, it is not necessary to prepare a tag 20 individually for each action that the device 10 can execute.

[0049] In the above description, the mobile terminal 30 transmits the selection result to the validation server 40, and the validation server 40 transmits an instruction to execute the action to the device control server 50. However, as shown in step S34 of FIG. 4, the mobile terminal 30 may be configured to directly transmit the instruction to execute the action to the device control server 50. Also, by combining the second embodiment, a configuration may be configured to further perform biometric authentication of the user. The biometric authentication of the user may be performed before the operation screen is displayed on the mobile terminal 30, or after the action selection operation is performed via the operation screen (immediately before the action is executed).

[0050] (Fourth Example) FIG. 5 shows an example of a processing sequence of the action control system according to the fourth embodiment. The fourth embodiment assumes that the action control system is used for payment processing in a store. In this case, the cash register terminal that settles the price in the store corresponds to the device 10. Also, a payment control server 50' is provided instead of the device control server 50.

[0051] The cash register terminal 10 transmits the payment amount to be paid by the user to the payment control server 50' (step S41). After that, the process up to biometric authentication of the user is the same as in the second embodiment, and the process thereafter will be described.

[0052] When the result of the biometric authentication of the user by the mobile terminal 30 is a success, the verification server 40 The payment control server 50' is permitted to perform payment processing (an example of an action) (step S42). If the payment processing is permitted, the payment control server 50' causes the mobile terminal 30 to display a payment screen for accepting payment operations (step S43). The payment screen displays the payment amount, the store name, a payment button, and the like.

[0053] When the mobile terminal 30 accepts a payment operation from the user through the payment screen, it sends a payment instruction to the payment control server 50' (step S44). The payment control server 50' executes the payment according to the payment instruction received from the mobile terminal 30, and instructs the cash register terminal 10 and the mobile terminal 30 to output the payment result (steps S45, S46). This allows the store clerk operating the cash register terminal 10 and the user of the mobile terminal 30 to recognize that the payment has been completed.

[0054] The above-described processing can prevent unauthorized actions from being performed by persons who are not present at the location where the tag 20 is installed, not only when controlling the mechanical or electrical operation of the device 10, but also when controlling the execution of services associated with the device 10.

[0055] In the above explanation, payment is executed in response to receiving a payment operation from the user on the mobile terminal 30, but it may also be configured to execute payment when it is determined that the tag access is genuine, or when it is determined that the user is a legitimate person. In the above description, the user's biometric authentication is performed before the payment screen is displayed on the mobile terminal 30, but the user's biometric authentication may be performed after the payment operation is performed through the payment screen (immediately before the payment is executed). In the above description, the payment amount is transmitted from the cash register terminal 10 to the payment control server 50', but this is not limited to this. For example, the user may input the payment amount on the payment screen displayed on the mobile terminal 30, or the payment amount may be set by other methods.

[0056] In the fourth embodiment, the execution of a payment service has been described as an example, but it goes without saying that the action control system according to the present invention can also be applied to the execution of other services. For example, the action control system according to the present invention can be applied to various actions that execute a record of being in a specific location, such as a patrol record, a time card, or a stamp rally. It is also conceivable that the action control system according to the present invention can be applied to other actions in situations such as applying for insurance or online shopping.

[0057] As described above, in the action control system of this example, the tag 20, which is installed at a location where the user is supposed to be when the action to be controlled is executed, sends out an encrypted code obtained by encrypting a verification code, the value of which changes with each access, in response to access from the mobile terminal 30 via short-range wireless communication. The mobile terminal 30 transmits the encrypted code obtained from the tag 20 to the verification server 40 via the network. The verification server 40 and the device control server 50 (or the payment control server 50') operating in conjunction with the verification server 40 decrypt the encrypted code received from the mobile terminal 30, and as a result, it is determined whether the decryption process is successful and whether the verification code obtained in this decryption process is different from the verification codes obtained in previous decryption processes is satisfied. If it is determined that this condition is satisfied, the action corresponding to the tag 20 is instructed to be executed.

[0058] According to such a configuration, an action is executed only when the tag 20 is accessed by the mobile terminal 30 in a location where the user should be when the action is executed (where the tag is installed). This makes it possible to prevent an action from being executed illegally by a person who is not in the location where the tag is installed.

[0059] Here, the verification code may be a code whose value increases with each access to the tag 20, such as a code that increases sequentially or a code that indicates the elapsed time from a reference time. In this case, the verification server 40 or the like may determine whether or not the conditions that the decryption process is successful and the verification code obtained in the current decryption process is larger than the verification codes obtained in the previous decryption processes are satisfied, and if it is determined that this condition is satisfied, may instruct the execution of an action corresponding to the tag 20. This eliminates the need to compare the verification code with all the verification codes obtained in the previous decryption processes when verifying the verification code, thereby reducing the processing burden of tag verification.

[0060] Alternatively, the verification server 40 or the like may request the mobile terminal 30 to perform user authentication before instructing the execution of an action corresponding to the tag 20, and instruct the execution of the action corresponding to the tag 20 when a response indicating that the user authentication was successful is received from the mobile terminal 30. This ensures that the user who reads the tag 20 with the mobile terminal 30 is the actual user with the authority to execute the action, making it possible to prevent the execution of the action by an unauthorized user. In particular, by performing biometric authentication on the mobile terminal 30 to verify the identity of the user using physical characteristics unique to each individual, not only can user spoofing be effectively prevented, but also data on physical characteristics can be prevented from circulating on the network.

[0061] Furthermore, before the verification server 40 or the like instructs the execution of an action corresponding to the tag 20, a screen for receiving an instruction operation for executing the action corresponding to the tag 20 from the user may be displayed on the mobile terminal 30, and when the execution operation is performed, the execution of the action corresponding to the tag 20 may be instructed. This allows for more detailed control over the execution of the action, improving user convenience.

[0062] Here, the verification server 40 and the device control server 50 (or the payment control server 50') in the above-mentioned action control system are composed of a computer equipped with hardware resources such as a CPU (Central Processing Unit) that performs various arithmetic processing, a main memory such as a RAM (Random Access Memory) that serves as the working area of ​​the CPU and a ROM (Read Only Memory) that records basic control programs, an auxiliary memory that stores various programs and data, a display device that displays and outputs various information, and an input / output interface unit that connects input devices such as operation buttons and touch panels, and a communication interface unit that communicates with other devices via wire or wirelessly. Then, by executing a predetermined program on the computer, each functional unit related to the action control server of the present invention is realized on the computer.

[0063] In this example, the validation server 40 and the device control server 50 (or the payment control server 50') are configured as separate devices that operate in cooperation with each other, but they may also be configured as an integrated device. The validation server 40 may be configured from multiple devices, and the same goes for the device control server 50 (or the payment control server 50'). These servers are not limited to the above-mentioned software configuration that realizes each functional unit, and each functional unit may be realized by a dedicated hardware module.

[0064] Although the present invention has been described in detail above, it goes without saying that the present invention is not limited to the above-mentioned configuration, and may be realized with configurations other than those described above. The present invention can also be provided as a method for executing the above-described processing, a program for realizing such a method by a computer having hardware resources such as a processor and memory, a readable storage medium for storing the program in a readable manner, etc. [Industrial Applicability]

[0065] The present invention can be used in a system that executes a predetermined action in response to a tag access. [Explanation of symbols]

[0066] 10: device, 20: tag, 30: mobile terminal, 40: verification server, 50: device control server, 50': payment control server, 31: communication unit, 32: tag reading unit, 33: user authentication unit, 41: communication unit, 42: data storage unit, 43: tag verification unit, 44: user verification unit, 51: communication unit, 52: execution instruction unit

Claims

1. In an action control system for controlling execution of an action, A tag placed at a location where the user should be when performing the action to be controlled; a mobile terminal carried by the user and capable of accessing the tag via short-range wireless communication; a server accessed by the mobile terminal via a network, the tag transmits an encrypted code obtained by encrypting a verification code, the value of which changes with each access, in response to an access from the mobile terminal; The portable terminal transmits the encrypted code obtained from the tag to the server; The server performs a decryption process on the encrypted code received from the mobile terminal, and if the decryption process is successful and the verification code obtained in this decryption process is different from the verification codes obtained in previous decryption processes, the server instructs the execution of an action corresponding to the tag.

2. The action control system according to claim 1 , the verification code is a code whose value increases every time the tag is accessed, The action control system is characterized in that the server instructs the execution of an action corresponding to the tag if the decryption process is successful and the verification code obtained in the current decryption process is larger than the verification code obtained in the previous decryption process.

3. 3. The action control system according to claim 1, The action control system is characterized in that the server requests the mobile terminal to perform user authentication before instructing the execution of an action corresponding to the tag, and if a response is obtained from the mobile terminal indicating that the user authentication was successful, instructs the execution of the action corresponding to the tag.

4. 4. The action control system according to claim 1, The action control system is characterized in that, before instructing the user to execute the action corresponding to the tag, the server displays a screen on the mobile terminal that accepts an instruction operation from the user to execute the action corresponding to the tag, and when the instruction operation is performed, instructs the user to execute the action corresponding to the tag.

5. In an action control server that controls the execution of an action, a storage unit that stores data indicating a correspondence between an action to be controlled and a tag installed at a location where a user is expected to be when the action is executed; a communication unit that receives, via the mobile terminal, an encrypted code obtained by encrypting a verification code that changes value each time the tag is accessed, the verification code being sent from the tag in response to an access to the tag by a mobile terminal carried by the user via short-range wireless communication; and a verification unit that performs a decryption process on the encrypted code received from the mobile terminal by the communication unit, and determines whether or not the decryption process is successful and whether or not a verification code obtained in this decryption process is different from verification codes obtained in previous decryption processes; and an execution instruction unit that instructs the execution of an action corresponding to the tag in accordance with the data stored in the memory unit when the verification unit determines that the condition is met.

6. 1. An action control method for controlling execution of an action, comprising: A portable terminal carried by a user accesses, via short-range wireless communication, a tag installed at a location where the user is to be located when the action to be controlled is to be performed; the tag transmits an encrypted code obtained by encrypting a verification code, the value of which changes with each access, in response to an access from the mobile terminal; The portable terminal transmits the encrypted code obtained from the tag to a server; The action control method is characterized in that the server performs a decryption process on the encrypted code received from the mobile terminal, and if the decryption process is successful and the verification code obtained in this decryption process is different from the verification codes obtained in previous decryption processes, instructs the execution of an action corresponding to the tag.

Images