WO2020042764A1 - 一种金额结算系统及方法 - Google Patents

一种金额结算系统及方法 Download PDF

Info

Publication number
WO2020042764A1
WO2020042764A1 PCT/CN2019/095346 CN2019095346W WO2020042764A1 WO 2020042764 A1 WO2020042764 A1 WO 2020042764A1 CN 2019095346 W CN2019095346 W CN 2019095346W WO 2020042764 A1 WO2020042764 A1 WO 2020042764A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
settlement
configuration
amount
nodes
Prior art date
Application number
PCT/CN2019/095346
Other languages
English (en)
French (fr)
Inventor
孙健
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2020042764A1 publication Critical patent/WO2020042764A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/085—Payment architectures involving remote charge determination or related payment systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems

Definitions

  • the embodiments of the present specification relate to the field of Internet application technology, and in particular, to an amount settlement system and method.
  • Electronic payment also known as online payment, online payment, etc.
  • cash payment As the preferred payment method for various users.
  • the convenience it brings to users has been far more than the basic link of "payment-receipt" payment.
  • convenient accounting functions derived from payment data.
  • “further settlement” refers to: after the payment amount is transferred to a payee account, The amount received needs to be further redistributed, such as revenue sharing among partners, salespersons deducting sales commissions into the total account of the merchant, etc.
  • the automatic settlement of payment amounts will significantly improve the convenience, accuracy, and real-time aspects of settlement.
  • the embodiments of this specification provide an amount settlement system and method.
  • the technical solution is as follows:
  • an amount settlement system is provided:
  • the system has a configurable number of nodes, each node corresponds to an account that supports the transfer function, and the nodes have configurable settlement relationship attributes;
  • the nodes are connected in a tree structure, and each group of parent-child relationships corresponds to a group of accounts with a settlement relationship: the settlement amount of the parent node is transferred to the account, and the settlement amount of the child node is transferred to the account;
  • the settlement relationship attribute of any node includes at least the parent node ID of the node.
  • a method for settlement of an amount based on the aforementioned system including:
  • any node in the system After any node in the system receives the recorded amount, it determines the settlement target according to the parent node ID of the node that is pre-configured;
  • a method for configuring the foregoing system includes:
  • a global configuration operation interface is provided, and the global configuration operation interface is at least used to implement: increase and decrease in the number of system nodes and the configuration of the parent node identifier of any node in the system;
  • the system is configured according to the information received by the global configuration operation interface.
  • a method for configuring the foregoing system includes:
  • a local configuration operation interface matching the configuration authority is provided; the local configuration operation interface is at least used to implement: increase or decrease the number of local nodes in the system and / or Parent node identification configuration for local nodes;
  • the local configuration operation interface According to the information received by the local configuration operation interface, locally configure the system that matches the configuration authority.
  • an amount settlement device based on the foregoing system.
  • the device is located at any node of the system and includes:
  • a settlement target determining unit configured to determine a settlement target according to a pre-configured parent node identifier of the node after the node receives the credited amount
  • a settlement processing unit is configured to settle the amount to a settlement target according to the received amount of the account.
  • a device for configuring the system is provided for the third aspect of the embodiments of the present specification.
  • the device is located on a system management client and includes:
  • the global configuration interface providing unit is used to provide a global configuration operation interface, which is used to implement at least: increase and decrease of the number of system nodes and configuration of settlement relationship attributes of any node of the system;
  • a configuration execution unit is configured to configure the system according to the information received by the global configuration operation interface.
  • a configuration device for the foregoing system is provided.
  • the device is located at a client corresponding to any node of the system, and includes:
  • the local configuration interface providing unit is configured to provide a local configuration operation interface matching the configuration permission according to the configuration permission of the node; the local configuration operation interface is at least used to implement: increase or decrease the number of local nodes in the system, and / or the system Local node settlement relationship attribute configuration;
  • a configuration execution unit is configured to configure a part of the system that matches the configuration authority according to the information received by the local configuration operation interface.
  • the technical solutions provided by the embodiments of the present specification can, on the one hand, realize automatic settlement of amounts for multi-level complex settlement scenarios, and on the other hand, decouple the settlement relationship of each node from the business type of the node itself, thereby realizing Flexible configuration of settlement relationships independent of business types to meet the needs of automatic settlement in scenarios where settlement relationships change dynamically.
  • FIG. 1 is a schematic diagram of a three-tier settlement architecture according to an embodiment of the present specification
  • FIG. 2 is a schematic flowchart of an amount settlement method according to an embodiment of the present specification
  • FIG. 3 is a schematic diagram of a chain store architecture according to an embodiment of the present specification.
  • FIG. 4 is a schematic structural diagram of an amount settlement device according to an embodiment of the present specification.
  • FIG. 5 is a schematic structural diagram of a system management client configuration device according to an embodiment of the present specification.
  • FIG. 6 is a schematic structural diagram of a device for configuring a node client according to an embodiment of the present specification
  • FIG. 7 is a schematic structural diagram of a device for configuring a device according to an embodiment of the present specification.
  • the simplest settlement system is a two-level, one-to-n relationship of the "General Merchant-Store”.
  • levels of settlement system for example: some merchants will also have “Teller Machines” under “Stores”, and some merchants will be in “General Merchants”.
  • region between “store” and “region”, and there may be multiple levels of "region”, such as country, province, city, and so on.
  • Different accounts belonging to the same identity type are in different positions in the settlement system.
  • a three-level settlement system such as "General Merchants-Stores-Teller Machines”
  • some ATMs are set up in stores, and their superior settlement objects are "stores,” and some ATMs are set up independently (not belonging to any store).
  • Its superior settlement object is "General Merchant”;
  • Different accounts belonging to the same level use different settlement rules in the settlement system, for example, different sales personnel have different sales commission percentages, different regions have different rebate points, and so on.
  • Lower-level accounts are settled to higher-level accounts, and there can be multiple levels of "subordinate-level” relationships. For example, ATMs settle at the stores, and the stores settle with the main merchants;
  • the superior account and the lower account are in a one-to-many relationship, that is, multiple lower accounts can be settled to the same superior account. For example, there are multiple ATMs under one store;
  • the settlement amount is settled in stages from bottom to top, and finally pooled into a general account
  • the embodiment of the present specification provides a flexible configurable amount settlement system.
  • the specific implementation scheme is as follows:
  • the system has a number of nodes, of which the number of nodes is configurable, that is, the system management user can add / delete the nodes of the system.
  • Each node corresponds to an electronic account. This account can rely on the client to implement basic functions such as amount transfer in / out, so it can be regarded as a functional module existing in the system.
  • Each node has several attributes, and one or more of these attributes are also configurable.
  • the nodes are connected in a tree structure, and each group of parent-child relationships corresponds to a group of accounts with a settlement relationship: the settlement amount of the parent node is transferred to the account, and the settlement amount of the child node is transferred to the account;
  • a tree structure generally refers to a data structure in which there is a one-to-many relationship between multiple nodes.
  • the root node has no parent node, and each other node has one and only one parent node; the leaf node has no child nodes. , Each remaining node can have one or more child nodes.
  • the amount settlement scenario corresponding to this manual is as follows: Except for the total account (root node), each lower-level account (child node) settles to its upper-level account (parent node), and supports multi-level settlement (multi-layer tree structure) , And support multiple lower-level accounts to settle with the same upper-level account (one parent node corresponds to multiple child nodes), and the settlement amount is finally pooled into the total account (only one root node).
  • Each node has several attributes, which can be divided into two types: “independent attributes” and “relational attributes”, which are introduced below:
  • the "relationship attribute” is used to characterize the relationship between this node and other nodes in the system. In order to meet the needs of the settlement application scenario, the relationship attribute should at least include the settlement relationship attribute.
  • the settlement relationship attribute of any node should include at least the parent node ID of the node.
  • the three-tier settlement system a is the root node, and the global settlement relationship includes: c1, c2 settles to b1, c3 setstles to b2, and b1 and b2 settles to a.
  • each node can use a uniform rule to settle to the next-level node, such as 100% of the transferred amount to the higher-level node, 80% of the transferred amount to the higher-level node, and so on.
  • a "settlement rule" can also be added to the settlement relationship attribute, which indicates the mapping relationship between the node's credited amount and the settlement-out amount.
  • c1, c2, and c3 are all settled to the superior node, and the proportion of b1 and b2 to the superior node is 0.9 and 0.8, respectively. It can be seen that not only nodes at different levels can support different upward settlement ratios, but also nodes at the same level can support different upward settlement ratios.
  • the settlement ratio is only a specific manifestation of the settlement rules.
  • the settlement rules can be configured into other forms of "accounting amount ⁇ transfer amount" mapping relationship.
  • a fixed settlement ratio equivalent to a mapping function being a linear function
  • “Different sources” can be different lower-level computing nodes, for example, for the b1 node in FIG. 3:
  • “Different sources” can be different types of entries, for example, for node b2 in Figure 3:
  • b2 (parent node: a), (settlement ratio: [if source subordinate node: 0.85], [if source direct debit: 0.75])
  • relationship attributes of any node can also include other content, such as:
  • Child node ID which can be used for verification and needs to be updated in synchronization with the parent node ID in the child node;
  • Business relationship information can be used to record the business superior / subordinate of the corresponding account of the node.
  • the business relationship and settlement relationship here can be the same or independent of each other, that is, the superior / subordinate in the business relationship is not necessarily the settlement.
  • the superior / subordinate in the relationship can be used to record the business superior / subordinate of the corresponding account of the node.
  • independent attributes are used to characterize the independent characteristics of any node, and these attributes are not associated with other nodes. For each account, “account name”, “bind user information”, “person in charge”, “address”, “telephone”, etc., all belong to the category of independent attributes. According to the solution of this application, the nodes located in the settlement system may also have one or more of the following configurable independent attributes:
  • label whose function is to facilitate the system management user to batch configure information for multiple nodes with the same label, that is, by modifying the value of a label, to achieve a unified configuration of all nodes with the label.
  • the label can be the business type of the node's corresponding account, such as "store”, “salesperson”, “terminal”, “first-level merchant”, “secondary merchant”, etc., or the type of settlement relationship of the corresponding account of the node. For example, “charge terminal type”, “intermediate settlement type”, “first-level child node”, “second-level child node”, etc.
  • the configuration type of a node can either reuse other types of accounts corresponding to the node, or be independent of other types of accounts corresponding to the node.
  • the service type of the node can be reused as the configuration type; and for the case where the service type and the settlement requirements are separated.
  • the service type and the settlement requirements are separated.
  • a three-level settlement system such as "General Merchant-Store-Teller Machine”
  • some Teller Machines are set up in stores, and some Teller Machines are set up independently.
  • their business types are "Teller Machines”, they have different Settlement configuration requirements.
  • any node can have multiple configuration types in different dimensions at the same time, which facilitates filtering nodes from multiple dimensions. For example, if a node can have the label "Salesman” and also the label "High Proportion”, then the node can match the "Salesman", “High Proportion” and “High Proportion & Salesman” tags respectively. Filtering rules.
  • the source type of a node's account can itself be a feature of the node, for example, it can be reused as the configuration type of the node; it can also be used to limit which types of account sources will participate in the settlement of the superior node; this attribute can also cooperate with the previous embodiment "Configure different settlement rules for different accounting sources" to achieve the function.
  • the source of any node's account can include two types: the child node account of the current node, and an account outside the settlement system.
  • a node account (leaf node in the tree structure) directly facing the customer's payment
  • its source of account is "outside account in the settlement system”
  • an intermediate-level account in the settlement system non-leaf node in the tree structure
  • its source of account is "child node account of current node”.
  • any node in the system can configure the whole or part of the system.
  • the configuration authority should be limited to a few nodes with management properties.
  • the attribute "configuration authority" can be used to indicate whether a node has overall or partial configuration authority for the system.
  • Configuration permissions can be divided according to configurable objects, such as:
  • the root node of the system has configuration rights for the entire system
  • Any node has configuration rights for its descendants
  • Any node has configuration rights for its first-level child nodes (but does not have configuration rights for its lower-level child nodes);
  • Configuration permissions can also be divided by content, for example:
  • configuration authority is only for illustrative purposes, and those skilled in the art can flexibly design according to requirements.
  • the configuration authority can also be separated from the restrictions of the settlement system tree structure itself, or set a dedicated configuration node outside the settlement system, and so on.
  • this specification also provides an amount settlement method, which runs on any node in the system. As shown in Figure 2, the method can include the following steps:
  • any node in the system determines a settlement target according to a pre-configured parent node identifier of the node;
  • any node in the system after receiving a transfer amount, according to the pre-configured parent node identifier, it can be determined to whom to settle.
  • Each node in the tree structure performs functions in accordance with the steps of S101 to S102, forming a complete system of settlement from level to level. It should be particularly noted that the total account corresponding to the root node will only receive the credited amount, and will not further initiate settlement to the superior. Here, it can be understood that the "parent node ID" configured by the root node is empty.
  • the system can calculate the settlement transfer-out amount corresponding to the received account amount according to the pre-configured settlement rules of the node, and then further calculate the settlement transfer-out amount. Out to settlement goals.
  • the node after the node receives the credited amount, it can further obtain the transferee's information to determine whether the transferee matches the pre-configured "source type" of the current node, or determine a difference based on the transferee's information Settlement rules, etc.
  • the transferee's information For specific function implementation, refer to the description of the foregoing embodiments, and the description is not repeated here.
  • this manual also provides corresponding system configuration methods. Users can configure the system through the client. Clients can be divided into system management clients and node clients according to basic functions:
  • a global configuration operation interface is provided.
  • This interface is for management users and can be provided in the form of command line or GUI.
  • the specific interaction methods can be buttons, touch, sound control, etc. This manual does not perform this. limited.
  • the global configuration operation interface can be used to at least increase or decrease the number of nodes in the system, the parent node identification configuration of any node in the system; further, the global configuration operation interface can also be used to implement independent attribute configuration of any node in the system, and so on.
  • the system management client configures the system based on the information received from the global configuration operation interface.
  • a local configuration operation interface on the client corresponding to any node is for the user of the node account and can also be provided in the form of command line or GUI.
  • the specific interaction methods can be buttons, touch, sound control, etc. This manual This is not limited.
  • the configurable items presented to users of different node accounts should match the content of the node's configuration permissions. It can be understood here that if the node does not have any configuration permissions, the user cannot see (or cannot use) any configurable items.
  • the local configuration operation interface can be used to implement: increase or decrease the number of local nodes in the system, and / or the configuration of the parent node identifier of the local nodes in the system. Further, the local configuration operation interface can also be used to implement the settlement rule configuration of any node within the authority scope, the independent attribute configuration of any node, and so on.
  • configuration type of node attribute can also be used to perform batch configuration on nodes with the same configuration type.
  • the node client configures the corresponding node according to the information received from the global configuration operation interface.
  • node client corresponds to a node in the settlement system
  • system management client can be located outside the settlement system and does not have to have “Accounts” interact with each other.
  • two versions of the client can be developed separately, or different functions can be provided for login users with different identities in one version.
  • the total account can be regarded as a root node.
  • the user can build any number of descendant nodes below to form a tree.
  • the content that can be configured for each node can be Including: settlement superior object, settlement formula, business type (such as store, area, directly operated store, etc.), other information (such as person in charge, address, telephone, QR code applied for the node, etc.).
  • Each node can set different permissions and support customized labels. Labels can be applied to different nodes, which is convenient for one-time configuration and applied to all associated nodes, reducing repetitive labor. And the label can be separated from the business type of the node, there will not be a fixed two-level structure where the store must hang under the merchant. For the system, there is no need to know the business type of "store” or "merchant” or "terminal”, etc. There is no mandatory business type at each layer or node of the tree structure, and the business type is weakly related to the attributes of a node , Implementation can be arbitrarily configured. In the same settlement level of the tree structure, nodes of different service types can appear, and different settlement relationship attributes can be configured.
  • each sales representative has its own customer.
  • the sales representative will provide his account code to the cash register. , Record the corresponding consumption to his account, so that the bonus dividend can be calculated later.
  • the store has a two-dimensional code, and all consumption at that store is aggregated up to the total account after deducting the store commission, and the store must distribute the corresponding commission part to the corresponding sales representative by itself .
  • each sales representative can print his own QR code.
  • Each sales representative corresponds to a settlement account.
  • This account belongs to the leaf node in the settlement system and has a superior settlement.
  • Object store
  • settlement rules percentage of commission
  • other attributes For other service type nodes in the system, the settlement method is similar. In this way, it is still the same payment process for consumers, but on the settlement system side, the system can clearly understand from which node the transfer amount was received, and how this amount should be distributed.
  • the settlement system provided in this manual can meet the settlement needs of various scales and structures. Especially for small and medium-sized merchants, they may not even have their own sales management system. Then the application of this application can effectively enhance these merchants. The efficiency and accuracy of the amount allocation.
  • this specification also provides an amount settlement device, which is located at any node of the system.
  • the device may include:
  • the settlement target determining unit 110 is configured to determine a settlement target according to a pre-configured parent node identifier of the node after the node receives the credited amount;
  • a settlement processing unit 120 is configured to settle an amount to a settlement target according to the received amount of account.
  • this specification also provides a configuration device for a settlement system.
  • the device is located on a system management client. Referring to FIG. 5, the device may include:
  • the global configuration interface providing unit 210 is configured to provide a global configuration operation interface, which is used to implement at least: increase and decrease of the number of system nodes and configuration of settlement relationship attributes of any node of the system;
  • a configuration execution unit 220 is configured to configure the system according to the information received by the global configuration operation interface.
  • this specification also provides a configuration device for the settlement system.
  • the device is located at a client corresponding to any node of the system.
  • the device may include:
  • the local configuration interface providing unit 310 is configured to provide a local configuration operation interface that matches the configuration permission according to the configuration permission of the node; the local configuration operation interface is at least used to implement: increasing or decreasing the number of local nodes in the system, and / or Configuration of settlement relationship attributes of local nodes of the system;
  • a configuration execution unit 320 is configured to configure a part of the system that matches the configuration authority according to the information received by the local configuration operation interface.
  • An embodiment of the present specification further provides a computer device including at least a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the foregoing method of settlement of amounts when the program is executed, and / Or system configuration method.
  • FIG. 7 shows a more specific schematic diagram of a hardware structure of a computing device provided by an embodiment of the present specification.
  • the device may include a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050.
  • the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 implement a communication connection within the device through a bus 1050.
  • the processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits, etc., for performing related operations. Program to implement the technical solutions provided by the embodiments of this specification.
  • a general-purpose CPU Central Processing Unit
  • ASIC Application Specific Integrated Circuit
  • the memory 1020 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage devices, dynamic storage devices, and the like.
  • the memory 1020 may store an operating system and other application programs.
  • related program codes are stored in the memory 1020 and are called and executed by the processor 1010.
  • the input / output interface 1030 is used to connect an input / output module to implement information input and output.
  • the input / output / module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions.
  • the input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc.
  • the output device may include a display, a speaker, a vibrator, and an indicator light.
  • the communication interface 1040 is used to connect a communication module (not shown in the figure) to implement communication interaction between the device and other devices.
  • the communication module can implement communication through a wired method (such as USB, network cable, etc.), and can also implement communication through a wireless method (such as mobile network, WIFI, Bluetooth, etc.).
  • the bus 1050 includes a path for transmitting information between various components of the device (for example, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040).
  • the device may also include necessary for achieving normal operation Other components.
  • the foregoing device may also include only components necessary to implement the solutions of the embodiments of the present specification, and does not necessarily include all the components shown in the drawings.
  • An embodiment of the present specification also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the foregoing amount settlement method and / or system configuration method are implemented.
  • Computer-readable media includes both permanent and non-persistent, removable and non-removable media.
  • Information can be stored by any method or technology.
  • Information may be computer-readable instructions, data structures, modules of a program, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), and read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, read-only disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media may be used to store information that can be accessed by computing devices.
  • computer-readable media does not include temporary computer-readable media, such as modulated data signals and carrier waves.
  • the embodiments of the present specification can be implemented by means of software plus a necessary universal hardware platform. Based on such an understanding, the technical solutions of the embodiments of the present specification may be embodied in the form of software products that are essentially or contribute to the existing technology.
  • the computer software product may be stored in a storage medium, such as ROM / RAM, Magnetic disks, optical disks, and the like include a number of instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform the methods described in the various embodiments or portions of the embodiments of this specification.
  • the system, device, module, or unit described in the foregoing embodiments may be specifically implemented by a computer chip or entity, or a product with a certain function.
  • a typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email sending and receiving device, and a game control Desk, tablet computer, wearable device, or a combination of any of these devices.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

