A blockchain-based address standardization method, system, device and medium

Abstract

The application provides a blockchain-based address standardization method, system, device and medium, wherein the address standardization method for a submitter comprises obtaining a preset standard parameter and an address text to be standardized; performing first standardization processing on the address text to obtain a first standard text, and performing homomorphic encryption processing on the address text according to the standard parameter to obtain homomorphic encryption data; sending the homomorphic encryption data to a participant to enable the participant to complete second standardization processing on the homomorphic encryption data to obtain mixed data from the participant; and performing decryption verification processing on the mixed data according to the first standard text to obtain a verification result. The address standardization method can achieve address standardization, effectively improve the security and reliability of address data, and effectively improve the security of the verification result. The application relates to the technical field of blockchains.

Description

Technical Field

[0001] This application relates to the field of blockchain technology, and in particular to a blockchain-based address standardization method, system, device, and medium. Background Technology

[0002] In the real world, addresses are important information used to describe geographical location, such as personal addresses, business addresses, and postal addresses. In information systems and data management, address standardization is an indispensable task, which can transform non-standard and inconsistent address data into a unified and standardized format.

[0003] Currently, traditional address standardization processes often involve large amounts of address data. This data is highly susceptible to information leakage during processing, transmission, or storage, resulting in low address data security. Furthermore, traditional address standardization is prone to tampering or manipulation of address verification results, leading to erroneous standardized addresses and consequently, low security and reliability of address data.

[0004] Therefore, the problems existing in the current technology still need to be solved and optimized. Summary of the Invention

[0005] To address at least one of the aforementioned technical problems, this application provides a blockchain-based address standardization method, system, device, and medium. This address standardization method can effectively improve the security and credibility of address data, as well as the security of address verification results, while simultaneously achieving address standardization.

[0006] According to a first aspect of this application, a blockchain-based address standardization method is provided for a submitter, the submitter being used to communicate with at least one participating party, the address standardization method comprising: Obtain the preset standard parameters, and the address text to be standardized; The address text is subjected to a first standardization process to obtain a first standard text, and the address text is subjected to homomorphic encryption processing according to the standard parameters to obtain homomorphic encrypted data. The homomorphically encrypted data is sent to the participants so that the participants can complete the second normalization process on the homomorphically encrypted data to obtain the mixed data from the participants; Based on the first standard text, the mixed data is decrypted and verified to obtain the verification result.

[0007] Further, in this embodiment of the application, the first standardization process of the address text to obtain the first standard text includes: The address text is subjected to first entity recognition processing to obtain first intermediate data; Perform a first multi-modal matching process on the first intermediate data to obtain the second intermediate data; The second intermediate data is subjected to a first filling and correction process to obtain the first standard text.

[0008] Furthermore, in this embodiment, the standard parameters include a security factor, an expansion factor, and a noise factor. The step of performing homomorphic encryption on the address text according to the standard parameters to obtain homomorphically encrypted data includes: Based on the security factor, a first public-private key pair is generated, the first public-private key pair including a first public key and a first private key; The address text is subjected to polynomial mapping to obtain the first address data; Based on the expansion factor and the noise coefficient, the first address data is subjected to noise addition processing to obtain noisy data; Based on the first public key, the noisy data is subjected to arithmetic encryption to obtain the homomorphic encrypted data.

[0009] Further, in this embodiment of the application, the first public key includes a first polynomial and a second polynomial, and the step of performing arithmetic encryption processing on the noisy data according to the first public key to obtain the homomorphic encrypted data includes: According to the first polynomial, the noisy data is subjected to multiplication encryption processing to obtain intermediate multiplication data; According to the second polynomial, the intermediate multiplication data is subjected to addition encryption to obtain the homomorphic encrypted data.

[0010] Further, in this embodiment of the application, the step of decrypting and verifying the mixed data according to the first standard text to obtain the verification result includes: Based on the first private key, the mixed data is homomorphically decrypted to obtain the second standard text; Based on the first standard text, the second standard text is subjected to effective verification processing to obtain the verification result.

