A self-service terminal application security exit method

Abstract

The application embodiment discloses a self-service terminal application security exit method, comprising the following steps: in the case that an exit command of the application of the self-service terminal is received, obtaining the current business scenario of the self-service terminal and the current execution command set of the self-service terminal, then determining whether the application meets the exit condition according to the current business scenario and the current execution command set, in the case that the application does not meet the exit condition, matching in a preset security exit rule table according to the current business scenario to obtain the target security exit rule corresponding to the current business scenario, finally executing the target security exit rule, and executing the exit command of the application after the target security exit rule is executed, realizing the security exit of the application, and effectively solving the technical problems existing in the prior art.

Description

Technical Field

[0001] This invention relates to the field of financial services technology, and in particular to a method for securely exiting a self-service terminal application. Background Technology

[0002] In the financial services industry, self-service terminals (i.e., ATMs and financial equipment) typically exit applications by directly executing the received exit command. However, this method ignores the current status of each module within the self-service terminal, which may result in modules remaining in busy operation or exiting abnormally, leading to risks of damage or performance degradation to the self-service terminal. Summary of the Invention

[0003] Based on this, it is necessary to propose a secure application exit method for self-service terminals to address the above-mentioned problems. This method enables secure application exit and effectively solves the technical problems existing in the prior art. It avoids the risk of damage or performance degradation to the self-service terminal due to neglecting the current status of each module in the self-service terminal, which may result in the modules being unable to exit, remaining in busy use, or exiting abnormally.

[0004] To achieve the above objectives, the present invention provides, in a first aspect, a method for securely exiting an application on a self-service terminal, the method comprising:

[0005] Upon receiving an exit command from the self-service terminal application, obtain the current business scenario of the self-service terminal and the current set of commands executed by the self-service terminal.

[0006] Determine whether the application meets the exit conditions based on the current business scenario and the current set of executed commands;

[0007] If the application does not meet the exit conditions, the target security exit rule corresponding to the current business scenario is obtained by matching the current business scenario in the preset security exit rule table.

[0008] Execute the target security exit rule, and after executing the target security exit rule, execute the application's exit command.

[0009] Optionally, determining whether the application meets the exit conditions based on the current business scenario and the current set of executed commands includes:

[0010] The current usage status of each module in the self-service terminal is determined based on the currently executed command set;

[0011] Based on the current business scenario and the current usage status of each module in the self-service terminal, determine whether the application meets the exit conditions.

[0012] Optionally, determining the current usage status of each module in the self-service terminal based on the currently executed command set; and determining whether the application meets the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, includes:

[0013] If the current set of executed commands includes a card reading command, and if the current business scenario is a query business scenario, and the current usage state of the card reader in the self-service terminal is a waiting card insertion state or a card reading state, then it is determined that the application does not meet the exit conditions.

[0014] The execution of the target safe exit rule includes:

[0015] If the current usage state of the card reader is waiting for card insertion, the current usage state of the card reader is cancelled.

[0016] If the current usage state of the card reader is card reading mode, the current usage state of the card reader is completed.

[0017] Optionally, determining the current usage status of each module in the self-service terminal based on the currently executed command set; and determining whether the application meets the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, includes:

[0018] If the current set of executed commands includes input plaintext commands or encrypted commands, and if the current business scenario is a money transfer business scenario, and the current usage state of the encrypted keyboard in the self-service terminal is waiting for plaintext input, plaintext input, or plaintext encrypted state, then it is determined that the application does not meet the exit conditions.

[0019] If the current set of executed commands includes an input ciphertext command or a calculation cipher block command, and if the current business scenario is a password change business scenario, and the current usage state of the encrypted keyboard in the self-service terminal is a waiting password input state, a password input state, or a password verification state, then it is determined that the application does not meet the exit conditions.

[0020] The execution of the target safe exit rule includes:

[0021] If the current usage state of the encrypted keyboard is either waiting for plaintext input or waiting for password input, then cancel the current usage state of the encrypted keyboard.

[0022] If the current usage state of the encrypted keyboard is plaintext encryption state, password entered state, or password verification state, the current usage state of the encrypted keyboard is completed.

[0023] If the current usage state of the encrypted keyboard is the plaintext input state, the current usage state of the encrypted keyboard is executed, and the remaining usage states of the encrypted keyboard are executed in sequence, until the plaintext encryption state of the encrypted keyboard is executed.

[0024] Optionally, determining the current usage status of each module in the self-service terminal based on the currently executed command set; and determining whether the application meets the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, includes:

[0025] If the current set of executed commands includes cash dispensing command, cash withdrawal command, or cash delivery command, and if the current business scenario is a cash withdrawal business scenario, and the current usage status of the cash dispensing mechanism in the self-service terminal is cash withdrawal waiting status, cash withdrawal status, cash withdrawal counting status, cash dispensing verification status, or delivery status, then it is determined that the application does not meet the exit conditions.

[0026] The execution of the target safe exit rule includes:

[0027] If the current usage state of the cash dispensing mechanism is a withdrawal waiting state, the current usage state of the cash dispensing mechanism is cancelled.

[0028] If the current usage state of the cash dispensing mechanism is cash dispensing verification state or cash dispensing state, the current usage state of the cash dispensing mechanism is completed.

[0029] When the current usage state of the cash dispensing mechanism is cash dispensing state or cash dispensing counting state, the current usage state of the cash dispensing mechanism is completed, and the remaining usage states of the cash dispensing mechanism are executed in sequence, until the cash dispensing verification state of the cash dispensing mechanism is completed.

[0030] Optionally, determining the current usage status of each module in the self-service terminal based on the currently executed command set; and determining whether the application meets the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, includes:

[0031] If the current set of executed commands includes a deposit preparation command, a cash door opening command, a cash door closing command, a cash verification command, or a cash box deposit command, and if the current business scenario is a deposit business scenario, and the current usage status of the deposit mechanism in the self-service terminal is a deposit waiting state, a cash dispensing state, a cash dispensing counting state, a deposit verification state, or a cash box deposit state, then it is determined that the application does not meet the exit conditions.

[0032] The execution of the target safe exit rule includes:

