Method and system for managing input mode of mes system based on permission control, and storage medium

Abstract

This invention discloses a method, system, and storage medium for input method management in a MES system based on access control. The method includes: obtaining access levels in response to user login operations; configuring the input interface of input controls according to the access level when loading the business data input interface; monitoring input events and identifying external input device types, intercepting the event when the device type does not match the activated input interface; ensuring that data submission includes at least the device type; the server obtains the access level based on session information and verifies it against the device type; and rejecting requests if a user with ordinary access uses an uncontrolled input device. This invention achieves fine-grained access control over input device types through a two-layer protection of front-end interception and back-end verification, effectively preventing unauthorized input and ensuring the security, accuracy, and traceability of data entry in the MES system.

Description

Technical Field

[0001] This invention relates to the field of intelligent semiconductor manufacturing, specifically to a method, system, and storage medium for managing input methods in a MES system based on access control. Background Technology

[0002] As the core of the information technology industry, the semiconductor industry is characterized by highly precise, automated, and complex production processes. Semiconductor factories are typical ultra-precise, high-cleanliness, and strictly controlled manufacturing environments. Production equipment (such as lithography machines, ion implanters, and thin-film deposition equipment) is structurally precise and costly, and the production process is highly automated and collaborative. In the Semiconductor Manufacturing Execution System (MES), the accuracy of data entry directly affects product yield, process stability, and quality traceability. Any data entry error can lead to batch scrapping, equipment malfunction, or even significant economic losses.

[0003] Currently, input permission management in MES systems primarily focuses on menu access control or function start / stop control, lacking differentiated control over input methods. Specifically, some traditional MES systems restrict user operations simply by hiding buttons or graying out controls; however, disabling or hiding front-end controls cannot prevent back-end bypassing or API calls leading to data modification. Furthermore, while some systems have permission verification, the input source is unrestricted. The system only verifies whether the user has the right to perform the operation, without distinguishing whether the user inputs via a barcode scanner or a keyboard, making it possible for the input source identifier to be tampered with or forged, thus failing to guarantee the authenticity and traceability of the data.

[0004] Therefore, there is an urgent need for an input method management approach that can finely control input device types based on user permission levels and has dual protection capabilities of front-end interception and back-end verification. Summary of the Invention

[0005] To address the aforementioned issues, this application proposes a method for managing input methods in an MES system based on access control, comprising the following steps: Step S1: In response to the user's login operation on the MES system client, obtain the current user's permission level, which includes normal permissions and advanced permissions; Step S2: When loading the business data input interface, configure the input interface of the input control according to the permission level; If the permission level is normal, only the input interface of the controlled input device will be opened, and the input interface of the human interaction device will be prohibited. If the permission level is high-level, then the input interfaces of both human interaction devices and controlled input devices are opened simultaneously; Step S3: During the user's interaction with the interface, monitor input events for the input controls and identify the type of external input device corresponding to the input events; When the external input device type is not one of the device types supported by the currently active input interface, the input event is intercepted; Step S4: Submit all input event data to the MES system server. All input event data must include at least the external input device type. The MES system server obtains the permission level based on the current user's session information and verifies the obtained permission level against the type of external input device received. If the external input device type is not a controlled input device and the current user's permission level is normal, the service request will be rejected; if the corresponding user's permission level is advanced, the request will continue.

[0006] In one embodiment, in step S3: The identification of the external input device type corresponding to the input event includes: identifying the external input device type corresponding to the input event based on one or more of the following methods: input time interval, input event type, and external input device interface identifier; The method of identifying the type of external input device corresponding to the input event based on the time interval includes: detecting the time interval between character inputs, determining it as a controlled input device when the time interval between consecutive character inputs is less than a preset threshold, and determining it as a human interaction device when the time interval is greater than the threshold; Identifying the type of external input device corresponding to the input event based on the input event type includes: distinguishing between human-interactive devices and controlled input devices by listening to the original event types of the front-end browser or client, including keyboard keystroke events, paste events, input method combination events and hardware interruption input events; Identifying the type of external input device corresponding to the input event based on the external input device interface identifier includes: when the input data comes from a USB-HID device, serial port device, Bluetooth device or dedicated industrial interface, reading the corresponding device identifier or port identifier and marking it as a controlled input device.

