Distributed storage methods, devices, equipment, and media for payment data

Abstract

This application discloses a distributed storage method, apparatus, device, and medium for payment data, relating to the field of data processing technology. The method includes: acquiring transaction data and confirming the transaction data; using erasure coding technology to segment the confirmed transaction data to obtain multiple transaction data segments; acquiring multiple target mobile terminals for storing the transaction data; and storing the multiple transaction data segments in the multiple target mobile terminals according to preset storage rules. Addressing the issue of continuously increasing data storage costs in payment systems, this application reconstructs the payment data storage architecture through mobile terminal edge computing and blockchain redundant storage, reducing cloud storage costs by more than 80% while effectively ensuring data security and queryability.

Description

Technical Field

[0001] This disclosure generally relates to the field of data processing technology, and specifically to a distributed storage method, apparatus, device, and medium for payment data. Background Technology

[0002] With the widespread adoption of mobile payments, mobile payment data has grown dramatically. Related technologies typically employ centralized cloud storage, traditional database sharding, and public blockchains for storage. Centralized cloud storage centrally stores all transaction data in a cloud database, such as a MySQL cluster. Traditional database sharding stores data in shards based on time or user ID. Public blockchains are decentralized, immutable, distributed ledger systems. Both centralized cloud storage and traditional database sharding are centralized storage methods; the cost of centralized cloud storage increases linearly with data growth, leading to higher annual storage fees. Furthermore, centralized architectures are susceptible to single points of failure, and system availability depends on the cloud. While public blockchain technology offers advantages such as decentralization and immutability, traditional blockchain nodes consume a lot of energy, making them unsuitable for high-frequency transaction scenarios in payment systems. Summary of the Invention

[0003] In view of the above-mentioned defects or deficiencies in the existing technology, it is desirable to provide a distributed storage method, device, equipment and medium for payment data. In response to the problem of the continuous increase in data storage costs of payment systems, the payment data storage architecture is reconstructed by mobile terminal edge computing and blockchain redundant storage, which reduces cloud storage costs by more than 80% while effectively ensuring data security and queryability.

[0004] In a first aspect, embodiments of this application provide a distributed storage method for payment data, including: Obtain transaction data and confirm the transaction data; Erasure coding technology is used to fragment the confirmed transaction data, resulting in multiple transaction data fragments; Acquire multiple target mobile terminals for storing the transaction data; The transaction data fragments are stored in multiple target mobile terminals according to preset storage rules.

[0005] In some embodiments, acquiring a plurality of target mobile terminals for storing the transaction data includes: For multiple initially selected mobile terminals, detect the real-time status of the initially selected mobile terminals; When the real-time status of the initially selected mobile terminal meets the preset conditions, the size of the available storage space of the initially selected mobile terminal is obtained. The initially selected mobile terminals whose available storage space is greater than or equal to the transaction data fragment are selected as candidate mobile terminals. From the candidate mobile terminals, a plurality of target mobile terminals are selected according to preset conditions.

[0006] In some embodiments, it also includes: For each target mobile terminal, the online duration of the target mobile terminal used to store the transaction data fragment is obtained; Based on the online duration, the reward resource information corresponding to the target mobile terminal is determined.

[0007] In some embodiments, it also includes: For each target mobile terminal, obtain the response speed of the target mobile terminal when querying the transaction data shard; Based on the response speed, determine the additional reward resource information corresponding to the target mobile terminal.

[0008] In some embodiments, it also includes: The target mobile terminal completes the storage of the transaction data fragment by synchronizing the block header corresponding to the transaction data fragment and verifying the verification information corresponding to the transaction data fragment.

[0009] In some embodiments, confirming the transaction data includes: The target trusted node confirms the transaction data; The target trust node is a pre-selected trust node with a clear identity.

[0010] Secondly, embodiments of this application provide a distributed storage device for payment data, comprising: The first acquisition module is used to acquire transaction data and confirm the transaction data; The sharding module is used to shard the confirmed transaction data using erasure coding technology to obtain multiple transaction data shards. The second acquisition module is used to acquire multiple target mobile terminals for storing the transaction data; The storage module is used to store multiple transaction data fragments into multiple target mobile terminals according to preset storage rules.