[0033] If the current usage status of the deposit machine is a deposit waiting status, then cancel the current usage status of the deposit machine.

[0034] If the current usage state of the deposit machine is the cash box deposit state, the current usage state of the deposit machine is completed.

[0035] When the current usage state of the deposit machine is cash dispensing, cash dispensing counting, or deposit verification, the current usage state of the deposit machine is completed, and the remaining usage states of the deposit machine are executed sequentially until the cash box deposit state of the deposit machine is completed.

[0036] Optionally, determining the current usage status of each module in the self-service terminal based on the currently executed command set; and determining whether the application meets the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, includes:

[0037] If the current set of executed commands includes print commands or media control commands, and if the current business scenario is a print flow business scenario, and the current usage status of the printer in the self-service terminal is waiting to print, printing, or paper feeding, then it is determined that the application does not meet the exit conditions.

[0038] The execution of the target safe exit rule includes:

[0039] If the printer is currently in a waiting-to-print state, cancel the printer's current usage state.

[0040] If the printer is currently in paper feeding mode, the current usage state of the printer is completed.

[0041] If the printer is currently in printing mode, the printer will complete the current usage mode and then sequentially complete the remaining usage modes until the printer is in paper feeding mode.

[0042] Optionally, determining the current usage status of each module in the self-service terminal based on the currently executed command set; and determining whether the application meets the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, includes:

[0043] If the current set of executed commands includes a preview command or a live photo capture command, and if the current business scenario is a live photo capture business scenario, and the current usage state of the camera device in the self-service terminal is a waiting photo capture state, a photo capture state, a photo capture verification state, a waiting video recording state, a video recording state, or a video recording verification state, then it is determined that the application does not meet the exit conditions.

[0044] The execution of the target safe exit rule includes:

[0045] If the current usage state of the camera device is waiting to take a picture or waiting to record a video, cancel the current usage state of the camera device.

[0046] If the current usage state of the camera device is photo verification state or video verification state, the current usage state of the camera device is completed;

[0047] If the current usage state of the camera device is the photo-taking state, the current usage state of the camera device is completed, and the remaining usage states of the camera device are executed in sequence until the photo-taking verification state of the camera device is completed.

[0048] If the current usage state of the camera device is recording, the current usage state of the camera device is executed, and then the remaining usage states of the camera device are executed in sequence, until the recording verification state of the camera device is executed.

[0049] Optionally, determining the current usage status of each module in the self-service terminal based on the currently executed command set; and determining whether the application meets the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, includes:

[0050] If the current set of executed commands includes commands to turn indicator lights on or off, and if the current business scenario is an indicator light prompt business scenario, and the current usage status of the indicator lights in the self-service terminal is either the indicator light on state or the indicator light off state, then it is determined that the application does not meet the exit conditions.

[0051] The execution of the target safe exit rule includes:

[0052] If the current usage state of the indicator light is "indicator light off", then complete the execution of the current usage state of the indicator light;

[0053] When the current usage state of the indicator light is the on indicator light state, the current usage state of the indicator light is completed, and the remaining usage states of the indicator light are executed in sequence, until the off indicator light state is executed.

[0054] Optionally, determining the current usage status of each module in the self-service terminal based on the currently executed command set; and determining whether the application meets the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, includes:

[0055] If the current set of executed commands includes the command to open / close the cash gate, and if the current business scenario is a cash gate notification business scenario, and the current usage status of the cash gate in the self-service terminal is either open or closed, then it is determined that the application does not meet the exit conditions.

[0056] The execution of the target safe exit rule includes:

[0057] If the current usage state of the banknote door is the closed banknote door state, the current usage state of the banknote door is completed;

[0058] If the current usage state of the cash gate is "open" and the current user is not the current transaction user, then the current usage state of the cash gate is cancelled.

[0059] If the current usage state of the cash gate is "open", the current user is the current transaction user, and the temporary storage module in the self-service terminal has no cash stored, then the current usage state of the cash gate is cancelled.

[0060] If the current usage state of the cash gate is the open cash gate state, and the open cash gate state is the deposit open cash gate state, and the current user is the current transaction user, and the temporary storage module in the self-service terminal has stored cash, and the cash stored in the temporary storage module has not been credited to the account, then the current usage state of the cash gate is completed, and the remaining usage states of the cash gate are completed in sequence, until the closed cash gate state is completed.

[0061] If the current usage state of the cash gate is the cash gate open state, and the cash gate open state is the deposit open cash gate state, and the current user is the current transaction user, and the temporary storage module in the self-service terminal has stored banknotes, and the banknotes stored in the temporary storage module have been credited to the account, then the current usage state of the cash gate is cancelled.

[0062] If the current usage state of the cash gate is the cash gate open state, and the cash gate is the cash withdrawal open state, and the current user is the current transaction user, and the temporary storage module in the self-service terminal has stored banknotes, and the banknotes stored in the temporary storage module have not been credited to the account, then the current usage state of the cash gate is cancelled.

[0063] If the current usage state of the cash gate is "open cash gate", and the cash gate is in the withdrawal opening state, and the current user is the current transaction user, and the temporary storage module in the self-service terminal has stored banknotes, and the banknotes stored in the temporary storage module have been credited to the account, then the current usage state of the cash gate is completed, and the remaining usage states of the cash gate are completed sequentially, until the cash gate is closed.

[0064] To achieve the above objectives, the present invention provides, in a second aspect, an application security exit device for a self-service terminal, the device comprising:

[0065] The acquisition module is used to acquire the current business scenario of the self-service terminal and the current set of commands executed by the self-service terminal when it receives an exit command from the application of the self-service terminal.

[0066] The determination module is used to determine whether the application meets the exit conditions based on the current business scenario and the current set of executed commands;

[0067] The matching module is used to match the current business scenario with a preset security exit rule table when the application does not meet the exit conditions, so as to obtain the target security exit rule corresponding to the current business scenario.

[0068] The execution module is used to execute the target security exit rule and, after executing the target security exit rule, execute the application's exit command.

[0069] To achieve the above objectives, the present invention provides, in a third aspect, a computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to perform the method as described in any one of the first aspects.