[0011] According to a second aspect of this application, a blockchain-based address standardization method is provided for participating parties, the address standardization method comprising: Receive homomorphically encrypted data sent by the submitter; The homomorphically encrypted data is subjected to a second normalization process to obtain hybrid data; The mixed data is sent to the submitter so that the submitter can decrypt and verify the mixed data according to the first standard text to obtain the verification result. The homomorphic encrypted data is obtained through the following steps: The submitter obtains preset standard parameters, as well as the address text to be standardized; The submitter performs a first standardization process on the address text to obtain the first standard text, and performs homomorphic encryption on the address text according to the standard parameters to obtain the homomorphic encrypted data.

[0012] Furthermore, in this embodiment of the application, the second normalization process performed on the homomorphic encrypted data to obtain hybrid data includes: The homomorphically encrypted data is subjected to a second entity recognition process to obtain the third intermediate data; The third intermediate data is subjected to a second multi-modal matching process to obtain the fourth intermediate data; The fourth intermediate data is subjected to a second filling and correction process to obtain the mixed data.

[0013] According to a third aspect of this application, a blockchain-based address standardization system is provided for a submitter, the submitter being used to communicate with at least one participating party, the address standardization system comprising: The acquisition unit is used to acquire preset standard parameters and the address text to be standardized. The processing unit is configured to perform a first standardization process on the address text to obtain a first standard text, and to perform homomorphic encryption on the address text according to the standard parameters to obtain homomorphic encrypted data. A sending unit is configured to send the homomorphically encrypted data to the participants, so that the participants can complete the second normalization process on the homomorphically encrypted data to obtain mixed data from the participants; The verification unit is used to perform decryption verification processing on the mixed data according to the first standard text to obtain the verification result.

[0014] According to a fourth aspect of this application, a computer device is provided, comprising: At least one processor; At least one memory for storing at least one program; When the at least one program is executed by the at least one processor, the at least one processor performs the method as described above.

[0015] According to a fifth aspect of this application, a computer-readable storage medium is provided, wherein a processor-executable program is stored, which, when executed by the processor, is used to implement the method as described above.

[0016] The beneficial effects of the technical solutions provided in this application are: This application provides a blockchain-based address standardization method, system, device, and medium. The method is used by a submitter who communicates with at least one participating party. The address standardization method includes: obtaining preset standard parameters and address text to be standardized; performing a first standardization process on the address text to obtain a first standard text; performing homomorphic encryption on the address text according to the standard parameters to obtain homomorphically encrypted data; sending the homomorphically encrypted data to the participating party, enabling the participating party to perform a second standardization process on the homomorphically encrypted data to obtain mixed data from the participating party; and performing decryption and verification processing on the mixed data according to the first standard text to obtain a verification result. This address standardization method can effectively improve the security and reliability of address data, as well as the security of address verification results, while simultaneously achieving address standardization. Attached Figure Description

[0017] Figure 1 A flowchart illustrating the first blockchain-based address standardization method provided in this application embodiment; Figure 2 A detailed flowchart of the first step S102 provided for the embodiments of this application; Figure 3 A detailed flowchart of the second step S102 provided for embodiments of this application; Figure 4 A detailed flowchart of step S1028 provided for an embodiment of this application; Figure 5 A flowchart illustrating blockchain registration for submitters and participants is provided as an embodiment of this application. Figure 6 A detailed flowchart of step S104 provided for an embodiment of this application; Figure 7 A flowchart illustrating a second blockchain-based address standardization method provided in this application embodiment; Figure 8 A timeline flowchart illustrating a blockchain-based address standardization method provided in this application embodiment; Figure 9 A structural block diagram of a blockchain-based address standardization system provided for embodiments of this application; Figure 10 This is a structural block diagram of a computer device provided in an embodiment of this application. Detailed Implementation

[0018] The present application will be further described below with reference to the accompanying drawings and specific embodiments. The described embodiments should not be considered as limitations on the present application, and all other embodiments obtained by those skilled in the art without inventive effort are within the scope of protection of the present application.

[0019] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0020] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0021] Before introducing the embodiments of this application, several terms involved in this application will be explained: Blockchain: Blockchain technology is a new distributed infrastructure and computing paradigm that uses a chain-like data structure to verify and store data, uses distributed node consensus algorithms to generate and update data, uses cryptography to ensure the security of data transmission and access, and uses smart contracts composed of automated script code to program and manipulate data. A block is the basic data unit in a blockchain, containing a certain amount of transaction information. Each block contains the hash value of the previous block, thus forming a chain-like data structure.