[0011] Thirdly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the method described in embodiments of this application.

[0012] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in embodiments of this application.

[0013] Fifthly, embodiments of this application provide a computer program product, including a computer program, characterized in that, when the computer program is executed by a processor, it implements the method described in embodiments of this application.

[0014] The distributed storage method, apparatus, device, and medium for payment data proposed in this application acquire and confirm transaction data. Erasure coding technology is used to segment the confirmed transaction data into multiple transaction data segments, which are then used to acquire multiple target mobile terminals for storing the transaction data. These multiple transaction data segments are stored in the multiple target mobile terminals according to preset storage rules. This effectively addresses the problem of continuously increasing data storage costs in payment systems by reconstructing the payment data storage architecture through mobile terminal edge computing and blockchain redundant storage, reducing cloud storage costs by more than 80% while effectively ensuring data security and queryability. Furthermore, pre-selected, clearly identified authorized nodes are used for transaction data confirmation, effectively ensuring transaction data confirmation efficiency.

[0015] Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0016] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings: Figure 1 The implementation environment architecture diagram of the distributed storage method for payment data provided in the embodiments of this application is shown; Figure 2 A flowchart illustrating a distributed storage method for payment data according to an embodiment of this application is shown; Figure 3 This invention provides a schematic diagram of the structure of a distributed storage device for payment data according to an embodiment of the present application. Figure 4 A schematic diagram of the structure of a computer system suitable for implementing an electronic device or server according to embodiments of this application is shown. Detailed Implementation

[0017] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings.

[0018] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0019] For the specific implementation environment of the distributed storage method for payment data proposed in this application, please refer to [link / reference needed]. Figure 1 . Figure 1 The diagram illustrates the implementation environment architecture of the distributed storage method for payment data provided in this application embodiment.

[0020] like Figure 1 As shown, the implementation environment architecture includes: target mobile terminal 101, target trusted node 102, and edge computing node 103.

[0021] The target mobile terminal 101 is used to store transaction data fragments that have been confirmed and fragmented by the transaction server. The target mobile terminal 101 has other conventional functions besides storing transaction data fragments. The target mobile terminal 101 can be a desktop computer, laptop computer, smartphone, tablet computer, e-book reader, smart glasses, smartwatch, in-vehicle device, ultra-mobile personal computer (UMPC), netbook, as well as cellular phone, personal digital assistant (PDA), augmented reality (AR), virtual reality (VR) device, etc., but is not limited to these.

[0022] The target trusted node 102 is used to confirm the transaction data. The edge computing node 103 is communicatively connected to both the target mobile terminal 101 and the target trusted node 102 to implement the distributed storage method for payment data proposed in this application. The edge computing node 103 can be a distributed node of the transaction server.

[0023] Edge computing node 103 is directly or indirectly connected to target mobile terminal 101 and target authorized node 102 via wired or wireless communication. Optionally, the aforementioned wireless or wired network uses standard communication technologies and / or protocols. The network is typically the Internet, but can also be any network, including but not limited to any combination of Local Area Network (LAN), Metropolitan Area Network (MAN), Wide Area Network (WAN), mobile, wired or wireless network, private network, or virtual private network.

[0024] also, Figure 1 The number of target mobile terminals, target trusted nodes and edge computing nodes shown is merely exemplary, and may actually include other numbers of target mobile terminals, target trusted nodes and edge computing nodes. This application does not specifically limit this number.

[0025] The distributed storage method for payment data proposed in this application can be implemented by a distributed storage device for payment data, which can be installed on a terminal device (i.e., an edge computing node) or a server.

