Asset information transfer recording method, device and electronic equipment

By synchronizing asset circulation information between transaction servers and forming a blockchain, and using UUID to encapsulate data, the problem of asset information being easily tampered in traditional databases is solved, and the secure storage and transmission of asset circulation information is realized.

CN111881468BActive Publication Date: 2025-01-10SINA TECH (CHINA) CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202010615065.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-06-30
Publication Date
2025-01-10
Estimated Expiration
2040-06-30

AI Technical Summary

Technical Problem

The asset information stored in traditional databases is easily tampered with, which poses security risks.

Method used

By recording asset circulation information into a transaction record table and synchronizing data between transaction servers, a blockchain is formed, and data is encapsulated using a universal unique identification code (UUID) to prevent tampering.

Benefits of technology

Ensure the security of asset circulation information, prevent data from being tampered with, and improve the integrity and reliability of information.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN111881468B_ABST
    Figure CN111881468B_ABST
Patent Text Reader

Abstract

The present invention discloses an asset information circulation recording method, device and electronic device, the method comprising: upon receiving an asset information circulation request sent by a client, sending the asset circulation information and a first universal unique identifier UUID of a first transaction record table to a first transaction server; receiving a first message returned by the first transaction server; sending a first synchronization instruction to other transaction servers; and upon the other transaction servers completing the execution of the first synchronization instruction, encapsulating the first transaction record table into a first block. The embodiment of the present invention saves the asset circulation information to a transaction server and synchronizes it to other transaction servers, and encapsulates the data in a block after the synchronization is completed. Since the block contains a universal unique identifier, the data in the block cannot be tampered with, thereby ensuring the security of the asset circulation information.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of blockchain technology, and in particular to a method, device and electronic device for recording asset information circulation. Background Art

[0002] With the development of the Internet, the asset information of enterprises will be stored in the database to centrally record and manage the flow of asset information. Currently, asset information is generally stored in traditional databases, such as MySql databases or other unstructured centralized databases.

[0003] However, since the above database can be tampered with by anyone with access rights to the database, the asset information is unsafe and there is a risk of tampering. Summary of the invention

[0004] The embodiments of the present invention provide a method, device and electronic device for recording asset information circulation, so as to solve the problem in the prior art that asset information is stored in a traditional database and is easily tampered with.

[0005] In order to solve the above-mentioned technical problems, the present invention is achieved as follows:

[0006] In a first aspect, a method for recording asset information circulation is provided, the method comprising:

[0007] Upon receiving an asset information transfer request sent by the client, sending the asset transfer information and the first universal unique identifier UUID of the first transaction record table to the first transaction server, wherein the asset information transfer request carries the asset transfer information;

[0008] receiving a first message returned by the first transaction server, where the first message is a notification message that the first transaction server records the asset transfer information into a first transaction record table corresponding to the first UUID;

[0009] Sending a first synchronization instruction to other transaction servers, where the first synchronization instruction is used to instruct the other transaction servers to synchronize asset transfer information in the first transaction record table from the first transaction server, and the other transaction servers are transaction servers other than the first transaction server;

[0010] When the other transaction server completes executing the first synchronization instruction, the first transaction record table is encapsulated into a first block.

[0011] In a second aspect, an asset information circulation recording device is provided, the device comprising:

[0012] A first receiving module is used to send the asset transfer information and the first universal unique identifier UUID of the first transaction record table to the first transaction server when receiving an asset information transfer request sent by the client, wherein the asset information transfer request carries the asset transfer information;

[0013] A second receiving module is configured to receive a first message returned by the first transaction server, where the first message is a notification message that the first transaction server records the asset transfer information into a first transaction record table corresponding to the first UUID;

[0014] A first sending module, configured to send a first synchronization instruction to other transaction servers, wherein the first synchronization instruction is used to instruct the other transaction servers to synchronize the asset flow information in the first transaction record table from the first transaction server, and the other transaction servers are transaction servers other than the first transaction server;

[0015] The encapsulation module is used to encapsulate the first transaction record table into a first block when the other transaction server completes the execution of the first synchronization instruction.

[0016] In a third aspect, an electronic device is provided, which includes a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps of the method described in the first aspect when executed by the processor.

[0017] In a fourth aspect, a computer-readable storage medium is provided, characterized in that a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method described in the first aspect are implemented.