[0022] Smart contracts: Smart contracts are programs (automated script code) that execute automatically on a blockchain, performing transactions or operations according to predefined rules and conditions. Currently, traditional address standardization often involves large amounts of address data, which is highly susceptible to information leakage during processing, transmission, or storage, resulting in low address data security. Furthermore, traditional address standardization is prone to tampering or manipulation of address verification results, leading to incorrect standardized addresses and low security of address verification results, thus reducing the reliability of address data.

[0023] In view of this, embodiments of this application provide a blockchain-based address standardization method, system, device, and medium. The address standardization method can effectively improve the security and credibility of address data, as well as the security of address verification results, while achieving address standardization.

[0024] This application provides a blockchain-based address standardization method, system, device, and medium, which can be specifically described through the following embodiments. First, a blockchain-based address standardization method is described in this application embodiment.

[0025] The blockchain-based address standardization method provided in this application can be applied to data management application scenarios. In these scenarios, data management service providers can use this method to standardize sensitive information such as personal and corporate addresses, effectively improving the security and reliability of address data and reducing the risk of address data leakage or tampering.

[0026] The blockchain-based address standardization method provided in this application can be applied to logistics application scenarios. In logistics applications, the address standardization method provided in this application can be used to standardize the original address information of the recipient or sender, effectively improving the accuracy and efficiency of filling in logistics addresses, reducing the leakage of address information, and effectively protecting the privacy of the recipient or sender.

[0027] This application can be used in a wide variety of general-purpose or special-purpose computer system environments or configurations. Examples include: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, and distributed computing environments including any of the above systems or devices. This application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform specific tasks or implement specific abstract data types. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0028] It should be noted that in all specific embodiments of this application, when processing data related to user identity or characteristics, such as user information, user behavior data, user historical data, and user location information, user permission or consent is obtained first. Furthermore, the collection, use, and processing of this data comply with relevant laws, regulations, and standards. In addition, when embodiments of this application require access to sensitive personal information of users, separate permission or consent from the user is obtained through pop-ups or redirection to confirmation pages. Only after obtaining the user's separate permission or consent is the necessary user-related data required for the proper functioning of these embodiments acquired.

[0029] Understandably, this application also describes one of the blockchain architectures required for implementing a blockchain-based address standardization method, which includes multiple nodes and a blockchain component, with one of the nodes acting as the submitter and the remaining nodes acting as participants.

[0030] Reference Figure 1 , Figure 1 This is an optional flowchart illustrating the first blockchain-based address standardization method provided in this application embodiment. Figure 1 The address standardization method in the document is used by the submitter, who is used to communicate with at least one participant, and may include, but is not limited to, steps S101 to S104.

[0031] Step S101: Obtain the preset standard parameters and the address text to be standardized; In this step, the standard parameters are parameters suitable for multi-party computation protocols between the submitter and multiple participants in the blockchain. The submitter and multiple participants can generate their respective key pairs based on these standard parameters. Furthermore, the address text to be standardized can be address information from a database, including at least one of personal addresses, business addresses, etc. It is understood that the address text mentioned in this application embodiment may only include address information, or it may include address information and corresponding ancillary information, such as name information, telephone number information, administrative region information, postal code information, etc. It is understood that, for ease of understanding, this application embodiment uses an example of address text only including address information, while the inclusion of address text including address information and corresponding ancillary information can be easily deduced by analogy.

[0032] Step S102: Perform a first standardization process on the address text to obtain a first standard text, and perform homomorphic encryption on the address text according to the standard parameters to obtain homomorphic encrypted data; Reference Figure 2Step S102, performing a first standardization process on the address text to obtain a first standard text, includes: Step S1021: Perform first entity recognition processing on the address text to obtain first intermediate data; Step S1022: Perform a first multi-modal matching process on the first intermediate data to obtain the second intermediate data; Step S1023: Perform a first filling and correction process on the second intermediate data to obtain the first standard text.

[0033] In this embodiment, corresponding address standardization rules can be predefined on the blockchain. The submitter executes these address standardization rules through a smart contract to standardize the address text. For example, the entities in the address text can first be extracted using a Named Entity Recognition (NER) algorithm to complete the first entity recognition process. The extracted entities can be address fragments, which can be address information at different levels such as country, province, city, district, street / town, community / village, road / alley, door (building) number, unit number, and apartment number. Address fragments can be flexibly combined according to requirements, which will not be elaborated further in this application.