[0007] In one embodiment, after intercepting the input event, an exception handling process is also triggered, the exception handling process including: Step S31: Generate an abnormal input prompt message and block the current input behavior; Step S32: Provide a temporary authorization application interface, allowing the current user to submit an abnormal input application request; the application request includes the operation account, business number, external input device type, application reason and timestamp; Step S33: Send the abnormal input request to the pre-configured approval user or approval role; Step S34: If the review is approved, a temporary authorization token is generated. The token contains user identity information, authorized external input device type, and valid time range. Step S35: During the token's validity period, the current user is allowed to perform authorized operations; after the token expires, the control state under the original permission level is automatically restored. Step S36: Record the exception handling process and approval results to the security audit log.

[0008] In one embodiment, disabling the input interface of the human interaction device in step S2 includes: disabling the input controls corresponding to the human interaction device, or hiding the input controls corresponding to the human interaction device.

[0009] In one embodiment, the controlled input device includes at least one of a barcode scanner, a fingerprint scanner, and an RFID reader / writer, and the human interaction device includes at least one of a keyboard, a mouse, and a touchscreen.

[0010] In one embodiment, step S4, when rejecting a service request, further includes: Record security audit logs, which at least include the operation account, timestamp, permission level, and type of external input device.

[0011] In one embodiment, obtaining the current user's permission level in step S1 includes: Call the unified permission management platform interface to obtain user permission information, including permission level, and store the permission information in the current session context and front-end global state.

[0012] This invention also proposes an input method management system for an MES system based on access control, used to implement the input method management method described above. The input method management system includes an MES system layer and a data layer. The MES system layer executes business logic and input control according to the user's corresponding input permissions, and the data layer is used to store system data. Specifically, the MES system layer includes: The user permission identification module is used to obtain the permission level identifier of the current user when the user logs in; The front-end permission control module is used to configure the input interface of the input control according to the permission level when loading the business data input interface; wherein, if the permission level is ordinary permission, only the input interface of the controlled input device is opened and the input interface of the human interaction device is prohibited; if the permission level is high permission, the input interfaces of both the human interaction device and the controlled input device are opened at the same time. The input event management module is used to monitor input events for input controls, identify the type of external input device corresponding to the input event, and intercept the input event when the type of external input device does not belong to the device types supported by the currently active input interface. The backend verification and auditing module is used to receive submitted input event data, obtain the permission level based on the current user's session information, and verify the obtained permission level and the received external input device type. If the external input device type does not belong to the controlled input device and the corresponding permission level is ordinary permission, the business request is rejected. The business execution module is used to execute business logic after the verification is passed.

[0013] In one embodiment, the data layer specifically includes: A log library is used to store security audit logs generated by the backend verification and auditing module. The business database is used to store business data submitted by the business execution module.

[0014] The present invention also proposes a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the input method management method as described above.

[0015] Compared with the prior art, the technical solution of the present invention has the following beneficial effects: 1) By controlling input methods based on permission levels, ordinary users cannot manually input data at will, which effectively prevents inconsistencies in data entry.

[0016] 2) Through the dual mechanism of front-end event interception and back-end secondary verification, ordinary users cannot enter data through non-scanning methods, eliminating the risk of untraceable records caused by human input errors or unauthorized operations.

[0017] 3) The dual-layer verification mechanism ensures that the input source and user permissions are strictly matched, which improves the security and accuracy of the system data entry process.

[0018] 4) By implementing a unified permission input control framework, module-level access is achieved, which unifies the permission input logic between different modules and improves the maintainability and scalability of the system. Attached Figure Description