[0018] In an embodiment of the present invention, upon receiving an asset information transfer request sent by a client, the asset transfer information and the first universal unique identifier UUID of the first transaction record table are first sent to the first transaction server, and then a notification message returned by the first transaction server to record the asset transfer information in the first transaction record table corresponding to the first UUID is received. After receiving the notification message, a first synchronization instruction to synchronize the first transaction record table of the first transaction server is sent to other transaction servers, and finally, upon receiving the completion of the first synchronization instruction by other transaction servers, the first transaction record table is encapsulated into a first block. In an embodiment of the present invention, the asset transfer information is saved in a transaction server and synchronized to other transaction servers, and the data is encapsulated in a block after the synchronization is completed. Since the block contains a universal unique identifier, the data in the block cannot be tampered with, thereby ensuring the security of the asset transfer information. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0020] Figure 1 It is a flow chart of an asset information circulation recording method provided by an embodiment of the present invention;

[0021] Figure 2 It is a flow chart of an asset information circulation recording method provided by an embodiment of the present invention;

[0022] Figure 3 It is a structural schematic diagram of an asset information circulation recording device provided by an embodiment of the present invention;

[0023] Figure 4 It is a schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0024] 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 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.

[0025] The embodiments of the present application provide a method, device and electronic device for recording asset information transfer. By recording asset transfer information in a transaction record table and forming a blockchain, the data of the asset transfer information is prevented from being tampered with, thereby ensuring information security during the asset transfer process.

[0026] Some of the terms used in this application are explained as follows:

[0027] Transaction record table: a file used to record asset transfer information. Each transaction record table can save a preset number of transfer records.

[0028] Transaction server: A server used to store transaction records.

[0029] Main server: used to connect the client and transaction server to save and distribute data.

[0030] like Figure 1 As shown, it is a flow chart of a method for recording asset information circulation provided by an embodiment of the present application. Figure 1 As shown, the asset information flow recording method may include the contents shown in steps S101 to S104.

[0031] In step S101, upon receiving an asset information transfer request sent by a client, the asset transfer information and the first universal unique identifier UUID of the first transaction record table are sent to the first transaction server, and the asset information transfer request carries the asset transfer information.

[0032] In an embodiment of the present application, when receiving an asset information transfer request sent by a client, the main server randomly sends the asset transfer information and the first universally unique identifier (UUID) of the first transaction record table to any transaction server. The first transaction server is used in this application.

[0033] In step S102, a first message returned by the first transaction server is received, where the first message is a notification message that the first transaction server records asset transfer information into a first transaction record table corresponding to the first UUID.

[0034] In an embodiment of the present application, after the main server sends the above information to the first transaction server, it can receive the first message returned by the first transaction server. That is, after the first transaction server receives the information sent by the main server, it records the asset transfer information in the first transaction record table corresponding to the first UUID sent by the main server. After the recording is successful, the first transaction server can send a notification message to the main server to notify the main server to successfully record the asset transfer information into the first transaction record table.

[0035] In step S103, a first synchronization instruction is sent to other transaction servers, where the first synchronization instruction is used to instruct other transaction servers to synchronize asset transfer information in the first transaction record table from the first transaction server, and the other transaction servers are transaction servers other than the first transaction server.

[0036] In an embodiment of the present application, after the main server receives the first message returned by the first transaction server, it sends a first synchronization instruction to synchronize the first transaction record table to other transaction servers to instruct other transaction servers to synchronize the first transaction record table containing asset circulation information from the first transaction server.

[0037] In step S104, when other transaction servers complete the execution of the first synchronization instruction, the first transaction record table is encapsulated into a first block.

[0038] In an embodiment of the present application, after the main server sends a first synchronization instruction to other transaction servers and receives a synchronization success message returned by other transaction servers, the first transaction record table is encapsulated into a first block, that is, the first transaction record table recording asset flow information is encapsulated in the first block.

