Permission application method based on equipment group code

Abstract

The invention relates to the technical field of permission application, and provides a permission application method based on a device group code, and the permission application method comprises the following steps: S1, a scanning end scans a device code, and the information in the device code comprises a device code type and a permission level; s2, acquiring scanning end information, verifying the scanning end information according to the authority level, and providing an authority password and an authority priority under the corresponding authority to the scanning end; and S3, the scanning end inputs a permission password to the equipment, and parameter query, behavior control and start-stop operation are performed on the equipment based on information in the equipment code, the permission of the scanning end and the permission priority. The invention aims to provide a corresponding permission password for a user according to permission verification, and ensures that only authorized personnel can control and operate equipment.

Description

Technical Field

[0001] The present invention relates to the technical field of permission application, and in particular to a permission application method based on device group code. Background Art

[0002] In modern industrial environments, especially in the fields of intelligent manufacturing and equipment management, equipment control and authority management are becoming more and more complex and important, especially for key equipment such as air compressors, whose performance, operating status and maintenance management are directly related to the smooth progress of production. Therefore, an effective way is needed to control and manage access to and operation of these devices to ensure the normal operation, security and authority management of the equipment.

[0003] Traditional equipment management methods usually rely on simple physical access (such as direct operation of the control panel) or password protection alone. This method cannot accurately distinguish the permissions of different users. For large enterprises or factory environments, multiple levels of managers and operators may be involved, and each user's operating permissions should be different, which brings challenges to permission management. In some cases, administrators or ordinary employees can start and stop equipment such as air compressors or adjust equipment parameters without authorization, resulting in misoperation or abuse of the equipment, thereby increasing the risk of equipment failure or the possibility of unstable operation. Summary of the invention

[0004] In view of the above-mentioned defects, the purpose of the present invention is to propose a permission application method based on device group code, aiming to provide users with corresponding permission passwords according to permission verification, ensuring that only authorized personnel can control and operate the device.

[0005] To achieve this object, the present invention adopts the following technical solutions:

[0006] A permission application method based on a device group code, the permission application method comprising the following steps:

[0007] S1: The scanning end scans the device code, and the information in the device code includes the device code type and permission level;

[0008] S2: Obtain the information of the scanning end, verify the information of the scanning end according to the permission level, and provide the permission password and permission priority under the corresponding permission to the scanning end;

[0009] S3: The scanner inputs the permission password to the device, and performs parameter query, behavior control, and start and stop operations on the device based on the information in the device code, the scanner's permissions, and permission priority.

[0010] Preferably, when the device code type is a user parameter code, when the result of verifying the scanning end information according to the authority level is that the scanning end is the user himself, the device provides the user parameter password to the scanning end, and the scanning end can obtain the name, email address, password, delivery address, payment method, maintenance record and maintenance area of ​​the user associated with the device after entering the password in the device;

[0011] If the result of verifying the scanner information according to the permission level is that the scanner is not the user himself, the access of the scanner is denied.

[0012] Preferably, the authority levels include user level, manufacturer level and developer level.

[0013] Furthermore, based on the information in the device code, the permissions of the scanning end and the permission priority, the device is queried for parameters, the behavior is controlled, and the start and stop operations are performed, including:

[0014] When the device code type is power-on code:

[0015] When the result of verifying the scanner information according to the permission level is that the scanner is at the user level, and the scanner information is bound to the device in advance, the device provides the scanner with the device's power-on password, and the scanner enters the password in the device and then powers on the device;

[0016] When the result of verifying the scanner information according to the permission level is that the scanner is not at the user level, the device directly provides the scanner with the device's power-on password, and the scanner enters the password in the device and then powers on the device.

[0017] Further, the device includes a manual mode and an automatic mode;

[0018] Based on the information in the device code, the permissions and permission priorities of the scanning end, the device can be queried for parameters, controlled for behavior, and started and stopped, including:

[0019] When the device is in automatic mode, the scanner is prohibited from controlling the device to stop the frequency conversion handshake;

[0020] When the device is in manual mode, the permission level of the scanner is authenticated:

[0021] If the authority level of the scanner is not lower than the manufacturer level, the device provides the scanner with a stop handshake password. After the scanner enters the password in the device, the device stops the frequency conversion handshake.

[0022] Furthermore, based on the information in the device code, the permissions of the scanning end and the permission priority, the device is queried for parameters, the behavior is controlled, and the start and stop operations are performed, including:

[0023] When the device code type is device parameter code, when the result of verifying the scanner information according to the permission level is that the scanner is at the user level, the device provides the scanner with the device parameter query password, and the scanner can obtain the device parameters after entering the password in the device;

[0024] When the result of verifying the scanner information according to the permission level is that the scanner is at the manufacturer level, the device provides the scanner with the device parameter operation password. After the scanner enters the password in the device, it can query and change the device parameters;

