A shared keypad refueling machine control method based on identity recognition

Abstract

This invention discloses a shared keyboard fuel dispenser control method based on identity recognition, specifically relating to the field of fuel dispenser control technology. It involves collecting user authentication information, analyzing and generating a user identity identifier, and combining this with the user's real-time operational behavior on the shared keyboard to identify the keyboard's operating mode. Based on the user identity identifier and keyboard mode identifier, it performs user permission level matching and keyboard mode security rule analysis to generate user permission level data and mode security rule data. Based on the user permission level data and mode rule data, it determines whether there is a risk of permission inheritance errors between the user identity and the keyboard mode. If a permission inheritance error risk exists, a keyboard state lock command is generated, resetting the shared keyboard to its initial standby state. Multiple fuel dispenser settings can be configured using the reset shared keyboard, enabling one keyboard to operate multiple fuel dispenser points, thus improving the security, reliability, and convenience of the fuel dispenser's human-machine interaction.

Description

Technical Field

[0001] This invention relates to the field of fuel dispenser control technology, and more specifically, to a shared keyboard fuel dispenser control method based on identity recognition. Background Technology

[0002] Modern gas stations generally use shared keyboards for setting equipment parameters and controlling fuel quality, while also introducing identity recognition to manage user permissions.

[0003] However, because shared keyboard devices need to support continuous and rapid operations by multiple users, especially during peak hours at gas stations when users frequently rotate, current identity recognition methods struggle to quickly and accurately bind user identity information to the real-time operation status of the shared keyboard. This easily leads to the previous user's operation permission information not being cleared in time and being incorrectly inherited by the next user, causing user permission confusion. For single-sided multi-point gas pumps, the panel is bulky, manufacturing costs are high, and the human-machine interface is poor. Summary of the Invention

[0004] In order to overcome the above-mentioned defects of the prior art, embodiments of the present invention provide a shared keyboard refueling machine control method based on identity recognition to solve the problems mentioned in the background art.

[0005] To achieve the above objectives, the present invention provides the following technical solution:

[0006] S1: Collect the authentication information of the user currently using the shared keyboard, analyze the user's identity feature data, and output the user's identity identifier;

[0007] S2: Collect current keyboard operation status data based on the real-time operation behavior of users on the shared keyboard, identify and determine the current mode of the keyboard, and output the current keyboard mode identifier;

[0008] S3: Based on the user identity identifier and the current keyboard mode identifier, perform user permission level matching and keyboard mode security rule analysis respectively, and output user permission level data and mode security rule data;

[0009] S4: Based on user permission level data and mode security rule data, assess whether the user identity identifier and the current keyboard mode identifier are accurately matched, and determine whether there is a risk of permission inheritance error.

[0010] S5: When there is a risk of permission inheritance error, generate a keyboard state lock command;

[0011] S6: Based on the keyboard state lock command, clear the session state of the previous user of the shared keyboard and reset the shared keyboard to the initial standby state;

[0012] S7: Configure settings for multiple gas stations using the reset shared keyboard.

[0013] In a preferred embodiment, S1 specifically refers to:

[0014] The identity information collection device installed on the shared keyboard operation panel collects the identity verification information of the user currently using the shared keyboard to operate the fuel dispenser.

[0015] The collected user authentication information is preprocessed with identity feature data and compared with standard identity feature templates in the pre-stored identity feature database to generate a user identity identifier corresponding to the current user's identity.

[0016] In a preferred embodiment, S2 specifically refers to:

[0017] Collect function key input events triggered by the current user on the shared keyboard, and parse the key code corresponding to each key input event;

[0018] Match the key codes with a predefined function module mapping table to identify the function module corresponding to the key input event;

[0019] The current mode type of the keyboard is determined by performing mode switching on the continuous key input event sequence using a state machine model.

[0020] Output a keyboard mode identifier that indicates the mode type.

[0021] In a preferred embodiment, S3 specifically refers to:

[0022] Access the pre-established user permission level mapping table, retrieve the permission level information corresponding to the user's identity, extract the range of functional modules that the user is allowed to access, the types of keyboard modes that can be operated, and the corresponding operation priorities, and generate user permission level data.

[0023] Based on the keyboard mode identifier, access the preset keyboard mode security rule parameter set, extract the access control rules, operation step constraints and session binding requirements corresponding to the current keyboard mode type, and generate the mode security rule data for the current keyboard mode.

[0024] In a preferred embodiment, S4 specifically refers to:

[0025] Compare user permission level data with pattern security rule data;

[0026] Determine whether the scope of allowed functional modules and operable keyboard modes in the user permission level data cover the scope of functional modules and keyboard modes corresponding to the access control rules specified in the current keyboard mode mode security rule data;

[0027] Determine whether the operation priority corresponding to the user permission level data meets the operation step constraints and session binding requirements specified in the mode security rule data of the current keyboard mode;

[0028] Based on the comprehensive judgment results, determine whether there is a risk of permission inheritance error between the user identity identifier and the keyboard mode identifier.

[0029] In a preferred embodiment, S5 specifically refers to:

[0030] When there is a risk of permission inheritance error between the user identity identifier and the keyboard mode identifier, the keyboard state locking rule is invoked according to the risk level corresponding to the permission inheritance error risk.