公开了一种金额结算系统及方法。一种金额结算系统，该系统具有数量可配置的若干节点，每个节点对应一个支持转账功能的账户，节点具有可配置的结算关系属性；节点间以树形结构关联，每组父子关系对应一组存在结算关系的账户：父节点对应结算金额转入账户、子节点对应结算金额转出账户；任一节点的结算关系属性中，至少包括该节点的父节点标识。

Description

一种金额结算系统及方法 技术领域
本说明书实施例涉及互联网应用技术领域，尤其涉及一种金额结算系统及方法。
背景技术
电子支付(也称网络支付、在线支付等)由于具有便捷、高效、低成本等优势，近些年来得到快速发展，甚至已经逐渐取代现金支付，成为各类用户的首选支付方式。不仅如此，基于电子支付的诸多特性，其为用户带来的方便已经远不止局限于“付款-收款”这一支付的基本环节。例如基于支付数据所衍生的便捷记账功能。
在实际应用中，一些收款方在收到费用之后，会存在进一步结算的需求，这里的“进一步结算”是指：支付金额转入某个收款方账户后，在收款方一侧还需要进一步对所收到的金额进行重新分配，例如合作伙伴之间的收入分成、业务员将收到的款项扣除销售提成后转入商户总账户，等等。在这种场景下，实现支付金额的自动结算，将对结算的便捷性、准确性、实时性等多方面产生显著改善。
现有技术中，针对一些简单且固定的结算关系，可以实现支付金额的自动结算，例如一些网约车平台针对司机端的费用结算系统。然而在实际应用中，存在很多更为复杂的结算关系，而且结算关系存在动态变化的可能，现有技术还无法满足这些场景下的自动结算需求。
发明内容
针对上述技术问题，本说明书实施例提供一种金额结算系统及方法，技术方案如下：
根据本说明书实施例的第1方面，提供一种金额结算系统：
该系统具有数量可配置的若干节点，每个节点对应一个支持转账功能的账户，节点具有可配置的结算关系属性；
节点间以树形结构关联，每组父子关系对应一组存在结算关系的账户：父节点对应结算金额转入账户、子节点对应结算金额转出账户；
任一节点的结算关系属性中，至少包括该节点的父节点标识。
根据本说明书实施例的第2方面，提供一种基于前述系统的金额结算方法，该方法包括：
系统中任一节点在收到入账金额后，根据预先配置的该节点的父节点标识确定结算目标；
根据所收到的入账金额，向结算目标进行金额结算。
根据本说明书实施例的第3方面，提供一种针对前述系统的配置方法，该方法包括：
在系统管理客户端，提供全局配置操作接口，所述全局配置操作接口至少用于实现：系统节点数量增减配置、以及系统任一节点的父节点标识配置；
根据所述全局配置操作接口接收到的信息，对系统进行配置。
根据本说明书实施例的第4方面，提供一种针对前述系统的配置方法，该方法包括：
在任一节点对应的客户端，根据该节点的配置权限，提供与配置权限相匹配的局部配置操作接口；所述局部配置操作接口至少用于实现：系统局部节点数量增减配置，和/或系统局部节点的父节点标识配置；
根据所述局部配置操作接口接收到的信息，对与配置权限相匹配的系统局部进行配置。
根据本说明书实施例的第5方面，提供一种基于前述系统的金额结算装置，该装置位于系统任一节点，包括：
结算目标确定单元，用于在节点在收到入账金额后，根据预先配置的该节点的父节点标识确定结算目标；
结算处理单元，用于根据所收到的入账金额，向结算目标进行金额结算。
根据本说明书实施例的第6方面，提供一种针对根据本说明书实施例的第三方面，提供述系统的配置装置，该装置位于系统管理客户端，包括：
全局配置接口提供单元，用于提供全局配置操作接口，所述全局配置操作接口至少用于实现：系统节点数量增减配置、以及系统任一节点的结算关系属性配置；
配置执行单元，用于根据所述全局配置操作接口接收到的信息，对系统进行配置。
根据本说明书实施例的第7方面，提供一种针对前述系统的配置装置，该装置位于系统任一节点对应的客户端，包括：
局部配置接口提供单元，用于根据该节点的配置权限，提供与配置权限相匹配的局部配置操作接口；所述局部配置操作接口至少用于实现：系统局部节点数量增减配置，和/或系统局部节点的结算关系属性配置；
配置执行单元，用于根据所述局部配置操作接口接收到的信息，对与配置权限相匹配的系统局部进行配置。
本说明书实施例所提供的技术方案，一方面，可以针对多层级的复杂结算场景实现金额的自动结算，另一方面，将每个节点的结算关系与节点本身的业务类型解耦，从而实现可独立于业务类型的结算关系灵活配置，满足结算关系动态变化场景下的自动结算需求。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本说明书实施例。
此外，本说明书实施例中的任一实施例并不需要达到上述的全部效果。
附图说明
为了更清楚地说明本说明书实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本说明书实施例中记载的一些实施例，对于本领域普通技术人员来讲，还可以根据这些附图获得其他的附图。
图1是本说明书实施例的三层结算体系结构示意图；
图2是本说明书实施例的金额结算方法的流程示意图；
图3是本说明书实施例的连锁店体系结构示意图；
图4是本说明书实施例的金额结算装置的结构示意图；
图5是本说明书实施例的系统管理客户端配置装置的结构示意图；
图6是本说明书实施例的节点客户端的配置装置的结构示意图；
图7是用于配置本说明书实施例装置的一种设备的结构示意图。
具体实施方式
为了使本领域技术人员更好地理解本说明书实施例中的技术方案，下面将结合本说 明书实施例中的附图，对本说明书实施例中的技术方案进行详细地描述，显然，所描述的实施例仅仅是本说明书的一部分实施例，而不是全部的实施例。基于本说明书中的实施例，本领域普通技术人员所获得的所有其他实施例，都应当属于保护的范围。
现有技术中，针对一些简单且固定的结算关系，已经可以实现支付金额的自动结算，以网约车平台为例，乘客支付的打车费用实际会被分为两部分：一部分是司机的实际收入，另一部分是平台的抽成。假设1个平台有n个司机，且平台以及每名司机都各自对应一个账户，那么就形成了一个“1对n”的两级结算体系。在网约车平台中，两级的结算体系结构是固定的，并且“平台”对“司机”的抽成额度也是固定的(例如平台抽取打车费用的20％)，那么就可以针对“平台账户”和“司机账户”这两种账户身份，设计一个具有固定结构和分配规则的体系，从而实现打车费用的自动结算。
然而在实际应用中，不同的应用场景可能存在截然不同的结算需求，举例说明如下：
不同的商户，具有不同的结算层级架构。例如最简单的结算体系是“总商户-门店”的两级1对n关系，更多层级的结算体系例如：有些商户在“门店”下还会有“柜员机”、有些商户在“总商户”和“门店”之间还有“区域”的概念，而“区域”又可能进一步存在多级，例如国家、省、市等等。
属于同一身份类型的不同账户，在结算体系中处于不同位置。例如在“总商户-门店-柜员机”这样的3级结算体系中，有些柜员机是设置在门店中，则其上级结算对象是“门店”，有些柜员机是独立设置(不属于任一家门店)，则其上级结算对象是“总商户”；
属于同一级别(或同一身份类型)的不同账户，在结算体系中使用不同的结算规则，例如不同销售人员的销售金额提成比例不同，不同地区的返利点数不同，等等。
可见，现有技术中的自动结算，仅是针对某个特定应用场景，设置固定的结算体系，无法满足多变的结算需求。
技术人员通过分析发现，在复杂的金额结算应用场景中，各个账户的结算关系具有以下特点：
下级账户向上级账户结算，并且可以存在多个层次的“上下级”关系。例如柜员机向门店结算、门店向总商户结算；
上级账户和下级账户是“一对多”的关系，即多个下级账户可以向同一个上级账户结算。例如一个门店下面有多个柜员机；
结算金额按照由下至上的方向，逐级结算，最终汇集至一个总账户；
针对上述具体应用场景，本说明书实施例提供一种可灵活配置的金额结算系统，具体实现方案如下：
系统具有若干数量的节点，其中节点数量是可配置的，即系统管理用户可以对系统的节点进行增加/删除操作。每个节点对应一个电子账户，该账户可依托于客户端实现金额转入/转出等基本功能，因此可视为系统中存在的一个功能模块。
每个节点具有若干属性，这些属性中的一种或多种也是可配置的。
节点间以树形结构关联，每组父子关系对应一组存在结算关系的账户：父节点对应结算金额转入账户、子节点对应结算金额转出账户；
树形结构一般指代多个节点之间存在“一对多”关系的数据结构，在树形结构中，根节点没有父节点，其余每个节点有且只有一个父节点；叶子节点没有子节点，其余每个节点可以有一个或多个子节点。对应于本说明书中的金额结算场景如下：除总账户(根节点)外，每个下级账户(子节点)均向其上级账户(父节点)结算，支持多级结算(多层树形结构)、以及支持多个下级账户向同一个上级账户结算(一个父节点对应多个子节点)，结算金额最终汇集至总账户(仅有一个根节点)。
每个节点具有若干属性，从性质上可以分为“独立属性”和“关系属性”两类，下面分别进行介绍：
“关系属性”用于表征该节点与系统中其他节点的关系，为了满足结算应用场景的需求，关系属性至少应包括结算关系属性。
对于系统中每个节点(除根节点之外)，收到一笔转入金额后，需要了解该向谁进行结算，因此在任一节点的结算关系属性中，至少应包括该节点的父节点标识。
如图1所示的三层结算体系，a为根节点，全局的结算关系包括：c1、c2向b1结算，c3向b2结算，b1和b2向a结算。
那么，除根节点的外的各节点结算关系配置如下：
c1：(父节点：b1)
c2：(父节点：b1)
c3：(父节点：b2)
b1：(父节点：a)
b2：(父节点：a)
默认情况下，各节点可以采用统一的规则向上一级节点进行结算，例如将转入金额的100％结算至上一级节点、将转入金额的80％结算至上一级节点，等等。为了满足更灵活的结算需求，还可以在结算关系属性中添加“结算规则”，表示节点的入账金额与结算转出金额的映射关系。
仍以图1所示的三层结算体系为例，添加结算规则后的配置结果示意如下：
c1：(父节点：b1)，(结算比例：1)
c2：(父节点：b1)，(结算比例：1)
c3：(父节点：b2)，(结算比例：1)
b1：(父节点：a)，(结算比例：0.9)
b2：(父节点：a)，(结算比例：0.8)
根据上述的结算规则配置，c1、c2、c3均为全额向上级节点结算，b1和b2向上级节点结算的比例分别为0.9和0.8。可见，不仅不同级别的节点之间可以支持不同的向上结算比例，相同级别的节点也可以支持不同的向上结算比例。
可以理解的是，结算比例只是结算规则的一种具体表现形式，根据实际需求，可以将结算规则配置为其他形式的“入账金额→转出金额”映射关系。例如，除了固定结算比例(相当于映射关系为线性函数)外，还可以利用分段函数、指数函数等形式，实现配置结算比例根据每次入账金额动态变化、或者结算比例根据统计周期(例如1个月)的入账总金额动态变化；当然，结算关系也不仅限于结算比例一种表现形式，本领域技术人员可以根据实际需求灵活进行配置。
此外，在任一节点中，还可以针对不同入账来源配置不同的结算规则，举例如下：
“不同来源”可以是不同的下级计算节点，例如针对图3的b1节点：
b1：(父节点：a)，(结算比例：[if来源c1:0.95]，[if来源c2:0.85])
“不同来源”可以是不同的入账类型，例如针对图3的b2节点：
b2：(父节点：a)，(结算比例：[if来源下级节点:0.85]，[if来源直接入账:0.75])
除“父节点标识”和“结算规则”之外，任一节点的关系属性中还可以包括其他内 容，例如：
子节点标识，可用于校验，需与子节点中的父节点标识同步更新；
业务关系信息，可用于记录该节点对应账户的业务上级/下级，注意这里的业务关系与结算关系可以是一致的，也可以相互独立，即：业务关系中的上级/下级，并不一定是结算关系中的上级/下级。
相对于“关系属性”而言，“独立属性”用于表征任一节点的独立特征，这些属性与其他节点不存在关联。对于每个账户而言，“账户名”、“绑定用户信息”、“负责人”、“地址”、“电话”等等，均属于独立属性的范畴。而根据本申请方案，位于结算系统中的节点还可以具有以下一种或多种可配置的独立属性：
节点的配置类型：
可以理解为一种“标签”，其作用是方便系统管理用户对多个具有相同标签节点进行批量信息配置，即：通过修改一个标签的值，实现所有具有该标签的节点的统一配置。
标签可以是节点对应账户的业务类型，例如“门店”、“业务员”、“终端机”、“一级商户”、“二级商户”等等，也可以是节点对应账户的结算关系类型，例如“收费终端型”、“中间结算型”、“一级子节点”、“二级子节点”等等，
需要说明的是，节点的配置类型，既可以复用该节点对应账户的其他类型，也可以独立于该节点对应账户的其他类型。
例如，在节点的业务类型和结算需求完全一致的情况下，可以将节点的业务类型复用为配置类型；而针对业务类型和结算需求分离的情况。例如前面的举例，“总商户-门店-柜员机”这样的3级结算体系中，有些柜员机是设置在门店中，有些柜员机是独立设置，尽管其业务类型都是“柜员机”，但是却具有不同的结算配置需求。应用本说明书实施例所提供的方案，将节点业务类型和结算需求解耦，从而可以脱离节点业务类型的限制，实现更为灵活的配置。
另外，任一节点可以同时具有多个不同维度下的配置类型，从而方便从多个维度筛选节点。例如，某个节点可以具有“业务员”标签，还可以同时具有“高比例提成”标签，则该节点可以分别匹配“业务员”、“高比例提成”以及“高比例提成&业务员”的筛选规则。
节点的入账来源类型：
节点的入账来源类型，本身可以作为节点的一种特征，例如可以复用为节点的配置类型；也可以用于限定哪些类型的入账来源将参与向上级节点结算；该属性还可以配合前面实施例中“针对不同入账来源配置不同的结算规则”来实现功能。
一般而言，任一节点的入账来源可以包括2个类型：当前节点的子节点账户、结算系统之外的账户。例如，直接面对客户收款的节点账户(树形结构中的叶子节点)，其入账来源为“结算系统外账户”，而结算体系中的中间阶层账户(树形结构中的非叶子节点)，其入账来源为“当前节点的子节点账户”。
值得注意的是，对于结算体系中的中间阶层账户，可以同时允许其入账来源为“结算系统外账户”以及“当前节点的子节点账户”。例如，对于“区域总店”这样一个业务节点而言，其既会接收“区域分店”的结算金额，同时也可以直接收款产生销售额。
当然，根据实际的应用需求，还可以对入账来源类型做进一步划分，或者增加其他的入账来源类型。
节点的配置权限：
理论上，系统中的任一节点都可以对系统的整体或局部进行配置，实际应用中，配置权限应仅限于少数具有管理性质的节点。跟据本说明书所提供的实现方式，可以用“配置权限”这一属性来表示节点是否具有对系统整体或局部的配置权限。
配置权限可以按照可配置对象进行划分，例如：
系统的根节点具有对系统整体的配置权限；
任一节点具有对其子孙节点的配置权限；
任一节点具有对其一级子节点的配置权限(但不具有对其更下级子节点的配置权限)；
……
配置权限还可以按照内容划分，例如：
是否允许在系统中新增/删除节点；
是否允许修改节点的结算关系；
是否允许对节点的结算规则进行配置；
……
当然，上述配置权限仅用于示意性说明，本领域技术人员可以根据需求灵活设 计。此外，配置权限也可以脱离结算体系树形结构本身的限制，或设置结算系统之外的专用的配置节点，等等。
基于前述提供的系统，本说明书还提供一种金额结算方法，该方法运行于系统中任一节点上，参见图2所示，该方法可以包括以下步骤：
S101，系统中任一节点在收到入账金额后，根据预先配置的该节点的父节点标识确定结算目标；
S102，根据所收到的入账金额，向结算目标进行金额结算。
根据前面实施例的描述，对于系统中任一节点，收到一笔转入金额后，根据预先配置的父节点标识，就可以确定需要向谁进行结算。
树形结构中的每一节点都按照S101～S102的步骤执行功能，就形成了一个完整的由下至上逐级结算的系统。需要特别说明的是，根节点对应的总账户仅会收到入账金额，不会进一步向上级发起结算，这里可以理解为根节点配置的“父节点标识”为空。
如果系统支持结算规则属性，则在节点发起结算之前，可以根据预先配置的该节点的结算规则，计算所收到入账金额对应的结算转出金额，然后进一步将计算得到的结算转出金额，转出至结算目标。
此外，在节点收到入账金额之后，还可以进一步获取转入方的信息，判断该转入方是否与预先配置的当前节点的“入账来源类型”相匹配，或者根据转入方的信息确定不同的结算规则，等等。具体功能实现可以参见前面实施例的描述，这里不再重复说明。
基于前述提供的系统，本说明书还提供相应的系统配置方法，用户可以通过客户端实现对系统的配置。按照基本功能可以将客户端划分为系统管理客户端和节点客户端：
在系统管理客户端，提供全局配置操作接口，该接口是面对管理用户的，可以是命令行或GUI形式提供，具体的交互方式可以是按键、触摸、声控等，本说明书对此并不进行限定。
全局配置操作接口至少可以用于实现系统节点数量增减配置，系统任一节点的父节点标识配置；进一步地，全局配置操作接口还可以用于实现系统任一节点的独立属性配置，等等。
用户在系统管理客户端进行配置操作时，可以创建或删除一个新系统、在已有系统中新增或删除节点、对已有系统的一个或多个节点的配置进行修改。这里可以利用“节点的配置类型”属性，对具有相同配置类型的节点进行批量配置。
用户完成配置操作并确认提交后，系统管理客户端根据从全局配置操作接口接收到的信息，对系统进行配置。
在任一节点对应的客户端，提供局部配置操作接口；该接口是面对节点账户使用者的，同样可以是命令行或GUI形式提供，具体的交互方式可以是按键、触摸、声控等，本说明书对此并不进行限定。
由于不同节点具有不同的配置权限，因此呈现给不同节点账户使用者的可配置项目应是与节点的配置权限内容相匹配的。这里可以理解为：如果节点不具有任何配置权限，则用户就看不到(或无法使用)任何可配置项目。
局部配置操作接口可以用于实现：系统局部节点数量增减配置，和/或系统局部节点的父节点标识配置。进一步地，局部配置操作接口还可以用于实现权限范围内的任一节点的结算规则配置，任一节点的独立属性配置，等等。这里的“系统局部”应理解为对应于配置权限所规定的范围。例如，如果规定任一节点的配置权限范围为其子孙节点，则该节点可以实现对其子孙节点的父节点标识、结算规则等属性进行配置。
用户在节点客户端进行配置操作时，可以在配置权限所规定的范围内新增或删除节点、对已有的一个或多个节点的配置进行修改。这里同样可以利用“节点的配置类型”属性，对具有相同配置类型的节点进行批量配置。
用户完成配置操作并确认提交后，节点客户端根据从全局配置操作接口接收到的信息，对相应的节点进行配置。
以上介绍了两种不同类型的客户端，其本质区别在于，“节点客户端”对应于结算系统中的某个节点，而“系统管理客户端”则可以位于结算系统之外，并且不必须具备“账户”相互功能。实际应用时，可以分别开发两种版本的客户端，也可以在一个版本中，为不同身份的登录用户提供不同功能。
可见，应用本说明书所提供的方案，实现复杂结算场景时，可以将总账户视为一个根节点，用户可以在下面建立任意多的子孙节点，形成一棵树，每一个节点可以配置的内容可以包括：结算上级对象、结算公式、业务类型(例如门店、区域、直营门店等)、其他信息(例如负责人、地址、电话、为该节点申请的二维码等)。
每个节点可以设置不同的权限，支持客制化标签，标签可以打到不同的节点上，方便做一次性配置并运用到所有相关联的节点上，减少重复性的劳动。并且标签可以与节点的业务类型分离，不会出现店铺一定挂在商户下面的固定两级结构。对于系统，不需要知道“店铺”或者“商户”或者“终端机”等等的业务类型，树形结构的每一层或者每一个节点都没有强制业务类型，业务类型作为一个节点的属性弱关联，实现可随意配置。树形结构的同一结算层级可以出现不同业务类型的节点，配置不同的结算关系属性。
下面结合一个实际应用场景，对本说明书提供的方案进行说明。如图3所示，以某品牌的连锁店为例，每一个销售代表都有自己的客户，客户得到销售代表的服务、并到收银台付款时，销售代表会把他的账户代码提供给收银台，把相应的消费记到他的账上，以便后面计算奖金分红。
根据现有技术的实现方案，店铺具有一个二维码，所有在那个店铺的消费都在扣除店铺提成后给向上汇总给总账户，店铺要自行二次把相应的提成部分分配给相应的销售代表。
而在本说明书所提供的系统中，除了店铺之外，每个销售代表都可以打印自己的二维码，每个销售代表对应一个结算账户，该账户属于结算系统中的叶子节点，具有上级结算对象(店铺)、结算规则(提成百分比)等属性。对于系统中的其他业务类型节点，结算方式类似。这样，对于消费者而言仍是相同的付款流程，但是在结算系统一侧，系统可以很清晰地了解到是从哪个节点收到的转入金额、并且应该如何分配这笔金额。
本说明书所提供的结算系统，可以适应各种规模、各种结构的结算需求，特别是对于中小型商户，可能连自己的销售管理系统都没有，那么应用本申请的方案，可以有效提升这些商户的金额分配的效率及准确性。
相应于上述方法实施例，本说明书还提供一种金额结算装置，该装置位于系统任一节点，参见图4所示，该装置可以包括：
结算目标确定单元110，用于在节点在收到入账金额后，根据预先配置的该节点的父节点标识确定结算目标；
结算处理单元120，用于根据所收到的入账金额，向结算目标进行金额结算。
相应于上述方法实施例，本说明书还提供一种针对结算系统的配置装置，该装 置位于系统管理客户端，参见图5所示，该装置可以包括：
全局配置接口提供单元210，用于提供全局配置操作接口，所述全局配置操作接口至少用于实现：系统节点数量增减配置、以及系统任一节点的结算关系属性配置；
配置执行单元220，用于根据所述全局配置操作接口接收到的信息，对系统进行配置。
相应于上述方法实施例，本说明书还提供一种针对结算系统的配置装置，该装置位于系统任一节点对应的客户端，参见图6所示，该装置可以包括：
局部配置接口提供单元310，用于根据该节点的配置权限，提供与配置权限相匹配的局部配置操作接口；所述局部配置操作接口至少用于实现：系统局部节点数量增减配置，和/或系统局部节点的结算关系属性配置；
配置执行单元320，用于根据所述局部配置操作接口接收到的信息，对与配置权限相匹配的系统局部进行配置。
本说明书实施例还提供一种计算机设备，其至少包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，处理器执行所述程序时实现前述的金额结算方法和/或系统配置方法。
图7示出了本说明书实施例所提供的一种更为具体的计算设备硬件结构示意图，该设备可以包括：处理器1010、存储器1020、输入/输出接口1030、通信接口1040和总线1050。其中处理器1010、存储器1020、输入/输出接口1030和通信接口1040通过总线1050实现彼此之间在设备内部的通信连接。
处理器1010可以采用通用的CPU(Central Processing Unit，中央处理器)、微处理器、应用专用集成电路(Application Specific Integrated Circuit，ASIC)、或者一个或多个集成电路等方式实现，用于执行相关程序，以实现本说明书实施例所提供的技术方案。
存储器1020可以采用ROM(Read Only Memory，只读存储器)、RAM(Random Access Memory，随机存取存储器)、静态存储设备，动态存储设备等形式实现。存储器1020可以存储操作系统和其他应用程序，在通过软件或者固件来实现本说明书实施例所提供的技术方案时，相关的程序代码保存在存储器1020中，并由处理器1010来调用执行。
输入/输出接口1030用于连接输入/输出模块，以实现信息输入及输出。输入输出/模块可以作为组件配置在设备中(图中未示出)，也可以外接于设备以提供相应功能。其中输入设备可以包括键盘、鼠标、触摸屏、麦克风、各类传感器等，输出设备可以包括显示器、扬声器、振动器、指示灯等。
通信接口1040用于连接通信模块(图中未示出)，以实现本设备与其他设备的通信交互。其中通信模块可以通过有线方式(例如USB、网线等)实现通信，也可以通过无线方式(例如移动网络、WIFI、蓝牙等)实现通信。
总线1050包括一通路，在设备的各个组件(例如处理器1010、存储器1020、输入/输出接口1030和通信接口1040)之间传输信息。
需要说明的是，尽管上述设备仅示出了处理器1010、存储器1020、输入/输出接口1030、通信接口1040以及总线1050，但是在具体实施过程中，该设备还可以包括实现正常运行所必需的其他组件。此外，本领域的技术人员可以理解的是，上述设备中也可以仅包含实现本说明书实施例方案所必需的组件，而不必包含图中所示的全部组件。
本说明书实施例还提供一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现前述的金额结算方法和/或系统配置方法。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
通过以上的实施方式的描述可知，本领域的技术人员可以清楚地了解到本说明书实施例可借助软件加必需的通用硬件平台的方式来实现。基于这样的理解，本说明书实施例的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等) 执行本说明书实施例各个实施例或者实施例的某些部分所述的方法。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机，计算机的具体形式可以是个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件收发设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任意几种设备的组合。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于装置实施例而言，由于其基本相似于方法实施例，所以描述得比较简单，相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的模块可以是或者也可以不是物理上分开的，在实施本说明书实施例方案时可以把各模块的功能在同一个或多个软件和/或硬件中实现。也可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
以上所述仅是本说明书实施例的具体实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本说明书实施例原理的前提下，还可以做出若干改进和润饰，这些改进和润饰也应视为本说明书实施例的保护范围。