[0070] To achieve the above objectives, the present invention provides a computer device in a fourth aspect, including a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the method as described in any one of the first aspects.

[0071] The present invention provides the following advantages: Upon receiving an application exit command from a self-service terminal, the method obtains the current business scenario and the current set of execution commands of the self-service terminal. Then, based on the current business scenario and the current set of execution commands, it determines whether the application meets the exit conditions. If the application does not meet the exit conditions, it matches the current business scenario against a preset secure exit rule table to obtain the target secure exit rule corresponding to the current business scenario. Finally, it executes the target secure exit rule, and after executing the target secure exit rule, it executes the application's exit command. In other words, by receiving an application exit command from a self-service terminal, the method determines the current status of each module in the self-service terminal based on the current business scenario and the current set of execution commands to determine whether the application meets the exit conditions. If not, it executes the target secure exit rule corresponding to the current business scenario, and then executes the application's exit command, thus achieving secure application exit. This effectively solves the technical problems existing in the prior art, avoiding the risk of damage or performance degradation to the self-service terminal due to neglecting the current status of each module, which could result in modules remaining busy or exiting abnormally. Attached Figure Description

[0072] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0073] in:

[0074] Figure 1 This is a schematic diagram of a secure application exit method for a self-service terminal according to an embodiment of this application;

[0075] Figure 2 This is a schematic diagram of an application security exit device for a self-service terminal in an embodiment of this application;

[0076] Figure 3 This is a diagram showing the internal structure of a computer device in some embodiments. Detailed Implementation

[0077] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0078] In the financial services industry, self-service terminals (i.e., ATMs and financial equipment) typically exit applications by directly executing the received exit command. However, this method ignores the current status of each module within the self-service terminal, which may result in modules remaining in busy operation or exiting abnormally, leading to risks of damage or performance degradation to the self-service terminal.

[0079] The self-service terminal includes, but is not limited to, card readers, encrypted keyboards, cash dispensing mechanisms, deposit mechanisms, printers, camera devices, indicator lights, or cash gates for the mechanism.

[0080] To address the aforementioned issues, this application proposes a secure application exit method for self-service terminals. This method enables secure application exit and effectively solves the technical problems existing in the prior art. It avoids the risk of damage or performance degradation to the self-service terminal due to neglecting the current status of each module in the self-service terminal, which could result in modules remaining busy or exiting abnormally. The specific implementation principle will be described in detail in the following embodiments.

[0081] It should be noted beforehand that this application has previously studied the application security exit method for self-service terminals, but it only involves executing a fixed configuration rule or specific program processing once before the application exits. Since this does not take into account the business scenario currently being executed by the self-service terminal and the current usage status of each module in the self-service terminal, multiple executions may occur, which greatly reduces the execution efficiency of application exit.

[0082] This application provides a method for securely exiting a self-service terminal application in its first aspect.

[0083] Please see Figure 1 This is a schematic diagram of an application security exit method for a self-service terminal according to an embodiment of this application. The method includes:

[0084] Step 110: Upon receiving an exit command from the self-service terminal application, obtain the current business scenario of the self-service terminal and the current set of commands executed by the self-service terminal.

[0085] The current business scenario refers to the business scenario that the self-service terminal is currently executing, such as a query business scenario or a transfer business scenario. The current execution command set (i.e., the current execution command sequence) refers to the command set corresponding to the current usage state of each module in the self-service terminal. For example, the card reading command corresponding to the card reading state of the card reader in the self-service terminal, and the password input command corresponding to the waiting password state of the encrypted keyboard in the self-service terminal.

[0086] Step 120: Determine whether the application meets the exit conditions based on the current business scenario and the current set of executed commands.

[0087] It should be noted that by determining whether the application meets the exit conditions based on the current business scenario and the current set of commands being executed, that is, by taking into account the business scenario currently being executed by the self-service terminal and the current usage status of each module in the self-service terminal, the application can exit directly when it meets the exit conditions without needing to execute more, which effectively improves the execution efficiency of application exit.

[0088] In some embodiments, determining whether an application meets the exit conditions based on the current business scenario and the current set of execution commands includes: obtaining a preset set of execution commands table; matching the preset set of execution commands table according to the current business scenario to obtain the target set of execution commands corresponding to the current business scenario; and determining whether the application meets the exit conditions based on the target set of execution commands and the current set of execution commands.

[0089] If there are identical commands between the target execution command set and the current execution command set, it indicates that there are some modules in the self-service terminal that may not be able to exit under the current business scenario, are still in busy use, or have exited abnormally. Therefore, it is determined that the application does not meet the exit conditions. If there are no identical commands between the target execution command set and the current execution command set, it indicates that there are no modules in the self-service terminal that may not be able to exit under the current business scenario, are still in busy use, or have exited abnormally. Therefore, it is determined that the application meets the exit conditions.

[0090] It should be noted that the preset execution command set table can be set in advance by the operator. It can be understood that the preset execution command set table contains each business scenario and the target execution command set corresponding to each business scenario.

[0091] Step 130: If the application does not meet the exit conditions, match it in the preset security exit rule table according to the current business scenario to obtain the target security exit rule corresponding to the current business scenario.

[0092] It should be noted that the preset safe exit rule table can be set in advance by the operator. It can be understood that the preset safe exit rule table contains each business scenario and the target safe exit rule corresponding to each business scenario.

[0093] In other embodiments, an application exit command is executed when the application meets the exit conditions.

[0094] Step 140: Execute the target security exit rule, and after executing the target security exit rule, execute the application's exit command.

[0095] It should be noted that after the target security exit rule is executed, some modules in the self-service terminal that may not be able to exit in the current business scenario, are still in busy use, or have exited abnormally have already completed their exit. At this time, there are no identical commands between the target execution command set and the current execution command set, that is, the application meets the exit conditions, so the application's exit command can be executed.

[0096] In this embodiment, upon receiving an exit command from an application in a self-service terminal, the current status of each module in the self-service terminal is determined based on the current business scenario and the current set of executed commands. This determines whether the application meets the exit conditions. If not, the target safe exit rule corresponding to the current business scenario is executed, and then the application's exit command is executed. This achieves safe application exit and effectively solves the technical problems existing in the prior art. It avoids the risk that the modules in the self-service terminal may not be able to exit due to neglecting the current status of each module, remaining busy in use, or exiting abnormally, thus causing damage or performance degradation to the self-service terminal.

