WO2016174519A1

WO2016174519A1 - Methods and devices for processing values

Info

Publication number: WO2016174519A1
Application number: PCT/IB2016/000620
Authority: WO
Inventors: Wenxue YANG
Original assignee: Alibaba Group Holding Limited
Priority date: 2015-04-27
Filing date: 2016-04-21
Publication date: 2016-11-03
Also published as: TW201640426A; CN106157141B; CN106157141A; TWI700655B

Abstract

Implementations of the present disclosure relate to methods and systems for processing values. The method may include transmitting a rule request message to a rule maintenance center, receiving a target conversion rule returned from the rule maintenance center based on the rule request message, and performing the data conversion processing based on the target conversion rule. The implementations reduce processing load of business systems and improve efficiency of the business systems.

Description

METHODS AND DEVICES FOR PROCESSING VALUES

CROSS REFERENCE TO RELATED PATENT APPLICATIONS

This application claims priority to Chinese Patent Application No. 201510204472.3, filed on April 27, 2015, entitled "Methods and devices for processing values," which is hereby incorporated by reference in its entirety.

TECH NICAL FIELD

Implementations herein relate to Internet technology, and particular relate to methods and devices for processing values.

BACKGROUN D

Transactions of business systems often involve certain special values that need to be processed by the business system. For example, the business systems may process multicurrency payment liquidation as well as back loans and other scenarios that often involve exchange operations (e.g., data conversion processing).

In general, data conversion processing belongs to a part of business processing. Business systems often maintain one or more sets of conversion rules. To perform the data conversion processing, the business systems may process the values based on conversion rules. This requires consumption of resources for maintaining the conversion rules, and therefore increases processing load of the business systems and affects processing efficiency of the business systems.

SUMMARY

Implementations herein relate to methods and devices for processing values. The implementations reduce processing load of business systems and improve their efficiency. This Summary is not intended to identify al l key features or essential features of the claimed subject matter, nor is it intended to be used alone as an aid in determining the scope of the claimed subject matter. The implementations include a method for processing values. The method includes transmitting a rule request message to a rule maintenance center, receiving a target conversion rule that is returned based on the rule request message from the rule maintenance center, and performing data conversion processing based on the target conversion rule.

The implementations further include a device for processing values. The computing device includes a transmitting module configured to transmit a rule request message to a rule maintenance center, a receiving module configured to receive a target conversion rule that is returned based on the rule request message from the rule maintenance center, and a conversion module configured to perform data conversion processing based on the target conversion rule.

The implementations maintain conversion rules via a rule maintenance center. In response to the data conversion processing, a computing device may transfer a rule request message to the rule maintenance center. The computing device may receive a target conversion rule that is returned based on the rule request message from the rule maintenance center. The maintenance of conversion rules is separated from a business system, and the rule maintenance center manages the conversion rules. This reduces the processing load of the business system, and improves the processing efficiency of the business system.

BRIEF DESCRIPTION OF THE DRAWINGS

The Detailed Description is described with reference to the accompanying figures. The use of the same reference numbers in different figures indicates similar or identical items.

FIG. 1 is a flow chart of an illustrative process for processing values.

FIG. 2 is a schematic view of a device for processing values.

DETAILED DESCRI PTION

The detailed description is described with reference to the accompanying figures and implementations. The described implementations merely represent a part of the implementations of the present disclosure. Based on the im plementations of the present disclosure, other embodiments made by those of ordinary skill without creative effort should belong to the scope of protection of the present disclosure. FIG. 1 is a flow chart of an illustrative process for processing values. At 102, a computing device may transmit a rule request message to a maintenance center. At 104, the computing device may receive a target conversion rule that is returned based on the rule request message from the rule maintenance center. At 106, the computing device may perform data conversion processing based on the target conversion rule. The method may be implemented by a device for processing values.

The computing device may include one or more modules associated with a variety of business systems and perform operations associated with the method for processing values.

The implementations maintain conversion rules via a rule maintenance center. In response to the data conversion processing, a rule request message may be transmitted to the rule maintena nce center from a computing device to request a desired conversion rule. The rule maintenance center may determine, based on a service scenario and a service type, a target conversion rule from a set of conversion rules maintained by the rule maintenance center. For ease of description, the desired conversion rule is called a target conversion rule. The rule maintenance center may return the target conversion rule to the computing device after determining the target conversion rule. The computing device may process the value based on the target conversion rule after receiving the target conversion rule.