[0025] Among them, device parameters include fixed parameters and variable parameters.

[0026] Furthermore, based on the information in the device code, the permissions of the scanning end and the permission priority, the device is queried for parameters, the behavior is controlled, and the start and stop operations are performed, including:

[0027] When the device parameters are changed on the scanning end, the change time and permission priority of the scanning end are recorded;

[0028] When only one scanner changes the device parameters at the same time, if the device parameters have been changed by another scanner with a higher priority before the scanner changes the device parameters, the scanner cannot change the device parameters.

[0029] When multiple scanning terminals query or modify device parameters at the same time, the device provides device parameter query and modification permissions to one or more scanning terminals with the highest permission priority, and the remaining scanning terminals obtain the parameter query permissions provided by the device.

[0030] Preferably, performing parameter query, behavior control, and start / stop operations on the device based on the information in the device code, the permissions of the scanning end, and the permission priority includes:

[0031] Parameter query includes consumable parameter query;

[0032] When there is no scanning end querying the consumable parameters of the device at the same time, the device provides a stop dynamic code to the scanning end, and the scanning end enters the stop dynamic code in the device, and the device stops updating the consumable parameters;

[0033] When one or more scanning ends query the device consumable parameters at the same time, if the authority level of the scanning end that is to instruct the device to stop updating the consumable parameters is the highest level among one or more scanning ends, then determine whether the authority priority of the scanning end that is to instruct the device to stop updating the consumable parameters is the highest value among the scanning ends with the highest level. If so, the device stops updating the consumable parameters.

[0034] Furthermore, the permission priority of the scanning end is positively correlated with the length of time the scanning end is bound to the device.

[0035] Further, the permission password under the corresponding permission granted to the scanning end includes a super password;

[0036] After the scanner enters the super password into the device, it can perform any parameter query, behavior control, and start / stop operations. Parameter query does not include user parameter query.

[0037] One of the above technical solutions has the following advantages or beneficial effects:

[0038] The present invention can effectively control device operation permissions through permission management based on device group codes, ensuring that different users perform corresponding operations according to their own permission levels, thereby greatly improving the security and flexibility of device management; by scanning the device code and combining user identity verification, it can accurately determine the user's permissions to avoid unauthorized operations by low-authority users; the design of permission priority ensures that when multiple users operate the device at the same time, the operations of high-authority users are executed first, avoiding the risk of operation conflicts and device settings being interfered with by unauthorized users, simplifying the device management process, improving the compliance and efficiency of operations, and effectively ensuring the stable operation and safe management of the equipment. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0040] Figure 1 It is a flow chart of a permission application method provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0041] Embodiments of the present invention are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and cannot be understood as limiting the present invention.

[0042] In the present invention, the terms "comprises", "comprising" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of more restrictions, an element defined by the sentence "comprising a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element.

[0043] In modern industrial environments, especially in the fields of intelligent manufacturing and equipment management, equipment control and authority management are becoming more and more complex and important, especially for key equipment such as air compressors, whose performance, operating status and maintenance management are directly related to the smooth progress of production. Therefore, an effective way is needed to control and manage access to and operation of these devices to ensure the normal operation, security and authority management of the equipment.

[0044] Traditional equipment management methods usually rely on simple physical access (such as direct operation of the control panel) or password protection alone. This method cannot accurately distinguish the permissions of different users. For large enterprises or factory environments, multiple levels of managers and operators may be involved, and each user's operating permissions should be different, which brings challenges to permission management. In some cases, administrators or ordinary employees can start and stop equipment such as air compressors or adjust equipment parameters without authorization, resulting in misoperation or abuse of the equipment, thereby increasing the risk of equipment failure or the possibility of unstable operation.

[0045] Therefore, a permission application method based on device group code is proposed, such as Figure 1 As shown, in a preferred embodiment of the present application, the permission application method includes the following steps:

[0046] S1: The scanning end scans the device code, and the information in the device code includes the device code type and permission level;

[0047] S2: Obtain the information of the scanning end, verify the information of the scanning end according to the permission level, and provide the permission password and permission priority under the corresponding permission to the scanning end;

[0048] S3: The scanner inputs the permission password to the device, and performs parameter query, behavior control, and start and stop operations on the device based on the information in the device code, the scanner's permissions, and permission priority.