[0039] Therefore, in the embodiment of the present application, when receiving the asset information transfer request sent by the client, the asset transfer information and the first universal unique identifier UUID of the first transaction record table are first sent to the first transaction server, and then the notification message returned by the first transaction server to record the asset transfer information in the first transaction record table corresponding to the first UUID is received. After receiving the notification message, the first synchronization instruction for synchronizing the first transaction record table of the first transaction server is sent to other transaction servers, and finally, when receiving the message from other transaction servers to execute the first synchronization instruction, the first transaction record table is encapsulated into the first block. The embodiment of the present application saves the asset transfer information to a transaction server and synchronizes it to other transaction servers. After the synchronization is completed, the data is encapsulated in a block. Since the block contains a universal unique identifier, the data in the block cannot be tampered with, thereby ensuring the security of the asset transfer information.

[0040] In a possible implementation of the present application, the asset information flow recording method may further include the following steps.

[0041] When the cumulative amount of asset transfer information sent to the first transaction server reaches a first preset amount, a hash operation is performed on the first preset amount of asset transfer information to obtain a first hash value, and the first hash value is used as the hash value of the first block;

[0042] Sending a hash value generation instruction to the first transaction server;

[0043] Receiving a second hash value generated according to the first transaction record table and returned by the first transaction server;

[0044] When the second hash value is the same as the first hash value, it is determined that the first transaction server has completed recording the first transaction record table.

[0045] In the embodiment of the present application, when the number of information recorded in the first transaction record table reaches the first preset number, the main server can perform a hash operation on the first preset number of information to obtain the hash value of the first transaction record table, that is, the first hash value, and can send a hash value generation instruction to the first transaction server, and receive the second hash value returned by the first transaction server. If the second hash value is the same as the first hash value, it is determined that the first snake dance server has completed recording the first transaction record table. That is, when the information in the first transaction record table is full, the main server will determine a hash value based on the information in the table, that is, the hash value of the first block after encapsulation, and can send a hash value generation instruction to the first transaction server to determine whether the first preset number of asset circulation information received by the first transaction server is correct, and whether it is all recorded in the first transaction record table, so that the block can have a unique identification code, so that the data in the block cannot be tampered with, and the security of the asset circulation information is guaranteed.

[0046] In a possible implementation of the present application, the method for determining whether other transaction servers have completed the execution of the first synchronization instruction may include the following steps.

[0047] Receive a second message returned by each other transaction server, the second message carries identification information of the corresponding other transaction server, the second message is a notification message that the corresponding other transaction server has completed the execution of the first synchronization instruction, and the second message includes a third hash value generated by the corresponding other transaction server according to the first transaction record table;

[0048] Compare the third hash value in the second message returned by each other transaction server with the second hash value;

[0049] If each third hash value is the same as the second hash value, it is determined that other transaction servers have completed the execution of the first synchronization instruction.

[0050] In the embodiment of the present application, the main server can also send a first synchronization instruction for synchronizing hash values ​​to other transaction servers, and receive a second message of successful synchronization and a third hash value returned by other transaction servers, and then the main server can compare each third hash value with the second hash value. If they are the same, it means that other transaction servers have completed the execution of the first synchronization instruction, otherwise the first synchronization instruction is resent to other transaction servers until other transaction servers have completed the execution of the first synchronization instruction. The accuracy of the data in each other transaction server can be guaranteed.

[0051] In a possible implementation of the present application, after receiving the second hash value generated according to the first transaction record table and returned by the first transaction server, the asset information flow recording method may further include the following steps.

[0052] When the cumulative amount of asset transfer information sent to the first transaction server exceeds the first preset amount, the asset transfer information exceeding the first preset amount and the second UUID of the second transaction record table are sent to the first transaction server;

[0053] Receive a third message returned by the first transaction server, where the third message is a notification message that the first transaction server records the asset circulation information exceeding the first preset amount into the second transaction record table corresponding to the second UUID;

[0054] Sending a second synchronization instruction to other transaction servers, where the second synchronization instruction is used to instruct the other transaction servers to synchronize asset transfer information in the second transaction record table from the first transaction server;

[0055] When other transaction servers complete the execution of the second synchronization instruction, the second transaction record table is encapsulated into a second block.

[0056] In an embodiment of the present application, after the first transaction record table is full of information, when an asset information transfer request sent by the client is received, the received asset transfer information exceeding the first transaction record table will be recorded in the second transaction record table. At this time, the main server will send the received asset transfer information exceeding the first transaction record table and the second UUID of the second transaction record table to the first transaction server, and receive the notification message of successful recording returned by the first transaction server. Then the main server sends a second synchronization instruction to other transaction servers, instructing other transaction servers to synchronize the asset transfer information in the second transaction record table from the first transaction server. The other transaction servers will return a message of successful synchronization. After receiving the success message, the main server will encapsulate the second transaction record table into a second block.