[0097] Furthermore, by incorporating a comprehensive consideration of the current business scenario and the current usage status of each module, this approach not only enables secure application exit from self-service terminals to avoid the risk of equipment damage or performance degradation caused by direct exit, but also improves the efficiency of application exit. This is of great significance for enhancing the stability and customer satisfaction of the financial services industry.

[0098] Furthermore, if any module in the self-service terminal exits abnormally, it may lead to errors in financial transactions. Therefore, this application also reduces the probability of accounting transaction errors to a certain extent, thereby ensuring the security of transactions.

[0099] In one feasible implementation, step 120 in the above embodiment, determining whether the application meets the exit conditions based on the current business scenario and the current set of executed commands, includes: determining the current usage status of each module in the self-service terminal based on the current set of executed commands; and determining whether the application meets the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal.

[0100] It should be noted that by determining whether an application meets the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, that is, by taking into account the business scenario currently being executed by the self-service terminal and the current usage status of each module in the self-service terminal, the application can exit directly when it meets the exit conditions without needing to execute further, effectively improving the execution efficiency of application exit.

[0101] In some embodiments, determining the current usage status of each module in the self-service terminal based on the current set of executed commands includes: obtaining a first preset usage status table; matching each command in the current set of executed commands in the first preset usage status table to obtain the target usage status corresponding to each command in the current set of executed commands; and using the target usage status corresponding to each command in the current set of executed commands as the current usage status of each module in the self-service terminal.

[0102] It should be noted that the first preset usage status table can be preset by the operator. It can be understood that the first preset usage status table contains each command and the target usage status corresponding to each command.

[0103] In some embodiments, determining whether an application meets the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal includes: obtaining a second preset usage status table; matching the second preset usage status table according to the current business scenario to obtain multiple target usage statuses corresponding to the current business scenario; and determining whether the application meets the exit conditions based on the multiple target usage statuses corresponding to the current business scenario and the current usage status of each module in the self-service terminal.

[0104] If multiple target usage states corresponding to the current business scenario are identical to the current usage states of various modules in the self-service terminal, it indicates that some modules in the self-service terminal may not be able to exit under the current business scenario, are still in busy use, or have exited abnormally. Therefore, it is determined that the application does not meet the exit conditions. If multiple target usage states corresponding to the current business scenario are not identical to the current usage states of various modules in the self-service terminal, it indicates that there are no modules in the self-service terminal that may not be able to exit under the current business scenario, are still in busy use, or have exited abnormally. Therefore, it is determined that the application meets the exit conditions.

[0105] It should be noted that the second preset usage status table can be preset by the operator. It can be understood that the second preset usage status table contains each business scenario and multiple target usage statuses corresponding to each business scenario.

[0106] In this embodiment, the current usage status of each module is extracted directly from the current set of executed commands. Then, the current business scenario being executed by the self-service terminal and the current usage status of each module being executed in the self-service terminal are considered to determine whether the application meets the exit conditions. That is, the current usage status of each module being executed in the self-service terminal can achieve a more refined judgment compared with the current set of executed commands, so as to more accurately determine whether the application meets the exit conditions.

[0107] Furthermore, by incorporating a comprehensive consideration of the current business scenario and the current usage status of each module, not only is secure application exit from the self-service terminal achieved to avoid the risk of device damage or performance degradation caused by direct exit, but the execution efficiency of application exit is also improved.

[0108] Furthermore, by using preset usage status tables (first preset usage status table and second preset usage status table) for matching, the accuracy and consistency of the judgment criteria are ensured.

[0109] In one feasible implementation, the current usage status of each module in the self-service terminal is determined based on the current set of executed commands in the above embodiments; the application is determined to meet the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, including: if the current set of executed commands includes a card reading command, and if the current business scenario is a query business scenario and the current usage status of the card reader in the self-service terminal is a waiting card insertion state or a card reading state, then it is determined that the application does not meet the exit conditions.

[0110] The execution target safe exit rule in the above embodiments includes: canceling the current use state of the card reader when the current use state of the card reader is waiting for card insertion; and completing the current use state of the card reader when the current use state of the card reader is reading a card.

[0111] In some embodiments, the card reader's usage states include, but are not limited to, initialization state, waiting for card insertion state, card reading state, card reading verification state, error state, card ejection state, maintenance state, fault state, sleep state, wake-up state, and locked state.

[0112] In this embodiment of the application, by executing the corresponding target security exit rule according to the specific usage state of the card reader (waiting for card insertion or reading card) in the query business scenario, not only is the application security exit of the self-service terminal realized to avoid the risk of device damage or performance degradation caused by direct exit, but also the execution efficiency of application exit is improved.

[0113] In one feasible implementation, the current usage status of each module in the self-service terminal is determined based on the current set of executed commands in the above embodiments; the application is determined to meet the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, including: if the current set of executed commands includes input plaintext commands or encrypted commands, and if the current business scenario is a transfer business scenario, and the current usage status of the encrypted keyboard in the self-service terminal is waiting for plaintext input, plaintext input, or plaintext encrypted, then the application is determined not to meet the exit conditions; if the current set of executed commands includes input ciphertext commands or password block calculation commands, and if the current business scenario is a password change business scenario, and the current usage status of the encrypted keyboard in the self-service terminal is waiting for password input, password input, or password verification, then the application is determined not to meet the exit conditions.

[0114] The execution target secure exit rule in the above embodiments includes: canceling the current use state of the encrypted keyboard when the current use state of the encrypted keyboard is waiting for plaintext input or waiting for password input; completing the current use state of the encrypted keyboard when the current use state of the encrypted keyboard is plaintext encryption, password input, or password verification; completing the current use state of the encrypted keyboard when the current use state of the encrypted keyboard is plaintext input, and sequentially completing the remaining use states of the encrypted keyboard until the plaintext encryption state of the encrypted keyboard is completed.