[0049] Taking an air compressor as an example, there are multiple device codes on the air compressor, which are embedded with codes about the device code type and its permission information. For example, scanning the first device code can obtain user information, scanning the second device code can obtain the power-on password, and the user enters the power-on password to perform the power-on operation. In addition, the permission level defines the permission control of the device code on the user, and determines which operations different users can perform on the device. The permission level of the device can include different roles, such as ordinary users, manufacturers, administrators, etc. The permission level determines whether the user can access the advanced settings of the device, query operations, or perform start-stop control, etc. The scanning end device (such as a smart phone, tablet computer, barcode scanner, etc.) extracts the unique identifier of the device code and the embedded permission information by reading the device code. This process is achieved by scanning a QR code or a barcode: After the scanning end obtains the device code, it will parse out the device code type (such as "power-on code") and permission level (such as "01-user permission"), and the permission level information in the device code is passed to the subsequent verification process to determine the next access and control strategy based on the user's role and permission.

[0050] In this embodiment, after scanning the device code, the scanning end device will send the data it reads to the background system. The background system identifies the permission requirements of the scanning end device according to the permission level information in the device code. The background system first checks the permission level embedded in the device code (such as "01", representing user permissions), and then, according to the identity of the current scanning end user (such as through the identity information of the user login or binding), the system will check whether the user has sufficient permissions to access the relevant functions of the device. If the verification is successful, the system generates or provides a permission password for the scanning end. This permission password is a key used by the system to verify that the user operation is legal. Only users who pass the permission verification can continue to perform subsequent operations. If multiple users (such as administrators, operators, etc.) access the device at the same time, the system will determine the priority of the operation according to the user's permission level. For example, the administrator has a higher permission level than ordinary users, and the user who accesses first has a higher permission priority than the user who accesses later. The system will respond to the administrator's request first to ensure that the control of the high-authority user is prioritized. The permission password ensures that the user's operations on the device are within the scope of their permissions. For example, ordinary users can only view the basic information of the device and cannot make any settings changes or start and stop controls. Administrators have higher permissions and can modify device configurations or perform key operations. Permission priority controls how to allocate operating permissions when multiple users operate the same device. High-priority users can preempt operating rights to prevent low-priority users from modifying or interfering with the core settings of the device.

[0051] In step S3, the user enters the permission password generated by the system according to the scanned device code and permission level. This password is an identity authentication method provided by the verification system to ensure that only authorized users can perform operations. After entering the correct permission password, the system will continue to perform permission management and operation control. The system performs corresponding operations on the device according to the permission password and priority of the scanning end. If the password is correct and the user has sufficient permissions, the system allows the user to perform the specified operation. For example, in parameter query, if the user's permissions allow, the system will return the current status or parameters of the device, such as the temperature, pressure, current, etc. during the operation of the device; in the operation of the device, if the user's permissions allow, the system will also provide more operation options, such as adjusting device parameters, starting and stopping the device, etc. For example, the manufacturer's permissions may allow users to adjust the internal settings of the device, while ordinary users can only query the device status.

[0052] The present invention can effectively control device operation permissions through permission management based on device group codes, ensuring that different users perform corresponding operations according to their own permission levels, thereby greatly improving the security and flexibility of device management; by scanning the device code and combining user identity verification, it can accurately determine the user's permissions to avoid unauthorized operations by low-authority users; the design of permission priority ensures that when multiple users operate the device at the same time, the operations of high-authority users are executed first, avoiding the risk of operation conflicts and device settings being interfered with by unauthorized users, which can simplify the device management process, improve the compliance and efficiency of operations, and effectively ensure the stable operation and safe management of the equipment.

[0053] Preferably, when the device code type is a user parameter code, when the result of verifying the scanning end information according to the authority level is that the scanning end is the user himself, the device provides the user parameter password to the scanning end, and the scanning end can obtain the name, email address, password, delivery address, payment method, maintenance record and maintenance area of ​​the user associated with the device after entering the password in the device;

[0054] If the result of verifying the scanner information according to the permission level is that the scanner is not the user himself, the access of the scanner is denied.

[0055] The scanning end (such as a smart phone, tablet computer, barcode scanner, etc.) scans the device code on the device, which contains user-related parameters. The permission level required by the scanning end device is determined based on the information in the device code. If the permission level meets the access rights, the identity of the scanning end device is then verified. If the scanning end is an authorized user (i.e., the user associated with the device), the system will provide the corresponding user parameter password; if the scanning end is not an authorized user (i.e., not the user himself), the system will deny access. The main purpose is to ensure that only authorized users can access and operate user parameter information related to the device through identity authentication, thereby improving the security of device operation and information protection. If the scanning end passes identity authentication and is a legitimate user, the system will provide a user parameter password, allowing the scanning end to enter the device and view user information related to the device, including user name, email address, password, delivery address, payment method, equipment maintenance record and maintenance area, etc. By providing password protection, only authorized users can access and operate sensitive information. If the scanning end is verified as not the user himself, the system will deny the scanning end's access request. Through this rejection mechanism, unauthorized users can be prevented from accessing, operating the device, or obtaining sensitive user information.