[0031] Generate a keyboard state lock command based on the immediate lock trigger conditions and keyboard state lock actions defined in the keyboard state lock rules;

[0032] The keyboard control unit executes a function module disable operation based on the received keyboard state lock command, locks all operation functions of the shared keyboard in the current mode, and prohibits the current user's operation input.

[0033] In a preferred embodiment, S6 specifically refers to:

[0034] After the keyboard control unit performs the function module disable operation, it calls the shared keyboard session state clearing command;

[0035] According to the shared keyboard session state clearing command, clear the previous user's authentication information, user permission level data, keyboard mode identification data, and unfinished operation input data of the user in the current keyboard mode stored in the keyboard control unit;

[0036] The predefined initial standby state recovery procedure is invoked to reset the shared keyboard's functional modules activation state, mode selection state, and user identity binding state to the initial standby state of inactive, unselected, and unbound, thus completing the shared keyboard state reset.

[0037] In a preferred embodiment, S7 specifically refers to:

[0038] The reset shared keyboard allows for the preset of fuel quantity and amount at multiple gas stations;

[0039] The reset shared keyboard can be used to stop transactions at multiple gas stations during the refueling process;

[0040] The reset shared keyboard can be used to round up the amount of fuel or the amount of money at multiple refueling points during the refueling process.

[0041] The technical effects and advantages of the shared keyboard refueling machine control method based on identity recognition of the present invention are as follows:

[0042] By collecting and accurately identifying the identity verification information of users currently using the shared keyboard in real time, misidentification is avoided; by continuously monitoring and recognizing the keyboard operation status, the system dynamically monitors standby, setting, or refueling modes; by matching user identity identifiers and keyboard mode identifiers with permission levels and analyzing security rules, a foundation for permission verification is established; based on user permission level data and mode security rule data, potential permission inheritance errors can be accurately identified; when a permission inheritance error risk exists, a keyboard status lock command is automatically generated and issued to immediately block unauthorized operations; by clearing the session state of the previous user on the shared keyboard and resetting the shared keyboard to its initial standby state, permission residues are completely eliminated, achieving dynamic and accurate binding and real-time verification of identity verification and keyboard status. This effectively prevents permission confusion and misoperation caused by rapid switching of multiple users during peak periods, and allows for setting operations at multiple refueling points using the reset shared keyboard, significantly improving the security, reliability, and user operation efficiency of the refueling machine control system. Attached Figure Description

[0043] Figure 1 This is a schematic diagram of a shared keyboard refueling machine control method based on identity recognition according to the present invention. Detailed Implementation

[0044] 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 of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0045] Example

[0046] Figure 1 The present invention provides a shared keypad refueling machine control method based on identity recognition, which includes the following steps:

[0047] S1: Collect the authentication information of the user currently using the shared keyboard, analyze the user's identity feature data, and output the user's identity identifier;

[0048] S2: Collect current keyboard operation status data based on the real-time operation behavior of users on the shared keyboard, identify and determine the current mode of the keyboard, and output the current keyboard mode identifier;

[0049] S3: Based on the user identity identifier and the current keyboard mode identifier, perform user permission level matching and keyboard mode security rule analysis respectively, and output user permission level data and mode security rule data;

[0050] S4: Based on user permission level data and mode security rule data, assess whether the user identity identifier and the current keyboard mode identifier are accurately matched, and determine whether there is a risk of permission inheritance error.

[0051] S5: When there is a risk of permission inheritance error, generate a keyboard state lock command;

[0052] S6: Based on the keyboard state lock command, clear the session state of the previous user of the shared keyboard and reset the shared keyboard to the initial standby state;

[0053] S7: Configure settings for multiple gas stations using the reset shared keyboard.

[0054] S1: Collect the authentication information of the user currently using the shared keyboard, analyze the user's identity feature data, and output the user's identity identifier, including:

[0055] The identity information collection device installed on the shared keyboard operation panel collects the identity verification information of the user currently using the shared keyboard to operate the fuel dispenser.

[0056] A shared keyboard control panel refers to the control panel installed on a fuel dispenser. It has multiple function key areas for users to input commands and select functions, and also has physical space to install additional information collection devices. To achieve user identification, an identity information collection device, including but not limited to fingerprint recognition devices, facial image acquisition devices, or IC card information reading devices, is installed on the surface of the shared keyboard control panel or at an appropriate location. For example, when using a fingerprint recognition device as an identity information collection device, the device can be placed in the middle area of ​​the shared keyboard operation panel or in an area that the user habitually uses. Before using the shared keyboard to refuel, the user places their finger on the surface of the fingerprint recognition device, which scans the user's fingerprint information in real time using an optical or capacitive sensor to generate raw fingerprint image data reflecting the user's identity characteristics. When using a facial image collection device, it is placed at the top or edge of the shared keyboard operation panel and uses a camera module to collect the current user's facial image information in real time, generating raw image data that represents the current user's facial features. When using an IC card information reading device, a dedicated card slot or IC card sensing area can be provided. The user inserts or holds the IC card to achieve contactless or contact reading of the IC card information, collecting the raw identity characteristic data information stored in the user's IC card in real time. The setup of each of these identity information collection devices ensures that the user's identity information is collected before using the shared keyboard to operate the refueling machine, achieving reliable acquisition of the current user's identity verification information.