In implementations, the computing device may implement a service based on a value derived from the data conversion processing. The data conversion processing may include any data conversion based on a certain conversion rule. For example, a long type value can be converted to an int value, a binary value to a decimal value, or U.S. Dollar converted into RMB, and the like. Depending on service scenarios and service types, the process of the data conversion processing may be different and need different conversion rules.

The rule maintenance center may maintain different conversion rules corresponding to different service scenarios and/or service types. Accordingly, the rule request message may include information of a service scenario and a service type. The rule maintenance center may parse the rule request message and obtain the service scenario and the service type after receiving the rule request message.

The rule maintenance center may determine, based on the service scenario and the service type, the target conversion rule from a set of conversion rules maintained by the rule maintenance center and return the target conversion rule to the com puting device. After transmitting the rule request message, the computing device may receive the target conversion rule corresponding to the service scenario and/or the service type.

The implementations maintain conversion rules via a rule maintenance center. In response to the data conversion processing, a rule request message may be transmitted to the rule maintenance center from a computing device. The computing device may receive a target conversion rule that is returned based on the rule request message from the rule maintenance center. Since the maintenance of conversion rules is separated from a business system, the rule maintenance center manages the conversion rules. This reduces the processing load of the business system and improves the processing efficiency of the business system.

Multi-currency payment liquidation as well as back loans and other scenarios often involve exchange operations. Taking CyberSource channel of international payment access of Agricultural Bank of China for example, when a buyer makes payment via the CyberSource channel, the buyer makes the payment using U.S. Dollar. Alipay secures transactions, and the CyberSource channel pays to Alipay using RMB with the corresponding exchange rate. After the transaction, Alipay transfers the fund in RMB to the buyer. Here, the exchange refers to the exchange from U.S. Dollar to RMB. I n this process, Alipay not only secures transactions, but also performs exchange operations, which are actions related to foreign exchange accounting.

Exchange operation is a specific data conversion process. I mplementations of the present disclosure are described in light of the exchange operation. The following procedures may be subject to, but not limited to, a business system.

In a payment system involving three parties, exchange operating scenarios may include: repudiation, payment, and refund. Repudiation refers to a condition that unauthorized users have made payment, but a credit card or payment account holder refuse the payment.

In the present disclosure, the exchange operation may include two service types: business exchange and fund exchange. For example, a complete exchange operation includes business exchange and fund exchange. Any unfinished exchange may be determined by checking a related logic. Fund exchange normally occurs in a process of reconciliation between the business system and a third pa rty financial institution. Business exchange normally occurs when the business system performs operations in response to user operations. The user operations may include a payment request made by a user at an e- commence website, a refund request made by the user in the e-commence website, or a repudiation request made by the user in the bank that issues a card.

For example, in a payment scenario, when the business system receives a payment request made by a user via a e-commence website, the business system may determine an appropriate amount of fund deducted from an account of the user, notify a third party financial institution to deduct the amount of fund from the account of the user in the third party financial institution, transfer the amount of fund to a pending settlement account of the user in the business system (e.g., Alipay), and return the results of payment liquidation.

After receiving the results of payment liquidation from the third party financial institution, the business system may determine whether to perform the exchange operation. For example, the exchange operation has to be performed if the currencies paid by the user and used by the third party financial institution a re not the same. Therefore, the business system may transmit a rule request message to a rule maintenance center. This indicates that the service scenario includes payment.

Accordingly, the exchange service indicated by the service type in the rule request message may include: fund exchange and business exchange. The rule maintenance center may parse the rule request message and obtain the service scenario and the service type after receiving the rule request message. The rule maintenance center may determine, based on the service scenario and the service type, the target conversion rule from a set of conversion rules maintained by the rule maintenance center and return the target conversion rule to the computing device.

Accordingly, the target conversion rule may include: in a payment scenario, an account and an exchange logic that are associated with the fund exchange and an account and an exchange logic that are associated with business exchange. Further, the computing device may perform the fund exchange based on the account and the exchange logic that are associated with the fund exchange, and perform business exchange based on the account and the exchange logic that are associated with the business exchange. In implementations, the business system may perform the reconciliation processing based on the results of payment liquidation to make a comparison between debit details returned from the third party financial institution and debit details recorded by the business system (e.g., fund exchange processing). If the two are consistent, it is determined that reconciliation is successful, the payment of the user has been received, and there is no problem with the payment.

