HK40104466A - Block chain-based production material management method, device and electronic equipment - Google Patents

Description

Blockchain-based methods, devices, and electronic equipment for managing means of production.

Technical Field

This application relates to the technical field of blockchain, specifically to blockchain-based methods, apparatus, and electronic devices for managing means of production.

Background Technology

Means of production refer to the various resources and equipment used by an enterprise in the production process to manufacture products or provide services, generally including both tangible and intangible aspects. Intangible means of production include technology, patents, brands, and human resources; these factors play an important role in the production process but are not in concrete material form. Tangible means of production mainly include raw materials, equipment, tools, and buildings; these are physical items directly used in the production process. Raw materials are the basic components of products, equipment and tools are used for processing and manufacturing, and buildings provide production and office space. An enterprise's means of production are the foundation for achieving production goals and improving production efficiency; their rational allocation and management are crucial to the enterprise's development.

Traditional methods of managing means of production rely heavily on manual operations, documentation, and centralized planning, resulting in low efficiency, inaccurate data, and slow response times. With the development of information technology, modern enterprises are increasingly adopting advanced digital and automation technologies, such as the Internet of Things, big data analytics, and artificial intelligence, to improve the efficiency and accuracy of means of production management.

However, even with advanced digital and automation technologies, enterprises still face challenges in the accuracy of production resource management. This is because centralized management relies excessively on central management equipment; if this equipment is attacked, production resource data can be tampered with, resulting in false data changes. This reduces the security of production resources and could even lead to production interruptions and other adverse consequences. Therefore, a method to improve the security of production resource management is needed.

Summary of the Invention

This application provides a blockchain-based method, apparatus, and electronic device for managing means of production, which improves the security of means of production management.

The first aspect of this application provides a blockchain-based method for managing means of production, applied to a first server, wherein the first server is any one of a plurality of servers included in a blockchain management system, and the plurality of servers are interconnected. The method includes:

Obtain user-inputted change data for production materials, wherein the change data is the increase or decrease data of the production materials;

The changed data is encrypted using the user's private key to generate a digital signature;

The changed data is encrypted using the public keys of each server to generate encrypted data. The public key of each server is the public key of the second server, which is a server other than the first server among the multiple servers.

The digital signatures are sent to each of the second servers respectively;

After receiving the verification information for the digital signature sent by each of the second servers, the encrypted data is sent to each of the second servers so that each of the second servers can synchronize the changed data.

By adopting the above technical solution, when a user needs to modify production materials, the first server generates a digital signature based on the modified data, which is then verified by the second server. The encrypted data is then sent to each of the second servers, ensuring that each server can verify the authenticity and integrity of the data. Once the digital signature verification is successful, the second server can synchronously encrypt the data, ensuring data consistency. Furthermore, this application uses a decentralized distributed ledger based on blockchain, with each server having a copy of the modified data. Compared to traditional centralized management, decentralization reduces reliance on a single central management device, minimizing the risk of single points of failure and attacks. Each server participates in the verification and storage of modified data, reducing the possibility of production material data being maliciously tampered with into false changes, thus improving the security of production materials.

Optionally, the step of encrypting the changed data using the user's private key to generate a digital signature specifically includes:

Perform a hash operation on the changed data to obtain the hash value of the changed data;

The hash value is encrypted using the user's private key to obtain the digital signature, so that the second server can decrypt the digital signature using the user's public key corresponding to the user's private key to obtain the hash value.

By employing the above technical solution, firstly, a hash operation is performed on the changed data to obtain a hash value. A hash operation is a one-way function that transforms changed data into a unique hash value of fixed length, which helps ensure the uniqueness and irreversibility of the changed data. Next, the hash value is encrypted using the user's private key to generate a digital signature. This digital signature, obtained by encrypting the hash value with the private key, can only be decrypted using the user's public key. This step achieves the digital signature of the changed data, ensuring the uniqueness of the signature and the authenticity of the user's identity.

Optionally, the step of encrypting the changed data using the public keys of each server to generate encrypted data specifically includes:

The changed data is encrypted using the target public key to obtain intermediate encrypted data, so that the target server can decrypt the intermediate encrypted data using the target private key corresponding to the target public key to obtain the changed data. The target public key is the public key corresponding to the target server, and the target server is any one of a plurality of second servers.

The intermediate encrypted data is encrypted using the user's private key to obtain the encrypted data, so that the second server can decrypt the encrypted data using the user's public key corresponding to the user's private key to obtain the intermediate encrypted data.

By employing the above technical solution, the changed data is encrypted using the target's public key to obtain intermediate encrypted data. This intermediate encrypted data is encrypted using the target server's public key, and only the target server with the corresponding private key can decrypt it. This step achieves target server authentication and confidentiality protection for the changed data. The intermediate encrypted data is then encrypted again using the user's private key to obtain the final encrypted data. This encrypted data protects the confidentiality of the intermediate encrypted data during transmission, and only the user's public key can decrypt it. This step achieves dual protection for the encrypted data through user authentication and re-encryption.

Optionally, receiving the verification pass information for the digital signature sent by each of the second servers specifically includes:

The system receives a comparison pass message for the digital signature sent by the target server. The target server decrypts the digital signature using the user's public key corresponding to the user's private key to obtain the hash value. The target server decrypts the encrypted data using the target private key and performs a hash operation on the decryption result. The operation result is compared with the hash value. If it is determined that the operation result is consistent with the hash value, the comparison pass message is generated.

The verification pass information is determined by comparing the information.