[0026] To further illustrate the technical solutions provided in the embodiments of this application, a detailed description is provided below in conjunction with the accompanying drawings and specific implementation methods. Although the embodiments of this application provide method operation instruction steps as shown in the following embodiments or drawings, the method may include more or fewer operation instruction steps based on conventional or non-creative effort. In steps where there is no logically necessary causal relationship, the execution order of these steps is not limited to the execution order provided in the embodiments of this application. In actual processing or when the device executes the method, it may be executed sequentially or in parallel according to the method shown in the embodiments or drawings.

[0027] It should be noted that the acquisition or use of data in the embodiments of this application requires the user's consent. The relevant data can only be obtained after the user's authorization and permission, and the acquisition or use of the data complies with the laws and regulations of the relevant regions.

[0028] Please refer to Figure 2 , Figure 2 A flowchart illustrating a distributed storage method for payment data according to an embodiment of this application is shown. Figure 2 As shown, the method includes: Step 201: Obtain transaction data and confirm the transaction data.

[0029] It should be noted that when a payment transaction occurs, transaction data can be generated, such as through a POS (point of sale) server.

[0030] In a preferred embodiment, when a payment transaction occurs, the edge computing node of the transaction server acquires the transaction data generated by the payment transaction. The edge computing node of the transaction server can be a mobile terminal such as a user's mobile phone, which acquires the transaction data as a computing element in a distributed server system.

[0031] Furthermore, the target credit node confirms the transaction data. The target credit node is a pre-selected credit node with a clearly identified identity.

[0032] It should be noted that, compared to the traditional blockchain system where accounting server nodes participate anonymously through staking tokens, this application proposes to use pre-selected nodes with clearly defined identities as trust nodes, which effectively ensures the efficiency and stability of the core accounting layer and complies with the regulatory requirements of the financial system.

[0033] In one feasible embodiment, the authorized node can be a pre-selected authorized node with a clearly defined identity, such as a mobile terminal used by a user registered with the payment system operator. That is, the payment system server determines the node's identity through node registration and selects a node that can be used as an authorized node from multiple registered nodes according to preset rules. The preset rules can be the contribution of the mobile terminal in the payment data storage system. For example, the contribution value can be calculated based on factors such as the mobile terminal's online time, the number of transaction data fragments stored, the storage duration of the transaction data fragments, and the response speed. If the contribution value is greater than or equal to a preset contribution threshold, the mobile terminal is determined to be an authorized node; if the contribution value is less than the preset contribution threshold, the mobile terminal is determined not to be an authorized node.

[0034] In some embodiments, after the transaction server obtains the transaction data, it selects a target trust node from multiple trust nodes, such as a mobile terminal that is currently online and has sufficient computing power as the target trust node, and then sends the transaction data to the target trust node, which confirms the transaction data.

[0035] Specifically, any candidate credit node is obtained according to a preset selection rule. The system then identifies whether the candidate credit node is online. If it is online, its available computing power is further determined. If the available computing power is greater than or equal to a preset computing power threshold, the candidate credit node is selected as the target credit node, and the transaction data is sent to the target credit node for confirmation. If the candidate credit node is not online or its available computing power is less than the preset computing power threshold, the next candidate credit node is obtained according to the preset selection rule. The preset selection rule can be a random rule or a rule based on distance from the transaction data, etc., and this application does not impose specific limitations on it.

[0036] In other embodiments, since the mobile terminal serving as the edge computing node of the transaction server also has a clearly identified identity, it can be selected as a trusted node. Specifically, after acquiring transaction data, the edge computing node of the transaction server directly determines whether it belongs to the target trusted node, for example, whether its computing power is sufficient. If it belongs to the target trusted node, it directly confirms the transaction data. If it does not belong to the target trusted node, it selects the target trusted node from multiple trusted nodes and then sends the transaction data to the target trusted node for confirmation.