Claims (21)

  1. 一种金额结算系统：
    该系统具有数量可配置的若干节点，每个节点对应一个支持转账功能的账户，节点具有可配置的结算关系属性；
    节点间以树形结构关联，每组父子关系对应一组存在结算关系的账户：父节点对应结算金额转入账户、子节点对应结算金额转出账户；
    任一节点的结算关系属性中，至少包括该节点的父节点标识。
  2. 根据权利要求1所述的系统，所述任一节点的结算关系属性中，还包括：
    该节点向其父节点进行结算时使用的结算规则，所述结算规则用于表示节点的入账金额与结算转出金额的映射关系。
  3. 根据权利要求2所述的系统，所述结算规则包括：
    针对不同的入账来源配置的不同结算规则。
  4. 根据权利要求1所述的系统，节点还具有可配置的独立属性。
  5. 根据权利要求4所述的系统，所述可配置的独立属性包括：
    节点的配置类型，用于实现相同配置类型节点的批量信息配置。
  6. 根据权利要求5所述的系统，节点的配置类型，复用或独立于该节点对应账户的其他类型。
  7. 根据权利要求4所述的系统，所述可配置的独立属性包括：
    节点的入账来源类型，所述入账来源类型包括：当前节点的子节点账户、和/或结算系统外账户。
  8. 根据权利要求4所述的系统，所述可配置的独立属性包括：
    节点的配置权限，用于表示当前节点是否具有对系统整体或局部的配置权限。
  9. 根据权利要求8所述的系统，系统的根节点具有对系统整体的配置权限。
  10. 根据权利要求8所述的系统，任一节点对系统局部的配置权限具体为：该节点对其子孙节点的配置权限。
  11. 一种基于权利要求1至10任一项所述系统的金额结算方法，该方法包括：
    系统中任一节点在收到入账金额后，根据预先配置的该节点的父节点标识确定结算目标；
    根据所收到的入账金额，向结算目标进行金额结算。
  12. 根据权利要求11所述的方法，所述根据所收到的入账金额，向结算目标进行金额结算，包括：
    根据预先配置的该节点的结算规则，计算所收到入账金额对应的结算转出金额；
    将计算得到的结算转出金额，转出至结算目标。
  13. 一种针对权利要求1至10任一项所述系统的配置方法，该方法包括：
    在系统管理客户端，提供全局配置操作接口，所述全局配置操作接口至少用于实现：系统节点数量增减配置、以及系统任一节点的父节点标识配置；
    根据所述全局配置操作接口接收到的信息，对系统进行配置。
  14. 一种针对权利要求1至10任一项所述系统的配置方法，该方法包括：
    在任一节点对应的客户端，根据该节点的配置权限，提供与配置权限相匹配的局部配置操作接口；所述局部配置操作接口至少用于实现：系统局部节点数量增减配置，和/或系统局部节点的父节点标识配置；
    根据所述局部配置操作接口接收到的信息，对与配置权限相匹配的系统局部进行配置。
  15. 根据权利要求14所述的方法，任一节点的配置权限具体为：该节点对其子孙节点的配置权限。
  16. 一种基于权利要求1至10任一项所述系统的金额结算装置，该装置位于系统任一节点，包括：
    结算目标确定单元，用于在节点在收到入账金额后，根据预先配置的该节点的父节点标识确定结算目标；
    结算处理单元，用于根据所收到的入账金额，向结算目标进行金额结算。
  17. 一种针对权利要求1至10任一项所述系统的配置装置，该装置位于系统管理客户端，包括：
    全局配置接口提供单元，用于提供全局配置操作接口，所述全局配置操作接口至少用于实现：系统节点数量增减配置、以及系统任一节点的结算关系属性配置；
    配置执行单元，用于根据所述全局配置操作接口接收到的信息，对系统进行配置。
  18. 一种针对权利要求1至10任一项所述系统的配置装置，该装置位于系统任一节点对应的客户端，包括：
    局部配置接口提供单元，用于根据该节点的配置权限，提供与配置权限相匹配的局部配置操作接口；所述局部配置操作接口至少用于实现：系统局部节点数量增减配置，和/或系统局部节点的结算关系属性配置；
    配置执行单元，用于根据所述局部配置操作接口接收到的信息，对与配置权限相匹配的系统局部进行配置。
  19. 一种计算机设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述程序时实现如权利要求11所述的方法。
  20. 一种计算机设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述程序时实现如权利要求13所述的方法。
  21. 一种计算机设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述程序时实现如权利要求14所述的方法。