[0057] In a possible implementation of the present application, the asset information flow recording method may further include the following steps.

[0058] When the cumulative amount of asset transfer information sent to the first transaction server reaches a second preset amount, a hash operation is performed on the asset transfer information of the second amount that exceeds the first preset amount to obtain a fourth hash value, and the fourth hash value is used as the hash value of the second block. The second preset amount is twice the first preset amount.

[0059] The first hash value of the first block is updated using the fourth hash value.

[0060] In an embodiment of the present application, when the cumulative amount of asset transfer information received reaches a second preset amount, that is, when the messages recorded in the second transaction record table are full, the main server determines a fourth hash value based on the information in the second transaction record table, that is, the hash value of the encapsulated second block, and updates the hash value of the first block with the second hash value, connects the first block with the second block, and forms a blockchain. The data in the blockchain cannot be tampered with, thereby ensuring the security of the asset transfer information.

[0061] The reference to the fourth hash value to update the hash value of the first block may be to send the fourth hash value to the first block, and then the first block uses the sum of the first hash value and the fourth hash value as the updated hash value of the first block. Other methods may also be used to update the hash value, which is not specifically limited in this application.

[0062] The embodiment of the present application also provides an asset information circulation recording method, which is applied to a first transaction server, such as Figure 2 As shown in FIG. 1 , it is a flow chart of an asset information circulation recording method provided by this application. Figure 2 As shown, the asset information flow recording method may include the contents shown in steps S201 to S204.

[0063] In step S201, asset transfer information and a first universal unique identifier UUID of a first transaction record table sent by a main server are received.

[0064] In step S202, the asset transfer information is recorded in the first transaction record table corresponding to the first UUID, and a first message is sent to the main server. The first message is a notification message that the asset transfer information is successfully recorded in the first transaction record table corresponding to the first UUID.

[0065] In step S203, a first synchronization instruction sent by the main server is received, and the first transaction record table is synchronized to other transaction servers, where the other transaction servers are transaction servers other than the first transaction server.

[0066] In the embodiment of the present application, upon receiving the asset transfer information and the first universal unique identifier UUID of the first transaction record table sent by the main server, the first transaction server records the asset transfer information in the first transaction record table corresponding to the first UUID, sends a message of successful recording to the main server, and finally synchronizes the first transaction record table to other transaction servers. Recording the asset transfer information in each transaction server can prevent data from being tampered with and ensure the security of the asset transfer information.

[0067] In a possible implementation of the present application, the asset information flow recording method may further include the following steps.

[0068] When the cumulative amount of asset circulation information sent by the main server reaches a first preset amount, receiving a hash value generation instruction sent by the main server, the first hash value being obtained by the main server performing a hash operation on the first preset amount of asset circulation information;

[0069] A second hash value is generated according to the information recorded in the first transaction record table, and the second hash value is sent to the main server.

[0070] Furthermore, when the cumulative amount of asset transfer information received exceeds a first preset amount, the asset transfer information exceeding the first preset amount can be recorded in the second transaction record table in the same manner as the process recorded in the above embodiment, which will not be repeated here.

[0071] The main server can encapsulate the first transaction record table into the first block, and the second transaction record table into the second block, and connect the two blocks through the hash values ​​of the first block and the second block to form a blockchain, so that the data recorded in the blockchain cannot be tampered with, thereby ensuring the security of asset flow information.

[0072] The present application also provides an asset information circulation recording device. Figure 3 As shown, it is a structural diagram of an asset information circulation recording device provided in an embodiment of the present application. Figure 3 As shown, the asset information flow recording device may include: a first receiving module 301, a second receiving module 302, a first sending module 303 and a packaging module 304.