The business system may notify the merchant to ship goods, convert the payment fund from a first currency to a second currency (e.g., U.S. Dollar to RMB), and make corresponding changes (e.g., deduction or addition) on corresponding accounts (e.g., a transition account and a user account), namely the business exchange processing.

Fund exchange may relate to accounts for exchange liquidation. For example, in a payment scenario, the accounts may include accounts for recharging and pending for liquidation. The concept is to be liquidated refers to a situation that the third party financial institution has acknowledged a recharge operation initialized by the user while the fund is not transferred to the business system (e.g., Alipay) by the third party institution for some reason. For example, there is a time difference between the business system and the actual processing. For another reason, the fund transfer may involve another bank, which takes time to tra nsfer the fund to a reserve account of the third party financial institution.

Accounts related to the business exchange includes a transition account, which refers to a merchant account with the same currency of the transition account (e.g., U.S. Dollar transition account). For example, in a refund scenario, when the business system receives a refund request made by a user via a e-commence website, the business system may determine an appropriate amount of fund deducted from a merchant account and transferred to a user account. If the process involves two currencies, the exchange has to be processed. Therefore, the business system may transmit the rule request message to the rule maintenance center, which indicates that the service scenario includes refund.

The exchange service indicated by the service type in the rule request message may include: fund exchange and business exchange. The rule maintenance center may parse the rule request message and obtain the service scenario a nd the service type after receiving the rule request message. The rule maintenance center may determine, based on the service scenario and the service type, the target conversion rule from a set of conversion rules maintained by the rule maintenance center and return the target conversion rule to the business system. The target conversion rule may include: in the refund scenario, a n account and an exchange logic that are associated with the fund exchange and an account and an exchange logic that are associated with business exchange. In these instances, the computing device may perform fund exchange based on the account and the exchange logic that are associated with the fund exchange, and perform business exchange based on the account and the exchange logic that are associated with the business exchange.

In implementations, when the refund fund in a first currency is transferred from the merchant account to the business system (e.g., Alipay), the refund fund may be converted to a second currency. The refund fund in the second currency is then transferred from a transition refund account using the first currency to a transition refund account using the second currency. The refund fund in the refund transition account using the second currency is then transferred to the user account using the second currency to complete the process of the business exchange. In this case, the process of the refund has not completed. This is because the refund fund is transferred directly from the transition account using the second currency to the user account. In fact, a process of liquidation requires when the refund fu nd is transferred from the merchant account to the transition account using the first currency. After receiving results of the liquidation from the third party financial institution, the business system determines that the refund fund is deducted from the merchant account and transferred to the transition account using the first currency and then performs reconciliation.

The business system may make comparison between debit details returned from the third party financial institution and debit details recorded by the business system. When the comparison results are consistent, it is determined that the reconciliation is successful and the refund process is completed. The liquidation process is the process of fund exchange for the refund. The fund exchange may relate to accounts for exchange liquidation. For example, in a refund scenario, the accounts may include accounts for refund and pending for liquidation. Accounts related to the business exchange include transition accounts, which refer to a transition account using the first currency and a transition account using the second currency. For example, in a repudiation scenario, when the business system receives a repudiation request made by a user at a e-commence website, the business system may determine an appropriate amount of fund deducted from a debit account and transferred to a user account. If the process involves two currencies, the exchange has to be processed. Therefore, the business system may transmit rule request message to the rule maintenance center, which indicates that the service scenario includes repudiation. Accordingly, the exchange service indicated by the service type in the rule request message may include: fund exchange and business exchange. The rule maintenance center may parse the rule request message and obtain the service scenario and the service type after receiving the rule request message. The rule maintenance center may determine, based on the service scenario and the service type, the target conversion rule from a set of conversion rules maintained by the rule maintenance center and return the target conversion rule to the business system.

Accordingly, the target conversion rule may include: in a repudiation scenario, an account and an exchange logic that are associated with the fund exchange a nd an account and an exchange logic that are associated with business exchange. Therefore, the computing device associated with the business system may perform data conversion processing based on the target conversion rule by performing fund exchange based on the account and the exchange logic that are associated with the fund exchange and by performing business exchange based on the account and the exchange logic that are associated with the business exchange.