[0019] Figure 1 This is a flowchart illustrating an embodiment of the MES system input method management method based on access control according to the present invention; Figure 2 This is a schematic diagram of the framework of an input method management system for a MES system based on access control, according to an embodiment of the present invention. Figure 3 This is a specific usage flow of the MES system input method management system based on access control, according to an embodiment of the present invention.

[0020] Figure Labels

[0021] Unified permission management platform 100, MES system layer 200, data layer 300, user permission recognition module 210, front-end permission control module 220, input event management module 230, back-end verification and auditing module 240, business execution module 250, log library 310, business database 320. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the invention.

[0023] like Figure 1 As shown, this invention proposes a method for managing input methods in a MES system based on access control, comprising the following steps: Step S1: In response to the user's login operation on the MES system client, obtain the current user's permission level, which includes normal permissions and advanced permissions.

[0024] In this embodiment, the unified permission management platform interface is called to obtain user permission information, including permission level, and the permission information is stored in the current session context and the front-end global state.

[0025] Step S2: When loading the business data input interface, configure the input interface of the input control according to the permission level.

[0026] Specifically, if the permission level is normal, only the input interface of the controlled input device will be opened, and the input interface of the human interaction device will be prohibited; if the permission level is high, the input interfaces of both the human interaction device and the controlled input device will be opened.

[0027] Furthermore, prohibiting the use of input interfaces for human-computer interaction devices includes disabling or hiding the input controls corresponding to the human-computer interaction device. Controlled input devices include at least one of barcode scanners, fingerprint scanners, and RFID readers / writers, while human-computer interaction devices include at least one of keyboards, mice, and touchscreens.

[0028] Step S3: During user interaction with the interface, monitor input events for input controls and identify the external input device type corresponding to the input event. If the external input device type does not belong to the device types supported by the currently active input interface, intercept the input event.

[0029] Furthermore, identifying the type of external input device corresponding to the input event includes: identifying the type of external input device corresponding to the input event based on one or more of the following methods: input time interval, input event type, and external input device interface identifier; The method of identifying the type of external input device corresponding to the input event based on the time interval includes: detecting the time interval between character inputs, determining it as a controlled input device when the time interval between consecutive character inputs is less than a preset threshold, and determining it as a human interaction device when the time interval is greater than the threshold; Identifying the type of external input device corresponding to the input event based on the input event type includes: distinguishing between human-interactive devices and controlled input devices by listening to the original event types of the front-end browser or client, including keyboard keystroke events, paste events, input method combination events and hardware interruption input events; Identifying the type of external input device corresponding to the input event based on the external input device interface identifier includes: when the input data comes from a USB-HID device, serial port device, Bluetooth device or dedicated industrial interface, reading the corresponding device identifier or port identifier and marking it as a controlled input device.

[0030] Furthermore, after intercepting the input event, an exception handling process is triggered, which includes: Step S31: Generate an abnormal input prompt message and block the current input behavior; Step S32: Provide a temporary authorization application interface, allowing the current user to submit an abnormal input application request; the application request includes the operation account, business number, external input device type, application reason and timestamp; Step S33: Send the abnormal input request to the pre-configured approval user or approval role; Step S34: If the review is approved, a temporary authorization token is generated. The token contains user identity information, authorized external input device type, and valid time range. Step S35: During the token's validity period, the current user is allowed to perform the restricted input operation; after the token expires, the control state under the original permission level is automatically restored; Step S36: Record the exception handling process and approval results to the security audit log.

[0031] Step S4: Submit all input event data to the MES system server. All input event data must include at least the external input device type.

[0032] The MES system server obtains the permission level based on the current user's session information and verifies the obtained permission level against the received external input device type. If the external input device type is not a controlled input device and the current user's permission level is normal, the business request is rejected. If the corresponding user's permission level is advanced, the request continues to be executed.

[0033] Furthermore, when a business request is rejected, the process also includes logging a security audit log. The security audit log must include at least the operating account, timestamp, permission level, and external input device type.