[0073] Specifically, the first receiving module 301 is configured to send the asset transfer information and the first universal unique identifier UUID of the first transaction record table to the first transaction server when receiving an asset information transfer request sent by the client, and the asset information transfer request carries the asset transfer information; the second receiving module 302 is configured to receive a first message returned by the first transaction server, and the first message is a notification message that the first transaction server records the asset transfer information into the first transaction record table corresponding to the first UUID; the first sending module 303 is configured to send a first synchronization instruction to other transaction servers, and the first synchronization instruction is used to instruct other transaction servers to synchronize the asset transfer information in the first transaction record table from the first transaction server, and the other transaction servers are transaction servers other than the first transaction server; the encapsulation module 304 is configured to encapsulate the first transaction record table into a first block when other transaction servers complete the execution of the first synchronization instruction.

[0074] In the embodiment of the present application, the first receiving module 301, upon receiving the asset information transfer request sent by the client, first sends the asset transfer information and the first universal unique identifier UUID of the first transaction record table to the first transaction server, and then the second receiving module 302 receives the notification message returned by the first transaction server to record the asset transfer information in the first transaction record table corresponding to the first UUID. After receiving the notification message, the first sending module 303 sends the first synchronization instruction to synchronize the first transaction record table of the first transaction server to other transaction servers, and finally the encapsulation module 304 encapsulates the first transaction record table into the first block upon receiving the first synchronization instruction executed by other transaction servers. The embodiment of the present invention saves the asset transfer information to a transaction server and synchronizes it to other transaction servers, and encapsulates the data in a block after the synchronization is completed. Since the block contains the universal unique identifier, the data in the block cannot be tampered with, thereby ensuring the security of the asset transfer information.

[0075] In a possible implementation manner of the present application, the asset information circulation recording device further includes: a calculation module, a second sending module, a third receiving module and a determination module.

[0076] The operation module is configured to perform a hash operation on the first preset number of asset circulation information when the cumulative number of asset circulation information sent to the first transaction server reaches a first preset number, obtain a first hash value, and use the first hash value as the hash value of the first block; the second sending module is configured to send a hash value generation instruction to the first transaction server; the third receiving module is configured to receive a second hash value generated according to the first transaction record table and returned by the first transaction server; the determination module is configured to determine that the first transaction server has completed recording the first transaction record table when the second hash value is the same as the first hash value.

[0077] In a possible implementation manner of the present application, the encapsulation module 304 includes: a first receiving unit, a comparing unit, and a determining unit.

[0078] The first receiving unit is configured to receive a second message returned by each other transaction server, the second message carries identification information corresponding to the other transaction server, the second message is a notification message that the corresponding other transaction server has completed the execution of the first synchronization instruction, and the second message includes a third hash value generated by the corresponding other transaction server according to the first transaction record table; the comparison unit is configured to compare the third hash value in the second message returned by each other transaction server with the second hash value; the determination unit is configured to determine that the other transaction server has completed the execution of the first synchronization instruction if each third hash value is the same as the second hash value.

[0079] In a possible implementation manner of the present application, the asset information flow recording device further includes: a third sending module, a fourth receiving module, a fourth sending module and a second encapsulation module.

[0080] The third sending module is configured to send the asset circulation information exceeding the first preset number and the second UUID of the second transaction record table to the first transaction server when the cumulative amount of asset circulation information sent to the first transaction server exceeds the first preset number; the fourth receiving module is configured to receive a third message returned by the first transaction server, the third message being a notification message that the first transaction server records the asset circulation information exceeding the first preset number into the second transaction record table corresponding to the second UUID; the fourth sending module is configured to send a second synchronization instruction to other transaction servers, the second synchronization instruction being used to instruct other transaction servers to synchronize the asset circulation information in the second transaction record table from the first transaction server; the second encapsulation module is configured to encapsulate the second transaction record table into a second block when other transaction servers complete the execution of the second synchronization instruction.

[0081] In a possible implementation manner of the present application, the asset information circulation recording device further includes: a second operation module and an update module.

[0082] The second operation module is configured to perform a hash operation on the asset circulation information in the second amount that exceeds the first preset amount when the cumulative amount of asset circulation information sent to the first transaction server reaches a second preset amount, to obtain a fourth hash value, and use the fourth hash value as the hash value of the second block, and the second preset amount is twice the first preset amount; the update module is configured to use the fourth hash value to update the first hash value of the first block.