By employing the above technical solution, the target server receives the verification information for the digital signature. The target server decrypts the digital signature using the user's public key to obtain a hash value. The pairing of the user's private key and the target public key ensures the validity of the digital signature. Only the user's private key and the target server's public key can correctly decrypt and verify the digital signature, preventing unauthorized signature verification. Subsequently, the target server decrypts the encrypted data using the target private key and performs a hash operation on the decryption result to generate a new hash value. Finally, the newly generated hash value is compared with the decrypted hash value; if they match, a verification message is generated. The target server decrypts the encrypted data using the target private key and performs a hash operation on the decryption result. Comparing the hash value with the hash value obtained from decrypting the digital signature ensures the integrity and authenticity of the data. This prevents unauthorized data decryption and tampering.

Optionally, after receiving the verification pass information for the digital signature sent by each of the second servers and sending the encrypted data to each of the second servers, the method further includes:

The system receives synchronization completion information from each of the second servers to determine that the production data change is complete. The second server decrypts the encrypted data using the server private key and generates the synchronization completion information after verifying the digital signature.

By employing the above technical solution, the first server ensures the synchronization of changed data across all second servers by sending encrypted data to them. Each second server receives and decrypts the data, verifies the digital signature, and generates a synchronization completion message, signifying successful synchronization of the changed data across all servers. This helps ensure that all participants receive the same, verified changed data, improving data consistency and trustworthiness. Furthermore, each second server, upon receiving the encrypted data, decrypts it using its private key and verifies the digital signature. Only when the digital signature verification is successful does the synchronization completion message generate. This ensures the integrity and authenticity of the data during transmission and storage, preventing the risk of data tampering or forgery.

Optionally, before encrypting the hash value using the user's private key to obtain the digital signature, so that the second server can decrypt the digital signature using the user's public key corresponding to the user's private key to obtain the hash value, the method further includes:

Perform a hash operation on the user's identity information code to obtain the result;

Set the result of the calculation as the user's private key;

The user's public key is generated using an asymmetric encryption algorithm based on the user's private key.

By employing the above technical solution, the user's identity information code is hashed to obtain a unique and irreversible hash result. This helps ensure the security and immutability of the user's identity information, providing a secure foundation for subsequent steps. The hash result of the identity information is set as the user's private key. This private key, obtained through hashing, is unique and irreversible, protecting the user's identity information. Generating the private key is a secure process, increasing the confidentiality of the user's identity information. Based on the generated private key, an asymmetric encryption algorithm is used to generate the user's public key. This public key is the counterpart to the private key and is used for subsequent digital signature generation and verification. The asymmetric encryption algorithm ensures the security of the public-private key pair, guaranteeing that only the private key holder can generate the corresponding digital signature.

Optionally, before encrypting the changed data using the public keys of each server to generate encrypted data, the method further includes:

Generate multiple random positive integers and multiple random letters;

Obtain the device identifier of the target server;

The target private key is obtained by inserting multiple random positive integers and multiple random letters into the device identifier;

Based on the target private key, the target public key is generated using an asymmetric encryption algorithm.

By employing the above technical solution, the generation of multiple random positive integers and random letters increases the complexity and randomness of the target private key. This design effectively prevents malicious attackers from obtaining the target private key through guessing or speculation, thus improving the security of the private key. The target server's device identifier is obtained, and random positive integers and random letters are inserted into the device identifier to form the target private key. This design associates the target private key with the specific device identifier of the target server, enhancing the uniqueness of the private key and the security of the device identifier. Based on the generated target private key, an asymmetric encryption algorithm is used to generate the target public key. This ensures that the target server can use the target public key corresponding to the generated target private key to decrypt data, while preventing unauthorized decryption attempts.

A second aspect of this application provides a blockchain-based production materials management device, wherein the device is a first server, including an acquisition module, an encryption module, and a sending module, wherein:

The acquisition module is used to acquire change data for production materials input by the user, wherein the change data is the increase or decrease data of the production materials;

The encryption module is used to encrypt the changed data using the user's private key and generate a digital signature;

The encryption module is used to encrypt the changed data using the public keys of each server to generate encrypted data. The public key of the server is the public key corresponding to the second server, and the second server is a server other than the first server among the multiple servers.

The sending module is used to send the digital signature to each of the second servers respectively;

The sending module is configured to receive the verification information for the digital signature sent by each of the second servers, and then send the encrypted data to each of the second servers so that each of the second servers can synchronize the changed data.

A third aspect of this application provides an electronic device including a processor, a memory, a user interface, and a network interface, wherein the memory is used to store instructions, the user interface and the network interface are both used to communicate with other devices, and the processor is used to execute the instructions stored in the memory to cause the electronic device to perform the method as described in any of the foregoing.

A fourth aspect of this application provides a computer-readable storage medium storing instructions that, when executed, perform the method described in any of the preceding descriptions.

In summary, one or more technical solutions provided in the embodiments of this application have at least the following technical effects or advantages:

When a user needs to modify production materials, the first server generates a digital signature based on the modified data, which is then verified by the second server. The encrypted data is then sent to each of the second servers, ensuring that each server can verify the authenticity and integrity of the data. Once the digital signature verification is successful, the second server can synchronously encrypt the data, ensuring data consistency. Furthermore, this application uses a decentralized distributed ledger based on blockchain, with each server having a copy of the modified data. Compared to traditional centralized management, decentralization reduces reliance on a single central management device, minimizing the risk of single points of failure and attacks. Each server participates in the verification and storage of modified data, reducing the possibility of production material data being maliciously tampered with into false changes, thus improving the security of production materials.