[0115] In some embodiments, the usage states of the encrypted keyboard include, but are not limited to, initialization state, waiting state (waiting for plaintext input or waiting for password input), input state (plaintext input or password input), encryption state (plaintext encryption or password encryption), verification state (plaintext verification or password verification), error state, unlock state, lock state, maintenance state, sleep state, and wake-up state.

[0116] It should be noted that the remaining usage states of the encrypted keyboard are executed sequentially according to the execution flow order. You can refer to the usage states of the encrypted keyboard listed above. For example, plaintext input state → plaintext encrypted state. That is, the next execution order after the plaintext input state is the plaintext encrypted state (the execution flow order of the other modules of the self-service terminal in the following embodiments is similar. You can also refer to the usage states of their modules listed below. It will not be repeated below).

[0117] In this application embodiment, in the transfer business scenario, the corresponding target security exit rule is executed according to the specific usage state of the encrypted keyboard (waiting for plaintext input, plaintext input, plaintext encryption, waiting for password input, password input, or password verification). This not only realizes the secure exit of the self-service terminal application to avoid the risk of device damage or performance degradation caused by direct exit, but also improves the execution efficiency of application exit.

[0118] In one feasible implementation, the current usage status of each module in the self-service terminal is determined based on the current set of executed commands in the above embodiments; the application is determined to meet the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, including: if the current set of executed commands includes cash dispensing command, cash withdrawal command or cash delivery command, and if the current business scenario is a cash withdrawal business scenario, and the current usage status of the cash dispensing mechanism in the self-service terminal is cash withdrawal waiting state, cash withdrawal state, cash withdrawal counting state, cash dispensing verification state or delivery state, then it is determined that the application does not meet the exit conditions.

[0119] The execution target security exit rule in the above embodiments includes: canceling the current use state of the cash dispensing machine when the current use state of the cash dispensing machine is the withdrawal waiting state; completing the current use state of the cash dispensing machine when the current use state of the cash dispensing machine is the cash dispensing verification state or the delivery state; completing the current use state of the cash dispensing machine when the current use state of the cash dispensing machine is the cash dispensing state or the cash dispensing counting state, and sequentially completing the remaining use states of the cash dispensing machine until the cash dispensing verification state of the cash dispensing machine is completed.

[0120] In some embodiments, the operating states of the cash dispensing mechanism include, but are not limited to, initialization state, withdrawal waiting state, cash dispensing state, cash dispensing counting state, cash dispensing verification state, stacking state, delivery state, error state, cash return state, maintenance state, sleep state, wake-up state, and locked state.

[0121] In this embodiment of the application, in the cash withdrawal business scenario, the corresponding target security exit rule is executed according to the specific usage state of the cash dispensing mechanism (withdrawal waiting state, cash dispensing state, cash dispensing counting state, cash dispensing verification state, or delivery state). This not only realizes the secure exit of the self-service terminal application to avoid the risk of equipment damage or performance degradation caused by direct exit, but also improves the execution efficiency of application exit.

[0122] In one feasible implementation, the current usage status of each module in the self-service terminal is determined based on the current set of executed commands in the above embodiments; the application is determined to meet the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, including: if the current set of executed commands includes a deposit preparation command, a cash door opening command, a cash door closing command, a cash verification command, or a cash box deposit command, and if the current business scenario is a deposit business scenario, and the current usage status of the deposit mechanism in the self-service terminal is a deposit waiting state, a cash dispensing state, a cash dispensing counting state, a deposit verification state, or a cash box deposit state, then it is determined that the application does not meet the exit conditions.

[0123] The execution target safe exit rules in the above embodiments include: when the current usage state of the deposit machine is the deposit waiting state, canceling the current usage state of the deposit machine; when the current usage state of the deposit machine is the cash box deposit state, completing the current usage state of the deposit machine; when the current usage state of the deposit machine is the cash dispensing state, cash dispensing counting state, or deposit verification state, completing the current usage state of the deposit machine, and sequentially completing the remaining usage states of the deposit machine until the cash box deposit state of the deposit machine is completed.

[0124] In some embodiments, the usage states of the deposit mechanism include, but are not limited to, initialization state, deposit waiting state, cash dispensing state, cash dispensing counting state, deposit verification state, cash storage state, stacking state, completion state, error state, cash return state, maintenance state, sleep state, wake-up state, and locked state.

[0125] In this embodiment of the application, in the deposit business scenario, the corresponding target security exit rule is executed according to the specific usage state of the deposit machine (deposit waiting state, cash dispensing state, cash dispensing counting state, deposit verification state, or cash box deposit state). This not only realizes the secure exit of the self-service terminal application to avoid the risk of equipment damage or performance degradation caused by direct exit, but also improves the execution efficiency of application exit.

[0126] In one feasible implementation, the current usage status of each module in the self-service terminal is determined based on the current set of executed commands in the above embodiments; the application is determined to meet the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, including: if the current set of executed commands includes printing commands or media control commands, and if the current business scenario is a printing flow business scenario, and the current usage status of the printer in the self-service terminal is waiting to print, printing, or paper feeding, then it is determined that the application does not meet the exit conditions.

[0127] The execution target safe exit rule in the above embodiment includes: canceling the current use state of the printer when the printer is in the waiting to print state; completing the current use state of the printer when the printer is in the paper feeding state; completing the current use state of the printer when the printer is in the printing state, and sequentially completing the remaining use states of the printer until the paper feeding state of the printer is completed.

[0128] In some embodiments, the printer's usage states include, but are not limited to, initialization state, waiting to print state, printing state, paper feeding state, paper out state, error state, maintenance state, sleep state, wake-up state, and locked state.

[0129] In this embodiment of the application, in the scenario of printing pipeline business, the corresponding target safe exit rule is executed according to the specific usage state of the printer (waiting to print, printing or paper feeding state). This not only realizes the safe exit of the self-service terminal application to avoid the risk of equipment damage or performance degradation caused by direct exit, but also improves the execution efficiency of application exit.