[0083] The asset information transfer recording device provided in this embodiment can refer to the device for executing the above Figure 1 The method flow shown in the figure is as follows, and each unit / module in the device and the above-mentioned other operations and / or functions are respectively for implementing the following Figure 1 The corresponding process in the asset information flow recording method shown in the figure can achieve the same or equivalent technical effect. For the sake of brevity, it will not be repeated here.

[0084] Figure 4 A schematic diagram of the hardware structure of an electronic device for implementing each embodiment of the present application is provided below.

[0085] The electronic device 400 includes but is not limited to: a radio frequency unit 401, a network module 402, an audio output unit 403, an input unit 404, a sensor 405, a display unit 406, a user input unit 407, an interface unit 408, a memory 409, a processor 410, and a power supply 411. Those skilled in the art will appreciate that Figure 4 The electronic device structure shown in the figure does not constitute a limitation on the electronic device, and the electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. In the embodiments of the present application, the electronic device includes but is not limited to a mobile phone, a tablet computer, a laptop computer, a PDA, a vehicle-mounted terminal, a wearable device, and a pedometer.

[0086] The processor 410 may be used for:

[0087] When receiving an asset information transfer request sent by the client, sending the asset transfer information and the first universal unique identifier UUID of the first transaction record table to the first transaction server, wherein the asset information transfer request carries the asset transfer information;

[0088] Receive a first message returned by the first transaction server, where the first message is a notification message that the first transaction server records the asset transfer information into a first transaction record table corresponding to the first UUID;

[0089] Sending a first synchronization instruction to other transaction servers, where the first synchronization instruction is used to instruct the other transaction servers to synchronize asset transfer information in the first transaction record table from the first transaction server, and the other transaction servers are transaction servers other than the first transaction server;

[0090] When other transaction servers complete the execution of the first synchronization instruction, the first transaction record table is encapsulated into a first block.

[0091] In an embodiment of the present application, upon receiving an asset information transfer request sent by a client, the asset transfer information and the first universal unique identifier UUID of the first transaction record table are first sent to the first transaction server, and then a notification message returned by the first transaction server to record the asset transfer information in the first transaction record table corresponding to the first UUID is received. After receiving the notification message, a first synchronization instruction to synchronize the first transaction record table of the first transaction server is sent to other transaction servers, and finally, upon receiving the completion of the first synchronization instruction by other transaction servers, the first transaction record table is encapsulated into a first block. In an embodiment of the present application, the asset transfer information is saved in a transaction server and synchronized to other transaction servers, and the data is encapsulated in a block after the synchronization is completed. Since the block contains a universal unique identifier, the data in the block cannot be tampered with, thereby ensuring the security of the asset transfer information.

[0092] It should be understood that in the embodiment of the present application, the radio frequency unit 401 can be used for receiving and sending signals during information transmission or calls. Specifically, after receiving downlink data from the base station, it is sent to the processor 410 for processing; in addition, the uplink data is sent to the base station. Generally, the radio frequency unit 401 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc. In addition, the radio frequency unit 401 can also communicate with the network and other devices through a wireless communication system.

[0093] The electronic device provides users with wireless broadband Internet access through the network module 402, such as helping users to send and receive emails, browse web pages, and access streaming media.

[0094] The audio output unit 403 can convert the audio data received by the RF unit 401 or the network module 402 or stored in the memory 409 into an audio signal and output it as sound. Moreover, the audio output unit 403 can also provide audio output related to a specific function performed by the electronic device 400 (for example, a call signal reception sound, a message reception sound, etc.). The audio output unit 403 includes a speaker, a buzzer, a receiver, etc.

[0095] The input unit 404 is used to receive audio or video signals. The input unit 404 may include a graphics processor (GPU) 4041 and a microphone 4042, and the graphics processor 4041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The processed image frame can be displayed on the display unit 406. The image frame processed by the graphics processor 4041 can be stored in the memory 409 (or other storage medium) or sent via the radio frequency unit 401 or the network module 402. The microphone 4042 can receive sound and can process such sound into audio data. The processed audio data can be converted into a format output that can be sent to a mobile communication base station via the radio frequency unit 401 in the case of a telephone call mode.