[0056] Preferably, the authority levels include user level, manufacturer level and developer level.

[0057] User level refers to the permissions of the end consumer or user. A user is an ordinary user of the system, usually associated with a specific device or service, and has basic operating permissions, but the permissions are relatively low. Users can view device information associated with their account, such as the current status of the device, usage history, basic configuration, etc.; perform basic operations, such as starting and shutting down the device, adjusting the basic settings of the device, etc., but not including the core settings of the device or high-authority operations. View maintenance records and historical data: You can view maintenance records, usage history, system upgrade information, etc. related to the device.

[0058] The manufacturer level refers to the authority of the manufacturer or service provider of the device. Users at this authority level have the ability to maintain, configure, and upgrade the device. The manufacturer administrator is responsible for large-scale management of the device, factory configuration of the device, and maintenance support. Comprehensive device management can view and manage the data, settings, and status of all registered devices. It is not limited to the device of a certain user, but operates on the entire device group. It can view the maintenance records, repair status, and troubleshooting information of all devices, and can perform equipment repairs or replace parts; it can perform advanced configuration of the device, such as hardware adjustment, system optimization, etc., to ensure the normal operation of the device.

[0059] The developer level usually refers to personnel engaged in device software development, system design, technical support, etc., who have the highest authority in the system and can perform all advanced operations related to devices and systems, including but not limited to code writing, system configuration, debugging, etc. Developers can view, modify and write the source code and programs of the device to perform system-level customized development; and have access to all hardware and software settings of the device, including low-level settings, hardware debugging, performance optimization, etc.; can develop, configure and deploy development tools, SDKs, APIs, etc. to support the continuous development and function expansion of the device.

[0060] Furthermore, based on the information in the device code, the permissions of the scanning end and the permission priority, the device is queried for parameters, the behavior is controlled, and the start and stop operations are performed, including:

[0061] When the device code type is power-on code:

[0062] When the result of verifying the scanner information according to the permission level is that the scanner is at the user level, and the scanner information is bound to the device in advance, the device provides the scanner with the device's power-on password, and the scanner enters the password in the device and then powers on the device;

[0063] When the result of verifying the scanner information according to the permission level is that the scanner is not at the user level, the device directly provides the scanner with the device's power-on password, and the scanner enters the password in the device and then powers on the device.

[0064] The power-on code is a unique identification code for a device, which is used to start the device and contains necessary verification information to ensure the safe activation of the device. When the scanning end is at the user level and the scanning end information is bound to the device in advance (usually the device code is bound to the user information to ensure that it is a legitimate user operation), the scanning end scans through the device code. The device first verifies the permission level of the scanning end and confirms whether it is at the user level. Based on the permission verification result, the device determines that the scanning end is a legitimate user (the device is bound to the user information). The device provides the power-on password to the scanning end. At this time, the power-on password of the device is transmitted to the scanning end through a secure channel (such as an encrypted channel). The scanning end enters the received power-on password, and the device verifies whether the password is correct. If the password is correct, the device starts; if the password is incorrect, the device refuses to start and may feedback an error message or require re-entry.

[0065] When the scanning end is at a non-user level, it means that the scanning end is not necessarily the end user, but may be the device manager, manufacturer representative or developer with a higher level of authority. The scanning end scans through the device code, and the device verifies the authority level of the scanning end and confirms that the scanning end belongs to the non-user level (manufacturer or developer level). The device directly provides the power-on password to the scanning end, and the device does not perform a binding check like the user level. The scanning end enters the power-on password of the device, and the device verifies whether the password is correct. If the password is correct, the device starts; if the password is incorrect, the device refuses to start and may feedback an error message or require re-entry, which can ensure that scanning ends with different authority levels can safely access the power-on function of the device and perform corresponding operations.

[0066] Further, the device includes a manual mode and an automatic mode;

[0067] Based on the information in the device code, the permissions and permission priorities of the scanning end, the device can be queried for parameters, controlled for behavior, and started and stopped:

[0068] When the device is in automatic mode, the scanner is prohibited from controlling the device to stop the frequency conversion handshake;

[0069] When the device is in manual mode, the permission level of the scanner is authenticated:

[0070] If the authority level of the scanner is not lower than the manufacturer level, the device provides the scanner with a stop handshake password. After the scanner enters the password in the device, the device stops the frequency conversion handshake.

