Data processing method and apparatus, electronic device, computer readable storage medium, and computer program product
By introducing domain trading components and micro-core components in electronic devices, decoupling transaction execution and resource transfer accounting, the poor performance of blockchain technology in complex domain trading scenarios and expansion of accounting systems has been solved, and multiple implementations have been achieved. Resource integration accounting in individual fields trading scenarios.
Patent Information
- Application Number
- PCT/CN2023/130357
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-22
- Filing Date
- 2023-11-08
- Publication Date
- 2024-11-28
AI Technical Summary
The existing blockchain technology has shown low performance in complex field transaction scenarios, and the accounting system of balance resources is difficult to expand, making it difficult to be applied to multiple field transaction scenarios at the same time, such as financial management and insurance, transactions of digital resources and balance resources. The coupling of the process leads to challenges in scalability and decoupling of the accounting system.
By introducing domain trading components and micro-core components into electronic devices, they handle transaction tasks and resource types in different fields respectively, decouple transaction execution and resource transfer accounting processes, and realize resource integration accounting in multiple domain trading scenarios.
It realizes the integrated accounting of different types of resources in multiple domain trading scenarios, improves the expansion and decoupling of the accounting system, and can be applied to complex domain trading scenarios at the same time, such as financial management and insurance.
Smart Images