[0034] Understandably, after completing the first entity recognition process, the obtained address fragments can be used as the first intermediate data. Then, multiple matching methods, such as regular expression (RE) matching and pattern matching, can be used to match and identify the first intermediate data, thereby obtaining the second intermediate data. Specifically, regular expression matching can be used to match and identify the first intermediate data, yielding the regular expression matching result. Similarly, if pattern matching fails, a pattern matching result can be obtained. Finally, the two matching results can be merged to obtain the second intermediate data.

[0035] It is worth mentioning that after obtaining the second intermediate data, the addresses can be filled and corrected using pre-acquired address standardization rules and address data to obtain the first standard text. For example, the address data in the second intermediate data can first be divided by address level, and administrative division correction, long address correction, etc., can be performed on the address information at each level. Missing address information at certain levels can also be filled in, and then the standardized first standard text is output according to the address standardization rules. It should be noted that in this embodiment, when the submitter performs the first standardization processing on the address text, the character format of the address text includes Chinese characters, numbers, letters, and other character formats.

[0036] In some embodiments, refer to Figure 3 The standard parameters include a security factor, an expansion factor, and a noise factor. Step S102, based on the standard parameters, performs homomorphic encryption on the address text to obtain homomorphically encrypted data, including: Step S1025: Generate a first public-private key pair according to the security coefficient, wherein the first public-private key pair includes a first public key and a first private key; Step S1026: Perform polynomial mapping processing on the address text to obtain the first address data; Step S1027: Based on the expansion factor and the noise coefficient, the first address data is subjected to noise addition processing to obtain noisy data; In this embodiment, the standard parameters include a security factor, an expansion factor, and a noise factor. The security factor is used to determine the public-private key pair between the submitter and other participants, while the expansion factor and noise factor are used to determine the noise range of the address text during encryption and decryption. It is worth noting that in the field of cryptography, security and computational efficiency are related. When selecting standard parameters, a balance between security and computational efficiency often needs to be considered. For example, in this embodiment, the security factor can be 2048 bits, the expansion factor can be 2, and the noise factor can be 2. 10 It can determine the noise range of the encryption and decryption process, as well as the public and private key pairs of the submitter and participants, thereby ensuring security while having high computational efficiency. The example in this application is only for illustration, and the specific values ​​can be set according to the actual situation to meet the actual needs.

[0037] Understandably, in this embodiment, each character in the address text can first be mapped into a polynomial form. Specifically, this can be done using either ASCII (American Standard Code for Information Interchange) encoding or Unicode encoding, thereby completing the polynomial mapping process and obtaining the first address data. Next, using a noise range determined by an expansion factor and a noise coefficient, noise is added to each monomial in the first address data to increase the randomness and security of the encrypted first address data, resulting in noisy data.

[0038] Step S1028: Perform arithmetic encryption on the noisy data according to the first public key to obtain the homomorphic encrypted data.

[0039] Furthermore, in some embodiments, reference is made to Figure 4The first public key includes a first polynomial and a second polynomial. Step S1028, which involves performing arithmetic encryption on the noisy data based on the first public key to obtain the homomorphic encrypted data, includes: Step S10281: Perform multiplication encryption processing on the noisy data according to the first polynomial to obtain intermediate multiplication data; Step S10282: According to the second polynomial, perform addition encryption processing on the intermediate multiplication data to obtain the homomorphic encrypted data.

[0040] In the embodiments of this application, reference is made to Figure 5 The first public key and the first private key can be obtained directly from standard parameters when the submitter registers on the blockchain, and the same applies to the registration of participating parties. This application will not elaborate further here. The first public key can contain a first polynomial and a second polynomial, and the first private key can be represented by a private polynomial. The first public key and the first private key have homomorphic encryption properties, meaning that processing homomorphically encrypted data to obtain an output, and then decrypting this output, yields the same result as processing the unencrypted original data using the same method. For example, the homomorphic property between the first public key and the first private key can be expressed by the equivalent formula:

[0041] Where A is the first polynomial in the first public key, s is the private polynomial corresponding to the first private key, B is the second polynomial in the first public key, q is the security coefficient, [1] is used to represent a polynomial that is all 1.