PCT/CN2019/095346 2018-08-27 2019-07-10 一种金额结算系统及方法 WO2020042764A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810979675.3 2018-08-27
CN201810979675.3A CN109284990A (zh) 2018-08-27 2018-08-27 一种金额结算系统及方法

Publications (1)

Publication Number Publication Date
WO2020042764A1 true WO2020042764A1 (zh) 2020-03-05

Family

ID=65183864

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/095346 WO2020042764A1 (zh) 2018-08-27 2019-07-10 一种金额结算系统及方法

Country Status (3)

Country Link
CN (1) CN109284990A (zh)
TW (1) TWI720519B (zh)
WO (1) WO2020042764A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113298665A (zh) * 2021-07-27 2021-08-24 太平财产保险有限公司 一种车险跟单的自动结算方法和基于该方法的结算系统

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109284990A (zh) * 2018-08-27 2019-01-29 阿里巴巴集团控股有限公司 一种金额结算系统及方法
CN110807627B (zh) * 2019-10-31 2022-07-26 国网数字科技控股有限公司 一种跨单位电费结算方法、装置及系统
CN112037067B (zh) * 2020-09-11 2023-08-25 中国银行股份有限公司 一种结算报文业务数据的处理系统及方法
CN113393228A (zh) * 2021-06-21 2021-09-14 中国工商银行股份有限公司 电子转账方法、系统、电子设备、存储介质及程序产品
CN114666141A (zh) * 2022-03-24 2022-06-24 阿里云计算有限公司 基于平台即服务的数据处理方法、设备、介质及产品

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101556718A (zh) * 2009-05-21 2009-10-14 中国建设银行股份有限公司 多级账户资金管理系统及装置
US20120323753A1 (en) * 2011-06-14 2012-12-20 Monica Norman Clearing system
CN105989434A (zh) * 2015-02-06 2016-10-05 天脉聚源（北京）科技有限公司 一种交易信息管理方法和系统
CN107679983A (zh) * 2017-10-20 2018-02-09 京北方信息技术股份有限公司 额度树构建方法和装置、额度占用路径检查方法和装置
CN109284990A (zh) * 2018-08-27 2019-01-29 阿里巴巴集团控股有限公司 一种金额结算系统及方法

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7206768B1 (en) * 2000-08-14 2007-04-17 Jpmorgan Chase Bank, N.A. Electronic multiparty accounts receivable and accounts payable system
CN101877107A (zh) * 2010-04-08 2010-11-03 苏州德融嘉信信用管理技术有限公司 集团企业资金归集业务系统及其应用方法
WO2012003156A1 (en) * 2010-06-27 2012-01-05 Visa International Service Association Scheduled funds transfer platform apparatuses, methods and systems
TW201207749A (en) * 2010-08-02 2012-02-16 Jian-Xian Wu BBPS system
CN104318473A (zh) * 2014-10-30 2015-01-28 中国建设银行股份有限公司 一种多级资金管理方法和系统
CN107358420B (zh) * 2017-06-09 2020-08-11 北京博晨技术有限公司 用于实现热点账户的区块链系统以及实现热点账户的方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101556718A (zh) * 2009-05-21 2009-10-14 中国建设银行股份有限公司 多级账户资金管理系统及装置
US20120323753A1 (en) * 2011-06-14 2012-12-20 Monica Norman Clearing system
CN105989434A (zh) * 2015-02-06 2016-10-05 天脉聚源（北京）科技有限公司 一种交易信息管理方法和系统
CN107679983A (zh) * 2017-10-20 2018-02-09 京北方信息技术股份有限公司 额度树构建方法和装置、额度占用路径检查方法和装置
CN109284990A (zh) * 2018-08-27 2019-01-29 阿里巴巴集团控股有限公司 一种金额结算系统及方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113298665A (zh) * 2021-07-27 2021-08-24 太平财产保险有限公司 一种车险跟单的自动结算方法和基于该方法的结算系统