[0130] In one feasible implementation, the current usage status of each module in the self-service terminal is determined based on the current set of executed commands in the above embodiments; the application is determined to meet the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, including: if the current set of executed commands includes a preview command or a live photo command, and if the current business scenario is a live photo business scenario, and the current usage status of the camera device in the self-service terminal is a waiting photo state, a photo state, a photo verification state, a waiting recording state, a recording state, or a recording verification state, then it is determined that the application does not meet the exit conditions.

[0131] The execution target security exit rules in the above embodiments include: canceling the current use state of the camera device when the current use state of the camera device is waiting to take a picture or waiting to record a video; completing the current use state of the camera device when the current use state of the camera device is photo verification or video verification; completing the current use state of the camera device when the current use state of the camera device is photo taking, and then sequentially completing the remaining use states of the camera device until the photo verification state of the camera device is completed; and completing the current use state of the camera device when the current use state of the camera device is video recording, and then sequentially completing the remaining use states of the camera device until the video verification state of the camera device is completed.

[0132] In some embodiments, the current usage state of the camera device includes initialization state, waiting state (waiting to take a picture or waiting to record a video), camera state (taking a picture or recording a video), verification state (taking a picture for verification or recording a video for verification), monitoring state, alarm state, maintenance state, sleep state, wake-up state, and lock state.

[0133] In this embodiment of the application, in the live photo-taking service scenario, the corresponding target security exit rule is executed according to the specific usage state of the camera device (waiting to take a photo, taking a photo, photo verification, waiting to record, recording, or recording verification). This not only realizes the secure exit of the self-service terminal application to avoid the risk of device damage or performance degradation caused by direct exit, but also improves the execution efficiency of application exit.

[0134] In one feasible implementation, the current usage status of each module in the self-service terminal is determined based on the current set of executed commands in the above embodiments; the application is determined to meet the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, including: if the current set of executed commands includes a command to turn on / off an indicator light, and if the current business scenario is an indicator light prompt business scenario, and the current usage status of the indicator lights in the self-service terminal is either the indicator light on state or the indicator light off state, then it is determined that the application does not meet the exit conditions.

[0135] The execution target safe exit rule in the above embodiment includes: when the current usage state of the indicator light is the off indicator light state, executing the current usage state of the indicator light; when the current usage state of the indicator light is the on indicator light state, executing the current usage state of the indicator light, and sequentially executing the remaining usage states of the indicator light, until executing the off indicator light state.

[0136] In some embodiments, the indicator light's usage states include, but are not limited to, initialization state, indicator light on state, and indicator light off state.

[0137] In this embodiment of the application, in the scenario of indicator light prompts, the corresponding target safe exit rule is executed according to the specific usage state of the indicator light (indicator light on or indicator light off). This not only realizes the safe exit of the self-service terminal application to avoid the risk of device damage or performance degradation caused by direct exit, but also improves the execution efficiency of application exit.

[0138] In one feasible implementation, the current usage status of each module in the self-service terminal is determined based on the current set of executed commands in the above embodiments; the application is determined to meet the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, including: if the current set of executed commands includes the command to open or close the cash gate, and if the current business scenario is the cash gate prompt business scenario, and the current usage status of the cash gate in the self-service terminal is either open or closed, then it is determined that the application does not meet the exit conditions.

[0139] The execution target security exit rules in the above embodiments include: completing the execution of the current usage state of the cash gate when the cash gate is currently closed; canceling the execution of the current usage state of the cash gate when the cash gate is currently open and the current user is not the current transaction user; and canceling the execution when the cash gate is currently open, the current user is the current transaction user, and the temporary storage module in the self-service terminal has no cash stored. Complete the current usage state of the cash gate mechanism; if the current usage state of the cash gate mechanism is "open cash gate," and the cash gate mechanism's "open cash gate" state is the deposit-open cash gate state, and the current user is the current transaction user, and the temporary storage module in the self-service terminal has stored cash, and the cash stored in the temporary storage module has not been credited to the account, then complete the current usage state of the cash gate mechanism, and sequentially complete the remaining usage states of the cash gate mechanism until the cash gate mechanism is closed; if the current usage state of the cash gate mechanism is "open cash gate," then complete the current usage state of the cash gate mechanism, and sequentially complete the remaining usage states of the cash gate mechanism, until the cash gate mechanism is closed. If the current user is the current transaction user, the self-service terminal's temporary storage module contains banknotes, and the banknotes stored in the temporary storage module have been credited to the account, then the current usage state of the cash gate is cancelled. If the current usage state of the cash gate is the open cash gate state, the current user is the current transaction user, the self-service terminal's temporary storage module contains banknotes, and the temporary storage module... If the stored banknotes have not been credited to the account, the current usage state of the cash gate is cancelled. If the current usage state of the cash gate is "open cash gate", and the cash gate opening state is "withdrawal cash gate opening", and the current user is the current transaction user, and the temporary storage module in the self-service terminal contains banknotes, and the banknotes stored in the temporary storage module have been credited to the account, the current usage state of the cash gate is completed, and the remaining usage states of the cash gate are completed in sequence, until the cash gate closing state is completed.

[0140] In some embodiments, the indicator light's usage states include, but are not limited to, initialization state, cash gate open state (cash gate open for deposits or cash gate open for withdrawals), and cash gate closed state (cash gate closed for deposits or cash gate closed for withdrawals).

[0141] In this embodiment of the application, in the scenario of the cash gate prompt, the corresponding target security exit rule is executed according to the specific usage state of the cash gate (cash gate open or cash gate closed). This not only realizes the secure exit of the self-service terminal application to avoid the risk of equipment damage or performance degradation caused by direct exit, but also improves the execution efficiency of application exit.

[0142] In a second aspect, this application provides an application security exit device for a self-service terminal.

[0143] Please see Figure 2 This is a schematic diagram of an application security exit device for a self-service terminal according to an embodiment of this application. The device 210 includes:

[0144] The acquisition module 211 is used to acquire the current business scenario of the self-service terminal and the current set of commands executed by the self-service terminal when it receives an exit command from the application of the self-service terminal.

[0145] The determination module 212 is used to determine whether the application meets the exit conditions based on the current business scenario and the current set of executed commands.

[0146] The matching module 213 is used to match the application with the preset security exit rule table according to the current business scenario when the application does not meet the exit conditions, so as to obtain the target security exit rule corresponding to the current business scenario.