[0037] Furthermore, there can be multiple target trusted nodes, for example, 5-10. That is, after the transaction server obtains the transaction data, it selects a preset number of target trusted nodes from multiple candidate trusted nodes, and then sends the transaction data to each target trusted node for confirmation. Alternatively, after the edge computing node of the transaction server obtains the transaction data, it determines whether it belongs to a target trusted node. If it does, it selects a preset number - 1 target trusted nodes from multiple trusted nodes, and then sends the transaction data to these preset number - 1 target trusted nodes for confirmation. If it does not belong to a target trusted node, it selects a preset number of target trusted nodes from multiple trusted nodes, and then sends the transaction data to each target trusted node for confirmation.

[0038] Step 202: The confirmed transaction data is fragmented using erasure coding technology to obtain multiple transaction data fragments.

[0039] It should be noted that erasure coding (EC) is a data protection method that achieves fault tolerance through data segmentation and redundant coding. Its core principle is to divide the original data into k segments and generate m redundant blocks, forming n=k+m data blocks for distributed storage, ensuring that complete information can still be recovered even if some data is lost.

[0040] Specifically, after the transaction data is confirmed by the target trusted node, the transaction server or the edge computing node of the transaction server uses erasure coding technology to fragment the transaction data, resulting in multiple transaction data fragments.

[0041] It should be noted that the number of transaction data shards corresponding to each transaction data can be fixed or variable. When the number of transaction data shards is variable, the number of transaction data shards can be dynamically adjusted according to the data popularity and importance of the transaction data. This application does not impose specific limitations on this.

[0042] Step 203: Obtain multiple target mobile terminals for storing transaction data.

[0043] In other words, after dividing the transaction data into multiple transaction data fragments, it is necessary to select a storage device, i.e., the target mobile terminal, to store the transaction data fragments, so as to transfer the storage cost to the edge by transforming a massive number of mobile terminals into distributed storage nodes.

[0044] Specifically, for multiple initially selected mobile terminals, the real-time status of the initially selected mobile terminals is detected; when the real-time status of the initially selected mobile terminals meets the preset conditions, the size of the available storage space of the initially selected mobile terminals is obtained; initially selected mobile terminals with available storage space greater than or equal to the transaction data fragments are selected as candidate mobile terminals; from the candidate mobile terminals, multiple target mobile terminals are selected according to the preset conditions.

[0045] In other words, mobile terminals with communication and storage capabilities can be used as initial selection terminals. Then, the real-time status of these initial selection terminals is monitored. This real-time status includes, but is not limited to, the network and power status of the initial selection terminals, such as network stability and whether they are in power-saving mode. Therefore, by sensing the real-time status and available storage space of the terminal devices, the data distribution storage strategy can be dynamically optimized, ensuring the reliability and stability of transaction data sharding storage.

[0046] If the initial mobile terminal's real-time status is stable and not in power-saving mode, the available storage space of the initial mobile terminal is obtained, and it is determined whether the available storage space is greater than or equal to the transaction data fragment. If the available storage space is greater than or equal to the transaction data fragment, the initial mobile terminal is selected as a candidate mobile terminal. If the available storage space is less than the transaction data fragment, the initial mobile terminal is not selected as a candidate mobile terminal for the current transaction data. Finally, multiple target mobile terminals are selected from the candidate mobile terminals according to preset conditions.

[0047] It should be noted that the preset conditions for selecting the target mobile terminal from the candidate mobile terminals can be conditions set for purposes such as improving the efficiency of transaction data query or reducing transmission costs. For example, the priority of candidate mobile terminals can be calculated based on their online time, response speed, and distance from the location where the transaction data was generated during a historical period, and the target mobile terminal can be selected according to the priority of the candidate mobile terminals.

[0048] It should also be noted that the number of target mobile terminals selected can be related to the number of transaction data fragments; that is, the number of target mobile terminals needs to ensure the fault tolerance capability of the transaction data fragment storage. For example, if the transaction data is divided into 4 fragments and 2 redundant blocks are generated, then the number of target mobile terminals can be determined to be 3, so that 2 transaction data fragments (including fragments and redundant blocks) are stored on each target mobile terminal. This design can utilize the fault tolerance capability of erasure coding, so that even if any 2 fragments are lost (e.g., a node fails), the original data can still be completely recovered from the remaining fragments, thereby effectively improving the balanced storage efficiency and data reliability of distributed transaction data storage.