Figure CN2023130357_28112024_PF_FP_ABST
Abstract
Description
Data processing method, device, electronic device, computer-readable storage medium, and computer program product
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] The embodiments of this application are based on the Chinese patent application with application number 202310582399.8 and application date May 22, 2023, and claim the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby introduced into the embodiments of this application as a reference. Technical Field
[0003] The present application relates to the field of computer technology, and in particular to a data processing method, device, electronic device, computer-readable storage medium, and computer program product. Background Art
[0004] The resources involved in online domain transaction scenarios mainly include digital resources and balance resources. Among them, balance resources refer to resources used as general equivalents in the transaction process; digital resources refer to virtual resources based on node networks and digital encryption algorithms.
[0005] In related technologies, the accounting of digital resources, especially decentralized encrypted resources, primarily relies on blockchain technology. However, blockchain transactions suffer from poor performance and are unsuitable for the more complex transaction scenarios involving balance resources, such as wealth management and insurance. Balance resource accounting systems rely on large databases, and the accounting process is heavily coupled with the transaction scenarios involved. Consequently, scalability of balance resource accounting systems is complex. For example, an accounting system suitable for wealth management scenarios is difficult to use for insurance. Furthermore, the transaction process for balance resources differs significantly from that for digital resources, making it difficult to directly use the balance resource accounting system for digital resources.
[0006] Summary of the Invention
[0007] The embodiments of the present application provide a data processing method, device, electronic device, computer-readable storage medium, and computer program product, which can realize integrated accounting of different types of resources in transaction scenarios in multiple fields.
[0008] An embodiment of the present application provides a data processing method, which is executed by an electronic device. The electronic device includes at least one domain transaction component and a micro-core component, including:
[0009] Receiving, through a target domain transaction component in at least one domain transaction component, a transaction task of a target domain corresponding to the target domain transaction component, and executing the transaction task to obtain a transaction execution result;
[0010] Sending the transaction execution result to the micro-core component through the target domain transaction component;
[0011] Determine the resource type associated with the transaction execution result through the micro-core component;
[0012] Through the micro-core component, based on the transaction execution results and the resource types associated with the transaction execution results, the transfer relationship of the account associated with the transaction task is determined, and based on the transfer relationship, the transfer accounting of the account resources is processed.
[0013] An embodiment of the present application provides a data processing device, which is applied to an electronic device. The electronic device includes at least one domain transaction component and a micro-core component. The device includes:
[0014] The transaction execution module is configured to receive, through a target domain transaction component in at least one domain transaction component, a target domain transaction task corresponding to the target domain transaction component, execute the transaction task, and obtain a transaction execution result; and send the transaction execution result to the micro core component through the target domain transaction component;
[0015] a type determination module configured to determine the resource type associated with the transaction execution result through the micro-core component;
[0016] The transfer accounting module is configured to determine the transfer relationship of the account associated with the transaction task based on the transaction execution result and the resource type associated with the transaction execution result through the micro core component, and perform transfer accounting processing on the account's resources based on the transfer relationship.
[0017] An embodiment of the present application provides an electronic device, including:
[0018] a memory configured to store executable instructions;
[0019] The processor is configured to implement the above-mentioned data processing method of the present application when executing the computer executable instructions stored in the memory.
[0020] An embodiment of the present application provides a computer-readable storage medium storing computer-executable instructions. When the computer-executable instructions are executed by a processor, the processor will execute the data processing method described above in the present application.
[0021] An embodiment of the present application provides a computer program product, which includes a computer program or computer-executable instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer program or computer-executable instructions from the computer-readable storage medium and executes the computer program or computer-executable instructions, causing the electronic device to perform the data processing method described above.
[0022] In an embodiment of the present application, a transaction task can be received by a target domain transaction component in one or more domain transaction components, the transaction task can be executed by the target domain transaction component, a transaction execution result can be obtained, and the transaction execution result can be sent to a micro-core component; then, in the micro-core component, the resource type associated with the transaction execution result is determined; based on the transaction execution result and the resource type associated with the transaction execution result, the transfer relationship of the account associated with the transaction task is determined by the micro-core component, and based on the transfer relationship, the transfer accounting processing of the account's resources is performed. Through the method provided in the embodiment of the present application, transaction tasks in different domain transaction scenarios are handed over to the corresponding domain transaction components for completion, and the transfer accounting process is uniformly completed by the micro-core component, decoupling the execution process of the transaction task from the transfer accounting process involved in the transaction task, and realizing the integrated accounting of different types of resources in multiple domain transaction scenarios. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] FIG1 is a schematic diagram of a network architecture provided by an embodiment of the present application;
[0024] FIG2 is a schematic diagram of a scenario of resource transfer accounting provided by an embodiment of the present application;
[0025] FIG3 is a flow chart of a data processing method provided in an embodiment of the present application;
[0026] FIG4 is a schematic diagram of a double-entry bookkeeping process provided in an embodiment of the present application;
[0027] FIG5 is a schematic diagram of a digital resource transfer process provided in an embodiment of the present application;
[0028] FIG6 is a flow chart of a data processing method provided in an embodiment of the present application;
[0029] FIG7 is a product schematic diagram of an accounting system provided in an embodiment of the present application;
[0030] FIG8 is a schematic diagram of the architecture of an accounting system provided in an embodiment of the present application;
[0031] FIG9a is a schematic diagram of a first account operation model provided in an embodiment of the present application;
[0032] FIG9 b is a schematic diagram of a second account operation model provided in an embodiment of the present application;
[0033] FIG10 is a schematic structural diagram of a data processing device provided in an embodiment of the present application;
[0034] FIG11 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0035] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.
[0036] Cloud computing is a computing model that distributes computing tasks across a resource pool consisting of a large number of computers, enabling various application systems to access computing power, storage space, and information services as needed. The network that provides these resources is called the "cloud." To users, these resources appear infinitely scalable and can be accessed at any time, used on demand, expanded at any time, and paid for on a per-use basis.
[0037] As a provider of cloud computing infrastructure, a cloud computing resource pool (referred to as a cloud platform, generally referred to as an IaaS (Infrastructure as a Service) platform) is established. Various types of virtual resources are deployed in the resource pool for external customers to choose and use. The cloud computing resource pool mainly includes: computing devices (virtualized machines, including operating systems), storage devices, and network devices.
[0038] Based on logical functional divisions, the PaaS (Platform as a Service) layer can be deployed on top of the IaaS (Infrastructure as a Service) layer, and the SaaS (Software as a Service) layer can be deployed on top of the PaaS layer. SaaS can also be deployed directly on top of IaaS. PaaS is a platform for software execution, such as databases and web containers. SaaS is a variety of business software, such as web portals and text messaging tools. Generally speaking, SaaS and PaaS are upper layers relative to IaaS.
[0039] The solution provided in the embodiments of the present application relates to cloud computing technology in the field of cloud technology, and is illustrated by the following embodiments.
[0040] Please refer to Figure 1, which is a schematic diagram of a network architecture provided by an embodiment of the present application. As shown in Figure 1, the network architecture may include an application server 100 and a terminal device cluster, wherein the terminal device cluster may include multiple terminal devices, as shown in Figure 1, including terminal device 10a, terminal device 10b, terminal device 10c, ..., terminal device 10n. As shown in Figure 1, terminal device 10a, terminal device 10b, terminal device 10c, ..., terminal device 10n can respectively be connected to the application server 100 through a network, so that each terminal device can exchange data with the application server 100 through a network connection, so that each terminal device can receive business data from the application server 100.
[0041] It should be understood that each terminal device in the terminal device cluster shown in FIG1 can be integrated with an application client corresponding to the target application. When the application client runs in each terminal device, it can respectively interact with the application server 100 shown in FIG1 above, so that the application server 100 can receive business data from each terminal device. Among them, the application client can include game applications, video editing applications, social applications, instant messaging applications, live broadcast applications, short video applications, video applications, music applications, shopping applications, novel applications, payment applications, browsers, and other application clients with the function of displaying text, images, audio, video and other data information. Among them, the application client can be an independent client or an embedded sub-client integrated in a client (such as an instant messaging client, a social client, a video client, etc.), which is not limited here.
[0042] As shown in Figure 1, one or more domain transaction components and micro-core components may be integrated and installed in the application server 100. A domain transaction component corresponds to a domain transaction scenario, and is used to process transaction tasks in the domain transaction scenario sent by the terminal device. For example, the domain transaction component may be an insurance transaction component, which is responsible for processing transaction tasks in the insurance transaction scenario. The micro-core component is used to account for and transfer transaction resources involved in the transaction tasks. Transaction resources may include digital resources and balance resources. Balance resources refer to traditional offline resources that serve as general equivalents in the transaction process; digital resources refer to virtual resources based on a node network and a digital encryption algorithm.
[0043] During actual implementation, any terminal device in the terminal device cluster can send a transaction task under the target domain transaction scenario to the application server 100. The application server 100 can receive the transaction task of the target domain corresponding to the target domain transaction component through the target domain transaction component in at least one domain transaction component, and execute the transaction task to obtain the transaction execution result; send the transaction execution result to the micro-core component through the target domain transaction component; determine the resource type associated with the transaction execution result through the micro-core component; determine the transfer relationship of the account associated with the transaction task based on the transaction execution result and the resource type associated with the transaction execution result through the micro-core component, and perform transfer accounting processing on the resources of the account based on the transfer relationship.
[0044] It can be understood that the above-mentioned network connection does not limit the connection method. It can be directly or indirectly connected through wired communication, directly or indirectly connected through wireless communication, or through other connection methods. This application does not limit it here.
[0045] It is understandable that the method provided in the embodiment of the present application can be executed by an electronic device, and the electronic device includes but is not limited to a terminal device or an application server. Among them, the application server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (Content Deliver Network, CDN), and big data and artificial intelligence platforms. Among them, the terminal device can include a mobile phone, a tablet computer, a laptop computer, a PDA, an intelligent speaker, a mobile internet device (mobile internet device, MID), a POS (Point Of Sales, point of sale) machine, a wearable device (such as a smart watch, a smart bracelet, etc.), a vehicle-mounted terminal, etc.
[0046] It is understandable that the above-mentioned devices (such as the above-mentioned application server 100, terminal device 10a, terminal device 10b, terminal device 10c, ..., terminal device 10n) can be a node in a distributed system, wherein the distributed system can be a blockchain system, and the blockchain system can be a distributed system formed by connecting the multiple nodes through network communication. Among them, a peer-to-peer (P2P) network can be formed between the nodes, and the P2P protocol is an application layer protocol running on the Transmission Control Protocol (TCP) protocol. In a distributed system, any form of electronic device, such as a server, terminal, or other electronic device, can become a node in the blockchain system by joining the peer-to-peer network.
[0047] It is understandable that the embodiments of the present application can be applied to various scenarios, including but not limited to cloud technology, artificial intelligence, blockchain, insurance, financial management, smart wallets and the like.
[0048] It is understandable that in the specific implementation of this application, the data related to transaction tasks, etc., when the above embodiments of this application are applied to specific products or technologies, need to obtain user permission or consent, and the collection, use and processing of relevant data need to comply with the relevant laws, regulations and standards of relevant countries and regions.
[0049] To facilitate understanding of the integrated accounting process of the above-mentioned digital resources and balance resources, a procurement transaction scenario is used as an example for explanation. Please also refer to Figure 2, which is a schematic diagram of a resource transfer accounting scenario provided by an embodiment of the present application. Among them, the terminal device 20 shown in Figure 2 can be any terminal device in the terminal device cluster shown in Figure 1 above, for example, the terminal device 20 can be the terminal device 10a; the application server 200 shown in Figure 2 can be the application server 100 shown in Figure 1 above.
[0050] As shown in Figure 2, terminal device 20 may be integrated with a procurement application 21. This application 21 can match the most appropriate procurement plan for each subject based on the subject's needs and costs. For example, suppose subject A is associated with terminal device 20 and needs to purchase 1,000 computers. Subject A can perform the purchase operation using procurement application 21. In response to subject A's purchase operation, terminal device 20 can generate a procurement transaction task 22 and then send it to application server 200.
[0051] As shown in Figure 2, application server 200 may be integrated with one or more domain transaction components. Different domain transaction components correspond to different domain transaction scenarios, i.e., are used to process transaction tasks in different domain transaction scenarios. For example, application server 200 may include a procurement transaction component 201a, an insurance transaction component 201b, ..., and a wealth management transaction component 201n. Procurement transaction component 201a processes transaction tasks in the procurement transaction scenario; insurance transaction component 201b processes transaction tasks in the insurance transaction scenario; and wealth management transaction component 201n processes transaction tasks in the wealth management transaction scenario. Upon receiving a procurement transaction task 22, application server 200 may send the procurement transaction task 22 to procurement transaction component 201a. After receiving the purchase transaction task 22 via the purchase transaction component 201a, the application server 200 can execute the purchase transaction task 22. For example, the application server 200 can match multiple purchase plans for the subject A based on the purchase requirements of the subject A included in the purchase transaction task 22 within the purchase transaction component 201a. The application server 200 can then return the multiple purchase plans to the terminal device 20. The subject A can then select and confirm the target purchase plan from the multiple purchase plans via the terminal device 20. After receiving the confirmation information for the target purchase plan, the application server 200 can execute the target purchase plan via the purchase transaction component 201a, obtaining a transaction execution result 202. The transaction execution result 202 can include the purchase cost and transportation cost corresponding to the target purchase plan. The application server 200 can then send the transaction execution result 202 to the micro-core component 203 via the purchase transaction component 201a. Among them, the micro-core component 203 is a component integrated and installed in the application server 200, which is responsible for accounting and resource transfer. It can be understood that each domain transaction component included in the application server 200 can communicate with the micro-core component 203 to complete the accounting of the corresponding transaction tasks and the transfer of resources.
[0052] As shown in FIG2 , the application server 200 can first determine the resource type associated with the transaction execution result in the micro-core component 203, that is, whether the resource involved in the current transaction task is a digital resource or a balance resource. If the resource type is determined to be a balance resource type, the application server 200 can determine the balance transfer relationship of the S first accounts associated with the transaction task based on the transaction execution result, wherein the S first accounts associated with the transaction task can include the first account corresponding to the object A, the first account corresponding to the computer manufacturer, and the first account corresponding to the transportation manufacturer. The application server 200 can then perform double-entry transfer accounting for the balance resources of the S first accounts based on the balance transfer relationship. If the resource type is determined to be a digital resource type, the application server 200 can determine the balance transfer relationship of the L second accounts associated with the transaction task based on the transaction execution result, wherein the L second accounts associated with the transaction task can include the second account corresponding to the object A, the second account corresponding to the computer manufacturer, and the second account corresponding to the transportation manufacturer. The application server 200 can then perform equal-value transfer accounting for the digital resources of the L second accounts based on the balance transfer relationship.
[0053] In actual implementation, please refer to Figure 3, which is a flow chart of a data processing method provided by an embodiment of the present application. The method can be executed by an electronic device (for example, the application server 100 in the embodiment corresponding to Figure 1 above), and the electronic device includes at least one domain transaction component and a micro-core component. The following will be described using the method executed by an electronic device as an example, wherein the data processing method may include at least the following steps S101-S104:
[0054] Step S101: receiving a target domain transaction task corresponding to the target domain transaction component through a target domain transaction component in at least one domain transaction component, executing the transaction task, and obtaining a transaction execution result.
[0055] In actual implementation, the logic and methods of implementing transaction tasks in different domain transaction scenarios are very different. The more complex the domain transaction scenario, the more factors and requirements need to be considered for a transaction task. For example, in a shopping transaction scenario, the transaction task usually only needs to consider the buyer, seller and commodity price; in a financial transaction scenario, the transaction task needs to consider the buyer, the issuer of the financial product, the rate of return, the risk rate, liquidity, etc. Therefore, by abstracting different domain transaction scenarios, the transaction tasks in different domain transaction scenarios can be handed over to different domain transaction components for implementation. Each domain transaction component only needs to focus on the processing and implementation of the transaction tasks in the corresponding domain transaction scenario. In some embodiments, when a new domain transaction scenario needs to be expanded, a new domain transaction component can be created to be responsible for the transaction tasks in the new domain transaction scenario, which will not affect the transaction tasks in the original domain transaction scenario, thereby facilitating the expansion of domain transaction scenarios.
[0056] Step S102: Send the transaction execution result to the micro-core component through the target domain transaction component.
[0057] Step S103: Determine the resource type associated with the transaction execution result through the micro core component.
[0058] In actual implementation, resource types include balance resource type and digital resource type. The resource type associated with the transaction execution result is the balance resource type, indicating that the resources involved in the transaction execution result are balance resources; the resource type associated with the transaction execution result is the digital resource type, indicating that the resources involved in the transaction execution result are digital resources.
[0059] In some embodiments, before determining the resource type associated with the transaction execution result, a transaction voucher for the transaction execution result can be generated through the target domain transaction component, and the transaction voucher can be sent to the micro-core component; the transaction voucher is verified and processed through the micro-core component to obtain a verification result. If the verification result is a passed verification result, the step of determining the resource type associated with the transaction execution result is executed.
[0060] Among them, transaction vouchers can be understood as documents, which refer to documents that can be used to prove that the transaction execution results have occurred or been completed and to clarify economic responsibilities. Through transaction vouchers, it is possible to verify at any time whether the transaction execution results corresponding to each transaction task have occurred or been completed, so it can be used as the original basis for accounting.
[0061] In some embodiments, the transaction voucher may include signature data. A feasible implementation process for verifying the transaction voucher through the micro-core component to obtain the verification result may be: determining the voucher public key associated with the target domain transaction component through the micro-core component; verifying the signature data according to the voucher public key to obtain the verification result; if the verification result is a successful verification result, determining the verification result as a passed verification result; if the verification result is a failed verification result, determining the verification result as a failed verification result.
[0062] In step S104, the micro-core component determines the transfer relationship of the account associated with the transaction task based on the transaction execution result and the resource type associated with the transaction execution result, and performs transfer accounting processing on the account resources based on the transfer relationship.
[0063] In actual implementation, as described above, resource types include balance resource types and digital resource types. If the resource type associated with a transaction result is a balance resource type, it indicates that the resource involved in the transaction result is a balance resource; if the resource type associated with a transaction result is a digital resource type, it indicates that the resource involved in the transaction result is a digital resource. Based on this, the following describes the cases where the resource type is a balance resource type and the resource type is a digital resource type.
[0064] In some embodiments, where the resource type is a balance resource type, the process of determining the transfer relationship of the account associated with the transaction task based on the transaction execution result and the resource type associated with the transaction execution result may be determining the balance transfer relationship of the S first accounts associated with the transaction task based on the transaction execution result, and thereby performing transfer accounting processing on the account's resources based on the transfer relationship. The process may be performing double-entry transfer accounting processing on the balance resources of the S first accounts based on the balance transfer relationship; S is a positive integer.
[0065] It should be noted that the micro-core component can include a transaction accounting layer and an object resource layer; among them, the transaction accounting layer is used for accounting, and the object resource layer is used for transferring resources between different objects.
[0066] Based on this, the process of determining the balance transfer relationship of the S first accounts associated with the transaction task based on the transaction execution result can be, in the transaction accounting layer, determining the balance transfer relationship of the S first accounts associated with the transaction task based on the transaction execution result; and thus the process of performing double-entry transfer accounting processing on the balance resources of the S first accounts based on the balance transfer relationship can be, performing double-entry accounting processing on the S first accounts based on the balance transfer relationship to obtain a double-entry accounting result; if the double-entry accounting result is a successful double-entry accounting result, then determining the balance resource management accounts corresponding to the S first accounts in the object resource layer; wherein, one balance resource management account is used to manage the balance resources of one or more first accounts; and the balance resources of the S first accounts are transferred based on the balance transfer relationship and the balance resource management accounts corresponding to the S first accounts.
[0067] It should be noted that double-entry bookkeeping is based on the balance between assets and equity. For each transaction, equal amounts must be recorded in two or more interconnected accounts, systematically reflecting the results of resource movements and changes. That is, the results of each transaction are recorded in at least one debit and one payer account, and the total amounts of the debit and payer for the transaction are equal, i.e., "every debit must be paid back, and the debit and payer must be equal." The account type of a first account can include a balance resource management type and a balance resource usage type. If the account type of the first account is a balance resource management type, it indicates that the first account can store balance resources, and the balance resource management account corresponding to the first account is itself. If the account type of the first account is a balance resource usage type, it indicates that the first account cannot store balance resources, but can store its balance resources in a first account of a balance resource management type. The first account of the balance resource management type is the balance resource management account corresponding to the first account of the balance resource usage type. It is understood that first accounts of multiple balance resource usage types can store their balance resources in the same first account of the balance resource management type.
[0068] A feasible implementation process for performing double-entry bookkeeping on the S first accounts based on the balance transfer relationship to obtain the double-entry bookkeeping result may be as follows: based on the balance transfer relationship, determining the first account of the S first account belonging to the debit type as the first debit account, and determining the first account of the S first account belonging to the repay type as the first repaying account; determining the debit balances corresponding to the first debit accounts based on the balance transfer relationship; determining the repaying balances corresponding to the first repaying accounts based on the balance transfer relationship; if the sum of the debit balances corresponding to the first debit accounts is equal to the repaying balances corresponding to the first repaying accounts, then recording the debit balances corresponding to the first debit accounts and the repaying balances corresponding to the first repaying accounts, and determining that the double-entry bookkeeping result is a successful double-entry bookkeeping result. When S is two, the balance transfer relationship may include a one-debit-one-repayment relationship; when S is an integer greater than two, the balance transfer relationship may include a one-debit-multiple-repayment relationship and a multiple-debit-multiple-repayment relationship. Among them, a one-borrow-one-repay relationship means that the number of the first debit account is one and the number of the first repaying account is one; a one-borrow-multiple-repay relationship means that the number of the first debit account is one and the number of the first repaying account is multiple; a multiple-borrow-multiple-repay relationship means that the number of the first debit account is multiple and the number of the first repaying account is multiple.
[0069] To facilitate understanding of the double-entry bookkeeping process between S first accounts, please refer to Figure 4, which is a schematic diagram of a double-entry bookkeeping process provided by an embodiment of the present application. As shown in Figure 4, when the balance transfer relationship is a one-debit-one-repayment relationship, for example, account A1 needs to transfer a balance resource of 200 to account B1, then in the transaction accounting layer, it is necessary to record the debit balance of account A1 as 200 and the repayment balance of account B1 as 200; when the balance transfer relationship is a one-debit-multiple-repayment relationship, for example, account A2 needs to transfer a balance resource of 40 to account B2, account A2 needs to transfer a balance resource of 60 to account C2, and account A2 needs to transfer a balance resource of 100 to account D2, then in the transaction accounting layer, it is necessary to record the repayment balance of account B2 as 40 and the repayment balance of account C2 as 60. The balance is 60, the repayment balance of account D2 is 100, and the debit balance of account A2 is 200. When the balance transfer relationship is a multiple-debit-multiple-repayment relationship, for example, account A3 and account B3 each provide a balance resource of 100, and then together transfer a balance resource of 80 to account C3, a balance resource of 80 to account D3, and a balance resource of 40 to account E3. In this case, in the transaction accounting layer, it can be recorded that the debit balance of account A3 is 100, the debit balance of account B3 is 100, the repayment balance of account C3 is 80, the repayment balance of account D3 is 80, and the repayment balance of account E3 is 40. It should be understood that before accounting is performed in the transaction accounting layer, it is necessary to first verify whether the sum of the debit balances corresponding to the first debit account and the sum of the repayment balances corresponding to the first repayment account are equal. Only when the sum of the debit balances corresponding to the first debit account is equal to the sum of the repayment balances corresponding to the first repayment account will the debit balances corresponding to the first debit account and the repayment balances corresponding to the first repayment account be recorded, thereby confirming that the double-entry accounting result is a successful result. As shown in Figure 4, the debit balance of account A1 is equal to the repayment balance of account B1, the debit balance of account A2 is equal to the sum of the repayment balances corresponding to accounts B2, C2, and D2, and the sum of the debit balance of account A3 and the debit balance of account B3 is equal to the sum of the repayment balances corresponding to accounts C3, D3, and E3.
[0070] In actual implementation, a feasible implementation process for transferring the balance resources of S first accounts based on the balance transfer relationship and the balance resource management accounts corresponding to the S first accounts can be: if the balance resource management accounts corresponding to the S first accounts are the same, then the account balances in the S first accounts are numerically updated based on the balance transfer relationship; wherein, an account balance is used to represent the amount of balance resources that can be redeemed by a first account from the balance resource management account; if the balance resource management accounts corresponding to the S first accounts are different, then the balance resource management accounts corresponding to the S first accounts are respectively subjected to balance resource transfer processing based on the balance transfer relationship to obtain a balance resource transfer result; and according to the balance resource transfer result, the account balances in the S first accounts are numerically updated.
[0071] For ease of understanding, let's take an example where S first accounts include first account X and first account Y, and the balance transfer relationship is that first account X transfers 10 balance resources to first account Y. Assume that the account balance of first account X is 50, and the account balance of first account Y is 60.
[0072] If the balance resource management account corresponding to both first accounts is management account Z1, then the amount of balance resources redeemable by first account X in management account Z1 is 50, and the amount of balance resources redeemable by first account Y in management account Z1 is 60. Since both accounts can redeem balance resources from management account Z1, it can be assumed that both balance resources are stored in management account Z1. In this case, there is no need to transfer the balance resources. Instead, the account balances of first account X and first account Y are numerically updated based on the balance transfer relationship. When the account balances of first account X and first account Y are 40 and 70, the transfer of the balance resources between first account X and first account Y is considered complete, because the amount of balance resources redeemable by first account X in management account Z1 has decreased to 40, while the amount of balance resources redeemable by first account Y in management account Z1 has increased to 70.
[0073] If the balance resource management account corresponding to first account X is management account Z2, and the balance resource management account corresponding to first account Y is management account Z3, since the balance resources of the two first accounts are stored in different balance resource management accounts, it is necessary to transfer 10 balance resources from management account Z2 to management account Z3. Obviously, after the transfer is completed, the number of balance resources that first account X can redeem in management account Z2 will be reduced to 40, and the account balance of first account X needs to be updated to 40; the number of balance resources that first account Y can redeem in management account Z3 will increase to 70, and the account balance of first account Y needs to be updated to 70.
[0074] In other embodiments, where the resource type is a digital resource type, the process of determining the transfer relationship of the account associated with the transaction task based on the transaction execution result and the resource type associated with the transaction execution result may be determining the digital resource transfer relationship between L second accounts associated with the transaction task based on the transaction execution result, and thereby performing equal-value transfer accounting processing on the digital resources of the L second accounts based on the digital resource transfer relationship. The process may be performing equal-value transfer accounting processing on the digital resources of the L second accounts based on the digital resource transfer relationship; L is a positive integer; wherein, among the L second accounts after the equal-value accounting processing, the total amount of transferred-out digital resources corresponding to the second account belonging to the transfer output type is equal to the total amount of transferred-in digital resources corresponding to the second account belonging to the transfer input type.
[0075] It should be noted that the total number of transferred-out digital resources corresponding to the second account belonging to the transfer output type is equal to the sum of the number of transferred-out unit digital resources corresponding to the second transfer-out account; the total number of transferred-in digital resources corresponding to the second account belonging to the transfer input type is equal to the sum of the number of transferred-in unit digital resources corresponding to the second transfer-out account; at the same time, as mentioned above, the micro-core component can include a transaction accounting layer and an object resource layer; among them, the transaction accounting layer is used for accounting, and the object resource layer is used for transferring resources between different objects.
[0076] Based on this, the process of determining the digital resource transfer relationship between the L second accounts associated with the transaction task according to the transaction execution result may be, in the transaction accounting layer, determining the digital resource transfer relationship between the L second accounts associated with the transaction task according to the transaction execution result; and thus the process of performing equal-value transfer accounting processing on the digital resources of the L second accounts based on the digital resource transfer relationship may be, performing equal-value accounting processing on the digital resources of the L second accounts based on the digital resource transfer relationship to obtain an equal-value accounting result; if the equal-value accounting result is an equal-value accounting success result, then in the object resource layer, performing digital resource transfer processing on the digital resources of the L second accounts based on the digital resource transfer relationship.
[0077] It should be noted that equal-value accounting means that the accounting equation must be balanced in each transaction. In other words, each transaction must have an equal number of digital resource units transferred out and received. The second account number may include an account address, which is used to store the digital resources of the second account. It should be understood that different second accounts correspond to different account addresses.
[0078] Among them, the above-mentioned equal-value accounting processing of the digital resources of L second accounts based on the digital resource transfer relationship to obtain a feasible implementation process of the equal-value accounting result can be: based on the digital resource transfer relationship, the second account belonging to the transfer output type among the L second accounts is determined as the second transfer-out account, and the second account belonging to the transfer input type among the L second accounts is determined as the second transfer-in account; according to the digital resource transfer relationship, the number of transfer-out unit digital resources corresponding to the second transfer-in account is determined; according to the digital resource transfer relationship, the number of transfer-in unit digital resources corresponding to the second transfer-in account is determined; if the sum of the number of transfer-out unit digital resources corresponding to the second transfer-out account is equal to the sum of the number of transfer-in unit digital resources corresponding to the second transfer-in account, then the number of transfer-out unit digital resources corresponding to the second transfer-out account and the number of transfer-in unit digital resources corresponding to the second transfer-in account are recorded, and the equal-value accounting result is determined to be a successful equal-value accounting result.
[0079] It should be noted that the "number of digital resources transferred out" refers to the number of digital resources per unit contained in the digital resources transferred out by the second transfer-out account. The number of digital resources per unit is a reference standard for measuring the quantity of digital resources and may vary based on actual settings. The "number of digital resources transferred in" refers to the number of digital resources per unit contained in the digital resources received by the second transfer-in account.
[0080] In actual implementation, at the object resource layer, when digital resources of L second accounts are transferred based on a digital resource transfer relationship, if L is two, the digital resource transfer relationship may include a one-out-one-in relationship. In this case, the digital resources of the second transfer-out account can be transferred to the second transfer-in account through a direct transfer transaction. If L is an integer greater than two, the digital resource transfer relationship may include a one-out-multiple-in relationship or a multiple-out-one-in relationship. When the digital resource transfer relationship is a one-out-multiple-in relationship, the digital resources of the second transfer-out account can be transferred to the second transfer-in account through a split-transfer transaction. When the digital resource transfer relationship is a multiple-out-one-in relationship, the digital resources of the second transfer-out account can be transferred to the second transfer-in account through a merge-transfer transaction. A direct transfer transaction refers to the full transfer of digital resources from one transaction party to another; a split transfer transaction refers to the splitting of a transaction party's digital resources into multiple smaller denominations, and then transferring the split digital resources to other transaction parties; and a merge transfer transaction refers to the merging of multiple transaction parties' digital resources into a larger denomination, and then transferring the merged digital resources to another transaction party.
[0081] To facilitate understanding of the digital resource transfer process between L second accounts, please refer to Figure 5, which is a schematic diagram of a digital resource transfer process provided by an embodiment of the present application. As shown in Figure 5, when the digital resource transfer relationship is a one-out-one-in relationship, for example, when owner A1 needs to transfer 10 units of digital resources to owner A2, then in the object resource layer, a direct transfer transaction can be used to directly transfer digital resource 1 containing 10 units of digital resources, and the owner of digital resource 1 will change from owner A1 to owner A2. As shown in Figure 5, when the digital resource transfer relationship is a one-out, multiple-in relationship, for example, owner A2 needs to transfer 10 units of digital resources to owner B2, 5 units of digital resources to owner C2, and 5 units of digital resources to owner D2, then at the object resource layer, a split transfer transaction can be used to split and transfer Digital Resource 2, which contains 20 units of digital resources, to obtain Digital Resource 3, which contains 10 units of digital resources, Digital Resource 4, which contains 5 units of digital resources, and Digital Resource 5, which contains 10 units of digital resources. Among them, Digital Resource 3 belongs to owner B2, Digital Resource 4 belongs to owner C2, and Digital Resource 5 belongs to owner D2. As shown in Figure 5, when the digital resource transfer relationship is a multiple-out, one-in relationship, for example, owners A3 and B3 need to transfer 10 units of digital resources to owner C3, then at the object resource layer, a merge transfer transaction can be used to merge and transfer Digital Resource 6, which contains 5 units of digital resources, and Digital Resource 7, which contains 5 units of digital resources, to obtain Digital Resource 8, which contains 10 units of digital resources. Digital Resource 8 belongs to owner C3. It should be understood that the above-mentioned owner may refer to the account address corresponding to the second account. When transferring digital resources, the sum of the number of transferred-out unit digital resources corresponding to the second transferred-in account should be equal to the sum of the number of transferred-in unit digital resources corresponding to the second transferred-in account.
[0082] In some embodiments, the electronic device may record the corresponding digital resource balance of each digital resource owned by the second account in the object resource layer, where the digital resource balance may be the sum of the number of digital resource units contained in the digital resources owned by the second account. For example, the second account W may own digital resource 9 and digital resource 10, where digital resource 9 contains 5 units of digital resources and digital resource 10 contains 12 units of digital resources. The digital resource balance corresponding to the second account may be 17.
[0083] Through the method provided in the embodiments of the present application, transaction tasks in different field transaction scenarios are handed over to the corresponding field transaction components for completion, and the transfer and accounting process of digital resources or balance resources is uniformly completed by the micro-core component, which decouples the execution process of the transaction task from the transfer and accounting process of the digital resources or balance resources involved in the transaction task, and can realize the integrated accounting of digital resources and balance resources in multiple field transaction scenarios.
[0084] In actual implementation, please refer to Figure 6, which is a flow chart of a data processing method provided in an embodiment of the present application. The method can be executed by an electronic device (for example, the application server 100 in the embodiment corresponding to Figure 1 above). The following will be described using the method executed by an electronic device as an example, wherein the data processing method may include at least the following steps S201-S206:
[0085] Step S201: Determine the task type of the transaction task through the target domain transaction component.
[0086] Step S202: Acquire an accounting sequence that matches the task type.
[0087] In actual implementation, an accounting sequence refers to a predetermined sequence of accounting operations within a specific business scenario, defined by business rules and logic. These operations may include asset transfers, transaction confirmations, and fund settlements. It is understood that the task type of each transaction task may correspond to a specific business scenario within its domain. Therefore, one or more common configuration task types can be preconfigured, and an accounting sequence can be pre-created for each configuration task type. The accounting sequence and the corresponding configuration task type are then stored, for example, in an accounting sequence database.
[0088] In actual implementation, if the accounting sequence database contains one or more configuration task types and the accounting sequence bound to each configuration task type, then a feasible implementation process for obtaining the accounting sequence that matches the task type can be: obtaining the accounting sequence database associated with the target domain transaction component; and determining the accounting sequence bound to the configuration task type with the same task type in the accounting sequence database as the accounting sequence that matches the task type.
[0089] Step S203: Execute the transaction task according to the accounting sequence to obtain the sequence transaction operation data corresponding to the transaction task.
[0090] It should be noted that the transaction execution result includes serial transaction operation data. The transaction task is executed according to the accounting sequence to obtain the serial transaction operation data corresponding to the transaction task. That is, the transaction task is executed according to the accounting sequence to obtain the transaction execution result corresponding to the transaction task.
[0091] In actual implementation, in a feasible embodiment, the accounting sequence may include M accounting operations; M is a positive integer; then a feasible implementation process of executing a transaction task according to the accounting sequence to obtain sequence transaction operation data corresponding to the transaction task can be: traversing the M accounting operations and obtaining the kth accounting operation; k is a positive integer less than or equal to M; executing the transaction task based on the kth accounting operation and k-1 transaction operation data to obtain the kth transaction operation data; when the traversal of the M accounting operations is completed, determining the kth transaction operation data as the sequence transaction operation data.
[0092] Among them, an accounting operation can be used to obtain transaction operation data. Transaction operation data can also be considered a type of accounting information. The accounting information that can be obtained includes accounting subjects, debit and payable directions, amounts, and other information. The accounting information obtained through the accounting operations of the accounting sequence forms a series of standard accounting entry sequences, that is, serial transaction operation data.
[0093] Step S204: Send the sequence transaction operation data to the micro-core component through the target domain transaction component.
[0094] In actual implementation, as described above, transaction execution results include sequenced transaction operation data. Executing a transaction task according to the accounting sequence yields the corresponding sequenced transaction operation data. This means executing the transaction task according to the accounting sequence yields the corresponding transaction execution result. Based on this, the target domain transaction component sends the sequenced transaction operation data to the micro-core component, and the target domain transaction component sends the transaction execution result to the micro-core component.
[0095] Step S205: Determine the resource type associated with the transaction execution result through the micro core component.
[0096] In step S206, the micro-core component determines the transfer relationship of the account associated with the transaction task based on the transaction execution result and the resource type associated with the transaction execution result, and performs transfer accounting processing on the account resources based on the transfer relationship.
[0097] In actual implementation, the realization of step S205-step S206 can refer to the description of step S103-step S104 in the embodiment corresponding to FIG3 above, and will not be repeated here.
[0098] Through the method provided in the embodiment of the present application, by pre-making accounting sequences for transaction tasks of different task types, the serial transaction operation data of each transaction business can be obtained quickly and accurately. The serial transaction operation data can be used as accounting entries for the transaction business, avoiding errors and omissions in manual operations, and also providing an accurate and reliable data basis for subsequent accounting in the micro-core components.
[0099] In actual implementation, please refer to Figure 7, which is a product schematic diagram of an accounting system provided by an embodiment of the present application. As shown in Figure 7, the accounting system 70 provided by an embodiment of the present application can include a Software as a Service (SAAS) platform, a general domain layer and an accounting micro-core. Among them, the SAAS platform is used to realize the SAASization of the accounting system product. SAASization of the product refers to the reconstruction and transformation of traditional stand-alone software products or services, based on cloud computing technology and network technology, and converting them into a cloud-based service model, which is provided to users through the network. Users only need to access the cloud service through the network to use the software functions anytime and anywhere, without having to worry about software installation, configuration, updating, etc., nor do they need to worry about the software's operating environment and hardware equipment. This can greatly improve the software's usage efficiency and user experience. As shown in Figure 7, in the field transaction scenarios corresponding to banking, three-party payment, insurance or various applications, the terminal side can be integrated with a corresponding wallet, and then data is exchanged with the SAAS platform through the wallet to perform transaction tasks in the corresponding field transaction scenario. The general domain layer is derived from a general domain abstraction of domain transaction scenarios, and its implementation can be achieved through the domain transaction components described in the embodiment corresponding to Figure 3 . The accounting micro-core is implemented using the micro-core components mentioned in the embodiment corresponding to Figure 3 . It should be understood that the accounting system 70 shown in Figure 7 can provide a one-stop accounting SaaS service for transaction tasks in various domain transaction scenarios.
[0100] In actual implementation, please refer to Figure 8, which is a schematic diagram of the architecture of an accounting system provided in an embodiment of the present application. As shown in Figure 8, the accounting system can be divided into three layers in terms of implementation: the domain model layer, the transaction accounting layer, and the object resource layer. As shown in Figure 8, the domain model layer is primarily used to implement the general domain layer shown in Figure 7. Based on the concept of microservices, the domain model layer can be split into business domain subsystems, namely the banking general domain layer, the three-party payment general domain layer, etc., as shown in Figure 7. Each business domain subsystem can execute the corresponding transaction task through the pre-made accounting sequence of the business domain. Please refer to the implementation of step S203 in the embodiment corresponding to Figure 6 above, and will not be repeated here. In addition, as shown in the figure, different general domain layers in the domain model layer can generate different transaction vouchers after executing the corresponding transaction tasks, such as original vouchers in the banking domain, original vouchers in the payment domain, and original vouchers in the insurance domain, etc. These transaction vouchers can be used to prove that the transaction task has occurred or been completed. As shown in Figure 8, the transaction accounting layer is responsible for distributed accounting transactions and performs accounting entry levels, thereby ensuring the balance of equal value transfers of M in and N out of digital resources and the balance of double transfers of remaining resources. As shown in Figure 8, the object resource layer is mainly responsible for managing the transfer of digital resources or balance resources. The application of the transaction accounting layer and the object resource layer can be found in the description of step S104 in the embodiment corresponding to Figure 3 above, and will not be repeated here.
[0101] It should be understood that the object resource layer does not need to understand the fields in which object resources or balance resources are used. That is, the accounting system architecture provided by the embodiment of the present application can achieve the decoupling of accounting, resource transfer, and transaction tasks, thereby improving the scalability of the accounting system.
[0102] It should be understood that the accounting system shown in FIG8 is used to ensure the balance of resource transfers based on transaction vouchers. When the accounting system is used to record the first account associated with the balance resource or the second account associated with the digital resource, if an account operation is required, it can be achieved through the account operation model. In the account operation model, the necessary operation primitives can be defined, and then sub-closed-loop full enumeration space operations can be defined for the account and resources (balance resources or digital resources). The operation method deduced from the theory MICE (Multiple Imputation by Chained Equations, missing value filling method) is implemented, thereby obtaining an account operation model that can meet the requirements of resource and account operations, thereby ensuring the scalability of the accounting system.
[0103] Please refer to Figure 9a, which is a schematic diagram of a first account operation model provided in an embodiment of the present application. As shown in Figure 9a, through the first account operation model, you can create / cancel the first account, and you can also freeze or unfreeze the first account. The first account can correspond to a balance resource, and through the first account, you can perform operations such as receiving, paying, transferring, freezing, and unfreezing its balance resources. Similarly, please refer to Figure 9b, which is a schematic diagram of a second account operation model provided in an embodiment of the present application. As shown in Figure 9b, through the second account operation model, you can create / cancel the second account, and you can also freeze or unfreeze the second account. For the digital resources of the second account, you can generate, consume, split, merge, lock, unlock, merge and transfer, directly transfer, and split and transfer operations. It can be understood that generating digital resources refers to generating digital resources with a unique identifier; consuming digital resources refers to using digital resources in a transaction, and after the digital resources are used, the digital resources with the unique identifier become invalid; freezing digital resources or balance resources refers to controlling a certain amount of balance resources or digital resources to prevent them from being used for other transactions; unfreezing digital resources or balance resources refers to lifting the quantity control on the balance resources or digital resources and opening them up for use in other transactions.
[0104] By adopting the accounting system and account operation model provided in the embodiments of the present application, it is possible to realize the integrated accounting of digital resources and balance resources in transaction scenarios in multiple fields.
[0105] Please refer to Figure 10, which is a schematic diagram of the structure of a data processing device provided in an embodiment of the present application. The data processing device can be a computer program (including program code) running on an electronic device, and the electronic device includes at least one domain transaction component and a micro-core component. The data processing device can be, for example, an application software; the data processing device 1 can be configured to execute the corresponding steps in the data processing method provided in an embodiment of the present application. As shown in Figure 10, the data processing device 1 may include: a transaction execution module 11, a type determination module 12, and a transfer accounting module 13.
[0106] The transaction execution module 11 is configured to receive, through a target domain transaction component in at least one domain transaction component, a transaction task corresponding to the target domain transaction component, execute the transaction task, and obtain a transaction execution result; and send the transaction execution result to the micro core component through the target domain transaction component;
[0107] A type determination module 12 is configured to determine the resource type associated with the transaction execution result through the micro-core component;
[0108] The transfer accounting module 13 is configured to determine the transfer relationship of the account associated with the transaction task based on the transaction execution result and the resource type associated with the transaction execution result through the micro core component, and perform transfer accounting processing on the account resources based on the transfer relationship.
[0109] Wherein, the resource type is a balance resource type;
[0110] The transfer accounting module 13 includes: a first transfer accounting unit 131;
[0111] The first transfer accounting unit 131 is further configured to determine the balance transfer relationship of S first accounts associated with the transaction task based on the transaction execution result, and perform double-entry transfer accounting processing on the balance resources of the S first accounts based on the balance transfer relationship; S is a positive integer;
[0112] Wherein, the resource type is a digital resource type;
[0113] The transfer accounting module 13 includes: a second transfer accounting unit 131;
[0114] The second transfer accounting unit 131 is configured to, if the resource type is a digital resource type, determine the digital resource transfer relationship between L second accounts associated with the transaction task based on the transaction execution result, and perform equal-value transfer accounting processing on the digital resources of the L second accounts based on the digital resource transfer relationship; L is a positive integer; among the L second accounts after the equal-value accounting processing, the total amount of transferred-out digital resources corresponding to the second accounts belonging to the transfer output type is equal to the total amount of transferred-in digital resources corresponding to the second accounts belonging to the transfer input type.
[0115] Among them, the implementation methods of the transaction execution module 11, the type determination module 12, and the transfer accounting module 13 can refer to the description of steps S101 to S104 in the embodiment corresponding to Figure 3 above, and will not be repeated here.
[0116] Among them, the transaction execution results include sequence transaction operation data;
[0117] The transaction execution module 11 includes a task determination unit 111 , a sequence acquisition unit 112 , a sequence execution unit 113 and a sending unit 114 .
[0118] The task determining unit 111 is configured to receive a transaction task through a target domain transaction component and determine a task type of the transaction task through the target domain transaction component;
[0119] A sequence acquisition unit 112 is configured to acquire an accounting sequence that matches the task type;
[0120] The sequence execution unit 113 is configured to execute the transaction task according to the accounting sequence and obtain the sequence transaction operation data corresponding to the transaction task;
[0121] The sending unit 114 is configured to send the sequence transaction operation data to the micro core component.
[0122] The implementation of the task determination unit 111 , the sequence acquisition unit 112 , the sequence execution unit 113 and the sending unit 114 may refer to the description of steps S201 to S204 in the embodiment corresponding to FIG6 , which will not be repeated here.
[0123] The sequence acquisition unit 112 includes a database acquisition subunit 1121 and a sequence determination subunit 1122 .
[0124] The database acquisition subunit 1121 is configured to acquire an accounting sequence database associated with the target domain transaction component, wherein the accounting sequence database includes one or more configuration task types and an accounting sequence bound to each configuration task type;
[0125] The sequence determination subunit 1122 is configured to determine the accounting sequence bound to the configuration task type having the same task type as that in the accounting sequence database as the accounting sequence matching the task type.
[0126] The implementation of the database acquisition subunit 1121 and the sequence determination subunit 1122 can refer to the description of step S202 in the embodiment corresponding to FIG6 , which will not be repeated here.
[0127] The bookkeeping sequence includes M bookkeeping operations; M is a positive integer;
[0128] The sequence execution unit 113 includes a traversal subunit 1131 , an execution subunit 1132 and a determination subunit 1133 .
[0129] The traversal subunit 1131 is configured to traverse M accounting operations and obtain the kth accounting operation; k is a positive integer less than or equal to M;
[0130] The execution subunit 1132 is configured to execute the transaction task according to the kth accounting operation and the k-1th transaction operation data to obtain the kth transaction operation data;
[0131] The determining subunit 1133 is configured to determine k transaction operation data as sequence transaction operation data when traversing M accounting operations is completed.
[0132] Among them, the implementation methods of the traversal subunit 1131, the execution subunit 1132 and the determination subunit 1133 can refer to the description of step S203 in the embodiment corresponding to Figure 6 above, and will not be repeated here.
[0133] The data processing device 1 further includes a credential generation module 15 , a credential verification module 16 and a verification pass module 17 .
[0134] The voucher generation module 15 is configured to generate a transaction voucher for the transaction execution result through the target domain transaction component and send the transaction voucher to the micro core component;
[0135] The credential verification module 16 is configured to verify the transaction credential through the micro-core component and obtain a verification result;
[0136] The verification pass module 17 is configured to execute a step of determining a resource type associated with the transaction execution result if the verification result is a verification pass result.
[0137] The implementation of the credential generation module 15 , the credential verification module 16 and the verification module 17 may refer to the description of step S103 in the embodiment corresponding to FIG. 3 , and will not be repeated here.
[0138] Among them, the transaction voucher includes signature data;
[0139] The credential verification module 16 includes a public key signature verification unit 161 and a result determination unit 162 .
[0140] The public key signature verification unit 161 is configured to determine the credential public key associated with the target domain transaction component through the micro core component;
[0141] The public key signature verification unit 161 is further configured to perform signature verification processing on the signature data according to the certificate public key to obtain a signature verification result;
[0142] The result determination unit 162 is configured to determine the verification result as a verification pass result if the signature verification result is a signature verification success result;
[0143] The result determination unit 162 is configured to determine the verification result as a signature verification failure result if the signature verification result is a signature verification failure result.
[0144] The implementation of the public key signature verification unit 161 and the result determination unit 162 can refer to the description of step S103 in the embodiment corresponding to FIG. 3 , which will not be repeated here.
[0145] Among them, the micro-core components include the transaction accounting layer and the object resource layer;
[0146] The first transfer accounting unit 131 includes: a first relationship determination unit 1311 , a first accounting unit 1312 , an account number determination unit 1313 and a first transfer unit 1314 .
[0147] The first relationship determining unit 1311 is configured to determine, in the transaction accounting layer, the balance transfer relationship of the S first accounts associated with the transaction task according to the transaction execution result;
[0148] The first accounting unit 1312 is configured to perform double-entry accounting on the S first accounts based on the balance transfer relationship to obtain a double-entry accounting result;
[0149] The account determination unit 1313 is configured to determine, in the object resource layer, balance resource management accounts corresponding to the S first accounts if the double-entry bookkeeping result is a successful double-entry bookkeeping result; one balance resource management account is used to manage the balance resources of one or more first accounts;
[0150] The first transfer unit 1314 is configured to transfer the balance resources of the S first accounts according to the balance transfer relationship and the balance resource management accounts corresponding to the S first accounts.
[0151] Among them, the implementation methods of the first relationship determination unit 1311, the first accounting unit 1312, the account determination unit 1313 and the first transfer unit 1314 can refer to the description of step S104 in the embodiment corresponding to Figure 3 above, and will not be repeated here.
[0152] The first accounting unit 1312 includes: a first determining subunit 13121 and a first accounting subunit 13122.
[0153] The first determining subunit 13121 is configured to determine, based on the balance transfer relationship, a first account belonging to the debit type among the S first accounts as a first debit account, and determine a first account belonging to the repay type among the S first accounts as a first repay account;
[0154] The first determining subunit 13121 is further configured to determine the debit balances corresponding to the first debit accounts respectively according to the balance transfer relationship;
[0155] The first determining subunit 13121 is further configured to determine the repaying balances corresponding to the first repaying account numbers according to the balance transfer relationship;
[0156] The first accounting sub-unit 13122 is configured to record the debit balances corresponding to the first debit accounts and the repayment balances corresponding to the first repayment accounts if the sum of the debit balances corresponding to the first debit accounts is equal to the repayment balances corresponding to the first repayment accounts, and determine that the double-entry accounting result is a successful double-entry accounting result.
[0157] Among them, the implementation methods of the first determination subunit 13121 and the first accounting subunit 13122 can refer to the description of step S104 in the embodiment corresponding to Figure 3 above, and will not be repeated here.
[0158] The first transfer unit 1314 includes a first transfer sub-unit 13141 and a second transfer sub-unit 13142 .
[0159] The first transfer sub-unit 13141 is configured to update the account balances of the S first accounts based on the balance transfer relationship if the balance resource management account corresponding to each of the S first accounts is the same; an account balance is used to represent the amount of balance resources that can be redeemed by a first account from the balance resource management account;
[0160] The second transfer subunit 13142 is configured to, if the balance resource management accounts corresponding to the S first accounts are different, perform balance resource transfer processing on the balance resource management accounts corresponding to the S first accounts based on the balance transfer relationship to obtain a balance resource transfer result;
[0161] The second transfer subunit 13142 is further configured to perform numerical update processing on the account balances in the S first accounts according to the balance resource transfer result.
[0162] The implementation of the first transfer subunit 13141 and the second transfer subunit 13142 can refer to the description of step S104 in the embodiment corresponding to FIG3 , which will not be repeated here.
[0163] Among them, the micro-core components include the transaction accounting layer and the object resource layer;
[0164] The second transfer accounting unit 132 includes: a second relationship determination unit 1321 , a second accounting unit 1322 and a second transfer unit 1323 .
[0165] The second relationship determination unit 1321 is configured to determine, in the transaction accounting layer, the digital resource transfer relationship between the L second accounts associated with the transaction task according to the transaction execution result;
[0166] The second accounting unit 1322 is configured to perform equal-value accounting processing on the digital resources of the L second accounts based on the digital resource transfer relationship to obtain an equal-value accounting result;
[0167] The second transfer unit 1323 is configured to perform digital resource transfer processing on the digital resources of the L second accounts based on the digital resource transfer relationship in the object resource layer if the equal value accounting result is a successful equal value accounting result.
[0168] Among them, the implementation of the second relationship determination unit 1321, the second accounting unit 1322 and the second transfer unit 1323 can refer to the description of step S104 in the embodiment corresponding to Figure 3 above, and will not be repeated here.
[0169] The second accounting unit 1322 includes: a second determining subunit 13221 and a second accounting subunit 13222.
[0170] The second determining subunit 13221 is configured to determine, based on the digital resource transfer relationship, a second account belonging to the transfer output type among the L second accounts as a second transfer-out account, and determine a second account belonging to the transfer input type among the L second accounts as a second transfer-in account;
[0171] The second determining subunit 13221 is further configured to determine the number of transfer-out unit digital resources corresponding to each of the second transfer-out accounts according to the digital resource transfer relationship;
[0172] The second determining subunit 13221 is further configured to determine the number of transferred digital resources corresponding to each of the second transferred-in accounts according to the digital resource transfer relationship;
[0173] The second accounting sub-unit 13222 is configured to record the number of transfer-out unit digital resources corresponding to the second transfer-out account and the number of transfer-in unit digital resources corresponding to the second transfer-in account if the sum of the number of transfer-out unit digital resources corresponding to the second transfer-in account is equal to the sum of the number of transfer-in unit digital resources corresponding to the second transfer-in account, and determine that the equal-value accounting result is a successful equal-value accounting result.
[0174] Among them, the implementation methods of the second determining subunit 13221 and the second accounting subunit 13222 can refer to the description of step S104 in the embodiment corresponding to Figure 3 above, and will not be repeated here.
[0175] Please refer to Figure 11, which is a structural diagram of an electronic device provided in an embodiment of the present application. As shown in Figure 11, the data processing device 1 in the embodiment corresponding to Figure 10 above can be configured as an electronic device 1000, which may include: a processor 1001, a network interface 1004 and a memory 1005. In addition, the electronic device 1000 may further include: a user interface 1003, and at least one communication bus 1002. Among them, the communication bus 1002 is configured to realize connection and communication between these components. Among them, the user interface 1003 may include a display screen (Display), a keyboard (Keyboard), and the user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 may be a high-speed RAM memory, or a non-volatile memory (non-volatile memory), such as at least one disk storage. In some embodiments, the memory 1005 may also be at least one storage device located away from the aforementioned processor 1001. As shown in FIG. 11 , the memory 1005 , which is a computer-readable storage medium, may include an operating system, a network communication module, a user interface module, and a device control application program.
[0176] In the electronic device 1000 shown in FIG11 , the network interface 1004 may provide a network communication element; the user interface 1003 may be primarily configured to provide an interface for user input; and the processor 1001 may be configured to invoke a device control application stored in the memory 1005 to implement:
[0177] Receiving, through a target domain transaction component in at least one domain transaction component, a transaction task of a target domain corresponding to the target domain transaction component, and executing the transaction task to obtain a transaction execution result;
[0178] Sending the transaction execution result to the micro-core component through the target domain transaction component;
[0179] Determine the resource type associated with the transaction execution result through the micro-core component;
[0180] Through the micro-core component, based on the transaction execution results and the resource types associated with the transaction execution results, the transfer relationship of the account associated with the transaction task is determined, and based on the transfer relationship, the transfer accounting of the account resources is processed.
[0181] It should be understood that the electronic device 1000 described in the embodiment of the present application can execute the description of the data processing method in any of the embodiments corresponding to Figures 3 and 6 above, which will not be repeated here. In addition, the description of the beneficial effects of adopting the same method will not be repeated.
[0182] In addition, it should be pointed out here that: the embodiment of the present application also provides a computer-readable storage medium, and the computer-readable storage medium stores a computer program executed by the data processing device 1 mentioned above, and the computer program includes program instructions. When the processor executes the program instructions, it can execute the description of the data processing method in any of the embodiments corresponding to Figures 3 and 6 above. Therefore, it will not be repeated here. In addition, the description of the beneficial effects of using the same method will not be repeated. For technical details not disclosed in the computer-readable storage medium embodiment involved in this application, please refer to the description of the method embodiment of this application.
[0183] The computer-readable storage medium may be the data processing device provided in any of the aforementioned embodiments or the internal storage unit of the electronic device, such as the hard disk or memory of the electronic device. The computer-readable storage medium may also be an external storage device of the electronic device, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device. The computer-readable storage medium may also include both the internal storage unit and the external storage device of the electronic device. The computer-readable storage medium is configured to store the computer program and other programs and data required by the electronic device. The computer-readable storage medium may also be configured to temporarily store data that has been output or is to be output.
[0184] In addition, it should be noted that embodiments of the present application also provide a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the method provided in any of the embodiments corresponding to FIG. 3 or FIG. 6 .
[0185] The terms "first", "second", etc. in the description, claims, and drawings of the embodiments of the present application are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "comprising" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, apparatus, product, or device that includes a series of steps or units is not limited to the listed steps or modules, but may also include steps or modules that are not listed, or may also include other steps and units inherent to these processes, methods, apparatuses, products, or devices.
[0186] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example in terms of network elements. Whether these network elements are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel may use different methods to implement the described network elements for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0187] The above disclosure is only a preferred embodiment of the present application, and certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.
Claims
1. A data processing method, the method being executed by an electronic device, the electronic device comprising at least one domain transaction component and a micro core component; the method include: Receiving, through a target domain transaction component in the at least one domain transaction component, a transaction task of a target domain corresponding to the target domain transaction component, and executing the transaction task to obtain a transaction execution result; Sending the transaction execution result to the micro core component through the target domain transaction component; Determining, through the micro core component, a resource type associated with the transaction execution result; Through the micro core component, based on the transaction execution result and the resource type associated with the transaction execution result, the transfer relationship of the account associated with the transaction task is determined, and based on the transfer relationship, the transfer accounting processing of the resources of the account is performed.
2. The method according to claim 1, in, The resource type is a balance resource type; and determining the transfer relationship of the account associated with the transaction task based on the transaction execution result and the resource type associated with the transaction execution result includes: Determining, according to the transaction execution result, a balance transfer relationship of S first accounts associated with the transaction task; The performing transfer accounting processing on the resources of the account based on the transfer relationship includes: Based on the balance transfer relationship, double-entry transfer accounting processing is performed on the balance resources of S first accounts, where S is a positive integer.
3. The method according to claim 1, in, The resource type is a digital resource type; and determining the transfer relationship of the account associated with the transaction task based on the transaction execution result and the resource type associated with the transaction execution result includes: Determining a digital resource transfer relationship between L second accounts associated with the transaction task according to the transaction execution result; The performing transfer accounting processing on the resources of the account based on the transfer relationship includes: Based on the digital resource transfer relationship, equal value transfer accounting processing is performed on the digital resources of L second accounts, where L is a positive integer; Among them, among the L second accounts after equal value accounting processing, the total number of transferred-out digital resources corresponding to the second accounts belonging to the transfer output type is equal to the total number of transferred-in digital resources corresponding to the second accounts belonging to the transfer input type.
4. The method according to any one of claims 1 to 3, in, The transaction execution result includes sequence transaction operation data; The executing the transaction task to obtain the transaction execution result includes: Determining the task type of the transaction task through the target domain transaction component; Obtaining an accounting sequence matching the task type; Execute the transaction task according to the accounting sequence to obtain sequence transaction operation data corresponding to the transaction task; The step of sending the transaction execution result to the micro core component through the target domain transaction component includes: The sequence transaction operation data is sent to the micro core component through the target domain transaction component.
5. The method according to claim 4, in, The obtaining of an accounting sequence matching the task type includes: Acquire an accounting sequence database associated with the target domain transaction component, wherein the accounting sequence database includes one or more configuration task types and an accounting sequence bound to each configuration task type; The accounting sequence in the accounting sequence database that is bound to the configuration task type that is the same as the task type is determined as the accounting sequence that matches the task type.
6. The method according to claim 4, in, The bookkeeping sequence includes M bookkeeping operations; M is a positive integer; The step of executing the transaction task according to the accounting sequence to obtain sequence transaction operation data corresponding to the transaction task includes: Traverse the M accounting operations and obtain the kth accounting operation, where k is a positive integer less than or equal to M; According to the kth accounting operation and k-1 transaction operation data, the transaction task is executed to obtain the kth transaction Operational data; When the traversal of the M accounting operations is completed, the k transaction operation data are determined as sequence transaction operation data.
7. The method according to any one of claims 1 to 6, in, The method further comprises: Generate a transaction voucher for the transaction execution result through the target domain transaction component, and send the transaction voucher to the micro core component; Through the micro core component, the transaction voucher is verified to obtain a verification result; If the verification result is a verification pass result, a step of determining a resource type associated with the transaction execution result is performed.
8. The method according to claim 7, in, The transaction voucher includes signature data; the micro-core component verifies the transaction voucher to obtain a verification result, including: Determining, by means of the micro core component, a credential public key associated with the target domain transaction component; Performing signature verification on the signature data according to the certificate public key to obtain a signature verification result; If the signature verification result is a successful signature verification result, then the verification result is determined to be a passed verification result; If the signature verification result is a signature verification failure result, then the verification result is determined to be a signature verification failure result.
9. The method according to claim 2, in, The micro-core component includes a transaction accounting layer and an object resource layer; The determining, according to the transaction execution result, the balance transfer relationship of the S first accounts associated with the transaction task includes: In the transaction accounting layer, determining a balance transfer relationship of S first accounts associated with the transaction task according to the transaction execution result; The performing double-entry transfer accounting processing on the balance resources of the S first accounts based on the balance transfer relationship includes: Perform double-entry bookkeeping processing on the S first accounts based on the balance transfer relationship to obtain a double-entry bookkeeping result; If the double-entry bookkeeping result is a double-entry bookkeeping success result, then determining, in the object resource layer, the balance resource management accounts corresponding to the S first accounts respectively; Wherein, a balance resource management account is used to manage the balance resources of one or more first accounts; The balance resources of the S first accounts are transferred according to the balance transfer relationship and the balance resource management accounts respectively corresponding to the S first accounts.
10. The method according to claim 9, in, The performing double-entry bookkeeping processing on the S first accounts based on the balance transfer relationship to obtain a double-entry bookkeeping result includes: Based on the balance transfer relationship, determining a first account belonging to the debit type among the S first accounts as a first debit account, and determining a first account belonging to the repay type among the S first accounts as a first repay account; Determine the debit balances respectively corresponding to the first debit accounts according to the balance transfer relationship; Determine the repayment balances corresponding to the first repayment accounts respectively according to the balance transfer relationship; If the sum of the debit balances corresponding to the first debit accounts is equal to the sum of the repayment balances corresponding to the first repayment accounts, the debit balances corresponding to the first debit accounts and the repayment balances corresponding to the first repayment accounts are recorded, and the double-entry bookkeeping result is determined to be a successful double-entry bookkeeping result.
11. The method according to claim 9, in, The transferring of the balance resources of the S first accounts according to the balance transfer relationship and the balance resource management accounts respectively corresponding to the S first accounts includes: If the balance resource management accounts respectively corresponding to the S first accounts are the same, then performing numerical update processing on the account balances in the S first accounts based on the balance transfer relationship; Wherein, an account balance is used to represent the amount of balance resources that a first account can redeem from a balance resource management account; If the balance resource management accounts respectively corresponding to the S first accounts are different, performing balance resource transfer processing on the balance resource management accounts respectively corresponding to the S first accounts based on the balance transfer relationship to obtain a balance resource transfer result; According to the balance resource transfer result, the account balances in the S first accounts are updated in numerical value.
12. The method according to claim 3, in, The micro-core component includes a transaction accounting layer and an object resource layer; The determining, according to the transaction execution result, a digital resource transfer relationship between L second accounts associated with the transaction task includes: In the transaction accounting layer, determining the digital resource transfer relationship between the L second accounts associated with the transaction task according to the transaction execution result; The performing equal-value transfer accounting processing on the digital resources of the L second accounts based on the digital resource transfer relationship includes: Based on the digital resource transfer relationship, equal-value accounting processing is performed on the digital resources of the L second accounts to obtain an equal-value accounting result; If the equal-value accounting result is an equal-value accounting success result, then in the object resource layer, digital resource transfer processing is performed on the digital resources of the L second accounts based on the digital resource transfer relationship.
13. The method according to claim 12, in, The performing equal-value accounting processing on the digital resources of the L second accounts based on the digital resource transfer relationship to obtain an equal-value accounting result includes: Based on the digital resource transfer relationship, determining a second account belonging to the transfer output type among the L second accounts as a second transfer-out account, and determining a second account belonging to the transfer input type among the L second accounts as a second transfer-in account; According to the digital resource transfer relationship, determine the number of transfer-out unit digital resources corresponding to each of the second transfer-out accounts; According to the digital resource transfer relationship, determine the number of transferred digital resources corresponding to each of the second transferred accounts; If the sum of the number of transfer-out unit digital resources corresponding to the second transfer-in account is equal to the sum of the number of transfer-in unit digital resources corresponding to the second transfer-in account, then the number of transfer-out unit digital resources corresponding to the second transfer-out account and the number of transfer-in unit digital resources corresponding to the second transfer-in account are recorded, and the equal value accounting result is determined to be a successful equal value accounting result.
14. A data processing device, the device is applied to an electronic device, the electronic device comprises at least one domain transaction component and a micro core component; the device include: The transaction execution module is configured to receive the transaction task of the target domain corresponding to the target domain transaction component through the target domain transaction component in the at least one domain transaction component, and execute the transaction task to obtain a transaction execution result; and send the transaction execution result to the micro core component through the target domain transaction component; A type determination module, configured to determine the resource type associated with the transaction execution result through the micro core component; The transfer accounting module is configured to determine the transfer relationship of the account associated with the transaction task based on the transaction execution result and the resource type associated with the transaction execution result through the micro core component, and perform transfer accounting processing on the resources of the account based on the transfer relationship.
15. An electronic device, include: a memory configured to store computer executable instructions; The processor is configured to implement the method described in any one of claims 1 to 13 when executing the computer executable instructions stored in the memory.
16. A computer-readable storage medium storing computer-executable instructions for causing a processor to execute the instructions to implement the method according to any one of claims 1 to 13.
17. A computer program product, comprising a computer program or a computer executable instruction, wherein when the computer program or the computer executable instruction is executed by a processor, the method according to any one of claims 1 to 13 is implemented.
Citation Information
Patent Citations
Accounting method, accounting system and storage medium
CN110910230A
Accounting processing method and device, computer equipment and storage medium
CN112734543A
Data processing system, method and device, electronic equipment and storage medium
CN114996281A
Accounting processing method and device
CN115034902A
Systems and methods for pooling and transferring digital assets
US20210065302A1
