Certificate chain equipment authorization method applied to cloud side collaborative system
Through the certificate chain device authorization method, using X.509 certificate and public key infrastructure, the hardware information acquisition and security problems of device authorization management in the cloud-edge collaborative system are solved, and high credibility and security authorization management are achieved. Reduced dependence on hardware manufacturers.
Patent Information
- Application Number
- CN202411215002.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-30
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2044-08-30
AI Technical Summary
In the existing cloud-edge collaborative system, there are problems such as hardware information acquisition and consistency, security dependence on hardware manufacturers, and high risk of private key leakage.
The certificate chain device authorization method is adopted to generate root certificates and multi-level certificate chains, and the X.509 certificate and public key infrastructure are used to encrypt and sign device authorization information to ensure the legality and security of the authorization certificate.
Reduce dependence on hardware manufacturers, improve the security and trust of the authorization system, ensure the credibility and effectiveness of the authorization files, and avoid the risk of private key leakage.
Smart Images

Figure CN118972072A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of cloud-edge collaboration, and in particular to a method for authorizing a certificate chain device applied to a cloud-edge collaboration system. Background Art
[0002] The cloud-edge collaborative system is a distributed computing architecture that distributes computing and data processing tasks between the cloud and edge devices. Cloud computing provides powerful computing and storage capabilities, while edge computing sinks computing and storage resources close to data sources and users to reduce latency and improve real-time performance. Through intelligent scheduling and management, the cloud-edge collaborative system enables the cloud and edge to work together to maximize resource utilization and service quality.
[0003] To ensure the security and integrity of their devices, edge device hardware manufacturers typically face the following requirements and possible defects: security requirements; device identity authentication, ensuring that authorization files can only authorize a single fixed device; authorization management requirements; access control, setting and managing which devices have the right to access specific resources or perform specific operations; authorization scope limitation, ensuring that each device can only run and perform operations within its authorized scope to avoid operations that exceed the authority; operational and management efficiency; simplified deployment and configuration, making the authorization management system easy to deploy and configure to reduce the complexity of equipment production lines and operations and maintenance.
[0004] In order to ensure that the device operates safely within the authorized scope, prevent unauthorized devices or operations, and prevent security issues caused by the leakage of authorization certificates, only hardware manufacturers can generate authorization files and then provide them to customers through suppliers or directly. The specific solutions adopted by the existing technology are as follows:
[0005] 1. Edge device authorization
[0006] Generate a machine code file through the hardware information of the device motherboard, and then generate and encrypt a license to generate an authorization lic file. The device loads the lic file to verify whether the machine code information is consistent with the hardware information of the device motherboard to perform authorization. The general steps are as follows:
[0007] (1) Obtain device hardware information:
[0008] Collect the unique hardware identification information of the device, which usually includes the motherboard serial number, CPU ID, MAC address, etc. This hardware information can be obtained through the device's BIOS, operating system interface, or dedicated tools.
[0009] (2) Generate machine code:
[0010] The collected hardware information is concatenated to form a unique string.
[0011] This string is hashed using a hash algorithm (such as SHA-256) to generate a fixed-length machine code. This machine code will be used as the unique identifier of the device for subsequent license generation and verification.
[0012] (3) Create a license file:
[0013] Create a license file containing device authorization information based on the generated machine code. The license file can contain information such as machine code, authorization period, device function permissions, etc.
[0014] (4) Encrypted license file:
[0015] The license file is encrypted using a public key encryption algorithm such as RSA. This ensures the security of the license file during transmission and storage, preventing unauthorized access and tampering. In the process of public key encryption, the public key is used for encryption and the private key is used for decryption. The public key generated by the manufacturer will be used to encrypt the license of the device, and the private key saved on the device side will be used to decrypt and verify the license.
[0016] 2. Loading and verifying the license on the device
[0017] On the device side, load the license file into memory or storage. Use the private key saved on the device side to decrypt the license file. After decryption, obtain the authorization information and machine code in the license. Obtain the current hardware information from the device hardware again and generate the machine code. Compare the machine code in the decrypted license with the currently generated machine code. If they match, the verification passes, indicating that the license is generated for the device and the device can run normally. If they do not match, the verification fails and the device cannot run.
[0018] The above-mentioned prior art solutions have the following disadvantages:
[0019] (1) It is difficult to obtain and ensure the consistency of hardware information: the machine code is inconsistent after the equipment is repaired and some hardware is replaced.
[0020] (2) Security: Once the private key stored on the device is leaked, an attacker can decrypt and forge the license, rendering the entire authorization system invalid.
[0021] (3) Dependence on hardware manufacturers: The implementation of this solution requires the hardware manufacturer to provide a consistent and reliable method for obtaining hardware information. If the hardware manufacturer does not provide relevant support or changes the acquisition method, it will bring difficulties to the implementation of the solution. Summary of the invention
[0022] The present invention provides a method for authorizing a certificate chain device applied to a cloud-edge collaborative system, so as to solve the technical problems existing in the above-mentioned prior art.
[0023] To achieve the above object, the present invention provides a method for certificate chain device authorization applied to a cloud-edge collaborative system, which includes:
[0024] S1: Generate the first private key and root certificate, and save the root certificate on the device;
[0025] S2: Generate a cloud platform intermediate certificate and a second private key, a third-party authorization certificate and a third private key based on the root certificate;
[0026] S3: The third-party authorization certificate holder sends an authorization request to the cloud platform, which includes device information and authorization information;
[0027] S4: After receiving the authorization request, the cloud platform uses the second private key to encrypt and encapsulate the authorization information into the extension field to generate a CSR, and then uses the cloud platform intermediate certificate and the second private key to sign and generate a device authorization certificate, and packages the device authorization certificate and the cloud platform intermediate certificate to generate a certificate chain package and return it to the third-party authorization certificate holder;
[0028] S5: After receiving the certificate chain, the third-party authorization certificate holder parses the device authorization certificate signed by the cloud platform, extracts the public key of the cloud platform intermediate certificate, uses the public key to parse the authorization information in the device authorization certificate, and re-encrypts the third private key to generate new authorization information, which is then encapsulated into the extension field to generate a CSR. After that, the third-party authorization certificate and the third private key are used to sign a new device authorization certificate, and the third-party authorization certificate, the received cloud platform intermediate certificate, and the signed device authorization certificate are packaged to form a three-level certificate chain;
[0029] S6: The device loads the three-level certificate chain and uses the root certificate saved on the device to verify whether the third-party authorization certificate and the cloud platform intermediate certificate in the three-level certificate chain are signed by the root certificate. If so, the third-party authorization certificate is further parsed and the public key information is extracted. The authorization information in the third-party authorization certificate is then parsed using the public key. The authorization information is compared with the device information on the device itself. If the two are consistent, it is confirmed that the certificate is reliable and the authorization information is valid.
[0030] In one embodiment of the present invention, in step S1, a first private key and a root certificate are generated by OpenSSL.
[0031] In one embodiment of the present invention, in step S2, the device information is a unique device identification code, and the authorization information includes an authorization time, an authorization algorithm, and an authorization resource limit.
[0032] In one embodiment of the present invention, the root certificate, the cloud platform intermediate certificate, the third-party authorization certificate, and the device authorization certificate are all X.509 certificates.
[0033] In one embodiment of the present invention, in step S2, a third-party authorization certificate and a third private key are generated for each third-party authorization certificate holder.
[0034] The method for certificate chain device authorization applied to the cloud-edge collaborative system provided by the present invention is suitable for edge device management in the fields of security, smart city, and smart home. In general, the present invention has the following beneficial technical effects:
[0035] (1) The present invention reduces the dependence on hardware manufacturers. It is no longer necessary to rely on specific hardware information or interfaces provided by hardware manufacturers. Distributors and agents at all levels can generate authorization files on their own, which facilitates business expansion, greatly improves business flexibility and scalability, and ensures the credibility and effectiveness of authorization files.
[0036] (2) Ensure the credibility and validity of the authorization file: With the help of X.509 certificate chain and public key infrastructure (PKI) standards, the present invention ensures that the generated device authorization certificate has a high degree of credibility and legitimacy. Each authorization file is signed and encrypted by the cloud platform and the third-party authorization party, ensuring the security and accuracy of the authorization information.
[0037] (3) Improve the security of the authorization system: Through the public key encryption and private key decryption mechanism, the present invention effectively protects the security of the authorization file during transmission and storage. The private key on the device side is only used to decrypt and verify the license, avoiding the risks that may be caused by the leakage of the private key and ensuring the security and stability of the entire authorization system.
[0038] (4) Support multi-level certificate chain verification: The three-level certificate chain verification mechanism loaded on the device ensures the source and legitimacy of the authorization certificate. By verifying the certificates issued by the cloud platform and the third-party authorization party, combined with the unique identification information of the device itself, the reliability and validity of the authorization information are ensured, thus improving the trust of the authorization system. 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 some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0040] Figure 1 A framework diagram of a method for authorizing a certificate chain device applied to a cloud-edge collaborative system provided by the present invention;
[0041] Figure 2 This is a flow chart of the execution process of the cloud platform in step S4;
[0042] Figure 3 This is a flowchart of the execution process of step S5 third-party authorization service;
[0043] Figure 4 This is a flow chart of the execution process of step S6 on the device side (edge device). DETAILED DESCRIPTION
[0044] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0045] like Figure 1 What is shown is a framework diagram of the method for authorizing the certificate chain device applied to the cloud-edge collaborative system provided by the present invention. The method for authorizing the certificate chain device applied to the cloud-edge collaborative system provided by the present invention mainly includes three parts: certificate management, authorization service and edge device.
[0046] The present invention provides a method for certificate chain device authorization applied to a cloud-edge collaborative system, which includes:
[0047] S1: Generate the first private key and root certificate, and save the root certificate on the device;
[0048] S2: Generate a cloud platform intermediate certificate and a second private key, a third-party authorization certificate and a third private key based on the root certificate;
[0049] S3: The third-party authorization certificate holder sends an authorization request to the cloud platform, which includes device information and authorization information;
[0050] S4: Figure 2 The flowchart of the execution process of the cloud platform in step S4 is shown. After receiving the authorization request, the cloud platform uses the second private key to encrypt and encapsulate the authorization information into the extension field (Extensions) to generate a CSR (data file of the certificate signing request), and then uses the cloud platform intermediate certificate and the second private key to sign and generate a device authorization certificate. The device authorization certificate and the cloud platform intermediate certificate are packaged to generate a certificate chain and returned to the third-party authorization certificate holder. Step S4 is Figure 1 The third-party authorization intermediate service 1;
[0051] S5: Figure 3The flowchart of the execution process of the third-party authorization service in step S5 is shown. After receiving the certificate chain, the third-party authorization certificate holder parses the device authorization certificate signed by the cloud platform, extracts the public key of the cloud platform intermediate certificate, uses the public key to parse the authorization information in the device authorization certificate, and re-encrypts the generated new authorization information with the third private key, and then encapsulates it into the extension field to generate CSR. After that, the third-party authorization certificate and the third private key are used to sign and generate a new device authorization certificate, and the third-party authorization certificate, the received cloud platform intermediate certificate and the signed device authorization certificate are packaged to form a three-level certificate chain. Step S5 is Figure 1 The third-party authorization intermediate service 2;
[0052] S6: Figure 4 The flowchart of the execution process of step S6 device side (edge device) is shown. The device side loads the three-level certificate chain, and uses the root certificate saved on the device side to verify whether the third-party authorization certificate and the cloud platform intermediate certificate in the three-level certificate chain are signed by the root certificate. If so, the third-party authorization certificate is further parsed and the public key information is extracted. After that, the authorization information in the third-party authorization certificate is parsed using the public key, and the authorization information is compared with the device information of the device side. If the two are consistent, it is confirmed that the certificate is reliable and the authorization information is valid. After confirming that the above information is valid, the authorization time, authorization service and other information can be further loaded on the device side.
[0053] In one embodiment of the present invention, in step S1, the first private key and the root certificate are generated by OpenSSL. OpenSSL is a powerful open source toolkit and cryptographic library widely used in the fields of secure communication and network security. It supports a variety of encryption algorithms, digital certificate management, and secure communication protocols, providing a reliable infrastructure and tools for secure communication.
[0054] In one embodiment of the present invention, in step S2, the device information is a unique device identification code, and the authorization information includes an authorization time, an authorization algorithm, and an authorization resource limit.
[0055] In one embodiment of the present invention, the root certificate, cloud platform intermediate certificate, third-party authorization certificate, and device authorization certificate are all X.509 certificates. X.509 is a widely used public key infrastructure (PKI) standard for managing digital certificates and public key pairs. It specifies the format and verification algorithm of digital certificates and is one of the core technologies to ensure the security of network communications. The basic structure of an X.509 certificate includes a version number, a serial number, a signature algorithm identifier, an issuer name, a validity period, a subject name, a subject public key information, an extension field, and a signature.
[0056] In one embodiment of the present invention, in step S2, a third-party authorization certificate and a third private key are generated for each third-party authorization certificate holder.
[0057] The present invention is a method for generating a three-level x.509 certificate chain based on OpenSSL. The method is not limited to device authorization and can be applied to authorization in multiple scenarios, such as software license authorization, algorithm service authorization, web service authorization, etc.
[0058] The method for certificate chain device authorization applied to the cloud-edge collaborative system provided by the present invention is suitable for edge device management in the fields of security, smart city, and smart home. In general, the present invention has the following beneficial technical effects:
[0059] (1) The present invention reduces the dependence on hardware manufacturers. It is no longer necessary to rely on specific hardware information or interfaces provided by hardware manufacturers. Distributors and agents at all levels can generate authorization files on their own, which facilitates business expansion, greatly improves business flexibility and scalability, and ensures the credibility and effectiveness of authorization files.
[0060] (2) Ensure the credibility and validity of the authorization file: With the help of X.509 certificate chain and public key infrastructure (PKI) standards, the present invention ensures that the generated device authorization certificate has a high degree of credibility and legitimacy. Each authorization file is signed and encrypted by the cloud platform and the third-party authorization party, ensuring the security and accuracy of the authorization information.
[0061] (3) Improve the security of the authorization system: Through the public key encryption and private key decryption mechanism, the present invention effectively protects the security of the authorization file during transmission and storage. The private key on the device side is only used to decrypt and verify the license, avoiding the risks that may be caused by the leakage of the private key and ensuring the security and stability of the entire authorization system.
[0062] (4) Support multi-level certificate chain verification: The three-level certificate chain verification mechanism loaded on the device ensures the source and legitimacy of the authorization certificate. By verifying the certificates issued by the cloud platform and the third-party authorization party, combined with the unique identification information of the device itself, the reliability and validity of the authorization information are ensured, thus improving the trust of the authorization system.
[0063] Those skilled in the art can understand that the accompanying drawings are only schematic diagrams of an embodiment, and the modules or processes in the accompanying drawings are not necessarily required to implement the present invention.
[0064] Those skilled in the art can understand that the modules in the device in the embodiment can be distributed in the device in the embodiment according to the description of the embodiment, or can be changed accordingly and located in one or more devices different from the embodiment. The modules in the above embodiment can be combined into one module, or can be further divided into multiple sub-modules.
[0065] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims
1. A method for certificate chain device authorization applied to a cloud-edge collaborative system, characterized in that: include: S1: Generate the first private key and root certificate, and save the root certificate on the device; S2: Generate a cloud platform intermediate certificate and a second private key, a third-party authorization certificate and a third private key based on the root certificate; S3: The third-party authorization certificate holder sends an authorization request to the cloud platform, which includes device information and authorization information; S4: After receiving the authorization request, the cloud platform uses the second private key to encrypt and encapsulate the authorization information into the extension field to generate a CSR, and then uses the cloud platform intermediate certificate and the second private key to sign and generate a device authorization certificate, and packages the device authorization certificate and the cloud platform intermediate certificate to generate a certificate chain package and return it to the third-party authorization certificate holder; S5: After receiving the certificate chain, the third-party authorization certificate holder parses the device authorization certificate signed by the cloud platform, extracts the public key of the cloud platform intermediate certificate, uses the public key to parse the authorization information in the device authorization certificate, and re-encrypts the third private key to generate new authorization information, which is then encapsulated into the extension field to generate a CSR. After that, the third-party authorization certificate and the third private key are used to sign a new device authorization certificate, and the third-party authorization certificate, the received cloud platform intermediate certificate, and the signed device authorization certificate are packaged to form a three-level certificate chain; S6: The device loads the three-level certificate chain and uses the root certificate saved on the device to verify whether the third-party authorization certificate and the cloud platform intermediate certificate in the three-level certificate chain are signed by the root certificate. If so, the third-party authorization certificate is further parsed and the public key information is extracted. The authorization information in the third-party authorization certificate is then parsed using the public key. The authorization information is compared with the device information on the device itself. If the two are consistent, it is confirmed that the certificate is reliable and the authorization information is valid.
2. The method for certificate chain device authorization applied to a cloud-edge collaborative system according to claim 1 is characterized in that: In step S1, a first private key and a root certificate are generated through OpenSSL.
3. The method for certificate chain device authorization applied to a cloud-edge collaborative system according to claim 1 is characterized in that: In step S2, the device information is the unique identification code of the device, and the authorization information includes the authorization time, the authorization algorithm and the authorization resource limit.
4. The method for certificate chain device authorization applied to a cloud-edge collaborative system according to claim 1, characterized in that: Root certificates, cloud platform intermediate certificates, third-party authorization certificates, and device authorization certificates are all X.509 certificates.
5. The method for certificate chain device authorization applied to a cloud-edge collaborative system according to claim 1, characterized in that: In step S2, a third-party authorization certificate and a third private key are generated for each third-party authorization certificate holder.
Citation Information
Patent Citations
Terminal identity authentication method, apparatus and system
CN107294722A
Certificate verification method and device based on block chain, storage medium and electronic device
CN110011988A
Method for realizing APK unified signature by using three-level certificate authentication
CN112560017A
Cloud edge cooperation system, method and device for device access control
CN115455395A
Mutual authentication between clusters
US20230353392A1