[0034] like Figure 2 As shown in the figure, an embodiment of the present invention provides an input method management system for a MES system based on access control, comprising: an MES system layer 200 and a data layer 300. The MES system layer 200, as the core business processing layer, is responsible for executing specific input control and business logic. This layer further includes a user access control module 210, a front-end access control module 220, an input event management module 230, a back-end verification and auditing module 240, and a business execution module 250. The MES system layer includes a front-end part and a back-end part. The front-end part runs on the MES system client and includes the user access control module 210, the front-end access control module 220, and the input event management module 230; the back-end part runs on the MES system server and includes the back-end verification and auditing module 240 and the business execution module 250. The user access control module 210 is used to obtain the current user's access level identifier when the user logs in. The front-end access control module 220 is used to configure the input interface of the input control according to the access level when loading the business data input interface. The input event management module 230 monitors input events for input controls, identifies the corresponding external input device type, and intercepts input events when there is a mismatch. The backend validation and auditing module 240 receives submitted input event data, obtains the permission level based on the current user's session information, and performs validation based on the permission level and input device type, rejecting non-compliant requests. The business execution module 250 executes business logic after successful validation. The data layer 300 stores various types of data generated during system operation, including a log database 310 and a business database 320. The log database 310 stores security audit logs generated by the backend validation and auditing module, and the business database 320 stores business data submitted by the business execution module.

[0035] In one specific embodiment, the MES system layer 200 also includes a front-end application state management module, which is mainly responsible for storing and sharing system state data, such as the current user permission level, input source, temporary authorization token, and other data.

[0036] The input method management system also includes a unified access control platform 100 (UAC, User Access Control), which communicates with the MES system layer 200. The unified access control platform 100 is used to centrally store and manage user access information, including user roles, menu permissions, and input method permission identifiers.

[0037] In this embodiment, as Figure 3 As shown, the specific usage flow of the input method management system based on the MES system is as follows: Step S101: The user enters their account and password in the MES system client to log in.

[0038] Step S102: In response to the login operation, the user permission identification module calls the unified permission management platform interface to obtain the user's role, menu and input method permission identifiers.

[0039] Step S103: The unified permission management platform queries the user's permission configuration based on the user account and returns user permission information, including the permission level. In this embodiment, the permission level includes two types: normal permissions and advanced permissions.

[0040] The system stores the acquired permission information in the current session context and synchronously caches it in the front-end application state management module (Global Context) to quickly retrieve the user's permission status during page rendering and input event processing. This design ensures that both the front-end interface and back-end services can quickly obtain the user's permission status throughout the entire business operation cycle, without repeatedly calling the UAC interface, thus improving system response efficiency.

[0041] Step S104: When a user accesses a business page requiring data input (such as material input, equipment maintenance, quality inspection, etc.) via menu navigation, the front-end permission control module dynamically adjusts the control state based on the permission identifier during the page rendering phase. Specifically, the front-end permission control module reads the current user's permission level from the global state and configures the input interface of the input control according to that permission level. (1) If the current user's permission level is high-level, the front-end permission control module simultaneously opens the input interfaces of both human interaction devices and controlled input devices. At this time, the user can manually enter data in the text box using human interaction devices such as keyboard, mouse, and touch screen, or automatically collect data using controlled input devices such as barcode scanners, fingerprint collectors, and RFID readers. The manual input box, barcode scanning button, fingerprint collection, and other input methods on the interface are all enabled, and the user can choose any input method according to actual needs.

[0042] (2) If the current user’s permission level is normal, the front-end permission control module will only open the input interface of the controlled input device and prohibit the use of the input interface of the manual interaction device.

[0043] The input interface of human-interaction devices can be disabled or hidden. Specifically, disabling involves setting the corresponding input controls (such as manual input boxes) to a disabled state; in this case, the controls are visible but cannot be edited. Hiding involves directly hiding the corresponding input controls of the human-interaction device, leaving only the QR code input device interface visible.