[0147] Execution module 214 is used to execute the target security exit rule and, after executing the target security exit rule, execute the application's exit command.

[0148] In this embodiment of the application, the relevant contents of the acquisition module 211, determination module 212, matching module 213 and execution module 214 can be found in the following references. Figure 1 The contents of the illustrated embodiments will not be repeated here.

[0149] It should be noted that the device 210 of this application also includes other modules. It can be understood that the method of this application and the device 210 have a one-to-one correspondence. Therefore, the other modules of the device 210 of this application are the contents corresponding to the method of this application in the above embodiments.

[0150] In this embodiment, upon receiving an exit command from an application in a self-service terminal, the current status of each module in the self-service terminal is determined based on the current business scenario and the current set of executed commands. This determines whether the application meets the exit conditions. If not, the target safe exit rule corresponding to the current business scenario is executed, and then the application's exit command is executed. This achieves safe application exit and effectively solves the technical problems existing in the prior art. It avoids the risk that the modules in the self-service terminal may not be able to exit due to neglecting the current status of each module, remaining busy in use, or exiting abnormally, thus causing damage or performance degradation to the self-service terminal.

[0151] Furthermore, by incorporating a comprehensive consideration of the current business scenario and the current usage status of each module, this approach not only enables secure application exit from self-service terminals to avoid the risk of equipment damage or performance degradation caused by direct exit, but also improves the efficiency of application exit. This is of great significance for enhancing the stability and customer satisfaction of the financial services industry.

[0152] Furthermore, if any module in the self-service terminal exits abnormally, it may lead to errors in financial transactions. Therefore, this application also reduces the probability of accounting transaction errors to a certain extent, thereby ensuring the security of transactions.

[0153] In a third aspect, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to perform an application secure exit method for a self-service terminal as described in the above method embodiments.

[0154] In a fourth aspect, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor performs an application security exit method for a self-service terminal as described in the above method embodiments.

[0155] Figure 3 Internal structural diagrams of a computer device are shown in some embodiments. This computer device can specifically be a terminal (i.e., the self-service terminal mentioned in the above embodiments), a server, or a gateway. Figure 3 As shown, the computer device includes a processor, memory, and network interface connected via a system bus.

[0156] The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium of the computer device stores an operating system and may also store a computer program. When executed by a processor, this computer program causes the processor to perform the steps in the above method embodiments. The internal memory may also store a computer program, which, when executed by a processor, causes the processor to perform the steps in the above method embodiments. Those skilled in the art will understand that... Figure 3 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0157] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a non-volatile computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above methods.

[0158] Any references to memory, storage, database, or other media used in the embodiments provided in this application may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.

[0159] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0160] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A method for securely exiting an application on a self-service terminal, characterized in that, The method includes: Upon receiving an exit command from the self-service terminal application, obtain the current business scenario of the self-service terminal and the current set of commands executed by the self-service terminal. Determine whether the application meets the exit conditions based on the current business scenario and the current set of executed commands; If the application does not meet the exit conditions, the target security exit rule corresponding to the current business scenario is obtained by matching the current business scenario in the preset security exit rule table. Execute the target security exit rule, and after executing the target security exit rule, execute the application's exit command.

2. The method according to claim 1, characterized in that, Determining whether the application meets the exit conditions based on the current business scenario and the current set of executed commands includes: The current usage status of each module in the self-service terminal is determined based on the currently executed command set; Based on the current business scenario and the current usage status of each module in the self-service terminal, determine whether the application meets the exit conditions.

3. The method according to claim 2, characterized in that, The current usage status of each module in the self-service terminal is determined based on the currently executed command set; Determine whether the application meets the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, including: If the current set of executed commands includes a card reading command, and if the current business scenario is a query business scenario, and the current usage state of the card reader in the self-service terminal is a waiting card insertion state or a card reading state, then it is determined that the application does not meet the exit conditions. The execution of the target safe exit rule includes: If the current usage state of the card reader is waiting for card insertion, the current usage state of the card reader is cancelled. If the current usage state of the card reader is card reading mode, the current usage state of the card reader is completed.

4. The method according to claim 2, characterized in that, The current usage status of each module in the self-service terminal is determined based on the currently executed command set; Determine whether the application meets the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, including: If the current set of executed commands includes input plaintext commands or encrypted commands, and if the current business scenario is a money transfer business scenario, and the current usage state of the encrypted keyboard in the self-service terminal is waiting for plaintext input, plaintext input, or plaintext encrypted state, then it is determined that the application does not meet the exit conditions. If the current set of executed commands includes an input ciphertext command or a calculation cipher block command, and if the current business scenario is a password change business scenario, and the current usage state of the encrypted keyboard in the self-service terminal is a waiting password input state, a password input state, or a password verification state, then it is determined that the application does not meet the exit conditions. The execution of the target safe exit rule includes: If the current usage state of the encrypted keyboard is either waiting for plaintext input or waiting for password input, then cancel the current usage state of the encrypted keyboard. If the current usage state of the encrypted keyboard is plaintext encryption state, password entered state, or password verification state, the current usage state of the encrypted keyboard is completed. If the current usage state of the encrypted keyboard is the plaintext input state, the current usage state of the encrypted keyboard is executed, and the remaining usage states of the encrypted keyboard are executed in sequence, until the plaintext encryption state of the encrypted keyboard is executed.

5. The method according to claim 2, characterized in that, The current usage status of each module in the self-service terminal is determined based on the currently executed command set; Determine whether the application meets the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, including: If the current set of executed commands includes cash dispensing command, cash withdrawal command, or cash delivery command, and if the current business scenario is a cash withdrawal business scenario, and the current usage status of the cash dispensing mechanism in the self-service terminal is cash withdrawal waiting status, cash withdrawal status, cash withdrawal counting status, cash dispensing verification status, or delivery status, then it is determined that the application does not meet the exit conditions. The execution of the target safe exit rule includes: If the current usage state of the cash dispensing mechanism is a withdrawal waiting state, the current usage state of the cash dispensing mechanism is cancelled. If the current usage state of the cash dispensing mechanism is cash dispensing verification state or cash dispensing state, the current usage state of the cash dispensing mechanism is completed. When the current usage state of the cash dispensing mechanism is cash dispensing state or cash dispensing counting state, the current usage state of the cash dispensing mechanism is completed, and the remaining usage states of the cash dispensing mechanism are executed in sequence, until the cash dispensing verification state of the cash dispensing mechanism is completed.