[0057] The collected user authentication information is preprocessed with identity feature data and compared with standard identity feature templates in the pre-stored identity feature database to generate a user identity identifier corresponding to the current user's identity.

[0058] The preprocessing process selects different data processing methods based on different types of raw data. For example, for the collected raw fingerprint image data, fingerprint image feature extraction is used to denoise, enhance the image, and extract fingerprint feature points (such as fingerprint ridge endpoints and bifurcation points) to obtain a feature fingerprint dataset reflecting the current user's identity. For the raw face image data, face detection is used to locate the user's face, and face image standardization, facial key point localization, and facial feature extraction are performed to obtain facial feature vector data reflecting the user's identity. For IC card information data, the user identity feature encoding information recorded in the IC card is extracted, and the user identity feature encoding information is format converted, data verified, and feature information extracted to form IC card feature data that can be used for identity recognition. The identity verification information collected in the above different ways is preprocessed accordingly to form standardized identity feature data, which can be compared with the standard identity feature templates stored in the identity feature database.

[0059] To achieve user identification, a standard identity feature database is pre-established, storing all valid user identity feature data. This database stores standard identity feature template data for each valid user in a structured manner, including standard fingerprint feature templates, standard facial feature templates, and standard IC card information templates. Each template corresponds to a unique user identifier, representing the user's identity, such as a user ID or user access number. The pre-processed current user identity feature data is compared with each standard identity feature template stored in the database. For example, for fingerprint feature data comparison, a fingerprint feature matching algorithm is used to calculate the similarity between the spatial location of fingerprint feature points and the fingerprint ridge structure features. For facial feature data comparison, a facial feature similarity calculation method is used to determine the degree of matching between the current user's facial feature data and the standard template. For IC card feature data comparison, a matching method using encoded information is used. When the degree of matching between the current user's identity feature data and a certain standard identity feature template exceeds a preset threshold, it is determined that the current user and the user corresponding to the standard template are the same user, thus identifying the user currently using the shared keyboard to operate the refueling machine.

[0060] Based on the comparison and matching results of identity feature data, a user identity identifier corresponding to the current user identity is generated, specifically a user number or a user permission identifier. This identifier is used to perform matching analysis and control of user permission level and keyboard pattern in shared keyboard permission verification and pattern matching, so as to avoid the risk of permission inheritance errors caused by inaccurate identity binding and to achieve the safe and reliable operation of shared keyboard.

[0061] S2: Collect current keyboard operation status data based on real-time user operation behavior on the shared keyboard, identify and determine the current keyboard mode, and output the current keyboard mode identifier, including:

[0062] Collect function key input events triggered by the current user on the shared keyboard, and parse the key code corresponding to each key input event;

[0063] When using the shared keyboard fuel dispenser, users first need to input corresponding operation commands through the shared keyboard control panel. These commands are triggered by function keys. The shared keyboard control panel includes several function key areas, each with a specific function. For example, the numeric input area is used to input the amount of fuel or the amount, the confirmation key confirms the user's input, and the mode selection key switches between standby mode, fueling mode, and settings mode. Each time a user manually presses any function key, a corresponding function key input event is triggered. To capture each user input action, the shared keyboard is equipped with an input signal acquisition unit for capturing key events. This unit can generate electrical signals through the closure of mechanical key contacts or through capacitive touch sensing. The input signal acquisition unit captures and records each function key input event triggered by the user in real time and transmits the captured event information as a digital signal to the key event parsing module within the shared keyboard. For example, when a user wants to input a fuel amount of 100 yuan, they press the numeric keys 1, 0, 0, and then the confirmation key in sequence. Each press generates a separate function key input event. The key event parsing module filters, debouncing, and standardizes the raw electrical signals of each function key input event to ensure signal stability and reliability. The processed key input event data is then parsed to determine the corresponding function key code. The function key code is a digital encoding that accurately represents the specific key value pressed by the user. For example, the key code for the number 1 key might be represented as hexadecimal 0x31 or other predefined encoding values, while the key code for the confirmation key might be represented as 0x0D or other specific encoding values. Based on a predefined mapping relationship, key code parsing converts each key event into digital key code data, forming a key event sequence data.

[0064] Match the key codes with a predefined function module mapping table to identify the function module corresponding to the key input event;

[0065] The function module mapping table is a structured data table pre-stored within the shared keyboard. It defines the correspondence between each key code and a specific function module. Function modules include, but are not limited to, standby, refueling, parameter setting, payment, and special maintenance modules. The function module mapping table can be stored using standard lookup tables, array structures, or other data structures to ensure that the corresponding function module information can be found after receiving a user's key input code. For example, when the user triggers a key code of 0x31, the function module mapping table can determine that the code corresponds to a numeric input function module, falling under the category of refueling quantity or monetary value input. When the user triggers a key code of 0x0D, the function module mapping table matches it to the confirmation function module, used to confirm the completion of the user's input or to proceed to the next function. When the user triggers the mode selection key, the function module mapping table will determine that the function module corresponding to the key input event is the mode selection function module, clarifying that the user currently wants to switch the shared keyboard to another operating mode. Through this matching mechanism, each key input event can be associated with a predefined specific function module.