[0071] Among them, variable frequency handshake appears in systems involving variable frequency drive (VFD) control. The variable frequency drive is a device that adjusts the speed and power of the motor. It controls the running speed, torque and energy efficiency of the motor by adjusting the power supply frequency. The variable frequency handshake usually refers to the signal exchange or synchronization process between the variable frequency drive and the motor to ensure that the motor controlled by the variable frequency drive can start, run and stop normally. In the variable frequency drive system, the variable frequency drive controls the speed of the motor by adjusting the frequency of the current. When the variable frequency drive and the motor work together, the communication or synchronization process between them is called "handshake". This handshake is completed by exchanging electrical signals to ensure that the variable frequency drive and the motor can work in coordination normally. The inverter handshake needs to be stopped in the following scenarios, such as troubleshooting: When a device fails, the inverter handshake process needs to be stopped to cut off the connection between the motor and the inverter to prevent further damage or safety hazards. For example, when the inverter detects abnormal conditions such as motor overload, overheating, and phase failure, it needs to stop the synchronization process between the inverter and the motor to protect the motor and the control system. When repairing or maintaining the equipment, the inverter control also needs to be stopped to ensure that the motor does not start accidentally or is not interfered with by the control signal; when adjusting system parameters (for example, changing the motor operating speed, acceleration and deceleration time, braking mode, etc.), the inverter and motor handshake needs to be stopped to ensure that the new control parameters can be applied smoothly and avoid conflicts. The adjustment of certain parameters may affect the operating status of the motor, so it is necessary to stop the current control signal first and then reinitialize the handshake process.

[0072] In automatic mode, the operation of the equipment is managed by a preset automatic control system (such as PID controller, frequency converter control, etc.), and the equipment automatically adjusts its behavior according to the predetermined program and input signal. This mode is used for self-regulation and stable operation of the equipment without manual intervention. In automatic mode, the process performed by the equipment (such as frequency conversion handshake) is triggered by the control system or sensor, and all external manual intervention is strictly prohibited. This is to ensure that the equipment automatically operates according to the predetermined control process and avoid interference and instability caused by manual operation. The control system of the equipment monitors the input signals (such as load changes, temperature changes, voltage signals, etc.) in real time, and adjusts the working state of the equipment (for example, frequency conversion adjustment, motor speed, etc.) according to these signals. Once entering automatic mode, the control system of the equipment will take over the operation of the equipment, and any manual control instructions will be ignored by the system.

[0073] In manual mode, the operation authority of the device is given to the user or operator. At this time, the device allows external scanners (such as mobile devices, workstations, etc.) to adjust the parameters or behaviors of the device through manual instructions (such as stopping the frequency conversion handshake, adjusting the device speed, start-stop control, etc.). Manual mode allows the device to adjust the working state according to the needs of the operator, but this control needs to be strictly verified to avoid unauthorized operations. Manufacturers such as equipment manufacturers, developers or equipment system administrators have full control authority and can perform key operations (such as stopping the frequency conversion handshake, adjusting key parameters, etc.). When the scanner initiates a control request, the device will first verify the authority of the scanner. The device determines its authority level based on the identity information of the scanner (such as device code, scanner authentication, etc.). If the authority level does not meet the requirements, the device will reject the request and prompt that the authority is insufficient. The device confirms the authority of the scanner through an internal authentication mechanism (such as device code verification, scanner authentication, authentication token, etc.). After the authentication is passed, the system will allow the scanner to perform subsequent operations; otherwise, the operation will be rejected. The device decides whether to allow external operation based on the working mode (automatic mode or manual mode). In manual mode, the device uses the permission verification and password mechanism of the scanning end to ensure that only operators with sufficient permissions can perform key operations (such as stopping the frequency conversion handshake), ensuring the operational safety and auditability of the device.

[0074] Furthermore, based on the information in the device code, the permissions of the scanning end and the permission priority, the device is queried for parameters, the behavior is controlled, and the start and stop operations are performed, including:

[0075] When the device code type is device parameter code, when the result of verifying the scanner information according to the permission level is that the scanner is at the user level, the device provides the scanner with the device parameter query password, and the scanner can obtain the device parameters after entering the password in the device;

[0076] When the result of verifying the scanner information according to the permission level is that the scanner is at the manufacturer level, the device provides the scanner with the device parameter operation password. After the scanner enters the password in the device, it can query and change the device parameters;

[0077] Among them, device parameters include fixed parameters and variable parameters.