Attached Figure Description

Figure 1 is a flowchart illustrating the blockchain-based production materials management method disclosed in an embodiment of this application;

Figure 2 is a schematic diagram of an application scenario of the blockchain-based production materials management method disclosed in the embodiments of this application;

Figure 3 is a schematic diagram of a process for encrypting changed data and generating a digital signature disclosed in an embodiment of this application;

Figure 4 is a schematic diagram of a process for decrypting and verifying encrypted data disclosed in an embodiment of this application;

Figure 5 is a schematic diagram of the structure of the blockchain-based production materials management device disclosed in the embodiments of this application;

Figure 6 is a schematic diagram of the structure of an electronic device disclosed in an embodiment of this application.

Explanation of reference numerals in the attached drawings: 501, acquisition module; 502, encryption module; 503, transmission module; 601, processor; 602, communication bus; 603, user interface; 604, network interface; 605, memory.

Detailed Implementation

To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

In the description of the embodiments of this application, the words "for example" or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design that is described as "for example" or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design options. Rather, the use of the words "for example" or "for instance" is intended to present the relevant concepts in a specific manner.

In the description of the embodiments of this application, the term "multiple" means two or more. For example, multiple systems means two or more systems, and multiple screen terminals means two or more screen terminals. Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the indicated technical features. Thus, a feature defined with "first" or "second" may explicitly or implicitly include one or more of that feature. The terms "comprising," "including," "having," and variations thereof all mean "including but not limited to," unless otherwise specifically emphasized.

Means of production refer to the various resources and equipment used by an enterprise in the production process to manufacture products or provide services, generally including both tangible and intangible aspects. Intangible means of production include technology, patents, brands, and human resources; these factors play an important role in the production process but are not in concrete material form. Tangible means of production mainly include raw materials, equipment, tools, and buildings; these are physical items directly used in the production process. Raw materials are the basic components of products, equipment and tools are used for processing and manufacturing, and buildings provide production and office space. An enterprise's means of production are the foundation for achieving production goals and improving production efficiency; their rational allocation and management are crucial to the enterprise's development.

Traditional methods of managing means of production rely heavily on manual operations, documentation, and centralized planning, resulting in low efficiency, inaccurate data, and slow response times. With the development of information technology, modern enterprises are increasingly adopting advanced digital and automation technologies, such as the Internet of Things, big data analytics, and artificial intelligence, to improve the efficiency and accuracy of means of production management.

However, even with advanced digital and automation technologies, enterprises still face challenges in the accuracy of production resource management. This is because centralized management relies excessively on central management equipment; if this equipment is attacked, production resource data can be tampered with, resulting in false data changes. This reduces the security of production resources and could even lead to production interruptions and other adverse consequences. Therefore, a method to improve the security of production resource management is needed.

This embodiment discloses a blockchain-based method for managing production materials. Referring to Figure 1, it includes the following steps S110-S150:

S110, Obtain the change data for production materials input by the user.

The blockchain-based production materials management method disclosed in this application is applied to a first server, which is any one of multiple servers included in the blockchain management system. The server includes, but is not limited to, electronic devices such as mobile phones, tablets, wearable devices, and PCs (Personal Computers), and can also be a backend server running the blockchain-based production materials management method. The server can be implemented using a standalone server or a server cluster composed of multiple servers.

Based on the principles and concepts of blockchain, and considering the practical needs of production materials management, this application discloses a blockchain management system. The blockchain management system includes servers similar to the management nodes of a traditional blockchain system. Referring to Figure 2, multiple servers are interconnected to communicate with each other via wired or wireless communication. This communication can employ reliable protocols, such as Transmission Control Protocol/Internet Protocol (TCP/IP), to achieve data transmission and synchronization. The server is a fundamental component of the blockchain management system network, responsible for maintaining and operating the network. In the blockchain management system, the server connects to the blockchain network via the Internet and undertakes several key responsibilities, including data transmission, data storage, and data updates.

Furthermore, in traditional public blockchains, nodes are typically anonymous to each other. This means that while each node's transaction history and blockchain data are publicly transparent, the identity of the node itself (such as the individual or organization running the node) is usually not disclosed. However, for the management of production materials, strong anonymity is not necessary because, in the event of problems with the production material data, not being anonymous facilitates tracing the processing. This further implies that in the blockchain management system of this application, the identities of multiple servers are known to each other, and they can obtain each other's device identification information to determine each other's identities.

This application also utilizes other blockchain-related technologies or ideas, including but not limited to asymmetric encryption, digital signatures, and hash operations, and makes adaptive adjustments to suit the scenario of production materials management. Specific implementation methods will be described in detail below.

For means of production, including technology, patents, brands, human resources, raw materials, equipment, tools, and buildings, the main changes include, but are not limited to, increasing the quantity of means of production, decreasing the quantity of means of production, and replacing means of production. Based on the changes to the means of production, corresponding change data is generated.

For example, suppose a manufacturing company decides to upgrade its production line. This includes adding new production equipment (e.g., purchasing five new automated assembly machines), reducing the number of old equipment (removing three obsolete machines), and replacing certain key technical components (e.g., updating existing machines with more advanced sensors). First, this change information is recorded in detail, including the quantity, type, specifications, purchase date, and obsolescence date of each item. Then, this change data is formatted into a specific data structure, such as a spreadsheet or database entry.

Finally, this change data is stored to update inventory records, financial statements, and assess production capacity, which may then be used to achieve production targets and improve efficiency. Therefore, it is necessary to store change data for production materials and ensure the security of this data storage to prevent tampering.