[0044] In this embodiment, the controlled input device includes at least one of a barcode scanner, a fingerprint collector, and an RFID reader / writer, and the human interaction device includes at least one of a keyboard, a mouse, and a touch screen.

[0045] Step S105: The user performs an input operation.

[0046] Step S106: During user interaction with the interface, the input event management module monitors all input events targeting the input controls and identifies and verifies the source of each input event. Specifically, the input event management module identifies the type of external input device corresponding to the input event through one or more of the following methods: (1) Identification based on input time interval Identification is achieved by detecting the time interval between character inputs. When a user manually inputs data via a keyboard, there is a human reaction time and key action time between each keystroke, which is usually a relatively long interval. However, when a user inputs data via a barcode scanner, the scanner parses the barcode content in one go and inputs it at a very fast speed. Therefore, when the detected time interval between consecutive character inputs is less than a preset threshold (generally 80 milliseconds), it is determined to be a controlled input device; when the time interval is greater than the preset threshold, it is determined to be a human-interactive device.

[0047] (2) Identification based on input event type

[0048] The input event management module identifies input devices by listening to the raw event types observed in the front-end browser or client. It registers various event listeners, including keyboard keystroke events (keydown, keypress), paste events, input method combination events (compositionstart, compositionend), and hardware interrupt input events. By analyzing the combination of event types and the order in which they are triggered, it distinguishes between human-interactive devices and controlled input devices. For example, if an input method combination event appears in the event sequence, it can be determined that the input is from a human-interactive device.

[0049] (3) Identification based on external input device interface identifier

[0050] The input device is identified by reading its physical interface information. When the input data comes from a USB-HID device, serial port device, Bluetooth device, or a dedicated industrial interface (such as RS232 or TCP acquisition terminal interface), the input event management module calls the device identification interface provided by the operating system to read the corresponding device identifier or port identifier and mark it as a controlled input device.

[0051] Through the above multi-dimensional identification methods, an external input device type identifier field corresponding to the input event is generated, namely the input source type identifier field (InputSourceType). This field is used for front-end interception judgment and back-end permission verification.

[0052] After identifying the type of external input device, the input event management module determines whether the device type belongs to the device types supported by the currently active input interface. The specific determination logic is as follows: If the current user has advanced privileges, the input interfaces of both human interaction devices and controlled input devices are activated, so input events of any device type are allowed.

[0053] If the current user has normal permissions, only the input interface of the controlled input device is activated. At this time, if the identified external input device type is a human interaction device (such as a keyboard or mouse), it is determined to be a mismatch, and the input event management module immediately intercepts the input event, preventing it from being passed to the business logic layer.

[0054] After intercepting an input event, the system triggers an exception handling process, which includes the following steps: Step S31: Generate an abnormal input prompt message and block the current input behavior. For example, the system informs the user that the current operation is not allowed through a pop-up window or prompt bar on the interface.

[0055] Step S32: Provide a temporary authorization application interface, allowing the current user to submit an abnormal input application request. The system displays the application entry next to the prompt message; clicking it will bring up an application form. This application request includes the operation account, business number, external input device type, application reason, and timestamp.

[0056] Step S33: Send the abnormal input request to the pre-configured approval user or approval role. The approval user is usually a user with advanced privileges, and the system pushes the request to the approval user through the internal approval platform.

[0057] Step S34: If the review is approved, a temporary authorization token is generated. This token contains user identity information, the type of authorized external input device, and a validity period. The token is generated using encryption to prevent tampering. This token can be used once within its validity period, or it will expire after use.

[0058] Step S35: During the token's validity period, the current user is allowed to perform restricted input operations. The token expires automatically after use or after its validity period. After the token expires, the system automatically restores the control state under the original permission level, i.e., only the controlled input device interface is open.

[0059] Step S36: Record the exception handling process and approval results in the security audit log. The log content includes the applicant user, approving user, application time, approval time, authorized device type, application reason, and approval result.