[0042] It is worth mentioning that the noisy data is the first address data after adding noise, and its data format is in digital form. Therefore, the noisy data can be multiplied by using the first polynomial in the first public key, and the resulting product can be used as the intermediate data for multiplication. Then, the intermediate data for multiplication can be added by the second polynomial in the second public key, and the sum can be used as the homomorphic encrypted data.

[0043] Step S103: Send the homomorphic encrypted data to the participants so that the participants can complete the second normalization process on the homomorphic encrypted data and obtain the mixed data from the participants; In this embodiment of the application, after obtaining homomorphic encrypted data, the submitter can forward the homomorphic encrypted data to the participants through the blockchain. The participants can then call the address standardization rules to perform a second standardization process on the homomorphic encrypted data. Finally, the participants can send the mixed data to the submitter through the blockchain.

[0044] Step S104: Decrypt and verify the mixed data according to the first standard text to obtain the verification result.

[0045] Reference Figure 6 Step S104, which involves decrypting and verifying the mixed data based on the first standard text to obtain a verification result, includes: Step S1041: Based on the first private key, perform homomorphic decryption on the mixed data to obtain the second standard text; Step S1042: Based on the first standard text, perform effective verification processing on the second standard text to obtain the verification result.

[0046] In this embodiment, after receiving the mixed data, the submitter can use its own first private key to perform homomorphic decryption on the mixed data to obtain the second standard text. The data format of the second standard text is consistent with that of the first standard text. Then, the verification result can be obtained by comparing whether the first and second standard texts are consistent. It is worth noting that the verification result in this embodiment can include the comparison result between the first and second standard texts, as well as the execution task corresponding to the comparison result.

[0047] For example, in a blockchain, there are often multiple participants. Therefore, after receiving mixed data sent by multiple participants, the submitter can repeatedly execute steps S1041 and S1042 to obtain the verification results between the submitter and each participant, and execute the corresponding task based on the verification results. It is understood that if the verification results are consistent between the submitter and each participant, the submitter can record the first standard text on the blockchain through a smart contract based on these verification results. If the verification results are inconsistent between the submitter and one or more participants, the submitter can re-execute steps S101 to S104 based on these verification results. The specific execution method can be configured according to parameters such as the number of retries and the retry interval, and a specific retry mechanism can be set. This example is for illustrative purposes only and does not limit the application; it should meet the actual needs.

[0048] Reference Figure 7 , Figure 7 A flowchart illustrating a second blockchain-based address standardization method provided in this application embodiment, for use by participating parties, the address standardization method comprising: Step S105: Receive homomorphic encrypted data sent by the submitter; Step S106: Perform a second normalization process on the homomorphic encrypted data to obtain hybrid data; Step S106 involves performing a second normalization process on the homomorphic encrypted data to obtain hybrid data, including: Step S1061: Perform a second entity recognition process on the homomorphic encrypted data to obtain third intermediate data; Step S1062: Perform a second multi-modal matching process on the third intermediate data to obtain the fourth intermediate data; Step S1063: Perform a second filling and correction process on the fourth intermediate data to obtain the mixed data.

[0049] In this embodiment, the participants can standardize homomorphic encrypted data by calling the address standardization rules on the smart contract. The second standardization process is similar to the first standardization process mentioned above and can be easily deduced by analogy. Therefore, this application will not elaborate further here.

[0050] Step S107: Send the mixed data to the submitter so that the submitter can decrypt and verify the mixed data according to the first standard text to obtain the verification result; The homomorphic encrypted data is obtained through the following steps: The submitter obtains preset standard parameters, as well as the address text to be standardized; The submitter performs a first standardization process on the address text to obtain the first standard text, and performs homomorphic encryption on the address text according to the standard parameters to obtain the homomorphic encrypted data.

[0051] Understandably, referring to Figure 8 In a blockchain, the submitter and the participant are not fixed and can flexibly change according to the task progress of each node in the blockchain. For example, at a certain moment, when node A needs to standardize the address text stored in itself, node B can be a participant. Node A sends homomorphically encrypted data to node B, node B returns mixed data to node A, and node A decrypts it. The decrypted mixed data (second standard text) is then verified against the first standard text to determine the validity and correctness of the standardized address sent by the participant. Then, at the next moment, when node B needs to standardize the address text stored in itself, node B's role automatically changes to submitter, and node A's role automatically changes to participant. The subsequent actions of the submitter and participant are similar to those described above, and will not be elaborated further in this application.