[0078] Specifically, when the authority of the scanning end is verified as user level, the device will provide a device parameter query password to the scanning end. After the user enters the correct password, he can only view the fixed parameters of the device. These fixed parameters usually include the unique identification information of the device, such as device model, serial number, production date, hardware version, etc. This information is fixed throughout the life cycle of the device, so the user can only query but not modify it. This restriction ensures that ordinary users can only obtain necessary device information and cannot interfere with the specific settings or operating status of the device. When the authority of the scanning end is verified as manufacturer level, the device will provide a device parameter operation password to allow manufacturer level users to perform more operations after entering the correct password. Manufacturer level users can not only query the fixed parameters of the device, but also query and change the variable parameters, such as the device's working mode, operating frequency, output power, operating time, etc. These variable parameters may be adjusted according to actual needs during the operation of the device, so manufacturer level users have higher authority to optimize the working status of the device according to specific operating requirements. The entire permission control system dynamically adjusts the response and operability of the device based on the identity authentication of the scanning end. The priority of permissions is strictly managed according to the difference between user level and manufacturer level. The manufacturer level permissions cover all operation permissions, including querying and modifying device parameters and manipulating device behavior, while the user level is strictly restricted and can only perform information query operations, which can effectively prevent ordinary users from misoperating or making unauthorized changes to the device, while also ensuring efficient operation and security of the device. User level and manufacturer level use different passwords for identity authentication. Only after the password verification is passed, the device will provide corresponding operation functions according to the user's permissions. These passwords can be updated regularly and follow security policies to prevent permissions from being maliciously acquired.

[0079] Fixed parameters are parameters that are set when the device leaves the factory and will not change during its entire life cycle. They usually include basic information about the device, such as device model, serial number, factory date, hardware version, firmware version, etc. These fixed parameters are not allowed to be modified by any user and can only be queried. Variable parameters can be adjusted and optimized as needed during the operation of the device. They usually include the device's operating mode, frequency, power, and device operating time. Factory-level users can change these parameters according to actual needs to optimize device performance or adjust the device to adapt to different operating environments.

[0080] Furthermore, based on the information in the device code, the permissions of the scanning end and the permission priority, the device is queried for parameters, the behavior is controlled, and the start and stop operations are performed, including:

[0081] When the device parameters are changed on the scanning end, the change time and permission priority of the scanning end are recorded;

[0082] When only one scanner changes the device parameters at the same time, if the device parameters have been changed by another scanner with a higher priority before the scanner changes the device parameters, the scanner cannot change the device parameters.

[0083] When multiple scanning terminals query or modify device parameters at the same time, the device provides device parameter query and modification permissions to one or more scanning terminals with the highest permission priority, and the remaining scanning terminals obtain the parameter query permissions provided by the device.

[0084] In a multi-scanner environment, the device management system ensures the security and consistency of device parameter query, modification, and start-stop operations through precise permission control and priority mechanisms. When each scanner requests device operation, the system first verifies according to the scanner's permission level. Scanners with higher priority (such as administrator or manufacturer level) will have higher operation permissions. Specifically, when a scanner changes device parameters, the system will record the scanner ID, operation time, and permission level of the operation. If multiple scanners query or modify device parameters at the same time, the device will ensure that only the scanner with the highest permission priority can change the parameters, while other low-privilege scanners can only query parameters. If multiple scanners have the same and highest permissions, the device allows these scanners to change parameters at the same time, and other scanners can only query. In the event of a permission conflict, the device will reject the operation of the low-privilege scanner to ensure that parameter modifications are always completed by the scanner with higher permissions. In addition, the device will automatically record the timestamp and modification content of each parameter change to ensure that the operation is traceable and auditable. In terms of device start and stop and behavior control, the system also follows the principle of permission priority to prevent low-privilege scanning terminals from forcibly starting and stopping devices. All operations are managed through strict permission detection and conflict handling mechanisms to ensure the stability and security of the equipment.

[0085] Preferably, performing parameter query, behavior control, and start / stop operations on the device based on the information in the device code, the permissions of the scanning end, and the permission priority includes:

[0086] Parameter query includes consumable parameter query;

[0087] When there is no scanning end querying the consumable parameters of the device at the same time, the device provides a stop dynamic code to the scanning end, and the scanning end enters the stop dynamic code in the device, and the device stops updating the consumable parameters;

[0088] When one or more scanning ends query the device consumable parameters at the same time, if the authority level of the scanning end that is to instruct the device to stop updating the consumable parameters is the highest level among one or more scanning ends, then determine whether the authority priority of the scanning end that is to instruct the device to stop updating the consumable parameters is the highest value among the scanning ends with the highest level. If so, the device stops updating the consumable parameters.

[0089] When performing equipment maintenance, calibration or other similar operations, the device may need to suspend updating or reading parameters related to consumables. In order to avoid data inconsistency or affect the accuracy of operation due to frequent parameter updates during hardware inspection, maintenance or debugging, for example, when the printer or scanner is replacing consumables or debugging the equipment, stopping parameter updates can ensure stability during the maintenance process. When replacing consumables (such as replacing printer cartridges or copier toner cartridges), the device may stop updating parameters related to consumables until the new consumables are installed and confirmed. Stopping parameter updates at this time can prevent erroneous data recording or alarms caused by misoperation or erroneous reading during the replacement process. After the consumables are installed, the device will reactivate the update of consumable parameters.