[0096] The electronic device 400 also includes at least one sensor 405, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 4061 according to the brightness of the ambient light, and the proximity sensor can turn off the display panel 4061 and / or the backlight when the electronic device 400 is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), and can detect the magnitude and direction of gravity when stationary, which can be used to identify the posture of the electronic device (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; the sensor 405 can also include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, etc., which will not be repeated here.

[0097] The display unit 406 is used to display information input by the user or information provided to the user. The display unit 406 may include a display panel 4061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0098] The user input unit 407 can be used to receive input digital or character information, and to generate key signal input related to user settings and function control of the electronic device. Specifically, the user input unit 407 includes a touch panel 4071 and other input devices 4072. The touch panel 4071, also known as a touch screen, can collect the user's touch operation on or near it (such as the user's operation on the touch panel 4071 or near the touch panel 4071 using any suitable object or accessory such as a finger, stylus, etc.). The touch panel 4071 may include two parts: a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into the contact point coordinates, and then sends it to the processor 410, receives the command sent by the processor 410 and executes it. In addition, the touch panel 4071 can be implemented using various types such as resistive, capacitive, infrared and surface acoustic waves. In addition to the touch panel 4071, the user input unit 407 may also include other input devices 4072. Specifically, other input devices 4072 may include but are not limited to a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail here.

[0099] Furthermore, the touch panel 4071 may be overlaid on the display panel 4061. When the touch panel 4071 detects a touch operation on or near it, it is transmitted to the processor 410 to determine the type of the touch event. Then, the processor 410 provides a corresponding visual output on the display panel 4061 according to the type of the touch event. Figure 4 In the figure, the touch panel 4071 and the display panel 4061 are two independent components to realize the input and output functions of the electronic device. However, in some embodiments, the touch panel 4071 and the display panel 4061 can be integrated to realize the input and output functions of the electronic device, which is not limited here.

[0100] The interface unit 408 is an interface for connecting an external device to the electronic device 400. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, etc. The interface unit 408 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the electronic device 400 or may be used to transmit data between the electronic device 400 and an external device.

[0101] The memory 409 can be used to store software programs and various data. The memory 409 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, at least one application required for a function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area can store data created according to the use of the mobile phone (such as audio data, a phone book, etc.), etc. In addition, the memory 409 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0102] The processor 410 is the control center of the electronic device. It uses various interfaces and lines to connect various parts of the entire electronic device. It executes various functions of the electronic device and processes data by running or executing software programs and / or modules stored in the memory 409, and calling data stored in the memory 409, so as to monitor the electronic device as a whole. The processor 410 may include one or more processing units; preferably, the processor 410 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, etc., and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 410.

[0103] The electronic device 400 may also include a power supply 411 (such as a battery) for supplying power to each component. Preferably, the power supply 411 may be logically connected to the processor 410 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system.

[0104] In addition, the electronic device 400 includes some functional modules not shown, which will not be described in detail here.

[0105] Preferably, an embodiment of the present application also provides an electronic device, including a processor 410, a memory 409, and a computer program stored in the memory 409 and executable on the processor 410. When the computer program is executed by the processor 410, each process of the above-mentioned asset information flow recording method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0106] The embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, each process of the above-mentioned asset information flow recording method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here. The computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0107] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0108] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0109] The embodiments of the present invention are described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the enlightenment of the present invention, ordinary technicians in this field can also make many forms without departing from the scope of protection of the present invention and the claims, all of which are within the protection of the present invention.

Claims

1. A method for recording asset information circulation, characterized in that: Applied to the master server, including: Upon receiving an asset information transfer request sent by the client, sending the asset transfer information and the first universal unique identifier UUID of the first transaction record table to the first transaction server, wherein the asset information transfer request carries the asset transfer information; receiving a first message returned by the first transaction server, where the first message is a notification message that the first transaction server records the asset circulation information into a first transaction record table corresponding to the first UUID; Sending a first synchronization instruction to other transaction servers, where the first synchronization instruction is used to instruct the other transaction servers to synchronize asset transfer information in the first transaction record table from the first transaction server, and the other transaction servers are transaction servers other than the first transaction server; When the other transaction server completes executing the first synchronization instruction, encapsulating the first transaction record table into a first block; The method further comprises: When the cumulative amount of asset transfer information sent to the first transaction server reaches a first preset amount, performing a hash operation on the first preset amount of asset transfer information to obtain a first hash value, and using the first hash value as the hash value of the first block; Sending a hash value generation instruction to the first transaction server; Receiving a second hash value generated according to the first transaction record table and returned by the first transaction server; When the second hash value is the same as the first hash value, it is determined that the first transaction server has completed recording the first transaction record table.