[0060] Step S107: When the user completes data input and triggers the submit operation, the front end encapsulates the input event data into a request and sends it to the MES system server. The request data must at least contain the external input device type.

[0061] Step S108: After receiving the submission request, the backend verification and auditing module executes the following verification process: Obtain the permission level from the current user's session information, rather than the permission identifier that may be carried in the trust request body; Parse the external input device type field from the request body; If the current user has high-level permissions, then regardless of the type of external input device, the validation will pass and the business execution module will continue to execute the business logic. If the current user's permission level is normal and the external input device type is not a controlled input device, the verification will fail.

[0062] Step S109: When the verification fails, the backend verification and auditing module rejects the business request, returns an error response to the client, and records the security audit log.

[0063] The security audit log should include at least the following fields: operation account, timestamp, permission level, and external input device type. Specifically, the operation account is the account of the current user, the timestamp is the time the request arrived at the server, the permission level is the current user's permission level, and the external input device type is the input source identifier carried in the request.

[0064] The audit log is persistently stored in the data layer's log library for subsequent security reviews, anomaly tracing, and data consistency analysis.

[0065] Once the verification passes, the request is forwarded to the business execution module. The business execution module executes the corresponding business logic based on the specific business scenario, such as material input registration, process posting, and equipment maintenance records. After processing, the business execution module stores the business data in the business database of the data layer.

[0066] This method is not only applicable to the material input stage, but can also be extended to MES modules such as equipment operation records, work order reporting, and quality inspection data entry. By achieving module-level access through a unified permission input control framework, it ensures data consistency and permission compliance across the entire production execution system in multiple scenarios.

[0067] Compared with the prior art, the technical solution of the present invention has the following beneficial effects: 1) By controlling input methods based on permission levels, ordinary users cannot manually input data at will, which effectively prevents inconsistencies in data entry.

[0068] 2) Through the dual mechanism of front-end event interception and back-end secondary verification, ordinary users cannot enter data through non-scanning methods, eliminating the risk of untraceable records caused by human input errors or unauthorized operations.

[0069] 3) The dual-layer verification mechanism ensures that the input source and user permissions are strictly matched, which improves the security and accuracy of the system data entry process.

[0070] 4) By implementing a unified permission input control framework, module-level access is achieved, which unifies the permission input logic between different modules and improves the maintainability and scalability of the system.

[0071] The embodiments described above are merely further illustrations of the present invention and are not intended to limit the present invention in any other way. The present invention may have many other embodiments. Without departing from the spirit and essence of the present invention, those skilled in the art can make various corresponding modifications and changes based on the present invention, but all such modifications and changes should fall within the protection scope of the present invention.

Claims

1. A method for managing input methods in a MES system based on access control, characterized in that, Includes the following steps: Step S1: In response to the user's login operation on the MES system client, obtain the current user's permission level, which includes normal permissions and advanced permissions; Step S2: When loading the business data input interface, configure the input interface of the input control according to the permission level; If the permission level is normal, only the input interface of the controlled input device will be opened, and the input interface of the human interaction device will be prohibited. If the permission level is high-level, then the input interfaces of both human interaction devices and controlled input devices are opened simultaneously; Step S3: During the user's interaction with the interface, monitor input events for the input controls and identify the type of external input device corresponding to the input events; When the external input device type is not one of the device types supported by the currently active input interface, the input event is intercepted; Step S4: Submit all input event data to the MES system server. All input event data must include at least the external input device type. The MES system server obtains the permission level based on the current user's session information and verifies the obtained permission level against the type of external input device received. If the external input device type is not a controlled input device and the current user's permission level is normal, the service request will be rejected; if the corresponding user's permission level is advanced, the request will continue.