[0090] When no scanning end queries the consumable parameters of the device, the device will provide a "stop dynamic code" to the scanning end. After the scanning end enters the stop dynamic code, the device stops updating the consumable parameters, which means that in the absence of any scanning end query, the device can enter static mode and stop automatically updating the consumable parameters, saving system resources and avoiding unnecessary data changes.

[0091] If one or more scanning terminals query the consumable parameters of the device at the same time, the system will judge the permission level of the query request. The device will first determine the permission level of the scanning terminal that is to stop the consumable parameter update. If the permission level of the scanning terminal is the highest among all scanning terminals, the device will continue to make a priority judgment. Next, the system will compare the permission priorities of the scanning terminals. If the permission priority of the scanning terminal is the highest value among all high-authority scanning terminals, the device will stop updating the consumable parameters. If the permission level of the scanning terminal does not reach the highest level, or the permission priority does not reach the highest value, the device will continue to update the consumable parameters until suitable conditions are met to meet the requirements for stopping the update. For example, there are scanning terminals A, B and C, with permission levels (the higher the level, the greater the permission): scanning terminal A: permission level = 3 (highest permission level), scanning terminal B: permission level = 2, scanning terminal C: permission level = 1 (lowest permission level), permission priority (the priority within each scanning terminal, the higher the priority, the stronger): scanning terminal A: permission priority = 10 (highest priority), scanning terminal B: permission priority = 7, scanning terminal C: permission priority = 5. Assume that scanning terminals A, B, and C send query requests to the device at the same time. After receiving these requests, the device will judge the requested permissions one by one to decide whether to stop updating the consumable parameters. The device first judges the permission levels of all scanning terminals: the permission level of scanning terminal A is 3, scanning terminal B is 2, and scanning terminal C is 1. Scanner A has the highest permission level among all scanners (permission level 3), so A can stop updating the consumable parameters. If B's ​​permission level is also 3, since scanners A and B have the highest permission levels, the device continues to judge based on the permission priority: Scanner A's permission priority is 10, and Scanner B's is 7. Among the scanners with the highest permission level, Scanner A also has the highest permission priority (priority 10). The device will stop the automatic update of consumable parameters based on the request of Scanner A until certain conditions are met and then resume the update.

[0092] Furthermore, the permission priority of the scanning end is positively correlated with the length of time the scanning end is bound to the device.

[0093] If the permission priority of the scanner is positively correlated with the length of time the scanner is bound to the device, then when multiple scanners simultaneously request to query the consumable parameters of the device, the device will not only make judgments based on the permission level, but also consider the length of time each scanner has been bound to the device. Specifically, the longer the binding time of the scanner, the higher its permission priority, and the scanner with a higher priority will preferentially affect the behavior of the device.

[0094] For example, suppose scanners A, B, and C are bound to the device for different lengths of time, scanner A has the shortest binding time, scanner B is the second, and scanner C has the longest binding time. In this case, if scanner C has the longest binding time with the device, the device will follow the priority rule, and C has the highest permission priority among the same permission levels, and can decide whether to stop updating the consumable parameters according to the permission priority of scanner C. In this way, the device will not only consider the permission level, but also the length of time the scanner has been bound to the device, to ensure that the scanner that has been bound to the device for a longer time has stronger priority control. It is worth noting that the comparison of permission priorities can only be performed under the same permission level. If the permission levels are different, the permission comparison depends on the comparison results of the permission levels.

[0095] Preferably, the permission password for the corresponding permission granted to the scanning end includes a super password;

[0096] After the scanner enters the super password into the device, it can perform any parameter query, behavior control, and start / stop operations. Parameter query does not include user parameter query.

[0097] Each scanner has a corresponding permission password in the system, which authorizes it to access different functions and resources of the device. The strength or function of the permission password depends on the permission level of the scanner. For example, scanner A may have a strong permission password, while scanner C has a weaker permission password. The super password is a special password that is designed to enable the scanner to perform all operations, including executing any parameter query, controlling device behavior (such as starting and stopping device functions), and starting and stopping device operations. The super password has a certain effect on the permission level. After entering the password, the authorized scanner can bypass the normal permission restrictions and obtain a higher level of access rights. Even if the scanner obtains extensive control over the device through the super password, there are still some parameters that cannot be queried, such as privacy or security data related to the user (such as user account information, permission settings, etc.). This is to protect the user's privacy and security and prevent unauthorized scanners from obtaining sensitive information. After the scanner enters the super password into the device, the device will verify the validity of the password. If the password is correct, the device will authorize the scanner to perform any allowed operations, such as querying any other parameters of the device, controlling device behavior, or starting and stopping the device. Once the super password is entered correctly, the device will temporarily increase the permissions of the scanner and allow it to perform tasks beyond normal permissions until the device is reset or the super password expires (such as timeout, device restart, etc.).