6. The method according to claim 2, characterized in that, The current usage status of each module in the self-service terminal is determined based on the currently executed command set; Determine whether the application meets the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, including: If the current set of executed commands includes a deposit preparation command, a cash door opening command, a cash door closing command, a cash verification command, or a cash box deposit command, and if the current business scenario is a deposit business scenario, and the current usage status of the deposit mechanism in the self-service terminal is a deposit waiting state, a cash dispensing state, a cash dispensing counting state, a deposit verification state, or a cash box deposit state, then it is determined that the application does not meet the exit conditions. The execution of the target safe exit rule includes: If the current usage status of the deposit machine is a deposit waiting status, then cancel the current usage status of the deposit machine. If the current usage state of the deposit machine is the cash box deposit state, the current usage state of the deposit machine is completed. When the current usage state of the deposit machine is cash dispensing, cash dispensing counting, or deposit verification, the current usage state of the deposit machine is completed, and the remaining usage states of the deposit machine are executed sequentially until the cash box deposit state of the deposit machine is completed.

7. The method according to claim 2, characterized in that, The current usage status of each module in the self-service terminal is determined based on the currently executed command set; Determine whether the application meets the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, including: If the current set of executed commands includes print commands or media control commands, and if the current business scenario is a print flow business scenario, and the current usage status of the printer in the self-service terminal is waiting to print, printing, or paper feeding, then it is determined that the application does not meet the exit conditions. The execution of the target safe exit rule includes: If the printer is currently in a waiting-to-print state, cancel the printer's current usage state. If the printer is currently in paper feeding mode, the current usage state of the printer is completed. If the printer is currently in printing mode, the printer will complete the current usage mode and then sequentially complete the remaining usage modes until the printer is in paper feeding mode.

8. The method according to claim 2, characterized in that, The current usage status of each module in the self-service terminal is determined based on the currently executed command set; Determine whether the application meets the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, including: If the current set of executed commands includes a preview command or a live photo capture command, and if the current business scenario is a live photo capture business scenario, and the current usage state of the camera device in the self-service terminal is a waiting photo capture state, a photo capture state, a photo capture verification state, a waiting video recording state, a video recording state, or a video recording verification state, then it is determined that the application does not meet the exit conditions. The execution of the target safe exit rule includes: If the current usage state of the camera device is waiting to take a picture or waiting to record a video, cancel the current usage state of the camera device. If the current usage state of the camera device is photo verification state or video verification state, the current usage state of the camera device is completed; If the current usage state of the camera device is the photo-taking state, the current usage state of the camera device is completed, and the remaining usage states of the camera device are executed in sequence until the photo-taking verification state of the camera device is completed. If the current usage state of the camera device is recording, the current usage state of the camera device is executed, and then the remaining usage states of the camera device are executed in sequence, until the recording verification state of the camera device is executed.

9. The method according to claim 2, characterized in that, The current usage status of each module in the self-service terminal is determined based on the currently executed command set; Determine whether the application meets the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, including: If the current set of executed commands includes commands to turn indicator lights on or off, and if the current business scenario is an indicator light prompt business scenario, and the current usage status of the indicator lights in the self-service terminal is either the indicator light on state or the indicator light off state, then it is determined that the application does not meet the exit conditions. The execution of the target safe exit rule includes: If the current usage state of the indicator light is "indicator light off", then complete the execution of the current usage state of the indicator light; When the current usage state of the indicator light is the on indicator light state, the current usage state of the indicator light is completed, and the remaining usage states of the indicator light are executed in sequence, until the off indicator light state is executed.

10. The method according to claim 2, characterized in that, The current usage status of each module in the self-service terminal is determined based on the currently executed command set; Determine whether the application meets the exit conditions based on the current business scenario and the current usage status of each module in the self-service terminal, including: If the current set of executed commands includes the command to open / close the cash gate, and if the current business scenario is a cash gate notification business scenario, and the current usage status of the cash gate in the self-service terminal is either open or closed, then it is determined that the application does not meet the exit conditions. The execution of the target safe exit rule includes: If the current usage state of the banknote door is the closed banknote door state, the current usage state of the banknote door is completed; If the current usage state of the cash gate is "open" and the current user is not the current transaction user, then the current usage state of the cash gate is cancelled. If the current usage state of the cash gate is "open", the current user is the current transaction user, and the temporary storage module in the self-service terminal has no cash stored, then the current usage state of the cash gate is cancelled. If the current usage state of the cash gate is the open cash gate state, and the open cash gate state is the deposit open cash gate state, and the current user is the current transaction user, and the temporary storage module in the self-service terminal has stored cash, and the cash stored in the temporary storage module has not been credited to the account, then the current usage state of the cash gate is completed, and the remaining usage states of the cash gate are completed in sequence, until the closed cash gate state is completed. If the current usage state of the cash gate is the cash gate open state, and the cash gate open state is the deposit open cash gate state, and the current user is the current transaction user, and the temporary storage module in the self-service terminal has stored banknotes, and the banknotes stored in the temporary storage module have been credited to the account, then the current usage state of the cash gate is cancelled. If the current usage state of the cash gate is the cash gate open state, and the cash gate is the cash withdrawal open state, and the current user is the current transaction user, and the temporary storage module in the self-service terminal has stored banknotes, and the banknotes stored in the temporary storage module have not been credited to the account, then the current usage state of the cash gate is cancelled. If the current usage state of the cash gate is "open cash gate", and the cash gate is in the withdrawal opening state, and the current user is the current transaction user, and the temporary storage module in the self-service terminal has stored banknotes, and the banknotes stored in the temporary storage module have been credited to the account, then the current usage state of the cash gate is completed, and the remaining usage states of the cash gate are completed sequentially, until the cash gate is closed.

Images