[0052] In summary, the address standardization method described in this application can effectively improve the security of address verification results and the security and reliability of address data by performing address verification without exposing plaintext data, while simultaneously achieving address standardization.

[0053] Figure 9 This application provides a blockchain-based address standardization system for use by a submitter, which communicates with at least one participating party. The address standardization system includes: The acquisition unit 310 is used to acquire preset standard parameters and address text to be standardized; The processing unit 320 is configured to perform a first standardization process on the address text to obtain a first standard text, and to perform homomorphic encryption on the address text according to the standard parameters to obtain homomorphic encrypted data. The sending unit 330 is used to send the homomorphic encrypted data to the participants so that the participants can complete the second normalization process of the homomorphic encrypted data and obtain the mixed data from the participants. The verification unit 340 is used to perform decryption verification processing on the mixed data according to the first standard text to obtain the verification result.

[0054] It is understood that the content of the above method embodiments is applicable to this system embodiment. The specific functions implemented in this system embodiment are the same as those in the above method embodiments, and the beneficial effects achieved are also the same as those achieved in the above method embodiments.

[0055] Figure 10 A schematic diagram of the structure of a computer device provided in this application embodiment includes: At least one processor 980; At least one memory 920 is used to store at least one program; When the at least one program is executed by the at least one processor 980, the at least one processor 980 performs the method as described in the foregoing embodiments.

[0056] This application also provides a computer-readable storage medium storing a processor-executable program, which, when executed by the processor 980, is used to implement the methods described in the foregoing embodiments.

[0057] Figure 10 Specifically, computer equipment can be either a user terminal or a server.

[0058] This application uses a computer device as a user terminal as an example, as detailed below: like Figure 10As shown, the computer device 900 may include an RF (Radio Frequency) circuit 910, a memory 920 including one or more computer-readable storage media, an input unit 930, a display unit 940, a sensor 950, an audio circuit 960, a WiFi module 970, a processor 980 including one or more processing cores, and a power supply 990, among other components. Those skilled in the art will understand that... Figure 10 The device structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0059] The RF circuit 910 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink information from the base station and hands it over to one or more processors 980 for processing; additionally, it transmits uplink data to the base station. Typically, the RF circuit 910 includes, but is not limited to, an antenna, at least one amplifier, a tuner, one or more oscillators, a Subscriber Identity Module (SIM) card, a transceiver, a coupler, an LNA (Low Noise Amplifier), a duplexer, etc. Furthermore, the RF circuit 910 can also communicate wirelessly with networks and other devices. Wireless communication can use any communication standard or protocol, including but not limited to GSM (Global System for Mobile communication), GPRS (General Packet Radio Service), CDMA (Code Division Multiple Access), WCDMA (Wideband Code Division Multiple Access), LTE (Long Term Evolution), email, SMS (Short Messaging Service), etc.

[0060] The memory 920 can be used to store software programs and modules. The processor 980 executes various functional applications and data processing by running the software programs and modules stored in the memory 920. The memory 920 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the device 900 (such as audio data, telephone directory, etc.). In addition, the memory 920 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 920 may also include a memory controller to provide access to the memory 920 for the processor 980 and the input unit 930. Although Figure 10 The RF circuit 910 is shown, but it is understood that it is not a necessary component of the device 900 and can be omitted as needed without changing the nature of the invention.

[0061] The input unit 930 can be used to receive input digital or character information, and to generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control. Specifically, the input unit 930 may include a touch-sensitive surface 932 and other input devices 931. The touch-sensitive surface 932, also known as a touch display screen or touchpad, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch-sensitive surface 932), and drive the corresponding connection device according to a pre-set program. Optionally, the touch-sensitive surface 932 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, sends it to the processor 980, and can receive and execute commands from the processor 980. In addition, the touch-sensitive surface 932 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch-sensitive surface 932, the input unit 930 may also include other input devices 931. Specifically, other input devices 931 may include, but are not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc.