The first server needs an interface or method to receive user input data. This could be a form, an API, or any other way that allows users to input data. After validating the input change data to ensure it is correctly formatted and conforms to the expected data type and range, the change data for production materials is input to the first server via the API or other input interface.

S120 uses the user's private key to encrypt the changed data and generate a digital signature.

The first server performs a hash operation on the user-inputted change data according to the set hash function, generating a unique string (hash value) of fixed length. The choice of hash function depends on the user's encryption requirements; a suitable hash function, such as SHA-256, is selected. This embodiment does not impose specific limitations on this.

For example, suppose a company needs to record changes in its production data. This change data might include information such as newly added machinery, obsolete tools, or changes in raw material inventory. For instance, the company added 5 3D printers, obsolete 10 old milling machines, and purchased 1000 kg of plastic granules. This change data can be represented as a data structure, such as a JSON object, then the above content could be represented as: {"New Equipment":{"3D Printers":5},"Obsolete Equipment":{"Milling Machines":10},"New Raw Materials":{"Plastic Granules":"1000 kg"}}. Next, to generate the hash value of the data, a defined hash function, such as SHA-256, is needed. Using the generated JSON object as input to the hash function, a fixed-length unique string, i.e., the hash value, is generated. Since hashing is only a common technique in related technical fields and the process is very complex, it will not be explained in detail here. After performing the above hash operation, the output hash value will be a fixed-length and unique string, such as "83b2ac5b6f......a8b6e43a". This hash value represents a unique fingerprint of the original changed data. Even minor data changes, such as a change in the number of new devices, will generate a completely different hash value.

Hash functions are irreversible, meaning it's impossible to deduce the original changed data from the hash value. Furthermore, hash functions are typically highly adversarial; even minor adjustments to a value in the changed data will result in a significantly different hash function. For example, modifying the quantity of a batch of materials in the change data will yield vastly different hash results before and after the modification. It should be noted that, since it's not convenient to specify a particular hash function here, and hash operations are a standard technique in the relevant technical field, further details will not be provided.

Then, the hash value obtained in the previous step is digitally signed using the user's private key. This involves encrypting the hash value using an asymmetric encryption algorithm with the user's private key. The user's private key is crucial in the data encryption process and is typically held only by the corresponding owner (user). When the first server needs to encrypt the hash value to generate a digital signature, it uses a pre-defined signature algorithm, such as RSA or ECDSA. This algorithm defines how to use the private key to encrypt the hash value. Different algorithms have different characteristics and security levels; the security requirements of the changed data should be considered when selecting one.

The generated hash value is taken as input and encrypted using a selected signature algorithm and the user's private key. Technically, this is not "encryption" in the traditional sense, but rather generates a unique output that can only be produced by the corresponding user's private key; this output is the digital signature. The encryption process is usually automated by encryption libraries or tools; the user only needs to provide their private key through the relevant input interface. The digital signature, obtained by encrypting the hash value with the private key, is typically a combination of letters and numbers, used to verify the authenticity and integrity of subsequently modified data, ensuring the tamper-proof nature of the modified data.

For example, the hash value obtained in the above example is "83b2ac5b6f......a8b6e43a". If we use the RSA algorithm for signing, assume the user has the following RSA private key: "5s5f96sdf174d". Next, we use the RSA private key to digitally sign the hash value. This process is usually implemented through encryption software or programming libraries. For example, using the OpenSSL command-line tool, the command might look like this: "echo -n "83b2ac5b6f...a8b6e43a"|openssl dgst-SHA256-sign user_private_key "5s5f96sdf174d" pem". This command will generate a digital signature, which is a cryptographic representation of the hash value. After executing the above command, a digital signature will be output, such as "5f4dcc3b5a......6e309e".

Before proceeding, a key pair, including a public key and a private key, needs to be generated. First, the user's identity information needs to be obtained. This information can be the user's ID, fingerprint, or other unique identifier, and will be used as the unique identifier for the user. The first server uses a hash function to perform a hash operation on the user's identity information, generating a fixed-length hash value. Similarly, if the user's identity information is entered incorrectly, such as an incorrect ID, the output hash value will change. Furthermore, entering even a single incorrect character will significantly alter the output hash value. For example, for the ID "123456789", the hash output might be "4dd51fg4yrs300ssd". And for the ID "023456789", the hash output might be "fh452sr52sfg".

Hash operations are one-way, meaning the original identity information cannot be reconstructed from the hash value and then used as the user's private key. However, in practical applications, this hash value may need further conversion or formatting to adapt to specific encryption algorithm requirements, which will not be elaborated further here.

Next, an asymmetric encryption algorithm (such as RSA) is used to generate a corresponding public key based on the user's private key. Public key generation typically involves complex mathematical operations to ensure a match between the user's public and private keys. In most encryption systems, this process is automated; the user only needs to provide their private key, and the encryption library or framework handles the public key generation. During this process, the user's private and public keys form a key pair with a specific mathematical relationship, guaranteeing that only the holder of the user's private key can decrypt information encrypted with the user's public key, or vice versa.

The user's identity information code is hashed to obtain a unique and irreversible hash result. This helps ensure the security and immutability of the user's identity information, providing a secure foundation for subsequent steps. The hash result of the identity information is set as the user's private key. This private key, obtained through hashing, is unique and irreversible, protecting the user's identity information. Generating the private key is a secure process, increasing the confidentiality of the user's identity information. Based on the generated private key, an asymmetric encryption algorithm is used to generate the user's public key. This public key is the counterpart to the private key and is used for subsequent digital signature generation and verification. The asymmetric encryption algorithm ensures the security of the public-private key pair, ensuring that only the private key holder can generate the corresponding digital signature.