[0049] In one specific embodiment, the following code can be used: { "tx_id":"TX202311230001", "data_shards": 4, "parity_shards": 2, "storage_nodes": ["device_123","device_456","device_789"] } In other words, the transaction data with the number TX202311230001 is divided into 4 fragments and 2 redundant blocks are generated. These fragments will then be stored on the target mobile terminals "device_123", "device_456", and "device_789".

[0050] Step 204: Store multiple transaction data fragments into multiple target mobile terminals according to preset storage rules.

[0051] It should be noted that the transaction data fragments are stored in the target mobile terminal as encrypted data blocks, and only the payment system can decrypt and query them.

[0052] Furthermore, in order to improve the efficiency of storing payment data fragments on the target mobile terminal and ensure the stability of the target mobile terminal user experience, when storing payment data fragments on the target mobile terminal, the target mobile terminal verifies the transaction data fragments by synchronizing the block headers corresponding to the transaction data fragments and verifying the verification information corresponding to the transaction data fragments.

[0053] In other words, the target mobile terminal focuses on storage functions and does not participate in consensus. It combines the aforementioned pre-selected, clearly identified authorized nodes for transaction confirmation, effectively achieving efficiency balance and decentralization under the payment data storage architecture.

[0054] In one feasible embodiment, after storing transaction data fragments, the target mobile terminal submits storage proofs at a preset frequency to ensure that the transaction data fragments are recoverable. It should be understood that when transaction data needs to be recovered, it is recovered from the transaction data fragments effectively stored in multiple online target mobile terminals.

[0055] Therefore, the distributed storage method for payment data proposed in this application obtains and confirms transaction data, and uses erasure coding technology to segment the confirmed transaction data into multiple transaction data segments. Multiple target mobile terminals are then acquired to store the transaction data. These multiple transaction data segments are stored in the multiple target mobile terminals according to preset storage rules. This effectively addresses the problem of continuously increasing data storage costs in payment systems by reconstructing the payment data storage architecture through mobile terminal edge computing and blockchain redundant storage, reducing cloud storage costs by more than 80% while effectively ensuring data security and queryability. Furthermore, the use of pre-selected, clearly identified authorized nodes for transaction data confirmation effectively ensures efficient transaction data confirmation.

[0056] Furthermore, in order to ensure that there are sufficient redundant storage devices (i.e., target mobile terminals) participating in data storage and to guarantee the reliability of data query, this application also proposes an incentive method for the target mobile terminal.

[0057] Specifically, for each target mobile terminal, the online duration used by the target mobile terminal to store transaction data shards is obtained; based on the online duration, the reward resource information corresponding to the target mobile terminal is determined.

[0058] In other words, only by ensuring sufficient online time can the target mobile terminal respond promptly during data storage and retrieval, and provide storage and retrieval functions. Therefore, the online time of the target mobile terminal is an important reference factor for reward resource information.

[0059] In a preferred embodiment, for each target mobile terminal, the response speed of the target mobile terminal when querying transaction data shards is obtained, and the additional reward resource information corresponding to the target mobile terminal is determined based on the response speed.

[0060] In other words, additional reward resources can be provided to the target mobile terminal based on its response speed, in order to encourage users to use mobile terminals with faster response speeds and higher availability to obtain higher additional reward resources.

[0061] In one specific embodiment, the reward resource information can be expressed as follows: Daily Reward = Basic Storage Reward Resources × Online Rate + Performance Reward Resources × Response Speed ​​Coefficient The response speed coefficient is the normalized value of the response speed of each target mobile terminal.

[0062] It should be noted that the reward resources are virtual resources provided by the payment system, which can be redeemed for corresponding benefits within the payment system. The specific details are determined by the rules of the payment system, and this application does not impose any specific restrictions.

[0063] In another feasible embodiment, to further increase the online time of the target mobile terminal, the user can also obtain additional reward resources through other online activities. For example, the user can ensure the network stability of the target mobile terminal by watching videos in order to obtain additional reward resources.