Also Published As

Publication number Publication date
CN109284990A (zh) 2019-01-29
TWI720519B (zh) 2021-03-01
TW202026970A (zh) 2020-07-16

Similar Documents

Publication Publication Date Title
US11961067B2 (en) Splittable security token
WO2020042764A1 (zh) 一种金额结算系统及方法
US20200034813A1 (en) Systems and methods for scheduling business-to-individual payments
US10540375B2 (en) Systems and methods for self-pairing databases
JP5087261B2 (ja) データ要素命名システムおよび方法
AU2019285610A1 (en) Blockchain-based exchange method and apparatus for available resource quotas
US11663592B2 (en) Automatic transaction-based verification of account ownership
WO2020088130A1 (zh) 一种基于区块链的财产执行方法及系统
CN109559164B (zh) 优惠信息处理方法、装置、电子设备及计算机可读介质
US10417059B1 (en) Staged application programming interface
AU2017425676B2 (en) System for data consolidation across disparate namespaces
TW201624370A (zh) 業務資訊處理方法及裝置
TW201903662A (zh) 一種資料物件展示方法及裝置
CN103745402A (zh) 一种具有有效期的电子货币管理方法
US11494831B2 (en) System and method of providing customer ID service with data skew removal
CN115841395A (zh) 一种会计分录数据的生成方法、系统及相关设备
US20210295283A1 (en) Methods and systems for blockchain digital currency stake delegation
US20210142422A1 (en) Computerized transaction optimization
TWM648300U (zh) 線上記帳系統
CN116911838A (zh) 一种交易数据管理方法、装置及存储介质
CN115082199A (zh) 协议存款产品生成方法、系统和终端设备
CN118154336A (zh) 一种对账方法、系统及相关设备
US20060190405A1 (en) Utilizing distribution types to assign attributes to distribution lines in an accounting system
WO2022265953A1 (en) Distributed ledger-based decentralized autonomous organizations and collaborations
CN111985919A (zh) 支付数据处理方法、装置及电子设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19854068

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19854068

Country of ref document: EP

Kind code of ref document: A1