After generating a digital signature, the first server sends the digital signature to each of the second servers, ensuring that each second server receives the user's signature on the changed data. The second servers are any servers in the blockchain management system other than the first server. Alternatively, the first server sends the digital signature to some of the second servers, and these second servers then send the digital signature to the other second servers, achieving synchronization of the digital signature across all second servers. Each second server uses the user's public key to decrypt the received digital signature, obtaining a hash value. Since the digital signature is encrypted using the user's private key, only the user's public key can decrypt it. Therefore, the decryption of the hash value ensures that the hash value was generated by the user's signature. Furthermore, since the user's public key is used to verify the digital signature generated by the user's private key, when a user digitally signs information using their private key, anyone can use the user's public key to verify the authenticity of the signature. This proves that the information was indeed sent by the holder of the user's private key and has not been tampered with during transmission. Therefore, the user's public key can be publicly disclosed, and any server in the blockchain management system can store the user's public key for direct use in decrypting digital signatures.

First, a hash operation is performed on the changed data to obtain a hash value. A hash operation is a one-way function that transforms changed data into a unique hash value of fixed length, which helps ensure the uniqueness and irreversibility of the changed data. Next, the hash value is encrypted using the user's private key to generate a digital signature. This digital signature, obtained by encrypting the hash value with the private key, can only be decrypted using the user's public key. This step implements the digital signature of the changed data, ensuring the uniqueness of the signature and the authenticity of the user's identity.

S130 uses the public keys of each server to encrypt the changed data, generating encrypted data.

Similar to the user's public and private keys, a key pair needs to be generated based on the device identifiers of each second server for encryption and decryption. This application discloses a key generation method based on random numbers, the specific implementation process of which is as follows:

First, use a random number generator to generate the required number of random positive integers, ensuring that the generated integers have sufficient randomness and uniformity. Then, randomly select letters from the alphabet to generate the required number of random letters; this can be achieved by using a random number generator to select an index from the alphabet. Next, obtain the device identifier from the target server. The device identifier is a unique identifier used to identify the device; it can be a MAC address or other information used to identify the device.

The generated random positive integer and random letter are inserted into the device identifier to generate the target private key. This can be achieved by inserting random numbers and letters into different positions in the device identifier according to certain rules. For example, if the device identifier is "ABC123XYZ", the inserted random positive integer is "456", and the random letter is "MNO". The insertion rule could be that each number or letter is inserted between two characters of the device identifier, resulting in a target private key like "AB4C56MNO123XYZ". Finally, an asymmetric encryption algorithm (such as RSA) is used to generate the corresponding target public key based on the generated target private key. This typically involves steps such as selecting prime numbers, calculating the modulus, and selecting the public key exponent to ensure that the generated key pair is a sufficiently strong asymmetric key pair.

The generation of multiple random positive integers and random letters increases the complexity and randomness of the target private key. This design effectively prevents malicious attackers from obtaining the target private key through guessing or speculation, thus improving its security. The target server's device identifier is obtained, and random positive integers and random letters are inserted into the device identifier to form the target private key. This design associates the target private key with the specific device identifier of the target server, enhancing the uniqueness of the private key and the security of the device identifier. Based on the generated target private key, an asymmetric encryption algorithm is used to generate the target public key. This ensures that the target server can use the target public key corresponding to the generated target private key to decrypt data, while preventing unauthorized decryption attempts.

For each second server, the first server obtains its corresponding public key. Taking any one of the multiple second servers as an example, the target server also pre-sets a key pair: a target public key and a target private key. The target public key is used for encryption, and the target private key is used for decryption. The first server encrypts the changed data using the target server's target public key, generating intermediate encrypted data. This ensures that only the target server can decrypt this data using its target private key. Then, the intermediate encrypted data obtained in the previous step is re-encrypted using the user's private key to generate the final encrypted data.

The modified data is encrypted using the target's public key to obtain intermediate encrypted data. This intermediate encrypted data is encrypted using the target server's public key and can only be decrypted using the corresponding target private key. This step achieves target server authentication and confidentiality protection for the modified data. The intermediate encrypted data is then encrypted again using the user's private key to obtain the final encrypted data. This encrypted data protects the confidentiality of the intermediate encrypted data during transmission and can only be decrypted using the user's public key. This step achieves dual protection for the encrypted data through user authentication and re-encryption.

S140, send the digital signature to each of the second servers respectively.

Since the first server encrypts the changed data to obtain a digital signature based on the public keys of each server, the digital signature can be sent to all second servers using the server's public key as the address, provided that a mapping relationship is established between the server's public key and the server identifier. This ensures that each server receives the user's signature on the changed data.

Subsequently, the target server verifies the user's signature. However, since the digital signature is encrypted using the user's private key, if the target server does not obtain the user's public key, or if the received digital signature is tampered with, the target server cannot successfully decrypt the digital signature and therefore cannot successfully verify it.