In implementations, after receiving the repudiation request, the business system may deduct the repudiation fund from the debit account and transferred the repudiation fund to the user account, and then determine whether the business system or the merchant is responsible for paying the repudiation fund. If the business system pays the repudiation fund, the business system may transfer the repudiation fund from the debit account of the business system to the receivable account (e.g., the user account). If the merchant pays the repudiation fund, the business system may transfer the repudiation fund from the merchant account to the receivable account. Fund exchange may relate to accounts for exchange liquidation. For example, in a repudiation scenario, the accounts may include accounts for repudiation and pending for liquidation. Accounts related to the business exchange include a transition account, which, in a repudiation scenario, is the receivable account (e.g., a user account).

Accordingly, by using the implementations, various business systems may be freed from maintaining conversion rules and be able to focus on business operations. If exchange is needed, the business system may transmit a rule request message to the rule maintena nce center and receive the rule returned from the rule maintenance center. I n addition, the business system may control the exchange process and record as well as control foreign exchange gains and losses if any.

It is noted that those skilled in the art should be aware that the present disclosure is not limited to the described order of operations. Certain operations may be performed in other orders or simultaneously and may not be necessary for implementations of the present disclosure, and certain implementations may be combined with other implementations.

FIG. 2 is a schematic view of a computing device 200 for processing values. The computing device 200 may be a user device or a server for a multiple location login control. In one exemplary configuration, the computing device 200 includes one or more processors 202, input/output interfaces 204, network interface 206, and memory 208.

The memory 208 may include computer-readable media in the form of volatile memory, such as random-access memory (RAM) and/or non-volatile memory, such as read only memory (ROM) or flash RAM. The memory 208 is an example of computer-readable media.

Computer-readable media includes volatile and non-volatile, removable and nonremovable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, 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), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that may be used to store information for access by a device. As defined herein, com puter-readable media does not include transitory media such as modulated data signals and carrier waves.

Turning to the memory 208 in more detail, the memory 208 may include a transmitting module 210, a receiving module 212, a nd a conversion module 214. The transmitting module 210 may be configured to transmit a rule request message to a rule maintenance center. The receiving module 212 may be configured to receive a target conversion rule that is returned based on the rule request message from the rule maintenance center. The conversion module 214 may be configured to perform data conversion processing based on the target conversion rule.

In implementations, the computing device may implement a service based on a value derived from the data conversion processing. Accordingly, the rule request message may include information of a service scenario and a service type. Accordingly, the receiving module 212 may be configured to receive the target conversion rule that is returned based on the rule request message from the rule maintenance center and corresponds to the service scenario and the service type. For instances, in a payment scenario, the service type indicated by the exchange service may include a fund exchange a nd a business exchange. Accordingly, the target conversion rule may include: in a payment scenario, a n account and an exchange logic that are associated with the fund exchange and an account and an exchange logic that are associated with business exchange. The conversion module 214 may be configured to perform fund exchange based on the account and the exchange logic that are associated with the fund exchange and to perform business exchange based on the account and the exchange logic that are associated with the business exchange.

In implementations, in a refund scenario, the service type may include: a fund exchange and a business exchange. Accordingly, the target conversion rule may include: in a refund scenario, an account and an exchange logic that are associated with the fund exchange and an account a nd an exchange logic that are associated with business exchange. The conversion module 214 may be configured to perform fund exchange based on the account and the exchange logic that are associated with the fund exchange, and perform business exchange based on the account and the exchange logic that are associated with the business exchange. In implementation, in a repudiation scenario, the service type may include: a fund exchange and a business exchange. Accordingly, the target conversion rule may include in the repudiation scenario, an account and an exchange logic that are associated with the fund exchange and an account and an exchange logic that are associated with business exchange. The conversion module 214 may be configured to perform fund exchange based on the account and the exchange logic that are associated with the fund exchange, and perform business exchange based on the account and the exchange logic that are associated with the business exchange.

The implementations maintain conversion rules via a rule maintenance center. For example, a rule request message may be transmitted to the rule maintenance center from a computing device associated with a business system. The computing device may receive a target conversion rule that is returned based on the rule request message from the rule maintenance center. Since the maintenance of conversion rules is separated from a business system, the rule maintenance center manages the conversion rules. The implementations reduce the processing load of business system and im prove the efficiency of the business system.