[0066] The current mode type of the keyboard is determined by performing mode switching on the continuous key input event sequence using a state machine model.

[0067] A state machine model is a predefined mode transition method used to describe the mode type transition rules of a shared keyboard. A shared keyboard may exist in several different mode types during use, including standby mode, refueling mode, and settings mode, each with a unique mode identifier. The state machine model describes how the shared keyboard transitions between different modes based on a continuous sequence of key input events by the user. For example, when a user triggers a key input event corresponding to the mode selection function module in standby mode, the shared keyboard transitions from standby mode to refueling mode according to the state machine model. When a user continuously inputs a special key combination in refueling mode, such as an administrator-specific command, the shared keyboard transitions from refueling mode to settings mode according to the state machine model. By inputting the result of function module matching into the state machine model, the current mode type of the shared keyboard can be identified in real time and accurately, ensuring that each user operation complies with the security rules and permission level requirements of the current mode type.

[0068] Output a keyboard mode identifier that indicates the mode type;

[0069] After completing the mode transition processing of the state machine model, the shared keyboard outputs a keyboard mode identifier that indicates the specific mode type of the shared keyboard. This identifier is expressed in the form of numeric codes, letter identifiers, or strings, representing the current mode type of the shared keyboard. For example, the number 01 represents standby mode, the number 02 represents refueling mode, and the number 03 represents setting mode.

[0070] S3: Based on the user's identity identifier and the current keyboard pattern identifier, perform user permission level matching and keyboard pattern security rule analysis, and output user permission level data and pattern security rule data, including:

[0071] Access the pre-established user permission level mapping table, retrieve the permission level information corresponding to the user's identity, extract the range of functional modules that the user is allowed to access, the types of keyboard modes that can be operated, and the corresponding operation priorities, and generate user permission level data.

[0072] The user permission level mapping table is a structured data table pre-established and stored within the shared keyboard fuel dispenser control system. It defines the correspondence between the user identifiers and user permission level information of all legitimate users within the shared keyboard system. Specifically, the table associates each user's identifier with their permission level information based on their responsibilities and security requirements. For example, user ID 001 is defined as having administrator permission level, and user ID 002 is defined as having ordinary user permission level. Each permission level includes data items such as the range of functional modules the user is allowed to access, the types of keyboard modes they can operate, and the corresponding operation priority. The scope of functional modules refers to the set of predefined functional modules within the shared keyboard that users can legally access and operate. For example, the scope of functional modules corresponding to the administrator privilege level can cover all functional modules such as refueling start, parameter setting, payment confirmation, and maintenance, while the scope of functional modules corresponding to the ordinary user privilege level only includes basic functional modules such as numeric input, refueling start, and payment confirmation. The operable keyboard mode type refers to the mode type of the shared keyboard that users are allowed to access and perform operations in. For example, users with administrator privilege level are allowed to operate in standby mode, refueling mode, and settings mode, while users with ordinary user privilege level are only allowed to operate in standby mode and refueling mode, and are not allowed to operate in settings mode. The corresponding operation priority refers to the priority level that users have when performing operations on the shared keyboard. The operation priority determines the order or permission in which users can perform operations. For example, users with administrator privilege level have higher priority than users with ordinary user privilege level.

[0073] For example, when a user's identity is confirmed as user number 002 after authentication, the shared keyboard fuel dispenser control system accesses the user permission level mapping table. Based on user identity 002, it retrieves and extracts the corresponding permission level information to obtain the ordinary user permission level data. The extracted permitted function modules are identified as the numeric input module, the fuel initiation module, and the payment confirmation module. The operable keyboard modes are identified as standby mode and fuel refueling mode. The corresponding operation priorities are identified as the ordinary user priority level. After being aggregated and organized, the extracted data generates user permission level data, representing the permissions granted to the current user within the shared keyboard system.

[0074] Based on the keyboard mode identifier, access the preset keyboard mode security rule parameter set, extract the access control rules, operation step constraints and session binding requirements corresponding to the current keyboard mode type, and generate mode security rule data for the current keyboard mode.

[0075] The keyboard mode safety rule parameter set is a predefined and stored data set within the shared keyboard refueling machine control system. It defines the safety management requirements and access control rules corresponding to each type of shared keyboard operation mode.

[0076] Based on the identified keyboard mode identifiers, the shared keyboard system further accesses the keyboard mode security rule parameter set to extract the access control rules, operation step constraints, and session binding requirements corresponding to the current keyboard mode type. The access control rules define the permission conditions and restrictions that must be met to enter the current keyboard mode. For example, for the refueling mode, the access control rules stipulate that only administrators and ordinary users are allowed to enter. For the settings mode, the access control rules stipulate that only users with administrator privileges are allowed to enter, and ordinary users are not allowed to enter. Operation step constraints define the specific order and conditions for performing operations under the current mode type. For example, in the refueling mode, users must press the confirmation key after entering the refueling amount before the refueling start operation is allowed; if the operation step constraints are not followed, refueling is not allowed. Session binding requirements specify the user identity status that needs to be bound for operations under the current mode type to avoid confusion between different user operation statuses. For example, in the settings mode, the session binding requirements stipulate that parameter setting operations can only be allowed after the administrator user identity has been explicitly verified and bound.

