An authorization method and system for binding a device to host software based on multiple factors

Abstract

The application discloses a kind of authorization method and system based on multi-factor binding device and host computer software, it is related to embedded device security and software authorization management technical field, and authorization method includes the following steps: S1: upstream vendor securely solidifies core identity information to the read-only storage area of device by factory programming procedure, S2: upstream vendor generates authorization file for device by binding authorization management procedure according to the authorization data of primary customer, S3: primary customer uses the authorization file obtained from upstream vendor, and performs binding operation on device by device binding procedure;With device to establish communication, S4: end user connects host computer software and device, controls device to run;Authorization system includes factory programming procedure, binding authorization management procedure, device binding procedure, host computer procedure.The beneficial effects of the application include realizing the leap from "two-dimensional binding" to "multi-dimensional binding", and providing more control granularity and flexibility.

Description

Technical Field

[0001] This invention relates to the field of embedded device security and software license management technology, specifically to a license method and system based on multi-factor binding of devices and host computer software. Background Technology

[0002] Existing device binding solutions typically focus only on the association between the device and the software itself, lacking constraints on the software's operating environment. This means that once the licensed software is leaked, the bound device can run and be used on any compatible computer, still posing a security risk. Furthermore, existing solutions fail to link device usage permissions with the licensing status of the host computer software's development kit (SDK), failing to control the use of unauthorized software at its source. Summary of the Invention