2. The method according to claim 1, characterized in that The method for determining whether the other transaction server has completed the execution of the first synchronization instruction includes: Receive a second message returned by each other transaction server, where the second message carries identification information of the corresponding other transaction server, is a notification message that the corresponding other transaction server has completed executing the first synchronization instruction, and includes a third hash value generated by the corresponding other transaction server according to the first transaction record table; Compare the third hash value in the second message returned by each other transaction server with the second hash value; If each third hash value is the same as the second hash value, it is determined that the other transaction server has completed executing the first synchronization instruction.

3. The method according to claim 1, characterized in that After receiving the second hash value generated according to the first transaction record table and returned by the first transaction server, the method further includes: When the cumulative amount of asset transfer information sent to the first transaction server exceeds a first preset amount, sending the asset transfer information exceeding the first preset amount and the second UUID of the second transaction record table to the first transaction server; receiving a third message returned by the first transaction server, wherein the third message is a notification message that the first transaction server records the asset transfer information of the portion exceeding the first preset amount into the second transaction record table corresponding to the second UUID; Sending a second synchronization instruction to other transaction servers, where the second synchronization instruction is used to instruct the other transaction servers to synchronize asset transfer information in the second transaction record table from the first transaction server; When the other transaction server completes executing the second synchronization instruction, the second transaction record table is encapsulated into a second block.

4. The method according to claim 3, characterized in that The method further comprises: When the cumulative amount of asset transfer information sent to the first transaction server reaches a second preset amount, a hash operation is performed on the portion of the asset transfer information exceeding the first preset amount in the second preset amount to obtain a fourth hash value, and the fourth hash value is used as the hash value of the second block, and the second preset amount is twice the first preset amount; The hash value of the first block is updated with reference to the fourth hash value.

5. An asset information circulation recording device, characterized in that: Applied to the master server, including: A first receiving module is used to send the asset transfer information and the first universal unique identifier UUID of the first transaction record table to the first transaction server when receiving an asset information transfer request sent by the client, wherein the asset information transfer request carries the asset transfer information; A second receiving module is configured to receive a first message returned by the first transaction server, where the first message is a notification message that the first transaction server records the asset circulation information into a first transaction record table corresponding to the first UUID; A first sending module, configured to send a first synchronization instruction to other transaction servers, wherein the first synchronization instruction is used to instruct the other transaction servers to synchronize the asset flow information in the first transaction record table from the first transaction server, and the other transaction servers are transaction servers other than the first transaction server; an encapsulation module, configured to encapsulate the first transaction record table into a first block when the other transaction server completes executing the first synchronization instruction; The device also includes: a calculation module, configured to, when the cumulative amount of asset circulation information sent to the first transaction server reaches a first preset amount, perform a hash operation on the first preset amount of asset circulation information to obtain a first hash value, and use the first hash value as the hash value of the first block; A second sending module, used for sending a hash value generation instruction to the first transaction server; A third receiving module, configured to receive a second hash value generated according to the first transaction record table and returned by the first transaction server; A determination module is used to determine that the first transaction server has completed recording the first transaction record table when the second hash value is the same as the first hash value.

6. The device according to claim 5, characterized in that The packaging module comprises: A first receiving unit is configured to receive a second message returned by each other transaction server, the second message carrying identification information corresponding to the other transaction server, the second message being a notification message that the corresponding other transaction server has completed executing the first synchronization instruction, and the second message including a third hash value generated by the corresponding other transaction server according to the first transaction record table; A comparing unit, configured to compare the third hash value in the second message returned by each other transaction server with the second hash value; A determination unit is configured to determine that the other transaction server has completed the execution of the first synchronization instruction if each third hash value is the same as the second hash value.

7. An electronic device, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps of the method according to any one of claims 1 to 4 when executed by the processor.

8. A computer-readable storage medium, characterized in that: include: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented.

Citation Information

Patent Citations

  • Method and device for generating block, equipment and medium

    CN108830712A

  • Credit certificate transfer method and device, electronic equipment and storage medium

    CN109615515A

  • A data tamper-proofing method based on a block chain

    CN109635595A