[0077] For example, when the current mode identifier of the shared keyboard is determined to be 02, indicating refueling mode, the shared keyboard system internally accesses the keyboard mode security rule parameter set. It extracts the access control rules defined for refueling mode, which allow both administrator and regular user privilege levels to access the system. It also extracts the operation step constraints, requiring users to input the fuel quantity or amount and confirm before starting the fuel dispenser. Finally, it extracts the session binding requirements, ensuring that the current user's identity is verified and bound by the system. This specific data is then aggregated to form the current keyboard mode security rule data, reflecting the security rules and requirements of the shared keyboard under the current mode type.

[0078] S4: Based on user permission level data and mode security rule data, assess whether there is an accurate match between the user identity identifier and the current keyboard mode identifier, and determine whether there is a risk of permission inheritance errors, including:

[0079] Compare user permission level data with pattern security rule data;

[0080] Determine whether the scope of allowed functional modules and operable keyboard modes in the user permission level data cover the scope of functional modules and keyboard modes corresponding to the access control rules specified in the current keyboard mode mode security rule data;

[0081] Determine whether the operation priority corresponding to the user permission level data meets the operation step constraints and session binding requirements specified in the mode security rule data of the current keyboard mode;

[0082] Based on the comprehensive judgment results, determine whether there is a risk of permission inheritance error between the user identity identifier and the keyboard mode identifier.

[0083] This involves a step-by-step comparison between user permission level data and pattern security rule data. Specifically, it compares the range of allowed functional modules in the user permission level data with the range of functional modules corresponding to the access control rules specified in the pattern security rule data. It also compares the allowed keyboard mode types with the keyboard mode types specified in the pattern security rule data, and compares the operation priority with the operation step constraints and session binding requirements in the pattern security rule data. For example, if a user with ordinary user permission level is granted access to the refueling mode, and the user's current mode is identified as refueling mode, the comparison can determine the matching relationship between the user's permission level data and the pattern security rule data. This ensures that the user's actual permissions meet the security rules set for the shared keyboard mode, preventing security risks caused by permission mismatches.

[0084] After comparing the user permission level data with the mode security rule data, it is determined whether the scope of allowed functional modules and the allowed keyboard mode types contained in the current user's permission level data fully cover the scope of functional modules and mode types corresponding to the access control rules specified in the mode security rule data for the current mode. For example, if the shared keyboard's current mode is identified as "refueling mode," and the mode security rule data specifies that the permission levels allowed to enter and operate in refueling mode are administrator and ordinary user permission levels, and the current user's permission level data shows an administrator permission level, then the result indicates that the scope of functional modules and keyboard mode types in the user permission level data fully cover all functional modules and mode types corresponding to the access control rules specified in the mode security rule data. The user permission level meets the mode security requirements, and it is determined that there is no risk of permission inheritance error. If the current user's permission level data is an ordinary user permission level, and the shared keyboard's current mode is identified as "settings mode," while the mode security rule data specifies that only administrator-level users are allowed to enter settings mode, then the result indicates that the ordinary user permission level data does not cover the scope of functional modules and mode types corresponding to settings mode. Therefore, it is determined that there is a risk of permission inheritance error between the user permission level data and the mode security rule data. The above precise item-by-item judgment process makes the permission verification process for shared keyboards more accurate and secure, and can effectively avoid potential security risks caused by permission mismatch.

[0085] The operation priority in the user permission level data is assessed to determine whether it meets the constraints of the operation steps and session binding requirements specified in the mode security rules data. This ensures that the shared keyboard operation process follows the established security sequence and binding rules, preventing unauthorized or unauthorized operations due to insufficient operation priority in the user permission level. For example, in refueling mode, the mode security rules data stipulate that after a user enters numerical information, they must confirm the input with the confirmation key before initiating the refueling operation. Simultaneously, session binding requires successful user authentication and binding. If the operation priority in the user permission level data is at the normal level, but the operation process lacks identity binding or does not follow the confirmation steps specified in the mode security rules data, then the operation priority does not meet the requirements of the mode security rules data for the current keyboard mode, indicating a risk of permission inheritance error. Conversely, if the user permission level data is at the administrator priority level, the user identity is bound, and confirmation is performed according to the operation steps, then the operation priority meets all the requirements of the mode security rules data, and no risk of permission inheritance error is identified.

[0086] The overall judgment result is generated by combining the results of the two judgments: the matching of functional module scope and keyboard mode type, and the satisfaction of operation priority, operation step constraints, and session binding requirements. Based on the overall judgment result, it is determined whether there is a risk of permission inheritance error between the current user identity and the current keyboard mode identity. For example, if either judgment condition is not met—that is, the functional module scope is not covered or the operation priority is not met—a risk of permission inheritance error is determined to exist; if both judgment conditions are met, a risk of permission inheritance error is determined not to exist.

[0087] S5: When there is a risk of permission inheritance error, generate keyboard state lock instructions, including:

[0088] When there is a risk of permission inheritance error between the user identity identifier and the keyboard mode identifier, the keyboard state locking rule is invoked according to the risk level corresponding to the permission inheritance error risk.

