WO2020103275A1 - Procédé, appareil et dispositif de commande de déduction d'argent, support d'informations lisible - Google Patents

Procédé, appareil et dispositif de commande de déduction d'argent, support d'informations lisible

Info

Publication number
WO2020103275A1
WO2020103275A1 PCT/CN2018/123190 CN2018123190W WO2020103275A1 WO 2020103275 A1 WO2020103275 A1 WO 2020103275A1 CN 2018123190 W CN2018123190 W CN 2018123190W WO 2020103275 A1 WO2020103275 A1 WO 2020103275A1
Authority
WO
WIPO (PCT)
Prior art keywords
deduction
request
deduction request
charge control
control method
Prior art date
Application number
PCT/CN2018/123190
Other languages
English (en)
Chinese (zh)
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 WO2020103275A1 publication Critical patent/WO2020103275A1/fr

Links

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/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/108—Remote banking, e.g. home banking
    • 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/22—Payment schemes or models
    • 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/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/407—Cancellation of a transaction
    • 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02—Banking, e.g. interest calculation or account maintenance

Definitions

  • This application relates to the field of financial technology, and in particular, to a deduction control method, device, equipment, and readable storage medium.
  • the main purpose of this application is to provide a deduction control method, device, equipment, and readable storage medium, which are intended to solve the technical problems that existing banks are easy to debit and affect user experience when debiting.
  • the present application provides a deduction control method.
  • the deduction control method is applied to a collection system.
  • the collection system includes multiple distributed servers.
  • the deduction control method includes:
  • the step of locking the deduction request includes:
  • the deduction request is locked.
  • the step of locking the deduction request based on the distributed locking method provided by the Redis database includes:
  • the user account and the preset prefix are set as the first parameter content of the first parameter key pre-stored in the distributed locking mode, and the IP address of the target server is set as the pre-stored first parameter in the distributed locking mode
  • determining that the debit request is successfully locked includes:
  • the unlock processing is performed on the lock processing deduction request whose storage time is greater than the lock over time.
  • the lock deduction request is sent to the target server for the target server to perform pre-storage on the user account corresponding to the lock deduction request
  • the deduction operation steps include:
  • the deduction request corresponding to the successful deduction is unlocked.
  • the charge control method further includes:
  • the unlocking type of the deduction request is obtained based on the unlocking completion instruction
  • unlocking type is an active unlocking type, it is determined to generate the first prompt message of successful deduction
  • the unlocking type is a passive unlocking type, it is determined to generate a second prompt message that the deduction has failed.
  • This application also provides a charge control device, the charge control device includes:
  • a receiving module configured to determine the target server side of the deduction request according to the current number of pending requests of the multiple server sides when receiving the deduction request;
  • a locking module configured to perform a locking process on the deduction request, and send the deduction request after the locking process to the target server side, so that the target server side
  • the user account corresponding to the deduction request corresponds to the execution of the pre-stored deduction operation.
  • the locking module includes:
  • a calling unit used to call a pre-stored concurrency control program segment to intercept the deduction request
  • the locking unit is used for locking the deduction request based on the distributed locking method provided by the Redis database.
  • the locking unit includes:
  • the first obtaining subunit is used to obtain the user account corresponding to the deduction request, the IP address of the target server, and the preset lock timeout time;
  • a verification subunit configured to verify the target lock and determine whether a preset return value is received
  • the determination subunit is configured to determine that the deduction request is successfully locked if the preset return value is received.
  • the locking unit further includes:
  • a storage subunit configured to store the deduction request after successful locking in the Redis database, and periodically scan each deduction request after locking processing stored in the Redis database;
  • a detection subunit configured to detect the deduction request after the lock processing that the storage time is greater than the lock over time if the storage time of each deduction request after locking processing in the Redis database is greater than the lock over time Unlock processing.
  • the charge control device further includes:
  • the unlocking module is used for unlocking the deduction request corresponding to the successful deduction if the target server side detects that the client corresponding to the deduction request after the lock processing is successfully debited.
  • the charge control device further includes:
  • An obtaining module configured to obtain an unlocking type of the deduction request based on the unlocking completion instruction if it is detected that the deduction request has been unlocked and processed;
  • a first determining module configured to determine, if the unlocking type is an active unlocking type, the first prompt information of successful payment deduction
  • the second determining module is configured to determine, if the unlocking type is a passive unlocking type, to generate second prompt information that the deduction has failed.
  • the present application also provides a charge control device, the charge control device includes: a memory, a processor, a communication bus, and a charge control instruction readable stored on the memory,
  • the communication bus is used to realize the communication connection between the processor and the memory
  • the processor is used to execute the deduction control readable instructions to implement the following steps:
  • the present application also provides a readable storage medium that stores one or more programs, and the one or more programs may be executed by one or more processors to Used for:
  • the target server side of the deduction request is determined according to the current number of pending requests of the multiple servers; the lock request is processed to lock the deduction request
  • the processed deduction request is sent to the target server side for the target server side to perform a pre-stored deduction operation corresponding to the user account corresponding to the locked deduction request.
  • the client corresponding to the deduction request is locked synchronously, Therefore, if there is another deduction request that is synchronized with the deduction request, the other deduction request will be abandoned and not processed. Therefore, repeated deductions can be avoided and the user experience can be improved, thereby solving the problem that the existing bank debits Technical issues that are easy to debit and affect user experience.
  • FIG. 1 is a schematic flowchart of a first embodiment of a deduction control method of this application
  • FIG. 2 is a detailed flowchart of a lock processing step of the deduction request in the second embodiment of the deduction control method of the present application;
  • FIG. 3 is a schematic diagram of a device structure of a hardware operating environment involved in the method of an embodiment of the present application
  • FIG. 4 is a schematic flowchart of the deduction control device of the present application.
  • the present application provides a deduction control method.
  • the deduction control method is applied to a collection system.
  • the collection system includes a plurality of distributed distributions.
  • the charge control method includes:
  • Step S10 When receiving the deduction request, determine the target server end of the deduction request according to the current number of pending requests of the multiple server ends;
  • Step S20 Perform a lock processing on the deduction request, and send the deduction request after the lock processing to the target server side for the target server side to process the deduction after the lock processing Request the corresponding user account to perform the pre-stored deduction operation.
  • Step S10 When receiving the deduction request, determine the target server end of the deduction request according to the current number of pending requests of the multiple server ends;
  • the deduction control method is applied to a collection system, and the collection system includes a plurality of distributed server ends, each of which has a function of processing a deduction request, in which When a chargeback request is made, the multiple server ends may compete to process the chargeback request.
  • the specific competition method may be: determining the target server end of the chargeback request according to the current number of pending requests of the multiple server ends, and the server end The smaller the current number of pending requests, the greater the competitiveness, and the greater the current number of pending requests on the server, the lower the competitiveness.
  • the specific competition method may also be: determined according to the processing speed or processing capacity of the server Specifically, the better the configuration performance on the server side, the higher the processing speed or processing capacity on the server side, and the higher the processing speed or processing capacity on the server side, the greater the competitiveness of the server side, and the more likely it is to compete to get a deduction request.
  • the collection system After receiving the deduction request, the collection system determines the target server side through the above-mentioned competitive manner, and needs to send the deduction request to the target server side.
  • Step S20 Perform a lock processing on the deduction request, and send the deduction request after the lock processing to the target server side for the target server side to process the deduction after the lock processing Request the corresponding user account to perform the pre-stored deduction operation.
  • the lock processing is performed on the deduction request, where the lock processing on the deduction request includes the following two methods:
  • Method 1 Send the deduction request to the cache subsystem in the collection system, and lock the deduction request in the cache subsystem. After the lock processing is completed, send the deduction request after the lock to the target server end;
  • Method 2 Send the deduction request directly to the target server, and lock the deduction request on the target server.
  • the deduction request is locked, the account number of the client corresponding to the deduction request is synchronized and locked, that is, the deduction request is When locking, the user account cannot be used for other deduction operations, which will be described in specific embodiments.
  • the bank payment code is scanned twice in succession to generate two corresponding
  • the other payment request cannot be synchronously locked because the bank account already has a locked record.
  • the lock deduction request is sent to the target server for the target server to correspond to the user account corresponding to the lock deduction request Perform pre-stored deductions.
  • the target server performs corresponding pre-stored deduction operation steps corresponding to the user account corresponding to the deduction request after the lock processing includes: obtaining the deduction amount carried in the deduction request, the deduction account number, and the deduction agreement, Based on the deduction amount, deduction account number and deduction agreement, request a deduction from the bank.
  • an operation log file is generated.
  • the operation log file may be based on a NOSQL (non-relational) memory database Redis, and Using Redis' persistent storage.
  • Redis-based persistent storage AOF mode When receiving a debit request, Redis-based persistent storage AOF mode will "operate + "Data" is appended to the end of the corresponding operation log file in the form of formatting instructions, that is, as soon as the deduction request is received, the processing flow steps of the deduction request and the data obtained in the processing flow steps are written Into the log file, all historical operation processes are saved in the log file. Therefore, when data recovery is required, all operation processes can be restored according to the log file. Avoid various losses caused by the failure to find the deduction record.
  • the locked deduction request when it is detected that the deduction request is locked, the locked deduction request is permanently stored in the Redis database in real time.
  • the target server side of the deduction request is determined according to the current number of pending requests of the multiple servers; the lock request is processed to lock the deduction request
  • the processed deduction request is sent to the target server side for the target server side to perform a pre-stored deduction operation corresponding to the user account corresponding to the locked deduction request.
  • the client corresponding to the deduction request is locked synchronously, Therefore, if there is another deduction request that is synchronized with the deduction request, the other deduction request will be abandoned and not processed. Therefore, repeated deductions can be avoided and the user experience can be improved, thereby solving the problem that the existing bank debits Technical issues that are easy to debit and affect user experience.
  • the step of locking the deduction request includes:
  • Step S21 calling a pre-stored concurrency control program segment to intercept the deduction request
  • the concurrency control program segment is pre-stored in the collection system, and the DistributedLockAspect class is pre-stored in the concurrency control program segment.
  • the DistributedLockAspect class mainly encapsulates the implementation logic of the Redis distributed lock, so as to realize the locking processing of the deduction request, specifically ,
  • the DistributedLockAspect class uses the lock and unlock methods for concurrent lock control.
  • the specific implementation process of the DistributedLockAspect class program is: define "method annotation @Lock" and "parameter annotation @ParamLock", that is, use Spring annotation @Aspect to customize a distributed
  • the lock dynamic proxy class namely the DistributedLockAspect class, implements concurrency control.
  • the concurrency control program segment can intercept the deduction request when the target server side that detects the deduction request is determined. The purpose of intercepting the deduction request is to Debit requests are locked.
  • Step S22 Lock the deduction request based on the distributed lock method provided by the Redis database.
  • the debit request is locked based on the distributed locking method provided by the Redis database.
  • the step of locking the deduction request based on the distributed locking method provided by the Redis database includes:
  • Step S221 Obtain the user account corresponding to the deduction request, the IP address of the target server, and the preset lock timeout time;
  • the deduction request carries the user account, the IP address of the target server side and the preset lock time, so the corresponding user account, the IP address of the target server side and the preset can be extracted from the deduction request Lock over time.
  • Step S222 Based on the Redis database, set the user account and the preset prefix to the first parameter content of the first parameter key pre-stored in the distributed locking mode, and set the IP address of the target server to the distributed locking mode Pre-store the second parameter content of the second parameter value, and set the preset lock overtime as the third parameter content of the third parameter second pre-stored in the distributed locking mode to obtain the target corresponding to the deduction request lock;
  • the specific locking process is set using the setnx (key, value, second) method provided by Redis, where key is the first parameter, value is the second parameter, and second is the third parameter.
  • the user account And the preset prefix are set as the first parameter content of the first parameter key pre-stored in the distributed locking method, for example, the prefix “LOCK_KEY_ACCT_” + user account is used as the first parameter content, and the IP address of the target server is set to be distributed
  • the second parameter content of the second parameter value is pre-stored in the lock mode, in particular, the IP address of the target server and the current setting time are set as the second parameter content of the pre-stored second parameter value in the distributed lock mode, For example, taking "node IP (target server) ******" + current system time as the second parameter content, the preset lock timeout time is set to the third parameter second pre-stored in the distributed locking method
  • the content of the third parameter for example, the lock timeout time may be set to 180 seconds, and the content of the third
  • Step S223 Perform verification processing on the target lock to determine whether a preset return value is received
  • Step S224 if the preset return value is received, it is determined that the deduction request is successfully locked.
  • setnx if setnx returns the preset return value or returns true, it means that the lock is successful, and the charge operation can be performed. If setnx does not return the preset return value and does not return true, it means that the lock fails.
  • Step S225 Store the deduction request after successful locking in the Redis database, and regularly scan each deduction request after locking processing stored in the Redis database;
  • the deduction request after successful locking is stored in the Redis database, and after the deduction request after locking processing is sent to the target server, the target server will process the deduction after locking Request, because the target server may be under maintenance, or the target server may not be working properly, the target server may not be able to complete the deduction operation.
  • the compensation mechanism includes: the collection system starts the pre-stored JAVAJOB (timed task), and regularly scans the deduction request after locking processing saved in Redis.
  • the "node IP (target server) ******" + current system time is used as the second parameter, it is possible to obtain the storage time of the deduction request after the lock processing in the Redis database.
  • the storage time of the deduction request after lock processing in the Redis database is greater than the lock timeout time, if the storage time is greater than 180 seconds (lock timeout time), it will be unlocked immediately to release the locked resources to ensure that the account is not locked abnormally The operation is executed smoothly.
  • the lock can be released after the deduction is successful, that is, after the deduction is successful, the user account corresponding to the deduction request is not locked to avoid affecting the client's next deduction operation.
  • the IP address of the target server and the preset lock timeout time are set to distributed locking
  • the first parameter content of the first parameter key is pre-stored in the mode
  • the IP address of the target server is set to the second parameter content of the second parameter value pre-stored in the distributed locking mode
  • the preset lock overtime is set
  • Pre-store the third parameter content of the third parameter second in the distributed lock mode to obtain the target lock corresponding to the deduction request; verify the target lock to determine whether a preset return value is received; if received When the preset return value is reached, it is determined that the deduction request is successfully locked.
  • the lock processing for the deduction request is implemented, which lays the foundation for avoiding repeated deductions.
  • the present application provides another embodiment of a deduction control method.
  • the deduction request after the lock processing is sent to the target server side for the target server side
  • After performing the pre-stored deduction operation steps corresponding to the user account corresponding to the deduction request after the lock processing includes:
  • step A1 if it is detected that the client server corresponding to the deduction request after the lock processing is successfully debited by the target server, the deduction request corresponding to the successful deduction is unlocked.
  • the deduction request corresponding to the successful deduction is unlocked. That is, in this embodiment, as long as the deduction is successful, it is unlocked to avoid affecting the client's subsequent non-simultaneous deduction operation.
  • the charge control method further includes:
  • Step B1 if it is detected that an unlocking completion instruction of the deduction request has been unlocked, obtain the unlocking type of the deduction request based on the unlocking completion instruction;
  • the unlock type of the deduction request is obtained based on the unlock completion instruction, where the unlock type includes an active unlock type and a passive unlock type,
  • the active unlocking type refers to unlocking after successful deduction
  • the passive unlocking type refers to unlocking unprocessed locked deduction requests after the lock timeout time is reached.
  • Step B2 if the unlocking type is an active unlocking type, it is determined to generate the first prompt message of successful deduction;
  • Step B3 if the unlocking type is a passive unlocking type, it is determined to generate a second prompt message that the deduction has failed.
  • the unlocking type is an active unlocking type, it is determined that the first prompt information of successful deduction is generated, and if the unlocking type is a passive unlocking type, it is determined that a second prompting information of the deduction failure is generated.
  • the prompt content and the prompt method of the first prompt information and the second prompt information are different to distinguish whether the prompt deduction is successful.
  • the unlocking type of the deduction request is obtained based on the unlocking completion instruction; if the unlocking type is an active unlocking type, it is determined to generate The first prompt message of successful payment deduction; if the unlock type is a passive unlock type, it is determined that the second prompt message of failed payment deduction is generated.
  • the unlocking type is a passive unlock type, it is determined that the second prompt message of failed payment deduction is generated.
  • differentiate between prompting active unlocking and passive unlocking to obtain a more effective prompting effect and improve user experience.
  • FIG. 3 is a schematic diagram of a device structure of a hardware operating environment involved in a solution of an embodiment of the present application.
  • the deduction control device in the embodiment of the present application may be a PC, or may be a smartphone, tablet computer, e-book reader, MP3 (Moving Picture Experts Group Audio Layer III, motion picture expert compression standard audio layer 3 player, MP4 (Moving Picture Experts Group Audio Layer IV, the standard audio layer for motion picture experts compression 3) Terminal devices such as players and portable computers.
  • MP3 Moving Picture Experts Group Audio Layer III, motion picture expert compression standard audio layer 3 player
  • MP4 Moving Picture Experts Group Audio Layer IV, the standard audio layer for motion picture experts compression 3
  • Terminal devices such as players and portable computers.
  • the charge control device may include: a processor 1001, such as a CPU, a memory 1005, and a communication bus 1002.
  • the communication bus 1002 is used to implement connection communication between the processor 1001 and the memory 1005.
  • the memory 1005 may be a high-speed RAM memory or a stable memory (non-volatile memory), such as disk storage.
  • the memory 1005 may optionally be a storage device independent of the foregoing processor 1001.
  • the charge control device may further include a target user interface, a network interface, a camera, and RF (Radio Frequency (radio frequency) circuits, sensors, audio circuits, WiFi modules, etc.
  • the target user interface may include a display (Display), an input unit such as a keyboard (Keyboard), and the optional target user interface may also include a standard wired interface and a wireless interface.
  • the network interface may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface).
  • the structure of the charge control device shown in FIG. 3 does not constitute a limitation on the charge control device, and may include more or less components than the illustration, or a combination of certain components, or different Parts arrangement.
  • the memory 1005 which is a computer storage medium, may include an operating system, a network communication module, and readable instructions for charge control.
  • the operating system is a program that manages and controls the hardware and software resources of the charge control device, and supports the operation of the charge control readable instructions and other software and / or programs.
  • the network communication module is used to implement communication between various components within the memory 1005 and other hardware and software in the charge control device.
  • the processor 1001 is used to execute the charge control readable instructions stored in the memory 1005 to implement the steps of any of the charge control methods described above.
  • the charge control device includes:
  • a receiving module configured to determine the target server side of the deduction request according to the current number of pending requests of the multiple server sides when receiving the deduction request;
  • a locking module configured to perform a locking process on the deduction request, and send the deduction request after the locking process to the target server side, so that the target server side
  • the user account corresponding to the deduction request corresponds to the execution of the pre-stored deduction operation.
  • the locking module includes:
  • a calling unit used to call a pre-stored concurrency control program segment to intercept the deduction request
  • the locking unit is used for locking the deduction request based on the distributed locking method provided by the Redis database.
  • the present application provides a readable storage medium that stores one or more computer-readable instructions, and the one or more computer-readable instructions may also be executed by one or more processors to Steps for realizing any of the deduction control methods described above.
  • the readable storage medium may be a non-volatile readable storage medium.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Technology Law (AREA)
  • Marketing (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Transfer Between Computers (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention concerne un procédé, un appareil et un dispositif de commande de déduction d'argent, et un support d'informations lisible.
PCT/CN2018/123190 2018-11-20 2018-12-24 Procédé, appareil et dispositif de commande de déduction d'argent, support d'informations lisible WO2020103275A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811394571.2 2018-11-20
CN201811394571.2A CN109670807A (zh) 2018-11-20 2018-11-20 扣款控制方法、装置、设备及可读存储介质

Publications (1)

Publication Number Publication Date
WO2020103275A1 true WO2020103275A1 (fr) 2020-05-28

Family

ID=66142706

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/123190 WO2020103275A1 (fr) 2018-11-20 2018-12-24 Procédé, appareil et dispositif de commande de déduction d'argent, support d'informations lisible

Country Status (2)

Country Link
CN (1) CN109670807A (fr)
WO (1) WO2020103275A1 (fr)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111324622A (zh) * 2020-02-20 2020-06-23 中国建设银行股份有限公司 一种资源抢购的处理方法、装置、设备及存储介质
CN111459963B (zh) * 2020-04-07 2024-03-15 中国建设银行股份有限公司 核心账务交易并发处理方法及装置
CN113593127B (zh) * 2020-04-30 2023-09-29 海南掌上能量传媒有限公司 一种移动电源租赁终端的控制方法
CN111833034B (zh) * 2020-07-02 2024-01-30 泰康保险集团股份有限公司 一种批量扣款方法、支付服务器、计算机设备及存储介质
CN112565467A (zh) * 2021-02-22 2021-03-26 常州微亿智造科技有限公司 业务处理方法、装置和存储介质
CN113516471B (zh) * 2021-07-07 2023-12-05 深圳市雪球科技有限公司 公交付费的方法、装置和设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103581273A (zh) * 2012-08-08 2014-02-12 阿里巴巴集团控股有限公司 一种分布式***执行业务的方法、装置及***
CN107358425A (zh) * 2017-06-29 2017-11-17 湖南搜云网络科技股份有限公司 交易费用的计算及支付方法和装置、交易平台及存储介质
CN107767140A (zh) * 2017-10-02 2018-03-06 头等尝网络餐饮管理科技（深圳）有限公司 支付方法、装置、设备及可读存储介质
CN107808285A (zh) * 2017-09-28 2018-03-16 深圳市生银万国网络科技有限公司 一种支付方法、设备及计算机可读存储介质
CN107818018A (zh) * 2016-09-14 2018-03-20 北京京东尚科信息技术有限公司 分布式锁的控制方法和装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103793843B (zh) * 2012-10-26 2017-10-13 阿里巴巴集团控股有限公司 一种账户数据的处理方法和装置
CN105988862B (zh) * 2015-02-04 2019-06-21 阿里巴巴集团控股有限公司 分布式事务处理方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103581273A (zh) * 2012-08-08 2014-02-12 阿里巴巴集团控股有限公司 一种分布式***执行业务的方法、装置及***
CN107818018A (zh) * 2016-09-14 2018-03-20 北京京东尚科信息技术有限公司 分布式锁的控制方法和装置
CN107358425A (zh) * 2017-06-29 2017-11-17 湖南搜云网络科技股份有限公司 交易费用的计算及支付方法和装置、交易平台及存储介质
CN107808285A (zh) * 2017-09-28 2018-03-16 深圳市生银万国网络科技有限公司 一种支付方法、设备及计算机可读存储介质
CN107767140A (zh) * 2017-10-02 2018-03-06 头等尝网络餐饮管理科技（深圳）有限公司 支付方法、装置、设备及可读存储介质

Also Published As

Publication number Publication date
CN109670807A (zh) 2019-04-23

Similar Documents

Publication Publication Date Title
WO2020103275A1 (fr) Procédé, appareil et dispositif de commande de déduction d'argent, support d'informations lisible
WO2019144738A1 (fr) Procédé de vérification de service financier, appareil et dispositif, et support d'informations informatique
WO2016137307A1 (fr) Attestation par mandataire
WO2020006852A1 (fr) Procédé, appareil et dispositif de traitement de vérification de remboursement de frais de déplacement en libre-service et support de stockage informatique
WO2020253135A1 (fr) Procédé et dispositif d'analyse automatique, équipement utilisateur et support de stockage
WO2020062642A1 (fr) Procédé, dispositif et équipement à base de chaîne de blocs pour signer des documents électroniques, et support d'informations
WO2017067293A1 (fr) Procédé et dispositif de déverrouillage par empreinte digitale, et terminal
WO2016169410A1 (fr) Procédé et dispositif d'ouverture de session, serveur et système d'ouverture de session
WO2020147383A1 (fr) Procédé, dispositif et système d'examen et d'approbation de processus utilisant un système de chaîne de blocs, et support de stockage non volatil
WO2020215681A1 (fr) Procédé et appareil de génération d'informations d'indication, terminal et support de stockage
WO2020107591A1 (fr) Procédé, appareil, dispositif de limitation de double assurance et support d'informations lisible
WO2021072881A1 (fr) Procédé, appareil et dispositif de traitement de demande fondée sur un stockage d'objet, et support de stockage
WO2013004065A1 (fr) Procédé et système de sécurité d'informations basés sur une acquisition d'image
WO2018233352A1 (fr) Procédé de transmission de données, dispositif, terminal, et support de stockage lisible par ordinateur
WO2020253131A1 (fr) Procédé, appareil et dispositif de paiement par carte bancaire, et support de stockage informatique
WO2018076844A1 (fr) Procédé et dispositif de copie de sauvegarde de données, support de stockage et appareil électronique
WO2018076865A1 (fr) Procédé, dispositif, support d'informations et dispositif électronique de partage de données
WO2020087981A1 (fr) Procédé et appareil de génération de modèle d'audit de contrôle de risque, dispositif, et support de stockage lisible
WO2020147385A1 (fr) Procédé et appareil d'entrée de données, terminal et support d'informations lisible par ordinateur
WO2020233073A1 (fr) Procédé, dispositif et appareil de traitement de test d'environnement de chaîne de blocs, et support de stockage
WO2020042464A1 (fr) Procédé, appareil et dispositif d'interaction de données, et support d'informations lisible
WO2018035929A1 (fr) Procédé et appareil de traitement de code de vérification
WO2020233060A1 (fr) Procédé et appareil de notification d'événement, serveur de notification d'événement et support de stockage
WO2020206899A1 (fr) Procédé, appareil et dispositif de vérification d'identité basée sur un horodatage, et support d'informations
WO2020077832A1 (fr) Procédé, appareil et dispositif d'accès à un bureau dans le nuage et support de stockage

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: 18940638

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: 18940638

Country of ref document: EP

Kind code of ref document: A1