Specifically, even if a malicious attacker obtains a user's public key, they cannot deduce the user's private key from it. This is due to the mathematical foundation of asymmetric encryption algorithms. These algorithms, such as RSA and ECC (Elliptic Curve Cryptography), are built upon the complexity of mathematical problems. For example, in the RSA algorithm, the public and private keys are generated by multiplying two large prime numbers. The public key contains this product (called the modulus n), while the private key is associated with the specific values of these two prime numbers. While multiplication (calculating the modulus n) is relatively easy, prime factorization of a large number (i.e., finding the two original prime numbers from n) is computationally extremely difficult. Currently, there is no known efficient algorithm that can solve this problem in real time, especially when dealing with very large numbers. The complexity of these mathematical problems ensures that even if an attacker possesses the user's public key, they cannot compute the corresponding user's private key in real time. This computational infeasibility is key to building secure asymmetric encryption systems, allowing the user's public key to be securely disclosed while the user's private key remains secure.

Based on the above principles, since digital signatures are encrypted using the user's private key, the target server only needs to attempt to decrypt the digital signature using the user's public key to determine if decryption is successful. If decryption fails and a hash value is obtained, it indicates that the digital signature may have been tampered with. Conversely, if the target server successfully decrypts the digital signature, the verification of the digital signature is successful.

S150: After receiving the verification information for the digital signature sent by each of the second servers, send encrypted data to each of the second servers.

After multiple secondary servers (including the target server) verify the digital signature, they return verification information to the primary server based on the communication address. According to preset rules, when the number of verification messages received by the primary server exceeds a preset threshold, the primary server sends encrypted data to all secondary servers based on the secondary servers' public keys, so that each secondary server can synchronously change the data.

Only after the second server verifies the digital signature and sends a verification confirmation message to the first server will the first server send the encrypted data to the second server. This is because the second server can only obtain the digital signature if it has the user's public key, and the first server can only send the digital signature to the second server if it has the user's public key. This means that the second server must be a known and secure server for it to possess the public key of the first server, and only then can the first server send encrypted data to the second server.

Furthermore, the first server first sends a digital signature to the second server, which can verify that the data indeed originated from the legitimate first server. The digital signature is encrypted using the first server's private key, and only the corresponding public key can verify its authenticity. This mechanism ensures the security and trustworthiness of the data source. If the second server cannot verify the digital signature, it indicates that the data may have originated from an untrusted source or has been tampered with. In this case, refusing to receive encrypted data prevents the receipt and processing of invalid or malicious data, thereby enhancing the security of the entire blockchain management system.

Since the encrypted data is encrypted using the public keys of each server, only the corresponding server can decrypt and read this data using its private key. If the data is further encrypted using the user's public key, the user's private key is also required to decrypt the encrypted data. Each second server uses its own private key to decrypt the received encrypted data and processes it, ensuring that the servers remain synchronized. This may include updating the local database and triggering corresponding production data management operations. After decrypting the encrypted data and verifying the digital signature, the second server sends a synchronization completion message to the first server. Upon receiving the synchronization completion message, the first server confirms that the change to the production data is complete.

The first server ensures the synchronization of changed data across all servers by sending encrypted data to each of the second servers. Each second server receives and decrypts the data, verifies the digital signature, and generates a synchronization completion message, signifying successful synchronization of the changed data across all servers in the blockchain management system. This helps ensure that all participants receive the same, verified changed data, improving data consistency and trustworthiness. Furthermore, each second server, upon receiving the encrypted data, decrypts it using its private key and verifies the digital signature. A synchronization completion message is only generated if the digital signature verification is successful. This ensures the integrity and authenticity of data during transmission and storage, preventing the risk of data tampering or forgery.

By adopting the above technical solution, when a user needs to modify production materials, the first server generates a digital signature based on the modified data, which is then verified by the second server. The encrypted data is then sent to each of the second servers, ensuring that each server can verify the authenticity and integrity of the data. Once the digital signature verification is successful, the second server can synchronously encrypt the data, ensuring data consistency. Furthermore, this application uses a decentralized distributed ledger based on blockchain, with each server having a copy of the modified data. Compared to traditional centralized management, decentralization reduces reliance on a single central management device, minimizing the risk of single points of failure and attacks. Each server participates in the verification and storage of modified data, reducing the possibility of production material data being maliciously tampered with into false changes, thus improving the security of production materials.

In one possible implementation, referring to Figure 3, when a user needs to manage changes in production data using encryption, the changed data is first hashed to obtain a unique hash value. Then, the user's private key is input into the first server to encrypt the hash value and generate a digital signature. Simultaneously, the first server encrypts the changed data using the public key of the second server, obtaining intermediate encrypted data. This intermediate encrypted data can only be decrypted using the private key corresponding to the server's public key. The intermediate encrypted data is then further encrypted using the user's private key to obtain the final encrypted data. After multiple second servers in the blockchain management system verify the digital signature, it is determined that the digital signature has been decrypted using the user's public key, and a verification pass message is sent to the first server. Upon receiving the verification pass message, the first server transmits the encrypted data to the second servers according to the communication address.

Furthermore, when any user of the second server wants to decrypt and verify the encrypted data, referring to Figure 4, the second server decrypts the digital signature using the user's public key to obtain a hash value. The user of the second server must first obtain permission from the user, i.e., the user must input their private key, before the second server can use the user's private key to decrypt the received encrypted data, obtaining intermediate encrypted data. Then, the second server's private key is used to decrypt the intermediate encrypted data to obtain the modified data. Finally, a hash operation is performed on the modified data to obtain a hash value. If the encrypted data has not been tampered with, and the digital signature has also not been tampered with, then the two hash values should be the same, because both hash values should be obtained by encrypting the modified data using the user's private key. Conversely, if the two hash values are different, it indicates that the encrypted data has been tampered with, or the digital signature has been tampered with.