[0089] For identified permission inheritance error risks, the shared keyboard fuel dispenser control system predefines permission inheritance error risk level classifications, with different handling measures corresponding to different risk levels. For example, risk levels can be divided into three levels: high, medium, and low. High risk indicates that the user is attempting sensitive or critical operations (such as setting parameters or modifying fuel price information); medium risk indicates that the user is attempting routine but unauthorized refueling operations; and low risk indicates that the user's current operation may only involve simple information viewing but lacks sufficient permissions. Based on the specific risk level, the shared keyboard system invokes the corresponding keyboard state locking rule. For example, when a high-level permission inheritance error risk occurs, a strict and immediately effective emergency locking rule is invoked to ensure that all current input operations on the shared keyboard are immediately stopped; when a medium-level permission inheritance error risk occurs, a general state locking rule is invoked, locking only the input function of the currently active mode; and when a low-level permission inheritance error risk occurs, a mild, suggestive locking rule is invoked, temporarily disabling only a few unauthorized function modules without affecting the continued use of the overall keyboard input function.

[0090] Generate a keyboard state lock command based on the immediate lock trigger conditions and keyboard state lock actions defined in the keyboard state lock rules;

[0091] The keyboard status lock rules are a predefined set of data for the shared keyboard fuel dispenser control system, specifying the immediate lock trigger conditions and specific lock actions. The immediate lock trigger conditions indicate under what circumstances a keyboard status lock should be implemented immediately. For example, when it is detected that a user's current permission level is insufficient but they attempt to execute a sensitive or important operation command, the immediate lock trigger condition is met. For instance, if a user with ordinary user privileges attempts to access a settings mode accessible only to administrators via the shared keyboard and modify parameters, the immediate lock trigger condition is triggered.

[0092] Keyboard state lock actions specify the locking actions to be taken after an immediate lock condition is triggered. These actions include specifying which functional modules to disable, the degree of lock, and the duration of the lock. For example, when a high-level permission inheritance error risk occurs, the lock action disables all functional modules in the current shared keyboard mode, completely prohibiting any user input commands. When a high-level permission inheritance error risk occurs, the lock action only disables specific functional modules involved in the risky operation. When a high-level permission inheritance error risk occurs, the lock action temporarily locks the current input action and displays a prompt to the user.

[0093] Based on the instant lock trigger conditions and keyboard status lock actions defined above, the shared keyboard system automatically generates keyboard status lock instructions. These instructions include the scope of locked functional modules, the method of executing the lock action, the duration of the lock action, and the post-lock status management method. For example, if the shared keyboard detects that a user with ordinary user privileges is attempting to enter settings mode to perform unauthorized parameter modification operations, it automatically generates a keyboard status lock instruction to lock all functional modules in the current mode based on the instant lock trigger conditions, prohibiting all user operations in the current mode.

[0094] The keyboard control unit executes a function module disable operation based on the received keyboard state lock command, locks all operation functions of the shared keyboard in the current mode, and prohibits the current user's operation input;

[0095] The keyboard control unit is a pre-installed hardware and software integrated control module within the shared keyboard fuel dispenser. It receives and executes various control commands generated within the shared keyboard system in real time. Once a keyboard status lock command is generated, it is immediately transmitted to the keyboard control unit via the data transmission channel. Upon receiving the command, the control unit executes the specific function module disabling operation according to the instructions. Specifically, the disabling operation completely closes or locks the software input channel corresponding to each function key on the shared keyboard panel, preventing the user from triggering any input events, thereby ensuring the overall safety of the shared keyboard fuel dispenser.

[0096] S6: Based on the keyboard state lock command, clear the session state of the previous user of the shared keyboard and reset the shared keyboard to the initial standby state, including:

[0097] After the keyboard control unit performs the function module disable operation, it calls the shared keyboard session state clearing command;

[0098] After the function module is disabled, the keyboard control unit automatically triggers a shared keyboard session state clearing command. This command is an electronic control instruction used to clear the current keyboard state data. The execution of this command is automatically initiated by the keyboard control unit, which actively sends a clearing operation request to the internal data storage unit or state memory unit via its built-in program instruction processing module.

[0099] For example, when a user with ordinary user privileges attempts to enter the settings mode and perform unauthorized sensitive parameter settings, the shared keyboard system, after comparison and judgment, identifies a risk of permission inheritance error and generates and sends a keyboard state lock command. After the keyboard control unit executes the keyboard state lock command, all function modules in the settings mode are disabled, preventing unauthorized operation. To completely avoid the recurrence of permission inheritance errors caused by residual state data from previous or current users on the shared keyboard, the keyboard control unit proactively invokes the shared keyboard session state clearing command. This ensures that the keyboard control unit can immediately clear all remaining session state data on the shared keyboard, cutting off any possibility of subsequent users inheriting the permissions or mode state of the previous user, and ensuring the safe and stable operation of the shared keyboard fuel dispenser control system.

[0100] According to the shared keyboard session state clearing command, clear the previous user's authentication information, user permission level data, keyboard mode identification data, and unfinished operation input data of the user in the current keyboard mode stored in the keyboard control unit;

[0101] After the shared keyboard session state clearing command is invoked by the keyboard control unit, the keyboard control unit immediately executes the clearing operation defined by the shared keyboard session state clearing command. The clearing operation is performed internally by the keyboard control unit, completed by its internal data storage unit or memory management module. The data storage unit of the keyboard control unit is a defined non-volatile or volatile electronic memory module, such as static random access memory or dynamic random access memory, used to store various real-time status data generated during the current use of the shared keyboard.