Those skilled in the art can clearly understand that, for convenience and simplicity of description, specific work process described above correspond to the implementations described herein. In the implementations of this disclosure, it should be understood that the disclosed systems, apparatuses and methods may be implemented using other ways.

For example, the computing devices described above are merely for the purpose of illustration. Division of various modules is merely for the division of logical functions, and may be subject to various divisional ways. For example, modules may be grouped to become another system, and one or more features associated with the modules may be ignored or not performed. Also, communications between modules, such as coupled, directly coupled or communicated with each other, may be implemented by interfaces, which can be electrical, mechanical, or in other forms. Separate modules may be physically separated or not, and may be located in one place or distrusted among places. Further, the various implementations of the present disclosure may involve one or more processing modules. The one or more processing modules may be implemented using hardware and/or software. The embodiments are merely for illustrating the present disclosure and are not intended to limit the scope of the present disclosure. It should be understood for persons in the technical field that certain modifications and improvements may be made and should be considered under the protection of the present disclosure without departing from the principles of the present disclosure.

Claims

CLAIMS What is claimed is:

1. A method for processing values, the method comprising:

transmitting, by a computing device, a rule request message to a rule maintenance center;

receiving, by the computing device, a target conversion rule that is returned based on the rule request message from the rule maintenance center; and

performing, by the com puting device, data conversion processing based on the target conversion rule.

2. The method of claim 1, further comprising:

implementing a service based on data derived from the data conversion processing.

3. The method of claim 1, wherein the rule request message includes information of a service scenario.

4. The method of claim 3, wherein the rule request message further includes information of a service type.

5. The method of claim 4, wherein receiving a target conversion rule that is returned based on the rule request message from the rule maintenance center includes receiving the target conversion rule that is returned based on the rule request message from the rule maintenance center and corresponds to the service scenario and the service type.

6. The method of claim 4, further comprising:

prior to the receiving the target conversion rule that is returned based on the rule request message from the rule maintenance center and corresponds to the service scenario and the service type,

determining, by the rule maintenance center based on the service scenario and the service type, the target conversion rule from a set of conversion rules.

7. The method of claim 6, wherein the set of conversion rules is maintained by the rule maintenance center.

8. A device comprising:

one or more processors; and

memory to maintain a plurality of components executable by the one or more processors, the plurality of components comprising:

a transmitting module configured to transmit a rule request message to a rule maintenance center,

a receiving module configured to receive a target conversion rule that is returned based on the rule request message from the rule maintenance center, and a conversion module configured to perform data conversion processing based on the target conversion rule.

9. The device of claim 8, wherein the plurality of components further comprise: a processing module configured to implement a service based on a data derived from the data conversion processing.

10. The device of claim 8, wherein the rule request message includes information of a service scenario.

11. The device of claim 10₇ wherein the rule request message further includes information of a service type.

12. The device of claim 11, wherein the receiving module is configured to receive the target conversion rule that is returned based on the rule request message from the rule maintenance center and corresponds to the service scenario and the service type.

13. The device of claim 12, wherein the rule maintenance center determines, based on the service scenario and the service type, the target conversion rule from a set of conversion rules.

14. The device of claim 13, wherein the set of conversion rules is maintained by the rule maintenance center.

15. One or more computer-readable media storing computer-executable instructions that, when executed by one or more processors, instruct the one or more processors to perform acts comprising:

transmitting a rule request message to a rule maintena nce center;

receiving a target conversion rule that is returned based on the rule request message from the rule maintenance center; and

performing data conversion processing based on the target conversion rule.

16. The one or more computer-readable media of claim 15, wherein the acts further comprise implementing a service based on a value derived from the data conversion processing.

17. The one or more computer-readable media of claim 15, wherein the rule request message includes information of a service scenario and a service type.

18. The one or more computer-readable media of claim 17, wherein the receiving a target conversion rule that is returned based on the rule request message from the rule maintenance center includes receiving the target conversion rule that is returned based on the rule request message from the rule maintenance center and corresponds to the service scenario and the service type.

19. The one or more computer-readable media of claim 17, wherein the acts further comprise:

20. The one or more computer-readable media of claim 19, wherein the set of conversion rules is maintained by the rule maintenance center.