[0098] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0099] Although the embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the claims and their equivalents.

Claims

1. A permission application method based on device group code, characterized in that: The permission application method comprises the following steps: S1: The scanning end scans the device code, and the information in the device code includes the device code type and permission level; S2: Obtain the information of the scanning end, verify the information of the scanning end according to the permission level, and provide the permission password and permission priority under the corresponding permission to the scanning end; S3: The scanner inputs the permission password to the device, and performs parameter query, behavior control, and start and stop operations on the device based on the information in the device code, the scanner's permissions, and permission priority.

2. The permission application method according to claim 1, characterized in that: When the device code type is user parameter code, the result of verifying the scanner information according to the permission level is that the scanner is the user himself, the device provides the user parameter password to the scanner, and the scanner enters the password in the device to obtain the user's name, email address, password, delivery address, payment method, maintenance record and maintenance area associated with the device; If the result of verifying the scanner information according to the permission level is that the scanner is not the user himself, the access of the scanner is denied.

3. The permission application method according to claim 1, characterized in that: Permission levels include user level, manufacturer level and developer level.

4. The permission application method according to claim 3, characterized in that: Based on the information in the device code, the permissions and permission priorities of the scanning end, the device can be queried for parameters, controlled for behavior, and started and stopped, including: When the device code type is power-on code: When the result of verifying the scanner information according to the permission level is that the scanner is at the user level, and the scanner information is bound to the device in advance, the device provides the scanner with the device's power-on password, and the scanner enters the password in the device and then powers on the device; When the result of verifying the scanner information according to the permission level is that the scanner is not at the user level, the device directly provides the scanner with the device's power-on password, and the scanner enters the password in the device and then powers on the device.

5. The permission application method according to claim 3, characterized in that: The equipment includes manual mode and automatic mode; Based on the information in the device code, the permissions and permission priorities of the scanning end, the device can be queried for parameters, controlled for behavior, and started and stopped, including: When the device is in automatic mode, the scanner is prohibited from controlling the device to stop the frequency conversion handshake; When the device is in manual mode, the permission level of the scanner is authenticated: If the authority level of the scanner is not lower than the manufacturer level, the device provides the scanner with a stop handshake password. After the scanner enters the password in the device, the device stops the frequency conversion handshake.

6. The permission application method according to claim 3, characterized in that: Based on the information in the device code, the permissions and permission priorities of the scanning end, the device can be queried for parameters, controlled for behavior, and started and stopped, including: When the device code type is device parameter code, when the result of verifying the scanner information according to the permission level is that the scanner is at the user level, the device provides the scanner with the device parameter query password, and the scanner can obtain the device parameters after entering the password in the device; When the result of verifying the scanner information according to the permission level is that the scanner is at the manufacturer level, the device provides the scanner with the device parameter operation password. After the scanner enters the password in the device, it can query and change the device parameters; Among them, device parameters include fixed parameters and variable parameters.

7. The permission application method according to claim 6, characterized in that: Based on the information in the device code, the permissions and permission priorities of the scanning end, the device can be queried for parameters, controlled for behavior, and started and stopped, including: When the device parameters are changed on the scanning end, the change time and permission priority of the scanning end are recorded; When only one scanner changes the device parameters at the same time, if the device parameters have been changed by another scanner with a higher priority before the scanner changes the device parameters, the scanner cannot change the device parameters. When multiple scanning terminals query or modify device parameters at the same time, the device provides device parameter query and modification permissions to one or more scanning terminals with the highest permission priority, and the remaining scanning terminals obtain the parameter query permissions provided by the device.

8. The permission application method according to claim 1, characterized in that: Based on the information in the device code, the permissions and permission priorities of the scanning end, the device can be queried for parameters, controlled for behavior, and started and stopped, including: Parameter query includes consumable parameter query; When there is no scanning end querying the consumable parameters of the device at the same time, the device provides a stop dynamic code to the scanning end, and the scanning end enters the stop dynamic code in the device, and the device stops updating the consumable parameters; When one or more scanning ends query the device consumable parameters at the same time, if the authority level of the scanning end that is to instruct the device to stop updating the consumable parameters is the highest level among one or more scanning ends, then determine whether the authority priority of the scanning end that is to instruct the device to stop updating the consumable parameters is the highest value among the scanning ends with the highest level. If so, the device stops updating the consumable parameters.

9. The permission application method according to claim 8, characterized in that: The permission priority of the scanner is positively correlated with the length of time the scanner is bound to the device.

10. The permission application method according to any one of claims 1 to 9, characterized in that: The permission password for the corresponding permission granted to the scanning end includes the super password; After the scanner enters the super password into the device, it can perform any parameter query, behavior control, and start / stop operations. Parameter query does not include user parameter query.

Images