2. The input method management method for an MES system based on access control according to claim 1, characterized in that, In step S3: The identification of the external input device type corresponding to the input event includes: identifying the external input device type corresponding to the input event based on one or more of the following methods: input time interval, input event type, and external input device interface identifier; The method of identifying the type of external input device corresponding to the input event based on the time interval includes: detecting the time interval between character inputs, determining it as a controlled input device when the time interval between consecutive character inputs is less than a preset threshold, and determining it as a human interaction device when the time interval is greater than the threshold; Identifying the type of external input device corresponding to the input event based on the input event type includes: distinguishing between human-interactive devices and controlled input devices by listening to the original event types of the front-end browser or client, including keyboard keystroke events, paste events, input method combination events and hardware interruption input events; Identifying the type of external input device corresponding to the input event based on the external input device interface identifier includes: when the input data comes from a USB-HID device, serial port device, Bluetooth device or dedicated industrial interface, reading the corresponding device identifier or port identifier and marking it as a controlled input device.

3. The input method management method for a MES system based on access control according to claim 1, characterized in that, After intercepting the input event, an exception handling process is also triggered, which includes: Step S31: Generate an abnormal input prompt message and block the current input behavior; Step S32: Provide a temporary authorization application interface, allowing the current user to submit an abnormal input application request. The application request includes the operation account, business number, external input device type, application reason, and timestamp. Step S33: Send the abnormal input request to the pre-configured approval user or approval role; Step S34: If the review is approved, a temporary authorization token is generated. The token contains user identity information, authorized external input device type, and valid time range. Step S35: During the token's validity period, the current user is allowed to perform authorized operations; after the token expires, the control state under the original permission level is automatically restored. Step S36: Record the exception handling process and approval results to the security audit log.

4. The input method management method for an MES system based on access control according to claim 1, characterized in that, The step S2 of prohibiting the use of the input interface of the human interaction device includes: disabling the input control corresponding to the human interaction device, or hiding the input control corresponding to the human interaction device.

5. The input method management method for a MES system based on access control according to claim 1, characterized in that, The controlled input device includes at least one of a barcode scanner, a fingerprint scanner, and an RFID reader / writer, and the human interaction device includes at least one of a keyboard, a mouse, and a touchscreen.

6. The input method management method for an MES system based on access control according to claim 1, characterized in that, In step S4, when the service request is rejected, the method further includes: Record security audit logs, which at least include the operation account, timestamp, permission level, and type of external input device.

7. The input method management method for a MES system based on access control according to claim 1, characterized in that, The step S1 of obtaining the current user's permission level includes: Call the unified permission management platform interface to obtain user permission information, including permission level, and store the permission information in the current session context and front-end global state.

8. A permission-based input method management system for an MES system, used to implement the input method management method as described in any one of claims 1 to 7, characterized in that, The input management system includes a MES system layer and a data layer. The MES system layer executes business logic and input control according to the user's corresponding input permissions, and the data layer is used to store system data. Specifically, the MES system layer includes: The user permission identification module is used to obtain the permission level identifier of the current user when the user logs in; The front-end permission control module is used to configure the input interface of the input control according to the permission level when loading the business data input interface; wherein, if the permission level is ordinary permission, only the input interface of the controlled input device is opened and the input interface of the human interaction device is prohibited; if the permission level is high permission, the input interfaces of both the human interaction device and the controlled input device are opened at the same time. The input event management module is used to monitor input events for input controls, identify the type of external input device corresponding to the input event, and intercept the input event when the type of external input device does not belong to the device types supported by the currently active input interface. The backend verification and auditing module is used to receive submitted input event data, obtain the permission level based on the current user's session information, and verify the obtained permission level and the received external input device type. If the external input device type does not belong to the controlled input device and the corresponding permission level is ordinary permission, the business request is rejected. The business execution module is used to execute business logic after the verification is passed.

9. The input method management system according to claim 8, characterized in that, The data layer specifically includes: A log library is used to store security audit logs generated by the backend verification and auditing module. The business database is used to store business data submitted by the business execution module.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the input method management method as described in any one of claims 1 to 7.

Images