[0003] The purpose of this invention is to provide an authorization method and system based on multi-factor binding of devices and host computer software. This method binds devices and software to specific computers (such as production line control hosts or authorized users' office computers) by integrating multi-factor information such as device identifiers, software identifiers, hardware environment identifiers, and SDK licenses. Even if the software is copied, the device cannot be used on other computers, effectively preventing the unlimited copying and distribution of authorized software to unauthorized end users. Furthermore, the device binding is associated with the SDK license used in the development of the host computer software, ensuring that only software developed using genuine, unexpired SDKs can communicate with the device.

[0004] On one hand, the present invention provides an authorization method for binding devices and host computer software based on multiple factors, comprising the following steps: S1: Upstream manufacturers securely embed core identity information into the device's read-only storage area through factory programming. Core identity information includes the upstream vendor's public key, device model, device serial number, and primary customer number; S2: Upstream manufacturers generate authorization files for devices by binding the authorization management program based on the authorization data of Tier 1 customers; Upstream manufacturers receive authorization data from Tier 1 customers. Authorized data includes the primary customer ID, device serial number, application scenario ID, and primary customer public key; The binding authorization management software uses the upstream vendor's private key to perform a first-level customer identity digital signature on the authorization data; The binding license management software outputs a standard, tamper-proof license file and sends it to the primary customer; S3: Tier 1 customers use the authorization documents obtained from upstream manufacturers to perform device binding operations through the device binding program; The device binding program integrates or loads the authorization file to establish communication with the device; The device binding program sends a binding request to the device, which includes a first-level customer identity digital signature and authorization data; After receiving the digital signature of the primary customer's identity, the device performs primary customer identity verification. Once the verification is successful, the device saves the binding information and completes the binding verification process. S4: The end user connects to the host computer software and device to control the operation of the device; The end user uses the primary client's private key to digitally sign the instructions to the host computer software to identify the end user. Securely communicate with the bound device and send the end-user's digital signature to the device; After receiving the digital signature of the end user, the device performs end user authentication. Once the authentication is successful, the device is unlocked, and the host computer software controls the device to operate.

[0005] Preferably, the authorization data may also include an operating environment identifier, which includes the computer's hardware environment identifier and software environment identifier.

[0006] Preferably, the computer's software environment identifier includes SDK authorization information, which includes the SDK's license ID or authorization validity period.

[0007] Preferably, the computer's hardware environment identifier includes one or more combined hash values ​​of MAC address, hard disk number, and CPU number.

[0008] Preferably, the Level 1 customer authentication involves matching the upstream vendor's private key, Level 1 customer number, and device serial number in the authorization file with the upstream vendor's public key, Level 1 customer number, and device serial number stored locally on the device. If the two match, the authentication is successful, and the binding operation continues. If the two do not match, the authentication fails, and the binding operation is terminated.

[0009] Preferably, during the Level 1 customer authentication process, if the authorization file includes the computer's hardware environment identifier, then the computer's hardware environment identifier in the authorization file needs to be matched with the hardware environment identifier of the computer running the binding program. If the two match, the verification is successful and the binding continues; if the two do not match, the verification fails and the binding program is terminated.

[0010] Preferably, during the Level 1 customer authentication process, if the authorization file includes a computer's software environment identifier, then the computer's software environment identifier in the authorization file needs to be matched with the software environment identifier of the computer running the binding program. If the two match, the verification is successful and the binding continues; if the two do not match, the verification fails and the binding program is terminated.

[0011] Preferably, end-user authentication involves matching the device's private key, which matches the instructions from the host computer software, with the device's public key stored locally on the device. If the two match, the authentication is successful, and the unlocking operation continues. If the two do not match, the authentication fails, and the unlocking operation is terminated.

[0012] Preferably, the host computer software instruction also includes an operating environment identifier. If the device side stores the operating environment identifier, the device will match the operating environment identifier in the host computer software instruction with the operating environment identifier stored on the device side before or after unlocking. The two must match completely; otherwise, the unlocking request will be rejected.

[0013] On the other hand, the present invention provides an authorization system based on multi-factor binding of devices and host computer software, for executing the above-mentioned authorization method based on multi-factor binding of devices and host computer software, including a factory-programmed program, a binding authorization management program, a device binding program, and a host computer program; The factory-programmed program is a program that upstream manufacturers use to securely solidify core identity information into the read-only storage area of ​​the device before shipping it to a primary customer. The binding authorization management program is a program used by upstream manufacturers to generate authorization files for devices based on authorization data from Tier 1 customers; Device binding program is a program that Tier 1 customers use to bind devices using authorization documents obtained from upstream manufacturers; The host computer program is the program used by the end user for daily operations and to control the operation of the equipment.

[0014] Compared with the prior art, the beneficial effects of the present invention are: 1. Achieving a leap from "two-dimensional binding" to "multi-dimensional binding": This invention breaks through the traditional "device-software" two-dimensional binding model and innovatively introduces a third dimension (software operating environment, specifically development tool authorization, SDK authorization number) and a fourth dimension (hardware operating environment, specifically computer motherboard or hard drive ID), forming a deeper and more difficult-to-crack authorization system.

[0015] 2. Offers greater control granularity and flexibility: Upstream manufacturers can flexibly choose binding factors (device only, device + software, device + software + specific host, etc.) based on the needs of Tier 1 customers and product strategies, to implement different security levels of authorization policies, ranging from lenient to extremely strict.

[0016] 3. An end-to-end integrity protection chain has been built: authorization control extends from the device all the way to the software development stage (SDK license) and the software runtime stage (host environment), ensuring that the entire chain from code writing to function execution is in a trusted state.

[0017] 4. Enhanced anti-copying and anti-diffusion capabilities: By binding specific computer hardware information, even if the licensed software and licensed files are copied at the same time, they cannot run on unauthorized computers, greatly reducing the risk of piracy and unauthorized dissemination.

[0018] 5. An innovative "one-time unlock within a session" authentication model was proposed and combined with multi-factor binding, which ensures both security and performance.

[0019] 6. Offline environment, does not rely on external network. Attached Figure Description

[0020] Figure 1 This is a flowchart of an authorization method for binding devices and host computer software based on multi-factor binding, as described in this invention. Figure 2 This is a schematic diagram of an authorization system based on multi-factor binding of devices and host computer software as described in this invention. Detailed Implementation

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

[0022] like Figure 1 As shown, this invention provides an authorization method for binding devices and host computer software based on multiple factors, comprising the following steps: S1: Upstream manufacturers securely embed core identity information into the device's read-only storage area through factory programming. Core identity information includes the upstream vendor's public key, device model, device serial number, and primary customer number. The upstream vendor's public key and private key form a pair, serving as the root of trust for the entire system. Both the device serial number and the primary customer number are unique, enabling identification of the device and the primary customer. The factory-programmed firmware is controlled by the upstream vendor, ensuring the initial trusted entry of the device's identity. The device typically integrates a computer that can run host computer programs; alternatively, the device can be equipped with an external computer.

[0023] S2: Upstream manufacturers generate authorization files for devices by binding the authorization management program based on the authorization data of Tier 1 customers; When an upstream manufacturer sells equipment to a Tier 1 customer, it first receives authorization data from the Tier 1 customer. This authorization data includes the Tier 1 customer ID, device serial number, application scenario ID (APP_ID), and Tier 1 customer public key. The Tier 1 customer ID and device serial number have already been written to the device's read-only storage area in step S1. The application scenario ID specifies the application scenario of the device, such as inkjet printing or biochemical synthesis technology. The Tier 1 customer public key and private key are a pair, used to verify identity when the device is bound to the host computer software's operating environment. The authorization data may also include an operating environment identifier, which includes both the computer's hardware and software environment identifiers.

[0024] The computer's software environment identifier includes SDK authorization information, which includes the SDK's license ID or authorization validity period. The computer's hardware environment identifier includes one or more combined hash values ​​of MAC address, hard disk serial number, and CPU serial number. The binding authorization management software uses the upstream vendor's private key (MANUFACTURER_PRIVATE_KEY) to perform a first-level customer identity digital signature on the authorization data. The binding authorization management software must be run in a secure environment to ensure that the upstream vendor's private key is not leaked. The binding license management software outputs a standard, tamper-proof license file and sends it to the primary customer; The factory-programmed program and the binding license management software can be two separate programs, or they can be integrated into one software as two functional modules.

[0025] S3: Tier 1 customers use the authorization documents obtained from upstream manufacturers to perform device binding operations through the device binding program; At this point, the equipment is shipped from the upstream manufacturer to the primary customer. The device binding program integrates or dynamically loads the authorization file from the upstream vendor during runtime. After establishing communication with the device, it sends a binding request to the device. The binding request includes a digital signature of the primary customer identity and authorization data. Upon receiving the digital signature of the primary customer identity, the device performs primary customer authentication. First, it matches the upstream vendor's private key, primary customer number, and device serial number in the authorization file with the upstream vendor's public key, primary customer number, and device serial number stored locally on the device. If they match, the verification is successful, and the binding operation continues; otherwise, the verification fails, and the binding operation terminates. Second, if the authorization file also includes the computer's hardware environment identifier, it needs to be matched with the hardware environment identifier of the computer running the binding program. If they match, the verification is successful, and the binding operation continues; otherwise, the verification fails, and the binding program terminates. Third, if the authorization file also includes the computer's software environment identifier, it needs to be matched with the software environment identifier of the computer running the binding program. If they match, the verification is successful, and the binding operation continues; otherwise, the verification fails, and the binding program terminates. After successful verification, the device saves the binding information, completing the binding verification process.

[0026] Tier 1 customers can develop dedicated host computer software with specific service functions based on the end user's needs, and ship it to the end user along with the equipment.

[0027] S4: The end user connects to the host computer software and device to control the operation of the device; After completing development on the device, the Tier 1 customer delivers the bound device and host computer software to the end user. The end user installs the host computer software on the computer integrated with or connected to the device. The host computer software dynamically loads the Tier 1 customer's private key corresponding to the Tier 1 customer's public key bound to the device, either built into the device or during runtime. The end user uses the primary client's private key to digitally sign the instructions to the host computer software to identify the end user. Securely communicate with the bound device and send the end-user's digital signature to the device; After receiving the digital signature of the end user, the device performs end user authentication. Once the authentication is successful, the device is unlocked, and the host computer software controls the device to operate. End-user authentication involves matching the device's private key, which is matched with the host computer software instructions, with the device's public key stored locally on the device. If they match, the authentication is successful, and the unlocking operation continues. If they do not match, the authentication fails, and the unlocking operation is terminated. The host computer software instructions also include an operating environment identifier. If the device side stores an operating environment identifier, the device will match the operating environment identifier in the host computer software instructions with the operating environment identifier stored on the device side before or after unlocking. If the operating environment identifier on the device side only includes the computer's software environment identifier, the computer's software environment identifier in the host computer software instructions will be matched with it. If they are the same, the verification passes; otherwise, the verification fails. If the operating environment identifier on the device side only includes the computer's hardware environment identifier, the computer's hardware environment identifier in the host computer software instructions will be matched with it. If they are the same, the verification passes; otherwise, the verification fails. If the operating environment identifier on the device side includes both the computer's software environment identifier and hardware environment identifier, the computer's software environment identifier and hardware environment identifier in the host computer software instructions will be matched with it. If both the software and hardware environment identifiers are the same, the verification passes; otherwise, the verification fails.

[0028] Only when the verification is successful and the unlock request is approved can the host computer software communicate normally with the device and control its operation; otherwise, the unlock request will be rejected.

[0029] On the other hand, such as Figure 2 As shown, the present invention provides an authorization system based on multi-factor binding of devices and host computer software, used to execute the above-mentioned authorization method based on multi-factor binding of devices and host computer software. The authorization system includes a factory-programmed program, a binding authorization management program, a device binding program, and a host computer program. The factory-programmed program is a program that upstream manufacturers use to securely solidify core identity information into the read-only storage area of ​​the device before shipping it to a primary customer. The binding authorization management program is a program used by upstream manufacturers to generate authorization files for devices based on authorization data from Tier 1 customers; Device binding program is a program that Tier 1 customers use to bind devices using authorization documents obtained from upstream manufacturers; The host computer program is the program used by the end user for daily operations and to control the operation of the equipment. The above four programs can be individual programs or combined as functional modules integrated into one software. Typically, the factory-programmed program and the binding license management software are mainly used by upstream manufacturers and can be installed on the upstream manufacturer's computer either individually or as an integrated program. The device binding program is mainly used by Tier 1 customers and can be installed on Tier 1 customers' computers either individually or as an integrated program, as Tier 1 customers need to use the Tier 1 software during the development process. The Tier 1 program is mainly used by end users and is installed on the end user's external computer or the computer on which the device is integrated.

Claims

1. An authorization method for binding a device to host software based on multiple factors, the method comprising: Includes the following steps, ​ S1: Upstream manufacturers securely embed core identity information into the device's read-only storage area through factory programming. Core identity information includes the upstream vendor's public key, device model, device serial number, and primary customer number; S2: Upstream manufacturers generate authorization files for devices by binding the authorization management program based on the authorization data of Tier 1 customers; Upstream manufacturers receive authorization data from Tier 1 customers. The authorized data includes the primary customer number, device serial number, application scenario number, primary customer public key, and operating environment identifier, which includes the computer's hardware environment identifier and software environment identifier. The hardware environment identifier of a computer includes one or more combined hash values ​​of MAC address, hard disk serial number, and CPU serial number; The software environment identifier of a computer includes SDK licensing information, which includes the SDK's license ID or license validity period; The binding authorization management software uses the upstream vendor's private key to perform a first-level customer identity digital signature on the authorization data; The binding license management software outputs a standard, tamper-proof license file and sends it to the primary customer; S3: Tier 1 customers use the authorization documents obtained from upstream manufacturers to perform device binding operations through the device binding program; The device binding program integrates or loads the authorization file to establish communication with the device; The device binding program sends a binding request to the device, which includes a first-level customer identity digital signature and authorization data; After receiving the digital signature of the primary customer's identity, the device performs primary customer identity verification. Once the verification is successful, the device saves the binding information and completes the binding verification process. S4: The end user connects to the host computer software and device to control the operation of the device; The end user uses the primary client's private key to digitally sign the instructions to the host computer software to identify the end user. Securely communicate with the bound device and send the end-user's digital signature to the device; After receiving the digital signature of the end user, the device performs end user authentication. Once the authentication is successful, the device is unlocked, and the host computer software controls the device to operate.

2. The authorization method for binding devices and host computer software based on multi-factor binding according to claim 1, characterized in that: Level 1 customer authentication involves matching the upstream vendor's private key, Level 1 customer number, and device serial number in the authorization file with the upstream vendor's public key, Level 1 customer number, and device serial number stored locally on the device. If they match, the authentication is successful, and the binding operation continues. If they do not match, the authentication fails, and the binding operation is terminated.

3. The authorization method for binding devices and host computer software based on multi-factor binding according to claim 2, characterized in that: During the Level 1 customer authentication process, if the authorization file includes the computer's hardware environment identifier, then the computer's hardware environment identifier in the authorization file needs to be matched with the hardware environment identifier of the computer running the binding program. If the two match, the verification is successful and the binding continues; if the two do not match, the verification fails and the binding program is terminated.

4. The authorization method for binding devices and host computer software based on multi-factor binding according to claim 3, characterized in that: During the Level 1 customer authentication process, if the authorization file includes the computer's software environment identifier, then the computer's software environment identifier in the authorization file needs to be matched with the software environment identifier of the computer running the binding program. If the two match, the verification is successful and the binding continues; if the two do not match, the verification fails and the binding program is terminated.

5. The authorization method for binding devices and host computer software based on multi-factor binding according to claim 4, characterized in that: End-user authentication involves matching the device's private key, which is matched with the host computer software instructions, with the device's public key stored locally on the device. If they match, the authentication is successful, and the unlocking operation continues. If they do not match, the authentication fails, and the unlocking operation is terminated.

6. The authorization method for binding devices and host computer software based on multi-factor binding according to claim 5, characterized in that: The host computer software instructions also include an operating environment identifier. If the device side stores the operating environment identifier, the device will match the operating environment identifier in the host computer software instructions with the operating environment identifier stored on the device side before or after unlocking. The two must match completely; otherwise, the unlocking request will be rejected.

7. An authorization system based on multi-factor binding of devices and host computer software, characterized in that: The method for performing the authorization method according to any one of claims 1-6 includes a factory-programmed program, a binding authorization management program, a device binding program, and a host computer program; The factory-programmed program is a program that upstream manufacturers use to securely solidify core identity information into the read-only storage area of ​​the device before shipping it to a primary customer. The binding authorization management program is a program used by upstream manufacturers to generate authorization files for devices based on authorization data from Tier 1 customers; Device binding program is a program that Tier 1 customers use to bind devices using authorization documents obtained from upstream manufacturers; The host computer program is the program used by the end user for daily operations and to control the operation of the equipment.

Images