[0062] Display unit 940 can be used to display information input by the user or information provided to the user, as well as various graphical user interfaces for controlling 900. These graphical user interfaces can be composed of graphics, text, icons, video, and any combination thereof. Display unit 940 may include display panel 941, optionally configured as LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), etc. Further, touch-sensitive surface 932 may cover display panel 941. When touch-sensitive surface 932 detects a touch operation on or near it, it transmits the information to processor 980 to determine the type of touch event. Subsequently, processor 980 provides corresponding visual output on display panel 941 according to the type of touch event. Although in Figure 10 In this embodiment, the touch-sensitive surface 932 and the display panel 941 are implemented as two separate components to realize input and output functions. However, in some embodiments, the touch-sensitive surface 932 and the display panel 941 can be integrated to realize input and output functions.

[0063] The computer device 900 may also include at least one sensor 950, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor. The ambient light sensor can adjust the brightness of the display panel 941 according to the ambient light level, and the proximity sensor can turn off the display panel 941 and / or backlight when the device 900 is moved to the ear. As a type of motion sensor, a gravity acceleration sensor can detect the magnitude of acceleration in various directions (generally three axes). When stationary, it can detect the magnitude and direction of gravity and can be used for applications that recognize the phone's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition-related functions (such as pedometers, taps), etc. Other sensors that the device 900 may be equipped with, such as gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.

[0064] Audio circuitry 960, speaker 961, and microphone 962 provide an audio interface between the user and device 900. Audio circuitry 960 converts received audio data into electrical signals, which are then transmitted to speaker 961, where they are converted into sound signals for output. Conversely, microphone 962 converts collected sound signals into electrical signals, which are received by audio circuitry 960, converted back into audio data, and then processed by processor 980 before being transmitted via RF circuitry 910 to another control device, or output to memory 920 for further processing. Audio circuitry 960 may also include an earphone jack to facilitate communication between peripheral headphones and device 900.

[0065] Device 900 can transmit information with the wireless transmission module set up on the battle equipment via WiFi module 970.

[0066] The processor 980 is the control center of the device 900. It connects various parts of the control device via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 920, and by calling data stored in the memory 920, it performs various functions of the device 900 and processes data, thereby providing overall monitoring of the control device. Optionally, the processor 980 may include one or more processing cores; optionally, the processor 980 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the aforementioned modem processor may also not be integrated into the processor 980.

[0067] The device 900 also includes a power supply 990 (such as a battery) that supplies power to the various components. Preferably, the power supply can be logically connected to the processor 980 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 990 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0068] Although not shown, device 900 may also include a camera, Bluetooth module, etc., which will not be described in detail here.

[0069] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to perform the methods described in the foregoing embodiments.

[0070] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatuses.

[0071] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0072] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.

[0073] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0074] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0075] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0076] The step numbers in the above method embodiments are set only for ease of explanation and do not limit the order of the steps. The execution order of each step in the embodiments can be adaptively adjusted according to the understanding of those skilled in the art.

[0077] The above is a detailed description of the preferred embodiments of this application, but this application is not limited to the embodiments described. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of this application, and these equivalent modifications or substitutions are all included within the scope defined by the claims of this application.

Claims

1. A blockchain-based address standardization method, characterized in that, For use by a submitter, the submitter being used to communicate with at least one participating party, the address standardization method includes: Obtain the preset standard parameters, and the address text to be standardized; The address text is subjected to a first standardization process to obtain a first standard text, and the address text is subjected to homomorphic encryption processing according to the standard parameters to obtain homomorphic encrypted data. The homomorphically encrypted data is sent to the participants so that the participants can complete the second normalization process on the homomorphically encrypted data to obtain the hybrid data from the participants; Based on the first standard text, the mixed data is decrypted and verified to obtain the verification result; The standard parameters include a security factor, an expansion factor, and a noise factor. The process of performing homomorphic encryption on the address text based on these standard parameters to obtain homomorphically encrypted data includes: Based on the security factor, a first public-private key pair is generated, the first public-private key pair including a first public key and a first private key; The address text is subjected to polynomial mapping to obtain the first address data; Based on the expansion factor and the noise coefficient, the first address data is subjected to noise addition processing to obtain noisy data; Based on the first public key, the noisy data is subjected to arithmetic encryption to obtain the homomorphic encrypted data; The step of decrypting and verifying the mixed data based on the first standard text to obtain the verification result includes: Based on the first private key, the mixed data is homomorphically decrypted to obtain the second standard text; Based on the first standard text, the second standard text is subjected to effective verification processing to obtain the verification result.