This embodiment also discloses a blockchain-based production materials management device. The device is a first server, and as shown in Figure 5, it includes an acquisition module 501, an encryption module 502, and a sending module 503, wherein:

The acquisition module 501 is used to acquire the change data of production materials input by the user, which is the increase or decrease data of production materials.

The encryption module 502 is used to encrypt the changed data using the user's private key and generate a digital signature.

The encryption module 502 is used to encrypt the changed data using the public keys of each server to generate encrypted data. The public key of the server is the public key of the second server, which is a server other than the first server among multiple servers.

The sending module 503 is used to send digital signatures to each of the second servers respectively.

The sending module 503 is used to send encrypted data to each of the second servers after receiving the verification information for the digital signature sent by each second server, so that each second server can synchronously change the data.

In one possible implementation, the encryption module 502 is used to perform a hash operation on the changed data to obtain the hash value of the changed data.

The encryption module 502 is used to encrypt the hash value using the user's private key to obtain a digital signature, so that the second server can decrypt the digital signature using the user's public key corresponding to the user's private key to obtain the hash value.

In one possible implementation, the encryption module 502 is used to encrypt the changed data using the target public key to obtain intermediate encrypted data, so that the target server can decrypt the intermediate encrypted data using the target private key corresponding to the target public key to obtain the changed data. The target public key is the public key corresponding to the target server, and the target server is any one of a plurality of second servers.

The encryption module 502 is used to encrypt intermediate encrypted data using the user's private key to obtain encrypted data, so that the second server can decrypt the encrypted data using the user's public key corresponding to the user's private key to obtain intermediate encrypted data.

In one possible implementation, the acquisition module 501 is used to receive the comparison pass information for the digital signature sent by the target server. The target server uses the user's public key corresponding to the user's private key to decrypt the digital signature to obtain a hash value. The target server uses the target private key to decrypt the encrypted data and performs a hash operation on the decryption result. The operation result is compared with the hash value. If it is determined that the operation result is consistent with the hash value, the comparison pass information is generated.

The sending module 503 is used to determine the verification pass information by sending the comparison pass information.

In one possible implementation, the acquisition module 501 is used to receive synchronization completion information sent by each second server to determine that the change of production data is completed. The second server uses its private key to decrypt the encrypted data and generates synchronization completion information after the digital signature is verified.

In one possible implementation, the encryption module 502 is used to perform a hash operation on the user's identity information code to obtain the result.

Encryption module 502 is used to set the calculation result as the user's private key.

The encryption module 502 is used to generate a user public key based on the user's private key using an asymmetric encryption algorithm.

In one possible implementation, the acquisition module 501 is used to generate multiple random positive integers and multiple random letters.

The acquisition module 501 is used to acquire the device identifier of the target server.

Encryption module 502 is used to insert multiple random positive integers and multiple random letters into the device identifier to obtain the target private key.

The encryption module 502 is used to generate the target public key based on the target private key using an asymmetric encryption algorithm.

It should be noted that the above embodiments of the apparatus are only illustrated by the division of the above functional modules. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

This embodiment also discloses an electronic device. Referring to FIG6, the electronic device may include: at least one processor 601, at least one communication bus 602, user interface 603, network interface 604, and at least one memory 605.

The communication bus 602 is used to enable communication between these components.

The user interface 603 may include a display screen and a camera. Optionally, the user interface 603 may also include a standard wired interface and a wireless interface.

The network interface 604 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface).

The processor 601 may include one or more processing cores. The processor 601 connects to various parts of the server using various interfaces and lines, and performs various functions of the server and processes data by running or executing instructions, programs, code sets or instruction sets stored in the memory 605, and by calling data stored in the memory 605.

The memory 605 may include random access memory (RAM) or read-only memory (ROM). As shown in the figure, the memory 605, as a computer storage medium, may include an operating system, a network communication module, a user interface module 603, and an application program for a blockchain-based production materials management method.

In the electronic device shown in Figure 6, the user interface 603 is mainly used to provide an input interface for the user and obtain the user input data; while the processor 601 can be used to call the application program stored in the memory 605 that is based on the blockchain-based production materials management method. When executed by one or more processors 601, the electronic device executes one or more methods as described in the above embodiments.

The foregoing description is merely an exemplary embodiment of this disclosure and should not be construed as limiting the scope of this disclosure. Any equivalent changes and modifications made in accordance with the teachings of this disclosure shall still fall within the scope of this disclosure. Those skilled in the art will readily conceive of other embodiments of this disclosure upon considering the specification and the disclosure of practical truth. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not described in this disclosure. The specification and embodiments are considered exemplary only, and the scope and spirit of this disclosure are defined by the claims.

Claims (5)

