Data processing method and device in transfer, equipment, medium and product
By automating data acquisition on the server side and realizing the orderly migration of digital tokens under a dedicated temporary storage node, the problem of low efficiency in digital token transfer in existing technologies is solved, and an efficient and standardized digital token transfer process is achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-12-11
- Publication Date
- 2026-04-14
AI Technical Summary
Existing technologies are inefficient in the process of transferring digital tokens, requiring users to manually enter a large amount of information and undergo multiple rounds of verification, resulting in a long processing time.
By proactively acquiring business-related data on the server side, generating dedicated temporary storage nodes, and automatically migrating digital tokens at preset time points, manual data entry and multiple rounds of verification are reduced, achieving automated flow.
It simplifies the digital token transfer process, improves transfer efficiency, reduces time consumption, and ensures full tracking and standardized management of digital tokens.
Smart Images

Figure CN121864367A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of data processing technology, and in particular to a data processing method, apparatus, equipment, medium and product for fund transfer. Background Technology
[0002] Digital token transfer refers to the process of transferring and storing value attribute data associated with a specific entity between storage nodes within a system. In a digital business environment, ensuring that digital tokens maintain their complete relevance, traceability, and security during cross-node transfers has become a pressing technical challenge.
[0003] In existing technologies, the user submits a digital token transfer request and enters information about the digital token to be transferred. After the system performs a preliminary verification of the submitted information, it pushes it to the review node to complete multiple rounds of verification and confirmation. After the review is passed, a digital token transfer notification is sent to the user. The user initiates the digital token transfer operation, and the system completes information synchronization and digital token status updates to realize the digital token transfer.
[0004] However, existing technologies suffer from low efficiency in digital token transfer. In current digital token transfer processes, users need to manually enter a large amount of digital token-related information and submit requests. The system requires multiple rounds of information verification and manual review, resulting in a lengthy and inefficient digital token transfer process. Summary of the Invention
[0005] This application provides a data processing method, apparatus, device, medium, and product for fund transfers, in order to solve the problem of low efficiency in digital token transfers in the prior art.
[0006] In a first aspect, embodiments of this application provide a data processing method for money transfers, applied to the server side of a data processing system for money transfers. The data processing system further includes a user terminal and an order generation terminal. The server side includes a first storage node and multiple sub-storage nodes. The method includes:
[0007] Acquire multiple target case data; wherein, the multiple target case data are used to represent the attributes of the target case, and the target case is any case in which digital token transfer is carried out at the current time.
[0008] Based on the multiple target case data, a first link is generated and sent to the user terminal; wherein, the first link is used for the user terminal to access in order to trigger the encryption of the multiple target case data and the transmission operation to the order generation terminal;
[0009] In response to the user accessing the first link, the data of the multiple target cases is encrypted to obtain an encrypted data packet, and the encrypted data packet is sent to the order generation terminal;
[0010] The system receives a second link sent by the order generation terminal and sends the second link to the user terminal. The second link is generated by the order generation terminal based on the encrypted data packet. The user terminal is used to transfer the digital token corresponding to the target case to the second storage node based on the second link. The second storage node is the only node among the plurality of sub-storage nodes used to temporarily store the digital token corresponding to the target case.
[0011] In response to the current time point reaching the preset digital token migration time point, the digital token corresponding to the target case is transferred from the second storage node to the first storage node, so as to complete the transfer of the digital token corresponding to the target case from the user terminal to the first storage node.
[0012] In one possible design, after sending the encrypted data packet to the order generation terminal, the process further includes:
[0013] Receive the business order for the target case sent by the order generation terminal; wherein, the business order is used to bind to the target case so that the target case is distinguished from multiple first cases, the multiple first cases refer to cases other than the target case among a preset multiple cases of digital token transfer at the current time;
[0014] Based on the data of the multiple target cases, a case detail table for the target cases is generated; wherein, the case detail table is used to record the transfer process of the digital token corresponding to the target case from the user terminal to the first storage node.
[0015] In one possible design, the business order includes a temporary storage status identifier, the case details table includes a first node storage status identifier, and after sending the second link to the user terminal, it further includes:
[0016] In response to the fact that the digital token corresponding to the target case has been transferred to the first storage node, the temporary storage status identifier is set to success, and the first node storage status identifier is set to success; wherein, setting the temporary storage status identifier to success indicates that the digital token corresponding to the target case has been sent from the user terminal to the first storage node, and setting the first node storage status identifier to success indicates that the digital token corresponding to the target case has arrived at the first storage node.
[0017] In one possible design, after transferring the digital token corresponding to the target case from the second storage node to the first storage node, the process further includes:
[0018] Obtain the first digital token transfer result; wherein, the first digital token transfer result includes failure;
[0019] In response to the failure of the first digital token transfer, attribution analysis is performed based on the multiple target case data, the business orders, and the case details table to obtain the attribution results;
[0020] The target processing strategy is obtained by matching the attribution result with multiple preset processing strategies; wherein, the target processing strategy is the processing strategy that corresponds to the maximum matching degree of the attribution result among the multiple processing strategies.
[0021] Execute the target processing strategy and obtain the second digital token transfer result; wherein, the second digital token transfer result includes failure;
[0022] In response to the failure of the second digital token transfer, a warning signal is generated and sent to the management node; wherein the management node is set on the server.
[0023] In one possible design, transferring the digital token corresponding to the target case from the second storage node to the first storage node includes:
[0024] Obtain the remaining amount of resources and the amount required for transfer; wherein, the amount required for transfer refers to the amount of resources required to transfer the digital token corresponding to the target case from the second storage node to the first storage node;
[0025] In response to the remaining amount of resources being greater than or equal to the amount required for the transfer, the digital token corresponding to the target case is transferred from the second storage node to the first storage node;
[0026] In response to the remaining amount of resources being less than the amount required for the transfer, the priority of each case is obtained, and the multiple cases are classified according to the priority of each case to obtain multiple second cases; wherein, the multiple second cases refer to the cases among the multiple cases whose priority is lower than the priority of the target case;
[0027] Stop executing a predetermined number of cases among the plurality of second cases, so that the remaining amount of resources is greater than or equal to the amount required for the transfer;
[0028] The digital token corresponding to the target case is transferred from the second storage node to the first storage node.
[0029] In one possible design, encrypting the multiple target case data to obtain an encrypted data packet includes:
[0030] The multiple target case data are classified to obtain multiple first data and multiple second data; wherein, the multiple first data refers to user data in the multiple target case data, and the multiple second data refers to data in the multiple target case data other than the multiple first data;
[0031] The plurality of first data are encrypted based on a preset first encryption rule to obtain a first encrypted data packet;
[0032] The plurality of second data are encrypted based on a preset second encryption rule to obtain a second encrypted data packet; wherein the encryption strength of the first encryption rule is greater than the encryption strength of the second encryption rule;
[0033] The first encrypted data packet and the second encrypted data packet are integrated to obtain the encrypted data packet.
[0034] Secondly, embodiments of this application provide a data processing device for fund transfers, applied to the server side of a data processing system for fund transfers. The data processing system for fund transfers further includes a user terminal and an order generation terminal. The server side includes a first storage node and multiple sub-storage nodes. The device includes:
[0035] The first acquisition module is used to acquire multiple target case data; wherein, the multiple target case data are used to represent the attributes of the target case, and the target case is any case in which digital token transfer is carried out at the current time.
[0036] A first generation module is configured to generate a first link based on the multiple target case data and send the first link to the user terminal; wherein, the first link is used for the user terminal to access in order to trigger the encryption of the multiple target case data and the transmission operation to the order generation terminal;
[0037] The encryption module is used to encrypt the multiple target case data in response to the user accessing the first link, obtain an encrypted data packet, and send the encrypted data packet to the order generation terminal;
[0038] The first receiving module is used to receive the second link sent by the order generating end and send the second link to the user end; wherein, the second link is generated by the order generating end based on the encrypted data packet, and the user end is used to transfer the digital token corresponding to the target case to the second storage node according to the second link, and the second storage node is the only node among the plurality of sub-storage nodes used to temporarily store the digital token corresponding to the target case;
[0039] The first transfer module is used to transfer the digital token corresponding to the target case from the second storage node to the first storage node in response to the current time point reaching the preset digital token migration time point, so as to complete the transfer of the digital token corresponding to the target case from the user terminal to the first storage node.
[0040] In one possible design, the data processing device for the transfer further includes:
[0041] The second receiving module is used to receive the business order for the target case sent by the order generating terminal; wherein the business order is used to bind to the target case so that the target case is distinguished from multiple first cases, and the multiple first cases refer to cases other than the target case among a preset number of cases for digital token transfer at the current time.
[0042] The second generation module is used to generate a case detail table of the target cases based on the multiple target case data; wherein, the case detail table is used to record the transfer process of the digital token corresponding to the target case from the user terminal to the first storage node.
[0043] In one possible design, the business order includes a temporary storage status identifier, the case details table includes a first node storage status identifier, and the data processing device in the transfer further includes:
[0044] The setting module is configured to, in response to the fact that the digital token corresponding to the target case has been transferred to the first storage node, set the temporary storage status identifier to success and set the first node storage status identifier to success; wherein, setting the temporary storage status identifier to success indicates that the digital token corresponding to the target case has been sent from the user terminal to the first storage node, and setting the first node storage status identifier to success indicates that the digital token corresponding to the target case has arrived at the first storage node.
[0045] In one possible design, the data processing device for the transfer further includes:
[0046] The second acquisition module is used to acquire the first digital token transfer result; wherein, the first digital token transfer result includes failure;
[0047] The attribution analysis module is used to perform attribution analysis based on the multiple target case data, the business order, and the case details table in response to the failure of the first digital token transfer, and to obtain the attribution result.
[0048] The matching module is used to match the attribution result with multiple preset processing strategies to obtain a target processing strategy; wherein, the target processing strategy is the processing strategy that corresponds to the maximum matching degree of the attribution result among the multiple processing strategies.
[0049] An execution module is used to execute the target processing strategy and obtain a second digital token transfer result; wherein, the second digital token transfer result includes failure;
[0050] The third generation module is used to generate a warning signal in response to the failure of the second digital token transfer, and send the warning signal to the management node; wherein the management node is set on the server.
[0051] In one possible design, the first transfer module includes:
[0052] The first acquisition unit is used to acquire the remaining amount of resources and the amount required for transfer; wherein, the amount required for transfer refers to the amount of resources required to transfer the digital token corresponding to the target case from the second storage node to the first storage node;
[0053] The first transfer unit is configured to transfer the digital token corresponding to the target case from the second storage node to the first storage node in response to the remaining amount of resources being greater than or equal to the amount required for transfer.
[0054] The second acquisition unit is configured to, in response to the remaining amount of resources being less than the amount required for the transfer, acquire the priority of each of the cases, and classify the multiple cases according to the priority of each of the cases to obtain multiple second cases; wherein, the multiple second cases refer to the cases among the multiple cases whose priority is lower than the priority of the target case;
[0055] The execution stop unit is used to stop the execution of a preset number of cases among the plurality of second cases, so that the remaining amount of resources is greater than or equal to the amount required for the transfer;
[0056] The second transfer unit is used to transfer the digital token corresponding to the target case from the second storage node to the first storage node.
[0057] In one possible design, the encryption module includes:
[0058] A classification unit is used to classify the plurality of target case data to obtain a plurality of first data and a plurality of second data; wherein, the plurality of first data refers to user data in the plurality of target case data, and the plurality of second data refers to data in the plurality of target case data other than the plurality of first data;
[0059] The first encryption unit is used to encrypt the plurality of first data according to a preset first encryption rule to obtain a first encrypted data packet;
[0060] The second encryption unit is used to encrypt the plurality of second data based on a preset second encryption rule to obtain a second encrypted data packet; wherein the encryption strength of the first encryption rule is greater than the encryption strength of the second encryption rule;
[0061] An integration unit is used to integrate the first encrypted data packet and the second encrypted data packet to obtain the encrypted data packet.
[0062] Thirdly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;
[0063] The memory stores computer-executed instructions;
[0064] When the processor executes the computer execution instructions stored in the memory, it is used to implement the data processing method in the transfer as described in any of the first aspects.
[0065] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the data processing method in a transfer as described in any of the first aspects.
[0066] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, is used to implement the data processing method in a transfer as described in any of the first aspects.
[0067] This application provides a data processing method, apparatus, equipment, medium, and product for fund transfers. It acquires target case data from a server and generates a first link, guiding the user to trigger data transmission. A second link is generated by an order generator, directly linking to a dedicated temporary storage node. This temporary storage node is the only one among multiple sub-storage nodes used for temporarily storing the corresponding target case's digital tokens. Each case's digital token corresponds to a dedicated temporary storage node. The user can quickly transfer digital tokens to this dedicated temporary storage node. Once the digital token migration time arrives, the system automatically migrates the digital tokens from the dedicated temporary storage node to the first storage node, achieving an orderly transfer of digital tokens from the temporary storage node to the final storage node. This approach establishes an independent transfer link for each case's digital tokens through the unique correspondence of dedicated temporary storage nodes, facilitating full-process tracking and standardized management. Furthermore, process automation reduces manual data entry and multiple verification rounds, simplifying the transfer process and shortening time, effectively improving the efficiency of digital token transfers. Attached Figure Description
[0068] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0069] Figure 1 A schematic diagram illustrating an application scenario of the data processing method in fund transfer provided in this application embodiment;
[0070] Figure 2 A flowchart illustrating the data processing method for fund transfers provided in this application embodiment. Figure 1 ;
[0071] Figure 3 A flowchart illustrating the data processing method for fund transfers provided in this application embodiment. Figure 2 ;
[0072] Figure 4 A flowchart illustrating the data processing method for fund transfers provided in this application embodiment. Figure 3 ;
[0073] Figure 5 A flowchart illustrating the data processing method for fund transfers provided in this application embodiment. Figure 4 ;
[0074] Figure 6 This is a schematic diagram of the structure of the data processing device in the transfer provided in the embodiments of this application;
[0075] Figure 7 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application.
[0076] The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to specific embodiments. Detailed Implementation
[0077] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.
[0078] The collection, storage, use, processing, transmission, provision, and disclosure of financial data or user data involved in the technical solution of this application all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.
[0079] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.
[0080] First, let me explain the terms used in this application:
[0081] Digital tokens are value units that carry core rights in digital transactions. They are digitally encapsulated entities that can be deterministically transferred between different responsible parties under specific system rules. Each state change of a digital token is protected by encryption technology and preset business logic, and is closely bound to a specific business action.
[0082] Business Order: A standardized contractual certificate created by the system to initiate a complete value exchange transaction. It defines the participants, digital tokens, rules and lifecycle of the transaction. As the core coordination hub of the entire process, it ensures that all stages from the initiation of the transaction to its final completion can be fully tracked, managed and coordinated.
[0083] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the invention as detailed in the appended claims.
[0084] The technical solution of the present invention will be described in detail below with reference to specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of the present invention will now be described with reference to the accompanying drawings.
[0085] To clearly understand the technical solution of this application, the solutions of existing technologies will first be described in detail. In a digital business environment, ensuring that digital tokens maintain complete relevance, traceability, and security during cross-node transfers has become an urgent technical challenge.
[0086] In existing technologies, the user submits a digital token transfer request, enters information about the digital token to be transferred, the system performs preliminary verification of the submitted information, and then pushes it to the review node for multiple rounds of verification and confirmation. Once the review is passed, a digital token transfer notification is sent to the user, who then initiates the digital token transfer operation. The system completes information synchronization and digital token status updates, thus realizing the digital token transfer. However, in existing digital token transfer processes, the user needs to manually enter a large amount of digital token-related information and submit the request, and the system needs to undergo multiple rounds of information verification and manual review, resulting in a time-consuming and inefficient digital token transfer process. Therefore, existing technologies suffer from low efficiency in digital token transfer.
[0087] Therefore, addressing the issue of low efficiency in digital token transfer in existing technologies, the research found that to solve this problem, the server can proactively acquire business-related data and build an automated transfer link. This involves encrypted transmission, dedicated temporary node storage, and pre-set time-series migration to replace manual data entry and multiple rounds of verification, achieving efficient digital token transfer: ① The system can proactively associate core related data within the business scenario, automatically completing data collection, organization, and preprocessing, replacing manual data entry. Simultaneously, a rule engine is introduced to build an intelligent verification model, transforming multiple rounds of manual review into automated verification at the system level, reducing process delays caused by manual intervention and improving the pre-processing efficiency of digital token transfer. ② A unique dedicated temporary storage node can be assigned to each business matter. This node is solely responsible for storing the digital tokens for that specific matter, achieving physical isolation between digital tokens and other matters. A fixed migration time point is preset; once the time is triggered, the system automatically migrates the digital tokens from the temporary storage node to the final storage node. ③ Based on the transfer needs of different business scenarios, standardized transfer rules can be pre-configured. When a digital token transfer request is triggered, the system automatically matches the corresponding rules and completes the entire process of resource allocation, storage migration, etc. No manual intervention is required for decision-making. The warning mechanism is only triggered in abnormal scenarios. By replacing manual operation and review with rule-based and automated execution, the entire cycle time of digital token transfer is shortened.
[0088] Specifically, a unique, dedicated temporary storage resource can be allocated to each business transaction. This resource is exclusively used to hold the digital tokens for the corresponding transaction. At the same time, a time-series migration rule is preset. Once the preset time condition is triggered, the system automatically starts the token migration process, transferring the digital tokens in the temporary storage resource to the target storage node. Combined with automated data collection, encrypted transmission, and intelligent verification mechanisms, this replaces manual data entry and multiple rounds of review, improving the efficiency of digital token transfer.
[0089] This application discloses a data processing method, apparatus, device, medium, and product for fund transfers. It obtains target case data from a server and generates a first link to guide the user to trigger data transmission. A second link is generated by an order generator and directly linked to a dedicated temporary storage node. This temporary storage node is the only one among multiple sub-storage nodes used for temporarily storing the corresponding target case's digital tokens. Each case's digital token corresponds to a dedicated temporary storage node. The user can quickly transfer digital tokens to this dedicated temporary storage node. Once the digital token migration time arrives, the system automatically migrates the digital tokens from the dedicated temporary storage node to the first storage node, achieving an orderly transfer of digital tokens from the temporary storage node to the final storage node. This not only establishes an independent transfer link for each case's digital tokens through the unique correspondence of the dedicated temporary storage nodes, facilitating full-process tracking and standardized management, but also reduces manual data entry and multiple verification rounds through process automation, simplifying the transfer process and shortening time, effectively improving the transfer efficiency of digital tokens.
[0090] Based on the above-mentioned inventive discovery, the technical solution of this application is proposed.
[0091] The following describes the application scenarios of the data processing method in fund transfer provided in the embodiments of the present invention. Figure 1 This is a schematic diagram illustrating an application scenario of the data processing method for fund transfers provided in this application embodiment. For example... Figure 1 As shown, this application scenario includes a user terminal 101 and a server terminal 102. The server terminal 102 acquires multiple target case data. Based on this data, it generates a first link and sends it to the user terminal. In response to the user terminal accessing the first link, the server terminal 102 encrypts the multiple target case data to obtain an encrypted data packet, which is then sent to the order generation terminal. The server terminal 102 receives a second link from the order generation terminal and sends it to the user terminal. Finally, in response to the current time point reaching a preset digital token migration time point, the server terminal 102 transfers the digital token corresponding to the target case from the second storage node to the first storage node, thus completing the transfer of the digital token corresponding to the target case from the user terminal 101 to the first storage node.
[0092] The embodiments of the present invention will now be described with reference to the accompanying drawings.
[0093] Figure 2 A flowchart illustrating the data processing method for fund transfers provided in this application embodiment. Figure 1 .like Figure 2 As shown, in this embodiment, the execution entity of this invention is the server. Therefore, the data processing method for fund transfers provided in this embodiment includes the following steps:
[0094] S201. Obtain multiple target case data; wherein, multiple target case data are used to represent the attributes of target cases, and a target case is any case in which digital token transfer is carried out at the current time.
[0095] Specifically, pending cases can be automatically identified based on the current time and business status. Then, the complete set of attribute information for the corresponding case can be retrieved through the data interface, including key fields such as case identifier, ownership details, and timeliness requirements. The data is then encapsulated in a unified format. This step is used to build a complete and standardized dataset of pending cases, providing an accurate and verifiable initial data foundation for the subsequent generation of dedicated access channels and the initiation of standardized workflow procedures.
[0096] S202. Based on multiple target case data, generate a first link and send the first link to the user terminal; wherein, the first link is used for the user terminal to access in order to trigger the encryption of multiple target case data and the transmission operation to the order generation terminal.
[0097] Specifically, a unique access address containing a unique identifier for the case data can be generated based on the packaged case data set. This link address can then be pushed to the corresponding user's interface via the system's built-in message channel. This step provides users with a standardized, one-click business startup entry point. By guiding users to access this unique link, subsequent data transmission and processing can be activated accurately, thereby avoiding errors and delays that may occur due to manual data entry.
[0098] S203. In response to the user accessing the first link, encrypt the data of multiple target cases to obtain an encrypted data packet, and send the encrypted data packet to the order generation end.
[0099] Specifically, based on the user's access to the link, the data processing flow can be automatically triggered. The case data is converted into an unreadable ciphertext format using a preset encryption algorithm and packaged into a protected data packet. This data packet is then automatically transmitted to the terminal responsible for generating business instructions. This step ensures the confidentiality and integrity of core case information during transmission after the user confirms the start of the process, laying the foundation for the secure and reliable generation of business instructions in the next stage.
[0100] For example, when a user initiates access to the first link through the user terminal, the system immediately triggers the encryption process for the target case data. The SM2 Elliptic Curve Public Key Cryptographic Algorithm can be used, combined with the corresponding key pair, to encrypt the collected target case data as a whole, converting the original plaintext data into ciphertext that cannot be directly parsed, and then packaging it into a complete encrypted data packet. Subsequently, the encrypted data packet is automatically sent to the order generation terminal through a preset secure transmission channel.
[0101] S204. Receive the second link sent by the order generating end and send the second link to the user end; wherein, the second link is generated by the order generating end based on the encrypted data packet, and the user end is used to transfer the digital token corresponding to the target case to the second storage node according to the second link. The second storage node is the only node among multiple sub-storage nodes used for temporary storage of the digital token corresponding to the target case.
[0102] Specifically, it can automatically receive a unique resource location address containing business instructions from the order generation terminal and forward the address to the user's operation interface through the system's internal channel. This step is used to accurately deliver the business operation entry point generated by the backend system and pointing to a specific temporary storage location to the user, providing the necessary and unique guidance for their subsequent execution confirmation and transfer operations.
[0103] S205. In response to the current time point reaching the preset digital token migration time point, the digital token corresponding to the target case is transferred from the second storage node to the first storage node to complete the transfer of the digital token corresponding to the target case from the user terminal to the first storage node.
[0104] Specifically, when the system time reaches a specified moment, the digital token transfer process can be automatically initiated, transferring digital token assets temporarily stored at dedicated temporary nodes to the central storage node in batches. This step is used to achieve automated and batch final archiving of digital tokens, ensuring that all temporarily stored digital tokens can complete ownership confirmation and unified management of storage location at the agreed time, thereby forming a complete closed-loop business process.
[0105] This embodiment provides a data processing method for fund transfers. The server acquires target case data and generates a first link, guiding the user to trigger data transmission. A second link is generated by the order generator, directly linking to a dedicated temporary storage node. This temporary storage node is the only one among multiple sub-storage nodes used for temporarily storing the corresponding target case's digital tokens. Each case's digital token corresponds to a dedicated temporary storage node. The user can quickly transfer digital tokens to this dedicated temporary storage node. Once the digital token migration time arrives, the system automatically migrates the digital tokens from the dedicated temporary storage node to the first storage node, achieving an orderly transfer of digital tokens from the temporary storage node to the final storage node. This method establishes an independent transfer link for each case's digital tokens through the unique correspondence of dedicated temporary storage nodes, facilitating full-process tracking and standardized management. Furthermore, process automation reduces manual data entry and multiple verification rounds, simplifying the transfer process and shortening time, effectively improving the efficiency of digital token transfers.
[0106] In one possible design, S205, transferring the digital token corresponding to the target case from the second storage node to the first storage node includes:
[0107] S2051. Obtain the remaining amount of resources and the amount required for transfer; wherein, the amount required for transfer refers to the amount of resources required to transfer the digital token corresponding to the target case from the second storage node to the first storage node.
[0108] Specifically, the remaining amount of available resources can be calculated by reading the current available resources recorded by the system resource management module, or by detecting the real-time resource occupancy and combining it with the total resource supply. By analyzing the resource consumption attributes corresponding to the transfer of digital tokens and combining them with the preset resource demand calculation rules, the amount of resources required to transfer digital tokens from the temporary storage node to the final storage node can be determined. This step is used to check in advance whether the currently available resources can support the digital token transfer operation, providing a key basis for subsequent decisions on whether to prioritize the transfer of the target case and adjust the execution plan of other cases based on the resource matching situation, ensuring that the transfer process of the target case is not affected by insufficient resources.
[0109] The remaining resources can refer to the current available core computing resources of the system, such as the number of available CPU computing units, the remaining capacity of dynamic memory space, and the real-time available value of network transmission bandwidth. The transfer requirement refers to the system resources required to complete the transfer of digital tokens for a specific case from temporary nodes to the central node. This typically includes the processor computing power required to complete data encapsulation and verification, the memory space occupied by temporary cached data, and the network bandwidth consumed in transmitting data blocks.
[0110] S2052. In response to the remaining amount of resources being greater than or equal to the amount required for transfer, the digital token corresponding to the target case is transferred from the second storage node to the first storage node.
[0111] Specifically, after confirming that the remaining resources can meet the transfer requirements, the system can automatically trigger the preset inter-node transfer execution logic. Through the dedicated data transmission channel between storage nodes, after verifying the connectivity between the temporary storage node and the final storage node and the integrity of the digital token, the digital token corresponding to the target case is migrated from the temporary storage node to the final storage node. This step is used to efficiently advance the final transfer process of the digital token under the premise of sufficient resource supply, ensuring that the digital token is successfully stored according to the preset path and guaranteeing the orderly completion of the target case transfer task.
[0112] S2053. In response to the fact that the remaining amount of resources is less than the amount required for transfer, the priority of each case is obtained, and multiple cases are classified according to the priority of each case to obtain multiple second cases; wherein, multiple second cases refer to cases whose priority is lower than the priority of the target case among multiple cases.
[0113] Specifically, the priority of each case can be obtained by reading the preset case priority configuration information, the priority judgment rules associated with case attributes, or the priority identifier set when the case is initiated. Then, the priority of each case is compared with the priority of the target case, and cases with lower priority than the target case are selected as the second case. This step is used to accurately identify low-priority cases that can be temporarily adjusted when resources are insufficient. This provides a classification basis for releasing resources by stopping some low-priority cases and ensuring the transfer needs of the target case, thus ensuring the targeted and reasonable allocation of resources.
[0114] S2054. Stop executing a predetermined number of cases among multiple second cases, so that the remaining resources are greater than or equal to the amount required for transfer;
[0115] Specifically, based on preset case stop rules, such as sorting by priority from low to high, a subset of interruptible cases can be selected from multiple second cases. The system can then trigger a pause operation to release the resources occupied by these cases until the remaining available resources are sufficient to meet the transfer requirements of the target case. This step is used to quickly release enough resources to ensure the transfer of the target case when resources are insufficient by reasonably reducing the resource occupation of low-priority cases. This ensures that the target case is transferred first while minimizing the impact on other cases, thus improving the flexibility and effectiveness of resource allocation.
[0116] Before selecting a case from multiple second cases that can be interrupted and triggering a pause operation according to the preset case stop rules, the system can automatically record the current execution progress, completed steps, key operating parameters, and unfinished task nodes of each case to be stopped. This status data is encrypted and stored in a dedicated cache area or persistent storage module. After the target case is transferred and the system resources are restored to the preset redundancy level, the system reads the complete status information of the stopped case from the storage module according to the preset recovery rules of "first stop, first recovery" or case priority sorting, and automatically triggers the recovery execution process. This allows the case to be seamlessly continued from the stop node, ensuring the transfer needs of the target case by releasing resources, and realizing the orderly recovery of the stopped case, avoiding task interruption or data loss, and improving the closed-loop management of resource allocation and task execution.
[0117] The preset quantity refers to the specific number of second cases that need to be stopped to release sufficient resources to meet the transfer requirements of the target case. This quantity can be flexibly set based on factors such as the current resource gap in the system, the resource consumption of each second case, the interruptibility level of the cases, the system's preset resource redundancy threshold, and the urgency of the target cases. The system can first calculate the difference between the remaining resources and the amount required for the transfer to determine the resource gap that needs to be supplemented. Then, combined with the core resource quotas such as computing, storage, and transmission used by each second case during execution, and taking into account whether the cases are marked as "temporarily interruptible" or "non-urgent," the system dynamically calculates the minimum number of cases that need to be stopped through a preset resource accounting model. If necessary, the quantity redundancy can be appropriately adjusted according to the system's resource scheduling strategy to ensure that the total amount of released resources stably meets the transfer requirements of the target case, while minimizing the impact on the execution progress of other cases, thus achieving precision and flexibility in resource allocation.
[0118] S2055. Transfer the digital token corresponding to the target case from the second storage node to the first storage node.
[0119] Specifically, after the remaining resources meet the transfer requirements, the connectivity between the temporary storage node and the final storage node, as well as the integrity of the digital token, can be verified first. Then, the preset inter-node digital token migration mechanism can be activated. The digital token corresponding to the target case can be safely and orderly transferred from the temporary storage node to the final storage node through a dedicated data transmission link. This step is used to complete the final storage of the digital token corresponding to the target case, realize the complete flow of digital tokens from temporary to fixed storage, and ensure that the digital tokens are accurately transferred under the premise that resources are in place.
[0120] The technical effect of this solution in this embodiment is that by comparing the remaining amount of resources with the amount required for transfer in real time, and automatically classifying cases according to priority when resources are insufficient, intelligently suspending low-priority tasks to release resources, the smooth execution of high-priority digital token transfers is guaranteed. This achieves efficient and reasonable allocation of system resources, ensures the reliability and timeliness of key digital token transfer tasks, and improves the overall resource utilization efficiency and task throughput of the system.
[0121] In one possible design, S203, multiple target case data are encrypted to obtain an encrypted data packet, including:
[0122] S2031. Classify multiple target case data to obtain multiple first data and multiple second data; wherein, multiple first data refers to user data in multiple target case data, and multiple second data refers to data in multiple target case data other than multiple first data.
[0123] Specifically, based on the attribute characteristics of the target case data and combined with preset data classification rules, relevant data directly related to the user subject can be identified and extracted as the first data, and the remaining case-related data that does not involve the user subject can be classified as the second data. This step is used to differentiate the target case data, providing a classification basis for subsequently adopting different strength encryption rules for different types of data. This not only ensures the security protection level of user-related data, but also realizes the reasonable allocation of encryption resources, and improves the overall targeting and efficiency of data encryption.
[0124] User data refers to a collection of information directly linked to the identity and behavior of the business initiator or related party. This type of data can be directly or indirectly associated with a specific individual or entity, reflecting their identity attributes, operation records, and rights and interests in business activities. Examples include the user's unique account identifier, historical business participation records, relationships with business partners, and operation authorization credentials within the system.
[0125] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of the relevant data all comply with relevant laws, regulations, and standards, necessary confidentiality measures have been taken, they do not violate public order and good morals, and corresponding operation portals are provided for users to choose to authorize or refuse.
[0126] Furthermore, the technical solution involved in this application, which involves big data analysis of user information (including but not limited to personal biometrics, identity data, consumption data, asset data, electronic terminal operation data, etc.) and the use of artificial intelligence technology for automated decision-making, and makes decisions that have a significant impact on personal rights based on the results of automated decision-making, provides users with corresponding operation entry points for users to choose to agree to or reject the results of automated decision-making; if the user chooses to reject, the process will proceed to the expert decision-making process.
[0127] S2032. Encrypt multiple first data based on a preset first encryption rule to obtain a first encrypted data packet.
[0128] Specifically, the first data after classification can be processed according to preset high-strength encryption rules and encryption logic that meets security protection requirements. Through targeted operations such as data security encoding and information desensitization and obfuscation, a first encrypted data packet is formed. This step is used to implement a higher level of security protection for sensitive user-related data, effectively avoiding security problems such as leakage and tampering of such data during subsequent transmission or processing, and ensuring the privacy and integrity of the data.
[0129] The first encryption rule is a high-strength encryption rule designed for sensitive user-associated data. It employs encryption algorithms with high resistance to attacks and strong privacy protection, coupled with strict key management and data verification mechanisms. For example, it can use the Galois / counter mode, a high-strength key-length version of the Advanced Encryption Standard (AES). During encryption, a randomly generated salt value is introduced, the key is stored in a hardware security module and rotated periodically, and the decryption process simultaneously verifies the key validity and data integrity check value to ensure that only authorized entities can access the original data.
[0130] S2033. Encrypt multiple second data based on a preset second encryption rule to obtain a second encrypted data packet; wherein the encryption strength of the first encryption rule is greater than the encryption strength of the second encryption rule.
[0131] Specifically, the second data after classification can be processed according to the preset adaptive encryption rules and the encryption logic that matches the security requirements of this type of data. Through basic data encoding, information integrity verification and other operations, a second encrypted data packet is formed. This step is used to ensure the security of data transmission and processing of non-user-related cases, avoid resource consumption caused by excessive encryption, balance data security and encryption processing efficiency, and ensure the rationality of the overall encryption process.
[0132] The second encryption rule is designed for non-user-sensitive case data. It employs encryption algorithms that meet basic protection requirements and have high execution efficiency, simplifying unnecessary complex processes. While ensuring data transmission and storage security, it avoids resource waste caused by excessive encryption. For example, it can use a medium-key-length electronic codebook mode based on advanced encryption standards, or a lightweight encryption algorithm. Keys are centrally managed through the system's secure storage module. The encryption process does not require additional complex verification information; data encryption and basic tamper-proofing are achieved solely through the algorithm itself, prioritizing processing speed.
[0133] S2034. Integrate the first encrypted data packet and the second encrypted data packet to obtain an encrypted data packet.
[0134] Specifically, according to the preset data packet integration rules, corresponding type identifiers or association tags can be added to the first and second encrypted data packets. Then, the two types of encrypted data packets can be merged into a unified data packet through a structured combination method. This step is used to uniformly encapsulate the case-related data after differential encryption to form a complete encrypted data carrier. This not only facilitates subsequent transmission and processing between different nodes, but also ensures that the two types of original data can be accurately distinguished and restored during decryption, thus ensuring the continuity and accuracy of data transmission and use.
[0135] The technical effect of this solution in this embodiment is that by classifying the target case data and applying different encryption strength rules to user data and other data for differentiated encryption, and finally integrating them into a unified encrypted data packet, the solution ensures that core user data is protected by a high level of security while taking into account the overall efficiency of data processing and transmission, thus achieving an optimized balance between security and system performance.
[0136] Figure 3 A flowchart illustrating the data processing method for fund transfers provided in this application embodiment. Figure 2 In this embodiment, in Figure 2 Based on the provided embodiments, the data processing method in fund transfers will be further explained. The data processing method in fund transfers includes:
[0137] S301. Obtain multiple target case data; wherein, multiple target case data are used to represent the attributes of target cases, and a target case is any case in which digital token transfer is carried out at the current time.
[0138] S302. Based on multiple target case data, generate a first link and send the first link to the user terminal; wherein, the first link is used for the user terminal to access in order to trigger the encryption of multiple target case data and the transmission operation to the order generation terminal.
[0139] S303. In response to the user accessing the first link, encrypt the data of multiple target cases to obtain an encrypted data packet, and send the encrypted data packet to the order generation end.
[0140] S301-S303 are similar to S201-S203, and will not be described again in this embodiment.
[0141] S304. Receive the business order for the target case sent by the order generation terminal; wherein, the business order is used to bind with the target case so that the target case is distinguished from multiple first cases, and multiple first cases refer to the cases other than the target case among the multiple preset cases for digital token transfer at the current time.
[0142] Specifically, the system can receive business orders for target cases sent by the order generation end through a preset communication link or data interaction interface. The business order can be generated by the order generation end parsing the received encrypted data packet, extracting the target case-related attribute information contained therein, and constructing a business order that uniquely corresponds to the target case based on preset order generation rules. This step is used to establish a unique binding relationship between the business order and the target case, so as to clearly distinguish the target case from other similar cases. At the same time, it provides an association identifier for the subsequent case details table to record the transfer process, ensuring the traceability and accuracy of information correspondence throughout the transfer process.
[0143] In this system, a business order is a unique business credential generated by the system, acting like a unique identifier for a specific business object being processed. This identifier is bound to the target case, aiming to accurately identify and distinguish the current transaction from a batch of similar transactions being processed in parallel, ensuring that each subsequent processing step can be independently and accurately tracked and managed. For example, in a system that processes multiple digital token transfers, when a user submits a new transfer application, the system generates an electronic document with a unique number—the business order. Subsequent inquiries about progress, execution of operations, and verification of information will all rely on this unique number to locate and process this digital token transfer, thus avoiding confusion with other digital token transfers.
[0144] S305. Based on multiple target case data, generate a case detail table for the target cases; wherein, the case detail table is used to record the transfer process of the digital token corresponding to the target case from the user terminal to the first storage node.
[0145] Specifically, key information related to the transfer process can be extracted from the relevant attribute data of the target case. According to the preset recording rules and table structure, the case attribute information is associated with the record items required for the transfer process to form a case detail table of the target case. This step is used to systematically and comprehensively record the key information of the corresponding case from initiation to final storage, providing complete and accurate information for the traceability, verification and subsequent management operations of the transfer process, and ensuring the traceability and integrity of the transfer process.
[0146] The case details table is a detailed file recording the complete processing history of a specific business transaction. It systematically records key information throughout the entire process, from initiation and through each stage to final completion, aiming to achieve traceability and transparency in the processing. For example, for the aforementioned digital token transfer, the corresponding case details table would act like a travel log, clearly recording when and by whom the transfer was initiated, when a temporary storage location was allocated, when it was transferred to the final storage location, and the system records for each step. By consulting this details table, the entire lifecycle of the transaction can be fully reviewed and verified.
[0147] S306. Receive the second link sent by the order generating end and send the second link to the user end; wherein, the second link is generated by the order generating end based on the encrypted data packet, and the user end is used to transfer the digital token corresponding to the target case to the second storage node according to the second link, and the second storage node is the only node among multiple sub-storage nodes used for temporary storage of the digital token corresponding to the target case.
[0148] S307. In response to the current time point reaching the preset digital token migration time point, the digital token corresponding to the target case is transferred from the second storage node to the first storage node to complete the transfer of the digital token corresponding to the target case from the user terminal to the first storage node.
[0149] S306-S307 are similar to S204-S205, and will not be described again in this embodiment.
[0150] The technical effect of this solution in this embodiment is as follows: By introducing a unique business order generated from encrypted data packets and bound to the target case, combined with a case details table recording the entire process, an independent digital identity and audit trail chain are created within the system for each target case. This design clearly distinguishes and isolates multiple cases that are processed in a mixed manner, realizing precise management and visual tracking of the digital token transfer process, avoiding confusion and cross-interference between cases, and improving the reliability of the process.
[0151] Figure 4 A flowchart illustrating the data processing method for fund transfers provided in this application embodiment. Figure 3In this embodiment, in Figure 2 Based on the provided embodiments, the data processing method in fund transfers will be further explained. The data processing method in fund transfers includes:
[0152] S401. Obtain multiple target case data; wherein, multiple target case data are used to represent the attributes of target cases, and a target case is any case in which digital token transfer is carried out at the current time.
[0153] S402. Based on multiple target case data, generate a first link and send the first link to the user terminal; wherein, the first link is used for the user terminal to access in order to trigger the encryption of multiple target case data and the transmission operation to the order generation terminal.
[0154] S403. In response to the user accessing the first link, encrypt the data of multiple target cases to obtain an encrypted data packet, and send the encrypted data packet to the order generation end.
[0155] S404. Receive the second link sent by the order generating end and send the second link to the user end; wherein, the second link is generated by the order generating end based on the encrypted data packet, and the user end is used to transfer the digital token corresponding to the target case to the second storage node according to the second link. The second storage node is the only node among multiple sub-storage nodes used for temporary storage of the digital token corresponding to the target case.
[0156] S401-S404 are similar to S201-S204, and will not be described again in this embodiment.
[0157] S405. In response to the fact that the digital token corresponding to the target case has been transferred to the first storage node, the temporary storage status flag is set to success, and the first node storage status flag is set to success; wherein, setting the temporary storage status flag to success is used to indicate that the digital token corresponding to the target case has been sent from the user terminal to the first storage node, and setting the first node storage status flag to success is used to indicate that the digital token corresponding to the target case has arrived at the first storage node.
[0158] Specifically, by detecting the digital token storage confirmation signal or the status information that the digital token has been successfully stored, the system can confirm that the digital token corresponding to the target case has been transferred to the first storage node. After this confirmation, the system will automatically trigger the temporary storage status flag in the business order and the first node storage status flag in the case details table to be updated to a successful status. This step is used to synchronize the status information of the final transfer of the digital token in the target case, providing a clear and accurate status basis for the verification of case-related processes and subsequent management operations, ensuring the visualization and traceability of the digital token transfer status, and guaranteeing the information consistency of the entire transfer process.
[0159] The temporary storage status identifier is used to track the status of digital tokens in the "transfer station" stage. It specifically records the transfer of digital tokens from the initiator to the temporary storage node, and its core function is to confirm whether the digital token has safely and accurately left the initiator and entered the temporary node. For example, when a package is delivered from the sender to the community's express delivery station, the system marks the package order as "temporarily stored at the station," which is similar to the temporary storage status identifier being set to "successful." It means that the package has completed the first leg of its journey.
[0160] The first-node storage status flag is used to confirm whether the digital token has finally arrived at the "destination" warehouse. It focuses on the final stage of the digital token's journey from the temporary node to the final storage node, marking the complete completion of the entire transfer task. Continuing the previous example, when the entrusted item is successfully transported from the relay station and signed for at the city's central distribution warehouse, the system's "Entered Central Warehouse" status on the item's complete journey details table is equivalent to the first-node storage status flag being set to "Successful." This indicates that the item has completed its entire transfer path and arrived at its final designated location.
[0161] S406. In response to the current time point reaching the preset digital token migration time point, the digital token corresponding to the target case is transferred from the second storage node to the first storage node to complete the transfer of the digital token corresponding to the target case from the user terminal to the first storage node.
[0162] S406 is similar to S205, and will not be described again in this embodiment.
[0163] The technical effect of this solution in this embodiment is that it introduces "temporary storage status identifier" and "first node storage status identifier" for business orders and case details, respectively, and dynamically updates the status of these two identifiers by responding to key nodes in the digital token transfer. This establishes a refined status synchronization and dual confirmation mechanism, enabling accurate and real-time tracking and cross-verification of the status at different stages in the digital token transfer process, and enhancing the system's ability to monitor the process.
[0164] Figure 5 A flowchart illustrating the data processing method for fund transfers provided in this application embodiment. Figure 4 In this embodiment, in Figure 2 Based on the provided embodiments, the data processing method in fund transfers will be further explained. The data processing method in fund transfers includes:
[0165] S501. Obtain multiple target case data; wherein, multiple target case data are used to represent the attributes of target cases, and a target case is any case in which digital token transfer is carried out at the current time.
[0166] S502. Based on multiple target case data, generate a first link and send the first link to the user terminal; wherein, the first link is used for the user terminal to access in order to trigger the encryption of multiple target case data and the transmission operation to the order generation terminal.
[0167] S503: In response to the user accessing the first link, encrypt the data of multiple target cases to obtain an encrypted data packet, and send the encrypted data packet to the order generation end.
[0168] S504. Receive the second link sent by the order generating end and send the second link to the user end; wherein, the second link is generated by the order generating end based on the encrypted data packet, and the user end is used to transfer the digital token corresponding to the target case to the second storage node according to the second link. The second storage node is the only node among multiple sub-storage nodes used for temporary storage of the digital token corresponding to the target case.
[0169] S505. In response to the current time point reaching the preset digital token migration time point, the digital token corresponding to the target case is transferred from the second storage node to the first storage node to complete the transfer of the digital token corresponding to the target case from the user terminal to the first storage node.
[0170] S501-S505 are similar to S201-S205, and will not be described again in this embodiment.
[0171] S506. Obtain the first digital token transfer result; wherein, the first digital token transfer result includes failure.
[0172] Specifically, the execution result of the digital token migration from the temporary storage node to the first storage node can be obtained by detecting the digital token reception status information and the execution status signal of the transfer process fed back by the first storage node, or by reading the status record data corresponding to the transfer stage. This step is used to clarify the completion status of the digital token migration to the final storage node, providing core basis for subsequent attribution analysis, processing strategy matching and anomaly handling if the migration fails, and ensuring that abnormal situations in the transfer process can be identified in a timely manner and trigger the corresponding processing mechanism.
[0173] The first digital token transfer result is a feedback on the execution status of the digital token migration process from the dedicated temporary storage node to the final storage node. It is used to determine whether the migration step has been successfully completed, and the result includes cases where the migration fails.
[0174] S507. In response to the failure of the first digital token transfer, attribution analysis is performed based on multiple target case data, business orders and case details to obtain the attribution results.
[0175] Specifically, it can retrieve and integrate the basic attribute data of the target case, the exclusive business order information, and the detailed records of the entire case process. The three types of information are cross-verified and anomaly investigated. The focus is on analyzing the completeness of the basic case information, the validity of the order binding, and the node anomalies in the process records, such as missing status changes and abnormal interactions of storage nodes. Combined with the preset anomaly feature matching rules, the root cause of the digital token transfer failure is located, and an attribution result is formed. This step is used to locate the core cause of the transfer failure, providing accurate cause support for subsequent matching of targeted processing strategies and efficient resolution of transfer anomalies, thereby improving the targeting and effectiveness of anomaly handling.
[0176] S508. Match the attribution results with multiple preset processing strategies to obtain the target processing strategy; wherein, the target processing strategy is the processing strategy that corresponds to the maximum matching degree of the attribution results among the multiple processing strategies.
[0177] Specifically, we can first identify the core characteristics of the anomalies represented by the attribution results, and then compare them with the applicable scenarios and anomaly cause matching conditions of various preset processing strategies. Through preset matching rules, such as anomaly type correspondence and cause similarity comparison, we can adapt the attribution results to each processing strategy one by one, and select the processing strategy with the highest matching degree with the attribution results as the target processing strategy. This step is used to establish a precise association between the core causes of the transfer failure and the targeted solutions, ensuring that the subsequent processing strategies can directly address the essence of the problem, avoid ineffective handling, improve the efficiency and success rate of anomaly repair, and promote the smooth restoration of the digital token transfer process as soon as possible.
[0178] S509. Execute the target processing strategy and obtain the second digital token transfer result; wherein, the second digital token transfer result includes failure.
[0179] Specifically, the system can automatically trigger targeted operations such as anomaly correction, process completion, or node interaction adjustment according to the operation logic corresponding to the target processing strategy. After the operation is completed, the execution result of the digital token transfer is obtained by detecting the reception feedback of the final storage node, the process execution status record, or related status signals. This step is used to verify the effectiveness of the target processing strategy. By re-initiating the digital token transfer attempt through targeted operations, the system strives to solve the previous transfer failure problem, promote the completion of the digital token transfer process, and provide clear result basis for triggering the warning mechanism if it still fails in the future.
[0180] For example, we can first analyze the core reasons for the failure of the second digital token transfer, and then execute different strategies according to different reasons: if the communication link between storage nodes is interrupted, we automatically start a multi-path detection mechanism, switch to a backup encrypted transmission link, and re-establish the node connection; if it is determined that packet loss or verification failure occurred during data transmission, we retrieve the original data backup from the transfer initiator, and use a combination of fragmented retransmission and checksum comparison to complete the missing data and verify its integrity; if it is found that the transfer task is blocked due to temporary insufficient system resources, we trigger a dynamic resource scheduling mechanism to prioritize the release of computing and storage resources occupied by low-priority tasks and allocate dedicated resource quotas for the transfer task. After completing the above targeted correction operations, we re-initiate the digital token transfer request from the original storage node to the final storage node according to the preset process steps of the target processing strategy, monitor the data transmission progress, node reception confirmation signals, and process execution status codes in real time, and generate a second digital token transfer result containing success or failure status by reading the reception completion receipt and data integrity verification result of the final storage node.
[0181] The second digital token transfer result is a feedback on the execution status of the targeted processing strategy and the re-initiation of the digital token transfer to the final storage node after the first migration fails. This is used to clarify whether the transfer after the anomaly correction was successfully completed, and the result includes the case of transfer failure.
[0182] S510. In response to the failure of the second digital token transfer, a warning signal is generated and sent to the management node; wherein, the management node is set on the server.
[0183] Specifically, after confirming that the second transfer of digital tokens has failed, the system can integrate key information such as abnormal information related to the digital token transfer, records of the two transfer attempts, and attribution results according to the preset warning signal generation rules, construct a warning signal containing abnormal details, and send the warning signal to the designated management node through the preset communication link or data interaction channel inside the server. This step is used to promptly report serious abnormalities in the digital token transfer to the management node after the execution of the automated processing strategy is ineffective, reminding relevant personnel to intervene for manual verification and handling, and avoiding the process from stalling due to unresolved abnormal issues for a long time.
[0184] The technical effect of this solution in this embodiment is as follows: when the transfer of digital tokens fails, attribution analysis is performed based on existing target case data, business orders and case details, and the optimal processing strategy is intelligently matched and executed from the preset strategy library based on the analysis results. If it fails again, a warning is automatically issued to the management node, thus constructing a closed-loop intelligent fault handling and reporting process. This realizes the automated and intelligent diagnosis and handling of transfer failures, improves the system's autonomy and anomaly handling efficiency, and ensures the controllability of the process through timely early warning.
[0185] This application also provides a data processing system for money transfer, including a server, a user, and an order generation terminal. The server includes a first storage node and multiple sub-storage nodes.
[0186] The server is used to coordinate the collaborative operation of various nodes and terminals, and is responsible for executing the entire process logic related to digital token transfer, including receiving case data, classifying and encrypting it, migrating digital tokens between nodes, managing storage status, calculating the remaining amount of resources and the amount required for transfer, allocating resources, analyzing the causes of abnormal situations and executing handling strategies, as well as generating and sending warning signals, to ensure the orderly, secure and efficient progress of the digital token transfer process.
[0187] The client is used to receive operation instructions related to digital token transfer initiated by users, collect and submit the basic data required for the target case to the server, and receive relevant information such as digital token transfer status and processing results from the server, providing users with an interactive entry point for initiating digital token transfer requests, submitting data, and querying results.
[0188] The order generation terminal is used to generate a business order uniquely bound to the target case based on the basic data of the target case submitted by the user and the system's preset order generation rules. The order contains key information such as the case-specific identifier, temporary storage status identifier, and core information related to the case, providing unified order data support for the server to carry out digital token transfer processes, status management, and exception handling.
[0189] The first storage node is used to receive and securely store the digital tokens corresponding to the target cases migrated from the sub-storage nodes, verify the integrity and accuracy of the digital token migration, report the storage status information of the digital tokens to the server, and ensure the security and accessibility of the stored digital tokens. It is the final landing node in the digital token transfer process.
[0190] Multiple sub-storage nodes serve as temporary storage carriers during the digital token transfer process. Each sub-storage node corresponds to carrying digital tokens for one or more target cases. During the transfer of digital tokens from the initial stage corresponding to the user to the first storage node, a transitional storage service is provided to verify the integrity of the temporary storage of digital tokens, lay the foundation for the subsequent migration of digital tokens to the first storage node, and ensure the secure storage of digital tokens during the transition phase.
[0191] Figure 6 This is a schematic diagram of the data processing device for fund transfer provided in an embodiment of this application. Figure 6 As shown, the data processing device in this transfer includes:
[0192] The first acquisition module 601 is used to acquire multiple target case data; wherein, the multiple target case data is used to represent the attributes of the target case, and the target case is any case in which digital token transfer is carried out at the current time.
[0193] The first generation module 602 is used to generate a first link based on multiple target case data and send the first link to the user terminal; wherein, the first link is used for the user terminal to access in order to trigger the encryption of multiple target case data and the transmission operation to the order generation terminal.
[0194] The encryption module 603 is used to encrypt multiple target case data in response to the user accessing the first link, obtain an encrypted data packet, and send the encrypted data packet to the order generation end.
[0195] The first receiving module 604 is used to receive the second link sent by the order generating end and send the second link to the user end; wherein, the second link is generated by the order generating end based on the encrypted data packet, and the user end is used to transfer the digital token corresponding to the target case to the second storage node according to the second link. The second storage node is the only node among multiple sub-storage nodes used for temporary storage of the digital token corresponding to the target case.
[0196] The first transfer module 605 is used to transfer the digital token corresponding to the target case from the second storage node to the first storage node in response to the current time point reaching the preset digital token migration time point, so as to complete the transfer of the digital token corresponding to the target case from the user terminal to the first storage node.
[0197] In one possible design, the data processing device during the transfer also includes:
[0198] The second receiving module is used to receive the business order for the target case sent by the order generating end; wherein, the business order is used to bind to the target case so that the target case is distinguished from multiple first cases, and multiple first cases refer to the cases other than the target case among the multiple preset cases for digital token transfer at the current time.
[0199] The second generation module is used to generate a case detail table of target cases based on multiple target case data; wherein, the case detail table is used to record the transfer process of the digital token corresponding to the target case from the user terminal to the first storage node.
[0200] In one possible design, the business order includes a temporary storage status identifier, the case details table includes a first node storage status identifier, the data processing device in the transfer process, and also includes:
[0201] The setting module is used to respond to the fact that the digital token corresponding to the target case has been transferred to the first storage node, and to set the temporary storage status flag to success and the first node storage status flag to success. The temporary storage status flag being set to success indicates that the digital token corresponding to the target case has been sent from the user terminal to the first storage node, and the first node storage status flag being set to success indicates that the digital token corresponding to the target case has arrived at the first storage node.
[0202] In one possible design, the data processing device during the transfer also includes:
[0203] The second acquisition module is used to acquire the first digital token transfer result; wherein the first digital token transfer result includes failure.
[0204] The attribution analysis module is used to perform attribution analysis based on multiple target case data, business orders, and case details tables in response to the failure of the first digital token transfer, and obtain the attribution results.
[0205] The matching module is used to match the attribution results with multiple preset processing strategies to obtain the target processing strategy; wherein, the target processing strategy is the processing strategy that corresponds to the maximum matching degree of the attribution results among the multiple processing strategies.
[0206] The execution module is used to execute the target processing strategy and obtain the second digital token transfer result; wherein the second digital token transfer result includes failure.
[0207] The third generation module is used to generate a warning signal in response to the failure of the second digital token transfer and send the warning signal to the management node; wherein the management node is set on the server.
[0208] In one possible design, the first transfer module 605 includes:
[0209] The first acquisition unit is used to acquire the remaining amount of resources and the amount required for transfer; wherein, the amount required for transfer refers to the amount of resources required to transfer the digital token corresponding to the target case from the second storage node to the first storage node.
[0210] The first transfer unit is used to transfer the digital token corresponding to the target case from the second storage node to the first storage node in response to the remaining amount of resources being greater than or equal to the amount required for transfer.
[0211] The second acquisition unit is used to acquire the priority of each case in response to the remaining amount of resources being less than the amount required for transfer, and to classify multiple cases according to the priority of each case to obtain multiple second cases; wherein, multiple second cases refer to cases whose priority is lower than the priority of the target case among multiple cases.
[0212] The stop execution unit is used to stop the execution of a preset number of cases among multiple second cases, so that the remaining resources are greater than or equal to the amount required for transfer.
[0213] The second transfer unit is used to transfer the digital token corresponding to the target case from the second storage node to the first storage node.
[0214] In one possible design, encryption module 603 includes:
[0215] The classification unit is used to classify multiple target case data to obtain multiple first data and multiple second data; wherein, the multiple first data refers to user data in the multiple target case data, and the multiple second data refers to data in the multiple target case data other than the multiple first data.
[0216] The first encryption unit is used to encrypt multiple first data based on a preset first encryption rule to obtain a first encrypted data packet.
[0217] The second encryption unit is used to encrypt multiple second data based on a preset second encryption rule to obtain a second encrypted data packet; wherein the encryption strength of the first encryption rule is greater than the encryption strength of the second encryption rule.
[0218] The integration unit is used to integrate the first encrypted data packet and the second encrypted data packet to obtain an encrypted data packet.
[0219] The data processing device for transfers provided in this embodiment can perform... Figures 2 to 5 The technical solution of the data processing method embodiment in the transfer is shown, and its implementation principle and technical effect are similar to those of the previous embodiment. Figures 2 to 5 The data processing method shown in the example is similar and will not be described in detail here.
[0220] Figure 7 This is a schematic diagram of the hardware structure of the electronic device provided in an embodiment of this application. Figure 7As shown, the electronic device 70 includes at least one processor 701 and a memory 702. The electronic device 70 also includes a communication component 703. The processor 701, memory 702, and communication component 703 are connected via a bus 704.
[0221] In a specific implementation, at least one processor 701 executes computer execution instructions stored in memory 702, causing at least one processor 701 to implement a data processing method in a transfer as described in the above embodiment.
[0222] The specific implementation process of processor 701 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.
[0223] In the above embodiments, it should be understood that the processor 701 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.
[0224] The memory 702 may include high-speed RAM memory, and may also include non-volatile memory NVM, such as at least one disk storage.
[0225] Bus 704 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Bus 704 can be divided into address bus, data bus, control bus, etc. For ease of illustration, the bus 704 in the accompanying drawings of this application is not limited to only one bus or one type of bus.
[0226] The above description of the functions implemented by electronic devices and main control devices has introduced the solutions provided by the embodiments of the present invention. It is understood that, in order to implement the above functions, the electronic device or main control device includes hardware structures and / or software modules corresponding to the execution of each function. By combining the units and algorithm steps of the various examples described in the embodiments of the present invention, the embodiments of the present invention can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the technical solutions of the embodiments of the present invention.
[0227] This application also provides a computer-readable storage medium storing computer-executable instructions. When executed by a processor, these instructions implement a data processing method for money transfer as described in the above embodiments. In the specific implementation of the aforementioned data processing method for money transfer, each module can be implemented as a processor.
[0228] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.
[0229] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in application-specific integrated circuits (ASICs). Alternatively, the processor and the readable storage medium can exist as discrete components in an electronic device or a host device.
[0230] This application also provides a computer program product, including a computer program, which, when executed by a processor, is used to implement a data processing method for fund transfers as described in the above embodiments.
[0231] The computer program is stored in a readable storage medium, and at least one processor can read the computer program from the readable storage medium and execute the computer program to perform the scheme provided in any of the above embodiments.
[0232] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disk, or optical disk.
[0233] The technical solutions of this application have been described above with reference to the preferred embodiments shown in the accompanying drawings. However, it is readily understood by those skilled in the art that the scope of protection of this application is obviously not limited to these specific embodiments. The above embodiments are only used to illustrate the technical solutions of this application and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. These modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.
Claims
1. A data processing method for fund transfers, characterized in that, A server-side application of a data processing system for money transfers, the data processing system for money transfers further including a user terminal and an order generation terminal, the server-side including a first storage node and multiple sub-storage nodes, the method including: Acquire multiple target case data; wherein, the multiple target case data are used to represent the attributes of the target case, and the target case is any case in which digital token transfer is carried out at the current time. Based on the multiple target case data, a first link is generated and sent to the user terminal; wherein, the first link is used for the user terminal to access in order to trigger the encryption of the multiple target case data and the transmission operation to the order generation terminal; In response to the user accessing the first link, the data of the multiple target cases is encrypted to obtain an encrypted data packet, and the encrypted data packet is sent to the order generation terminal; The system receives a second link sent by the order generation terminal and sends the second link to the user terminal. The second link is generated by the order generation terminal based on the encrypted data packet. The user terminal is used to transfer the digital token corresponding to the target case to the second storage node based on the second link. The second storage node is the only node among the plurality of sub-storage nodes used to temporarily store the digital token corresponding to the target case. In response to the current time point reaching the preset digital token migration time point, the digital token corresponding to the target case is transferred from the second storage node to the first storage node, so as to complete the transfer of the digital token corresponding to the target case from the user terminal to the first storage node.
2. The data processing method for fund transfers according to claim 1, characterized in that, After sending the encrypted data packet to the order generation terminal, the process further includes: Receive the business order for the target case sent by the order generation terminal; wherein, the business order is used to bind to the target case so that the target case is distinguished from multiple first cases, the multiple first cases refer to cases other than the target case among a preset multiple cases of digital token transfer at the current time; Based on the data of the multiple target cases, a case detail table for the target cases is generated; wherein, the case detail table is used to record the transfer process of the digital token corresponding to the target case from the user terminal to the first storage node.
3. The data processing method in fund transfer according to claim 2, characterized in that, The business order includes a temporary storage status identifier, the case details table includes a first node storage status identifier, and after sending the second link to the user terminal, it further includes: In response to the fact that the digital token corresponding to the target case has been transferred to the first storage node, the temporary storage status identifier is set to success, and the first node storage status identifier is set to success; wherein, setting the temporary storage status identifier to success indicates that the digital token corresponding to the target case has been sent from the user terminal to the first storage node, and setting the first node storage status identifier to success indicates that the digital token corresponding to the target case has arrived at the first storage node.
4. The data processing method in fund transfer according to claim 2, characterized in that, After transferring the digital token corresponding to the target case from the second storage node to the first storage node, the process further includes: Obtain the first digital token transfer result; wherein, the first digital token transfer result includes failure; In response to the failure of the first digital token transfer, attribution analysis is performed based on the multiple target case data, the business orders, and the case details table to obtain the attribution results; The target processing strategy is obtained by matching the attribution result with multiple preset processing strategies; wherein, the target processing strategy is the processing strategy that corresponds to the maximum matching degree of the attribution result among the multiple processing strategies. Execute the target processing strategy and obtain the second digital token transfer result; wherein, the second digital token transfer result includes failure; In response to the failure of the second digital token transfer, a warning signal is generated and sent to the management node; wherein the management node is set on the server.
5. The data processing method for fund transfers according to claim 2, characterized in that, The step of transferring the digital token corresponding to the target case from the second storage node to the first storage node includes: Obtain the remaining amount of resources and the amount required for transfer; wherein, the amount required for transfer refers to the amount of resources required to transfer the digital token corresponding to the target case from the second storage node to the first storage node; In response to the remaining amount of resources being greater than or equal to the amount required for the transfer, the digital token corresponding to the target case is transferred from the second storage node to the first storage node; In response to the remaining amount of resources being less than the amount required for the transfer, the priority of each case is obtained, and the multiple cases are classified according to the priority of each case to obtain multiple second cases; wherein, the multiple second cases refer to the cases among the multiple cases whose priority is lower than the priority of the target case; Stop executing a predetermined number of cases among the plurality of second cases, so that the remaining amount of resources is greater than or equal to the amount required for the transfer; The digital token corresponding to the target case is transferred from the second storage node to the first storage node.
6. The data processing method in fund transfer according to claim 3, characterized in that, The encryption of the multiple target case data to obtain an encrypted data packet includes: The multiple target case data are classified to obtain multiple first data and multiple second data; wherein, the multiple first data refers to user data in the multiple target case data, and the multiple second data refers to data in the multiple target case data other than the multiple first data; The plurality of first data are encrypted based on a preset first encryption rule to obtain a first encrypted data packet; The plurality of second data are encrypted based on a preset second encryption rule to obtain a second encrypted data packet; wherein the encryption strength of the first encryption rule is greater than the encryption strength of the second encryption rule; The first encrypted data packet and the second encrypted data packet are integrated to obtain the encrypted data packet.
7. A data processing device for fund transfers, characterized in that, A server-side component for a data processing system used in money transfers, the data processing system for money transfers also including a user terminal and an order generation terminal, the server-side component including a first storage node and multiple sub-storage nodes, the device comprising: The first acquisition module is used to acquire multiple target case data; wherein, the multiple target case data are used to represent the attributes of the target case, and the target case is any case in which digital token transfer is carried out at the current time. A first generation module is configured to generate a first link based on the multiple target case data and send the first link to the user terminal; wherein, the first link is used for the user terminal to access in order to trigger the encryption of the multiple target case data and the transmission operation to the order generation terminal; The encryption module is used to encrypt the multiple target case data in response to the user accessing the first link, obtain an encrypted data packet, and send the encrypted data packet to the order generation terminal; The first receiving module is used to receive the second link sent by the order generating end and send the second link to the user end; wherein, the second link is generated by the order generating end based on the encrypted data packet, and the user end is used to transfer the digital token corresponding to the target case to the second storage node according to the second link, and the second storage node is the only node among the plurality of sub-storage nodes used to temporarily store the digital token corresponding to the target case; The first transfer module is used to transfer the digital token corresponding to the target case from the second storage node to the first storage node in response to the current time point reaching the preset digital token migration time point, so as to complete the transfer of the digital token corresponding to the target case from the user terminal to the first storage node.
8. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; When the processor executes the computer execution instructions stored in the memory, it is used to implement the data processing method in the transfer as described in any one of claims 1 to 6.
9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the data processing method in the transfer as described in any one of claims 1 to 6.
10. A computer program product, characterized in that, Includes a computer program, which, when executed by a processor, is used to implement the data processing method in a transfer as described in any one of claims 1 to 6.