2. The blockchain-based address standardization method according to claim 1, characterized in that, The first standardization process of the address text to obtain the first standard text includes: The address text is subjected to first entity recognition processing to obtain first intermediate data; Perform a first multi-modal matching process on the first intermediate data to obtain the second intermediate data; The second intermediate data is subjected to a first filling and correction process to obtain the first standard text.

3. The blockchain-based address standardization method according to claim 2, characterized in that, The first public key includes a first polynomial and a second polynomial. The step of performing arithmetic encryption on the noisy data based on the first public key to obtain the homomorphic encrypted data includes: According to the first polynomial, the noisy data is subjected to multiplication encryption processing to obtain intermediate multiplication data; According to the second polynomial, the intermediate multiplication data is subjected to addition encryption to obtain the homomorphic encrypted data.

4. A blockchain-based address standardization method, characterized in that, For participating parties, the address standardization method includes: Receive homomorphically encrypted data sent by the submitter; The homomorphically encrypted data is subjected to a second normalization process to obtain hybrid data; The mixed data is sent to the submitter so that the submitter can decrypt and verify the mixed data according to the first standard text to obtain the verification result. The homomorphic encrypted data is obtained through the following steps: The submitter obtains preset standard parameters, as well as the address text to be standardized; The submitter performs a first standardization process on the address text to obtain the first standard text, and performs homomorphic encryption on the address text according to the standard parameters to obtain the homomorphic encrypted data. The standard parameters include a security factor, an expansion factor, and a noise factor. The process of performing homomorphic encryption on the address text based on these standard parameters to obtain homomorphically encrypted data includes: Based on the security factor, a first public-private key pair is generated, the first public-private key pair including a first public key and a first private key; The address text is subjected to polynomial mapping to obtain the first address data; Based on the expansion factor and the noise coefficient, the first address data is subjected to noise addition processing to obtain noisy data; Based on the first public key, the noisy data is subjected to arithmetic encryption to obtain the homomorphic encrypted data; The step of decrypting and verifying the mixed data based on the first standard text to obtain the verification result includes: Based on the first private key, the mixed data is homomorphically decrypted to obtain the second standard text; Based on the first standard text, the second standard text is subjected to effective verification processing to obtain the verification result.

5. The blockchain-based address standardization method according to claim 4, characterized in that, The second normalization process performed on the homomorphically encrypted data to obtain hybrid data includes: The homomorphically encrypted data is subjected to a second entity recognition process to obtain the third intermediate data; The third intermediate data is subjected to a second multi-modal matching process to obtain the fourth intermediate data; The fourth intermediate data is subjected to a second filling and correction process to obtain the mixed data.

6. A blockchain-based address standardization system, characterized in that, For use by a submitter, the submitter is used to communicate with at least one participating party, the address standardization system comprising: The acquisition unit is used to acquire preset standard parameters and the address text to be standardized. The processing unit is configured to perform a first standardization process on the address text to obtain a first standard text, and to perform homomorphic encryption on the address text according to the standard parameters to obtain homomorphic encrypted data. A sending unit is configured to send the homomorphically encrypted data to the participants, so that the participants can complete the second normalization process on the homomorphically encrypted data to obtain mixed data from the participants; The verification unit is used to perform decryption and verification processing on the mixed data according to the first standard text to obtain the verification result; The standard parameters include a security factor, an expansion factor, and a noise factor. The process of performing homomorphic encryption on the address text based on these standard parameters to obtain homomorphically encrypted data includes: Based on the security factor, a first public-private key pair is generated, the first public-private key pair including a first public key and a first private key; The address text is subjected to polynomial mapping to obtain the first address data; Based on the expansion factor and the noise coefficient, the first address data is subjected to noise addition processing to obtain noisy data; Based on the first public key, the noisy data is subjected to arithmetic encryption to obtain the homomorphic encrypted data; The step of decrypting and verifying the mixed data based on the first standard text to obtain the verification result includes: Based on the first private key, the mixed data is homomorphically decrypted to obtain the second standard text; Based on the first standard text, the second standard text is subjected to effective verification processing to obtain the verification result.

7. A computer device, characterized in that, include: At least one processor; At least one memory for storing at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements the method as described in any one of claims 1-5.

8. A computer-readable storage medium storing a processor-executable program, characterized in that, The processor-executable program, when executed by the processor, is used to implement the method as described in any one of claims 1-5.

Images