[0064] The types of reward resource information, additional reward resource information and other additional reward resource information may be the same or different, and this application does not make specific restrictions on this.

[0065] Therefore, by providing reward resources to target mobile terminals participating in the distributed storage of payment data, the embodiments of this application can greatly encourage users to participate in the distributed storage system of payment data using their target mobile terminals, ensuring the stability of the distributed storage space of payment data and thus ensuring the reliability of the distributed storage of payment data.

[0066] It should be noted that although the operation of the method of the present invention is described in a specific order in the accompanying drawings, this does not require or imply that the operations must be performed in that specific order, or that all the operations shown must be performed in order to achieve the desired result.

[0067] Figure 3 A schematic diagram of the structure of a distributed storage device for payment data provided in an embodiment of this application is shown.

[0068] like Figure 3 As shown, the distributed storage device 10 for the payment data includes: The first acquisition module 11 is used to acquire transaction data and confirm the transaction data; The sharding module 12 is used to shard the confirmed transaction data using erasure coding technology to obtain multiple transaction data shards. The second acquisition module 13 is used to acquire multiple target mobile terminals for storing the transaction data; Storage module 14 is used to store multiple transaction data fragments into multiple target mobile terminals according to preset storage rules.

[0069] In some embodiments, the second acquisition module 13 is specifically used for: For multiple initially selected mobile terminals, detect the real-time status of the initially selected mobile terminals; When the real-time status of the initially selected mobile terminal meets the preset conditions, the size of the available storage space of the initially selected mobile terminal is obtained. The initially selected mobile terminals whose available storage space is greater than or equal to the transaction data fragment are selected as candidate mobile terminals. From the candidate mobile terminals, a plurality of target mobile terminals are selected according to preset conditions.

[0070] In some embodiments, the storage module 14 is further configured to: For each target mobile terminal, the online duration of the target mobile terminal used to store the transaction data fragment is obtained; Based on the online duration, the reward resource information corresponding to the target mobile terminal is determined.

[0071] In some embodiments, the storage module 14 is further configured to: For each target mobile terminal, obtain the response speed of the target mobile terminal when querying the transaction data shard; Based on the response speed, determine the additional reward resource information corresponding to the target mobile terminal.

[0072] In some embodiments, the target mobile terminal completes the storage of the transaction data fragment by synchronizing the block header corresponding to the transaction data fragment and verifying the verification information corresponding to the transaction data fragment.

[0073] In some embodiments, the target trusted node confirms the transaction data; The target trust node is a pre-selected trust node with a clear identity.

[0074] It should be understood that the modules or modules recorded in the distributed storage device 10 for payment data are related to the reference. Figure 2 The steps in the described method correspond accordingly. Therefore, the operations and features described above for the method also apply to the distributed storage device 10 for payment data and the modules contained therein, and will not be repeated here. The distributed storage device 10 for payment data can be pre-implemented in the browser or other security applications of an electronic device, or it can be loaded into the browser or its security applications of an electronic device through downloading or other means. The corresponding modules in the distributed storage device 10 for payment data can cooperate with the modules in the electronic device to implement the solutions of the embodiments of this application.

[0075] The division of modules or units mentioned in the detailed description above is not mandatory. In fact, according to the embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0076] The following is for reference. Figure 4 , Figure 4 A schematic diagram of the structure of a computer system suitable for implementing the embodiments of this application is shown. like Figure 4 As shown, the computer system 400 includes a central processing unit (CPU) 401, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 402 or programs loaded from storage section 408 into random access memory (RAM) 403. RAM 403 also stores various programs and data required for the system's operating instructions. CPU 401, ROM 402, and RAM 403 are interconnected via bus 404. Input / output (I / O) interface 405 is also connected to bus 404.