[0102] The clearing operation involves deleting the previous user's authentication information, including but not limited to fingerprint data, facial data, or IC card encoding information. This information is temporarily stored in the keyboard control unit's data storage unit for real-time authorization verification when the user operates the shared keyboard. When the shared keyboard session state clearing command is executed, the keyboard control unit's data management module clears this information, completely deleting the previous user's identity information from the storage unit and preventing the current or next user from using or inheriting this identity data.

[0103] After the keyboard control unit executes the clear command, it deletes the user permission level data, thereby preventing this permission level data from being inherited or used by the current or subsequent users.

[0104] Keyboard mode identifier data is also stored in the keyboard control unit for real-time mode determination. The clear operation deletes the mode identifier data, completely clearing the mode state of the shared keyboard.

[0105] In the current keyboard mode, incomplete user input data refers to the set of instructions entered by the user in the current shared keyboard mode but not yet submitted or executed. For example, if a user enters the amount of fuel in refueling mode but has not yet pressed the confirmation key, this incomplete input data will be completely deleted. Through the above data clearing operation, the keyboard control unit ensures that all status data is completely cleared, leaving no residual status data.

[0106] Call the predefined initial standby state recovery procedure to reset the shared keyboard's functional module activation state, mode selection state, and user identity binding state to the initial standby state of inactive, unselected, and unbound, thus completing the shared keyboard's state reset;

[0107] After all data is cleared, the keyboard control unit actively invokes the initial standby state recovery procedure. This procedure resets the shared keyboard's functional module states, mode selection states, and user identity binding states to their initial states. Functional module activation states, mode selection states, and user identity binding states are uniformly set to the initial standby states of inactive, unselected, and unbound, ensuring the shared keyboard is restored to its initial power-on state, completely resetting the shared keyboard and preventing the risk of permission inheritance errors from recurring.

[0108] S7: Multiple refueling points can be configured using the reset shared keyboard, including:

[0109] The reset shared keyboard allows for the preset of fuel quantity and amount at multiple gas stations;

[0110] The reset shared keyboard can be used to stop transactions at multiple gas stations during the refueling process;

[0111] The reset shared keyboard can be used to round up the amount of fuel or the amount of money at multiple refueling points during the refueling process.

[0112] Specifically, when a fuel dispenser has multiple refueling points that can refuel simultaneously on one side, only one shared keyboard control panel needs to be configured to operate any one of the refueling points on that side. The keyboard operations for each refueling point include:

[0113] 1) System configuration operation: It is mainly used during system installation and maintenance, including setting the operation configuration information of the fuel dispenser, including system identification settings, communication address, fuel point configuration, hydraulic control parameters, data security management specifications, system operation log management, etc.

[0114] 2) Refueling Transaction Setup: Before a refueling transaction begins, the customer needs to preset a refueling amount or price. The operator needs to send the information to the refueling point via keyboard. When the transaction ends, unless there is a fuel tank capacity limit or the refueling is manually stopped, the transaction amount will stop at the preset value.

[0115] 3) Operation during refueling: Customers may request rounding when the transaction is about to end, especially the amount. At this time, you may need to stop refueling via the keyboard.

[0116] 4) At gas stations with attendants, attendants must undergo authentication procedures when starting and stopping get off work. After their identity is confirmed, they can operate the system at legitimate refueling points via keyboard.

[0117] In the above operations, the operator's identity, legitimacy, and the actual working status of the refueling point to be operated on must meet predetermined rules. If the operator has ensured their identity and the legitimacy to operate, for example, if the operator's identity has been confirmed as a gas station employee, and the current status of the corresponding fuel dispenser or refueling point is a system setting, then this operation will be blocked. For example, if the operator is a gas station attendant and the current operation is a pre-set refueling operation, but the refueling point is not locked, then the pre-set refueling operation will also be blocked.

[0118] During operation, the keyboard system will automatically connect to the desired refueling point based on its operational status. For example, before a shift is scheduled, the shared keyboard will simultaneously point to all refueling points on that panel. Of course, the operator can cancel any connection. When it's time to leave work, the keyboard will point to all refueling points on that panel that match the current operator's role.

[0119] During the work period at the gas station after registration, the keyboard system counts the frequency of operations at each gas station. However, after all gas stations remain silent for 5-15 minutes, the shared keyboard will point to the gas station with the highest usage frequency.

[0120] The keyboard control unit is equipped with indicator lights. After employees start work at the designated refueling points, the indicator lights will show the refueling point pointed to by the keyboard. The indicator lights can be designed to be sorted by location, display the name of the refueling product at the location, or indicate the refueling point by color. The indicator lights can use color and display frequency to indicate the working status of the connected refueling point, such as refueling in progress, preset completed, and payment in progress. When a refueling point malfunctions, the indicator lights can also provide corresponding information.

[0121] After verifying the operator's identity, permissions, and legitimacy, and considering the refueling point's operational status, the keyboard control unit can change the connection between itself and the operable refueling point using a toggle key. An indicator light simultaneously displays the refueling point indicated by the keyboard.