1. A production materials management method based on blockchain, characterized in that it is applied to a first server, wherein the first server is any one of multiple servers included in the blockchain management system, and the multiple servers are interconnected, the method comprising: Obtain user-inputted change data for production materials, wherein the change data is the increase or decrease data of the production materials; The changed data is encrypted using the user's private key to generate a digital signature; The changed data is encrypted using the public keys of each server to generate encrypted data. The public key of each server is the public key of the second server, which is a server other than the first server among the multiple servers. The digital signatures are sent to each of the second servers respectively; After receiving the verification information for the digital signature sent by each of the second servers, the encrypted data is sent to each of the second servers so that each of the second servers can synchronize the changed data; The step of encrypting the changed data using the user's private key to generate a digital signature specifically includes: Perform a hash operation on the changed data to obtain the hash value of the changed data; The hash value is encrypted using the user's private key to obtain the digital signature, so that the second server can decrypt the digital signature using the user's public key corresponding to the user's private key to obtain the hash value. The step of encrypting the changed data using the public keys of each server to generate encrypted data specifically includes: The changed data is encrypted using the target public key to obtain intermediate encrypted data, so that the target server can decrypt the intermediate encrypted data using the target private key corresponding to the target public key to obtain the changed data. The target public key is the public key corresponding to the target server, and the target server is any one of a plurality of second servers. The intermediate encrypted data is encrypted using the user's private key to obtain the encrypted data, so that the second server can decrypt the encrypted data using the user's public key corresponding to the user's private key to obtain the intermediate encrypted data. After receiving verification information for the digital signature from each of the second servers, and after sending the encrypted data to each of the second servers, the method further includes: The system receives synchronization completion information from each of the second servers to determine that the production data change is complete. The second server decrypts the encrypted data using its private key and generates the synchronization completion information after verifying the digital signature. Before encrypting the hash value using the user's private key to obtain the digital signature, so that the second server can decrypt the digital signature using the user's public key corresponding to the user's private key to obtain the hash value, the method further includes: Perform a hash operation on the user's identity information code to obtain the result; Set the result of the calculation as the user's private key; The user's public key is generated using an asymmetric encryption algorithm based on the user's private key. Before encrypting the changed data using the public keys of each server to generate encrypted data, the method further includes: Generate multiple random positive integers and multiple random letters; Obtain the device identifier of the target server; The target private key is obtained by inserting multiple random positive integers and multiple random letters into the device identifier; Based on the target private key, the target public key is generated using an asymmetric encryption algorithm. 2. The production materials management method based on blockchain according to claim 1, characterized in that, after receiving the verification information for the digital signature sent by each of the second servers, it specifically includes: The system receives a comparison pass message for the digital signature sent by the target server. The target server decrypts the digital signature using the user's public key corresponding to the user's private key to obtain the hash value. The target server decrypts the encrypted data using the target private key and performs a hash operation on the decryption result. The operation result is compared with the hash value. If it is determined that the operation result is consistent with the hash value, the comparison pass message is generated. The verification pass information is determined by comparing the information. 3. A blockchain-based means of production management device, characterized in that the device is used to execute the blockchain-based means of production management method as described in any one of claims 1-2, the device being a first server, comprising an acquisition module (501), an encryption module (502), and a sending module (503), wherein: The acquisition module (501) is used to acquire the change data of the production materials input by the user, wherein the change data is the increase or decrease data of the production materials; The encryption module (502) is used to encrypt the changed data using the user's private key and generate a digital signature; The encryption module (502) is used to encrypt the changed data using the public keys of each server to generate encrypted data. The public key of the server is the public key corresponding to the second server, and the second server is a server other than the first server among the multiple servers. The sending module (503) is used to send the digital signature to each of the second servers respectively; The sending module (503) is used to send the encrypted data to each of the second servers after receiving the verification information for the digital signature sent by each of the second servers, so that each of the second servers can synchronize the changed data. The encryption module (502) is used to encrypt the changed data using the user's private key to generate a digital signature. Specifically, it is used to perform a hash operation on the changed data to obtain a hash value of the changed data; and to encrypt the hash value using the user's private key to obtain the digital signature, so that the second server can decrypt the digital signature using the user's public key corresponding to the user's private key to obtain the hash value. The encryption module (502) is used to encrypt the changed data using the public keys of each server to generate encrypted data. Specifically, it is used to encrypt the changed data using the target public key to obtain intermediate encrypted data, so that the target server can decrypt the intermediate encrypted data using the target private key corresponding to the target public key to obtain the changed data. The target public key is the public key corresponding to the target server, and the target server is any one of a plurality of second servers. It also uses the user private key to encrypt the intermediate encrypted data to obtain the encrypted data, so that the second server can decrypt the encrypted data using the user public key corresponding to the user private key to obtain the intermediate encrypted data. The sending module (503) is used to send the encrypted data to each of the second servers after receiving the verification information for the digital signature sent by each of the second servers. The sending module (503) is also used to receive the synchronization completion information sent by each of the second servers to determine that the change of production data is completed. The second server uses the server private key to decrypt the encrypted data and generates the synchronization completion information after verifying the digital signature. The encryption module (502) is used to encrypt the hash value using the user's private key to obtain the digital signature, so that the second server can decrypt the digital signature using the user's public key corresponding to the user's private key to obtain the hash value. Before this, the sending module (503) is also used to perform a hash operation on the user's identity information code to obtain the operation result; set the operation result as the user's private key; and generate the user's public key using an asymmetric encryption algorithm based on the user's private key. The encryption module (502) is used to generate multiple random positive integers and multiple random letters before the encrypted data is generated by encrypting the changed data using the public keys of each server. The sending module (503) is also used to generate multiple random positive integers and multiple random letters; obtain the device identifier of the target server; insert the multiple random positive integers and multiple random letters into the device identifier to obtain the target private key; and generate the target public key using an asymmetric encryption algorithm based on the target private key. 4. An electronic device, characterized in that it comprises a processor (601), a memory (605), a user interface (603), and a network interface (604), wherein the memory (605) is used to store instructions, the user interface (603) and the network interface (604) are both used to communicate with other devices, and the processor (601) is used to execute the instructions stored in the memory (605) to cause the electronic device to perform the method as described in any one of claims 1-2. 5. A computer-readable storage medium, characterized in that the computer-readable storage medium stores instructions that, when executed, perform the method as described in any one of claims 1-2.