[0077] The following components are connected to I / O interface 405: an input section 406 including a keyboard, mouse, etc.; an output section 407 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 408 including a hard disk, etc.; and a communication section 409 including a network interface card such as a LAN card, modem, etc. The communication section 409 performs communication processing via a network such as the Internet. Drive 410 is also connected to I / O interface 405 as needed. Removable media 411, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 410 as needed so that computer programs read from them can be installed into storage section 408 as needed.

[0078] Specifically, according to embodiments of this application, the flowchart above refers to... Figure 2 The described process can be implemented as a computer software program. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowchart. In such an embodiment, the computer program contains program code for performing the methods shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via communication section 409, and / or installed from removable medium 411. When the computer program is executed by central processing unit (CPU) 401, it performs the functions defined in the system of this application.

[0079] It should be noted that the computer-readable medium shown in this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0080] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operational instructions of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two connected blocks may actually be executed substantially in parallel, or they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified functions or operational instructions, or using a combination of dedicated hardware and computer instructions.

[0081] The units or modules described in the embodiments of this application can be implemented in software or hardware. The described units or modules can also be housed in a processor; for example, a processor can be described as including a first acquisition module, a slicing module, a second acquisition module, and a storage module. The names of these units or modules do not necessarily limit the specific unit or module itself; for example, the first acquisition module can also be described as "acquiring transaction data and confirming the transaction data."

[0082] In another aspect, this application also provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiments, or may exist independently and not assembled into the electronic device. The aforementioned computer-readable storage medium stores one or more programs that, when used by one or more processors, execute the distributed storage method for payment data described in this application.

[0083] The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure in this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the foregoing disclosed concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this application.

Claims

1. A distributed storage method for payment data, characterized in that, include: Obtain transaction data and confirm the transaction data; Erasure coding technology is used to fragment the confirmed transaction data, resulting in multiple transaction data fragments; Acquire multiple target mobile terminals for storing the transaction data; The transaction data fragments are stored in multiple target mobile terminals according to preset storage rules.

2. The distributed storage method for payment data according to claim 1, characterized in that, The acquisition of multiple target mobile terminals for storing the transaction data includes: For multiple initially selected mobile terminals, detect the real-time status of the initially selected mobile terminals; When the real-time status of the initially selected mobile terminal meets the preset conditions, the size of the available storage space of the initially selected mobile terminal is obtained. The initially selected mobile terminals whose available storage space is greater than or equal to the transaction data fragment are selected as candidate mobile terminals. From the candidate mobile terminals, a plurality of target mobile terminals are selected according to preset conditions.

3. The distributed storage method for payment data according to claim 1, characterized in that, Also includes: For each target mobile terminal, the online duration of the target mobile terminal used to store the transaction data fragment is obtained; Based on the online duration, the reward resource information corresponding to the target mobile terminal is determined.

4. The distributed storage method for payment data according to claim 3, characterized in that, Also includes: For each target mobile terminal, obtain the response speed of the target mobile terminal when querying the transaction data shard; Based on the response speed, determine the additional reward resource information corresponding to the target mobile terminal.

5. The distributed storage method for payment data according to claim 1, characterized in that, Also includes: The target mobile terminal completes the storage of the transaction data fragment by synchronizing the block header corresponding to the transaction data fragment and verifying the verification information corresponding to the transaction data fragment.

6. The distributed storage method for payment data according to claim 2, characterized in that, The confirmation of the transaction data includes: The target trusted node confirms the transaction data; The target trust node is a pre-selected trust node with a clear identity.

7. A distributed storage device for payment data, characterized in that, include: The first acquisition module is used to acquire transaction data and confirm the transaction data; The sharding module is used to shard the confirmed transaction data using erasure coding technology to obtain multiple transaction data shards. The second acquisition module is used to acquire multiple target mobile terminals for storing the transaction data; The storage module is used to store multiple transaction data fragments into multiple target mobile terminals according to preset storage rules.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the distributed storage method for payment data as described in any one of claims 1-6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, this program implements the distributed storage method for payment data as described in any one of claims 1-6.

10. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program implements the distributed storage method for payment data as described in any one of claims 1-6.

Images