[0122] The refueling point switching button integrates static discharge and fuel type confirmation functions. Static discharge is completed simultaneously with the switching to the refueling point; it also features voice prompts to remind the operator and records the operation in the transaction log, indicating secondary confirmation of fuel selection. This streamlines important operations and simplifies necessary ones, resulting in a more streamlined refueling experience.

[0123] The above formulas are all dimensionless calculations. The formulas are derived from software simulations based on a large amount of collected data to obtain the most recent real-world results. The preset parameters and thresholds in the formulas are set by those skilled in the art according to the actual situation.

[0124] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. The semiconductor medium can be a solid-state drive.

[0125] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0126] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and modules described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0127] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0128] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0129] In addition, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module.

[0130] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0131] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0132] In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A shared keyboard refueling machine control method based on identity recognition, characterized in that, Includes the following steps: S1: Collect the authentication information of the user currently using the shared keyboard, analyze the user's identity feature data, and output the user's identity identifier; S2: Based on the real-time operation behavior of users on the shared keyboard, collect the current keyboard operation status data, identify and determine the current keyboard mode, and output the current keyboard mode identifier, specifically: Collect function key input events triggered by the current user on the shared keyboard, and parse the key code corresponding to each key input event; Match the key codes with a predefined function module mapping table to identify the function module corresponding to the key input event; The current mode type of the keyboard is determined by performing mode switching on the continuous key input event sequence using a state machine model. Output a keyboard mode identifier that indicates the mode type; S3: Based on the user identity identifier and the current keyboard mode identifier, perform user permission level matching and keyboard mode security rule analysis respectively, and output user permission level data and mode security rule data; S4: Based on user permission level data and mode security rule data, assess whether the user identity identifier and the current keyboard mode identifier are accurately matched, and determine whether there is a risk of permission inheritance error. S5: When there is a risk of permission inheritance error, generate a keyboard state lock command; S6: Based on the keyboard state lock command, clear the session state of the previous user of the shared keyboard and reset the shared keyboard to the initial standby state; S7: Configure settings for multiple gas stations using the reset shared keyboard.

2. The shared keyboard refueling machine control method based on identity recognition according to claim 1, characterized in that, S1, specifically: The identity information collection device installed on the shared keyboard operation panel collects the identity verification information of the user currently using the shared keyboard to operate the fuel dispenser. The collected user authentication information is preprocessed with identity feature data and compared with standard identity feature templates in the pre-stored identity feature database to generate a user identity identifier corresponding to the current user's identity.

3. The shared keyboard refueling machine control method based on identity recognition according to claim 2, characterized in that, S3, specifically: Access the pre-established user permission level mapping table, retrieve the permission level information corresponding to the user's identity, extract the range of functional modules that the user is allowed to access, the types of keyboard modes that can be operated, and the corresponding operation priorities, and generate user permission level data. Based on the keyboard mode identifier, access the preset keyboard mode security rule parameter set, extract the access control rules, operation step constraints and session binding requirements corresponding to the current keyboard mode type, and generate the mode security rule data for the current keyboard mode.

4. The shared keyboard refueling machine control method based on identity recognition according to claim 3, characterized in that, S4, specifically: Compare user permission level data with pattern security rule data; Determine whether the scope of allowed functional modules and operable keyboard modes in the user permission level data cover the scope of functional modules and keyboard modes corresponding to the access control rules specified in the current keyboard mode mode security rule data; Determine whether the operation priority corresponding to the user permission level data meets the operation step constraints and session binding requirements specified in the mode security rule data of the current keyboard mode; Based on the comprehensive judgment results, determine whether there is a risk of permission inheritance error between the user identity identifier and the keyboard mode identifier.

5. The shared keyboard refueling machine control method based on identity recognition according to claim 4, characterized in that, S5, specifically: When there is a risk of permission inheritance error between the user identity identifier and the keyboard mode identifier, the keyboard state locking rule is invoked according to the risk level corresponding to the permission inheritance error risk. Generate a keyboard state lock command based on the immediate lock trigger conditions and keyboard state lock actions defined in the keyboard state lock rules; The keyboard control unit executes a function module disable operation based on the received keyboard state lock command, locks all operation functions of the shared keyboard in the current mode, and prohibits the current user's operation input.

6. The shared keyboard refueling machine control method based on identity recognition according to claim 5, characterized in that, S6, specifically: After the keyboard control unit performs the function module disable operation, it calls the shared keyboard session state clearing command; According to the shared keyboard session state clearing command, clear the previous user's authentication information, user permission level data, keyboard mode identification data, and unfinished operation input data of the user in the current keyboard mode stored in the keyboard control unit; The predefined initial standby state recovery procedure is invoked to reset the shared keyboard's functional modules activation state, mode selection state, and user identity binding state to the initial standby state of inactive, unselected, and unbound, thus completing the shared keyboard state reset.

7. The shared keyboard refueling machine control method based on identity recognition according to claim 6, characterized in that, S7, specifically: The reset shared keyboard allows for the preset of fuel quantity and amount at multiple gas stations; The reset shared keyboard can be used to stop transactions at multiple gas stations during the refueling process; The reset shared keyboard can be used to round up the amount of fuel or the amount of money at multiple refueling points during the refueling process.

Images