WO2020034719A1 - 收款控制方法、装置、服务器及可读存储介质 - Google Patents

收款控制方法、装置、服务器及可读存储介质 Download PDF

Info

Publication number
WO2020034719A1
WO2020034719A1 PCT/CN2019/089036 CN2019089036W WO2020034719A1 WO 2020034719 A1 WO2020034719 A1 WO 2020034719A1 CN 2019089036 W CN2019089036 W CN 2019089036W WO 2020034719 A1 WO2020034719 A1 WO 2020034719A1
Authority
WO
WIPO (PCT)
Prior art keywords
friend
user
click
equalized
friends
Prior art date
Application number
PCT/CN2019/089036
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 阿里巴巴集团控股有限公司
Priority to SG11202010617RA priority Critical patent/SG11202010617RA/en
Priority to EP19850319.5A priority patent/EP3800603A4/en
Publication of WO2020034719A1 publication Critical patent/WO2020034719A1/zh
Priority to US17/086,192 priority patent/US11200547B2/en

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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02—Banking, e.g. interest calculation or account maintenance
    • 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/102—Bill distribution or payments
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/903—Querying
    • G06F16/9035—Filtering based on additional data, e.g. user or group profiles
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/903—Querying
    • G06F16/9038—Presentation of query results
    • 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/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • G06Q20/0655—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash e-cash managed centrally
    • 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/16—Payments settled via telecommunication 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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/326—Payment applications installed on the mobile devices
    • 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/386—Payment protocols; Details thereof using messaging services or messaging apps
    • 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
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0279—Fundraising management
    • 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
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/01—Social networking

Definitions

  • the embodiments of the present specification relate to the field of Internet technologies, and in particular, to a method, device, server, and readable storage medium for controlling receipts.
  • the embodiments of the present specification provide and a payment control method, device, server and readable storage medium.
  • an embodiment of the present specification provides a collection control method for controlling the selection of friends who share the collection, the method includes:
  • the one-click equalized friend list matches the friend of the current collection order, and if it matches, the collection is initiated; if it does not match, the friend is adjusted and the collection is initiated.
  • an embodiment of the present specification provides a collection control device for controlling the selection of friends for sharing payment, the device includes a sharing payment determination unit, a one-click sharing friend calling unit, a sharing friend adjustment unit, and Collection unit; of which:
  • the equalized receivable determination unit is configured to obtain an equalized receivable order initiated by a user and determine the number of receivables;
  • the one-click sharing friend calling unit is configured to determine that when a user calls one-click sharing friend, a one-click sharing friend list corresponding to the number of payees is generated, and based on the user's historical average sharing within a preset time period Collect and analyze user behavior cumulative data to determine the one-click spread friend list;
  • the equalized friend adjustment unit is configured to determine whether the one-click equalized friend list matches a friend of the current collection order by interacting with the user, and if it matches, instructs the collection unit to initiate collection, if not, , After adjusting the friend, instruct the collection unit to initiate collection.
  • an embodiment of the present specification provides a server, including a memory, a processor, and a computer program stored on the memory and executable on the processor.
  • a server including a memory, a processor, and a computer program stored on the memory and executable on the processor.
  • the processor executes the program, any one of the foregoing is implemented. Method steps.
  • an embodiment of the present specification provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the steps of the method described in any one of the foregoing are implemented.
  • the collection control method provided in the embodiment of this specification considers that in actual situations, the user's friends who receive AA payments each time have a high degree of similarity. In order to avoid the user manually selecting AA friends repeatedly, a large amount of data is automatically collected and analyzed based on big data collection and analysis.
  • the key AA is for users to choose, which can quickly determine AA friends, improve the efficiency and accuracy of AA collection, and improve the user experience.
  • the friend list is also optimized based on friend AA participation, so that users can quickly find AA friends.
  • FIG. 1 is a schematic diagram of a scenario of a collection control method according to an embodiment of the present specification
  • FIG. 2 is a flowchart of a method for controlling receipts provided by the first aspect of the embodiment of the present specification
  • FIG. 3 is a flowchart of an example of a payment control method provided by the first aspect of the embodiment of the present specification
  • FIG. 4 is a flow chart of one-click sharing among friends in an example of a collection control method provided by the first aspect of the embodiment of the specification;
  • FIG. 5 is a flowchart of generating an optimized address book in an example of a payment control method provided by the first aspect of the embodiment of the present specification
  • FIG. 6 is a schematic structural diagram of a payment control device according to a second aspect of the embodiment of the present specification.
  • FIG. 7 is a schematic structural diagram of a server according to a third aspect of the embodiment of the present specification.
  • FIG. 1 is a schematic diagram of a payment control method according to an embodiment of the present specification.
  • the scenario includes a collection operation platform 10 and a collection control platform 20.
  • the payment operation platform 10 may be a platform provided by various financial APPs or instant tool APPs. It can be understood that the payment operation platform 10 is generally located on a user terminal (such as a smartphone or a pad).
  • the collection control platform 20 refers to a module that controls the collection operation platform 10, and may be integrated in a financial APP or an instant tool APP (that is, also located in a user terminal), or may be located on a server side.
  • the per capita cost-sharing collection (equal collection collection, AA collection) is controlled, that is, the collection control platform 20 quickly matches the collection operation platform 10 to the selection of the sharing friends, thereby Improve the efficiency of the entire collection.
  • an embodiment of the present specification provides a collection control method for controlling the selection of friends who share the collection, please refer to FIG. 2, including:
  • S201 Obtain an equalized collection order initiated by a user, and determine the number of recipients.
  • AA collection which means that the individual needs to share the expenses equally, is also called equalized collection in the embodiments of this specification. For example, a few friends traveling together and sharing the travel expenses after the trip is a typical example of AA system.
  • S202 Determine whether the user chooses to call the one-click spread friend, and if so, generate a one-click spread friend list corresponding to the number of payees, wherein the accumulated data of user behavior is performed based on the user's historical equal pay collection orders within a preset period of time. Collect and analyze to determine your friend list with one click.
  • a function of “one-click sharing friends” is added to the payment control platform 20 (see FIG. 1), and the user does not need to manually add AA friends one by one, but can call AA friends by one button.
  • One-click equalizing friends refers to a one-click equalizing friend list that is collected and analyzed based on the user's historical equalizing payment collection orders within a preset period of time, and collecting and analyzing user behavior cumulative data.
  • the most likely 5 friends (such as friends A, B, C, D, E), as the one-click sharing friend list.
  • S203 By interacting with the user, it is determined whether the one-click spread friends list matches the friends of the current collection order. If they match, the collection is initiated; if they do not match, the friends are adjusted to initiate collection.
  • the user After determining the one-click spread friend list, the user is required to confirm whether it is consistent with the actual situation. If the one-click spread friends list matches the friends in this collection order, the collection is initiated. If it does not match, the friends need to be adjusted to match before the collection is initiated.
  • the user manually deletes mismatched friends, and then shows the user a manual adjustment interface (optimized address book), and the user adds missing friends from the optimized address book.
  • the one-click shared friend list includes friends A, B, C, D, and E.
  • the user After the user confirms that the friend B does not match, the user first deletes friend B and then selects another friend from the optimized contact list, such as friend F Then the final sharing friends include A, C, D, E, F.
  • one-click sharing friends can also be regenerated.
  • the re-generated one-click sharing friends are obtained by adjusting the priority of friends in the one-click sharing friend list. For example, in general, when a one-click equalized friend is generated, it is determined according to the statistics of the equalized participation of each friend in the user ’s historical equalized collection order. That is, which friend has a high equalized participation (frequency of participation in AA), the friend High priority. However, in actual situations, there may be situations where the equalized participation of two or more friends is very close or not much different. In this case, the friend priority can be adjusted to generate a one-click equalized friend that is different from the previous one.
  • the first-time shared friend list includes friends A, B, C, D, and E
  • the second-time shared friend list generated by readjusting friend priorities is, for example, friends A, C, D, and E. , F.
  • the traditional friend address book is optimized, which is called an optimized address book.
  • the optimized contact list is obtained based on the participation of friends in AA collection. For example, based on the user's historical equalized collection payment orders within a preset period of time, the user's behavioral cumulative data is collected and analyzed to determine the order of optimization of each friend in the contact list.
  • the optimized address book may be displayed to the user, and each friend selected by the user in the optimized address book is determined to be the friend of the collection order. Because the optimized contact list sorts friends based on AA receipt participation, users can quickly find AA receipt recipients.
  • FIG. 3 a flowchart of an example of a payment control method according to the first aspect of the embodiment of the present specification is shown.
  • each step of AA collection is given in detail, and the implementation process of one-click equalizing friends and optimizing contacts is introduced in detail.
  • Figure 3 includes the following steps:
  • S301 The user enters the APP and selects AA payment.
  • S302 The user fills in the relevant information of the AA collection order, such as the total amount, the total number of people, the reason for the collection, etc.
  • the number of collections filled by the user includes the user himself, which is convenient for calculating the average cost, and the invention is implemented
  • the number of recipients in the example does not include the user himself.
  • S303 Generate an AA collection order (receipt QR code), mainly to determine the average cost, for example, divide the total amount by the total number of people to obtain the average cost.
  • the AA method includes scanning the code AA and the friend AA. Scanning the code AA allows each friend to scan the payment QR code in person to complete the payment.
  • the friend AA is the embodiment of this manual.
  • the discussed method of determining friends, this method does not require every friend to be around the user, and is especially suitable for situations where friends are not present. Scanning code AA executes S305; friend AA executes S306.
  • S308 Determine whether the one-click AA friend list matches the actual AA friend list. If they match, execute S309; if they do not match, execute S310.
  • S310 Choose to adjust friends manually or automatically? If it is adjusted manually, execute S311; if it is adjusted automatically, return to execute S307, and regenerate the one-click AA friend list.
  • User behavior accumulation in short, is to record the daily behavior of users; take AA payment as an example, every time a user initiates AA payment, then in the wide table, the user "I" is the main user. The number of AA receipts is +1, and the participating objects of AA are called “cumulative objects". Each time the user gives one of his friends A, the "I" as the subject and the accumulated data of A as the object will be +1
  • the user sent an AA 2 days ago the target is A / B / C / D / E / F / G / H
  • the cumulative number of each accumulation object and the most recent accumulation time here can become an important indicator for judging the closeness of this object and related subjects. Based on this, a variety of variables can be added to limit the accumulation subject, accumulation object, accumulation time, accumulation method, etc., and finally form a complete set of big data user behavior accumulation system.
  • S401 Collect and analyze user behavior cumulative data to obtain a user's average friend information accumulation table (for example, the aforementioned Table 1).
  • S402 Based on the accumulated friend information accumulation table, whether it is possible to determine the maximum number of probable equalization objects exceeding a predetermined probability threshold, if yes, execute S403; otherwise, execute S405.
  • the largest AA in the AA combination that exceeds 50% (predetermined probability threshold) is a 5-person combination, and the maximum probability of the average number of objects is 5. If the AA combination has not exceeded 50% (predetermined probability threshold) of the AA combination in the last 30 days, S405 is performed.
  • S403 Determine whether the maximum number of equalized objects is consistent with the number of people receiving the order. If they are the same, execute S404; if they are not, execute S405.
  • the current number of AA sponsors is 8; this indicates that the numbers do not match; if the current number of AA sponsors is also 5 , It means that the number of people matches, then the five-person combination is executed as a one-click sharing friend list.
  • S404 Generate a one-click shared friend list based on each object corresponding to the maximum number of shared objects.
  • S405 Calculate the equalized participation of each friend in the equalized information accumulation table, and select the friends who are consistent with the number of beneficiaries of this order according to the equalized participation, as a one-click equalized friend list.
  • S501 Query the collection of AA collection objects for a period of time (for example, 90 days);
  • the execution order of S502-S504 is not limited.
  • S506 Sort the friends in the address book according to AA participation.
  • the AA collection information object output to the user is A / B / C / D / E;
  • the collection control method provided in the embodiment of this specification considers that in actual situations, the user's friends who receive AA payments each time have a high degree of similarity.
  • automatic Generate one-key AA for users to choose which can quickly determine AA friends, improve the efficiency and accuracy of AA collection, and improve user experience.
  • the friend list is also optimized based on friend AA participation, so that users can quickly find AA friends.
  • an embodiment of the present specification provides a payment control device. Please refer to FIG. 6, which includes: an average payment determination unit 601, a one-click average friend calling unit 602, an average friend adjustment unit 603, and a collection account. Section 604; of which:
  • the equalized receivable determination unit 601 is configured to obtain an equalized receivable order initiated by a user and determine the number of receivables;
  • the one-click equalizing friend calling unit 602 is configured to determine that when a user calls one-click equalizing friends, a one-click equalizing friend list corresponding to the number of payees is generated, and based on the historical equalization of the users within a preset time period Collection order, collecting and analyzing accumulated data of user behavior, and determining the one-click spread friend list;
  • the equalized friend adjustment unit 603 is configured to determine whether the one-click equalized friend list matches the friends of the current collection order by interacting with the user. If they match, instruct the collection unit 604 to initiate collection. If they do not match, the friend is instructed to initiate payment collection after adjusting the friend.
  • the apparatus further includes:
  • the optimized address book calling unit 605 is used to determine when the user has not selected to call the one-click sharing friend, the optimized address book is displayed to the user, wherein the user's behavior is accumulated based on the historical average payment collection order of the user within a preset time period. Perform collection and analysis to determine the order of the friends in the optimized address book; and determine that each friend selected by the user in the optimized address book is the friend of the collection order.
  • the equalized friend adjustment unit 603 is specifically configured to: based on the one-click equalized friend, display a manual adjustment interface to the user, and obtain the user's manually adjusted friend.
  • the sharing friend adjustment unit 603 displays the optimized address book to the user as the manual adjustment interface.
  • the equalized friend adjustment unit 603 is specifically configured to: regenerate a one-click equalized friend, wherein the regenerated one-click equalized friend is to adjust the priority of friends in the one-click equalized friend list owned.
  • the equalized friend adjustment unit 603 is further configured to determine, through interaction with the user, whether the current one-click equalized friend list matches the friend of the current collection order, and if it matches, instruct the receiving The payment unit 604 initiates payment collection. If there is no match, it determines whether to generate a one-click spread friend, or the user manually adjusts the friend, or selects a friend based on the optimized address book until the friend matches successfully.
  • the method further includes: one-click sharing friend generation unit 606;
  • the one-click sharing friend generation unit 606 includes:
  • a data analysis sub-unit 6061 configured to collect and analyze cumulative data of user behaviors to obtain a user's shared friend information accumulation table
  • a maximum probability equalization object number determination subunit 6062 configured to determine, based on the equalization friend information accumulation table, a maximum probability equalization number of objects that exceeds a predetermined probability threshold;
  • a judging subunit 6063 configured to judge whether the maximum number of equalized target persons is consistent with the number of people receiving the order
  • One-click equalizing buddy list determination subunit 6064 If the maximum number of equalized number of objects is consistent with the number of recipients of this order, the one-click equalized number of friends is generated based on each object corresponding to the maximum number of equalized number of objects List, if they are inconsistent, then statistics the equalized participation of each friend in the equalized information accumulation table, and selects the friends who are consistent with the number of beneficiaries of this order according to the equalized participation, as the one key Share your friends list.
  • the method further includes: an address book optimization unit 607, configured to collect and analyze user behavior cumulative data to obtain a user's shared friend information accumulation table; and collect statistics on the shared information accumulation table
  • an address book optimization unit 607 configured to collect and analyze user behavior cumulative data to obtain a user's shared friend information accumulation table; and collect statistics on the shared information accumulation table The equalized participation of each friend, and the arrangement order of each friend in the optimized address book is determined according to the averaged participation from high to low.
  • the present invention also provides a server, as shown in FIG. 7, including a memory 704, a processor 702, and stored in the memory 704 and can be processed.
  • a server as shown in FIG. 7, including a memory 704, a processor 702, and stored in the memory 704 and can be processed.
  • a computer program running on the processor 702, and when the processor 702 executes the program, the steps of the method for controlling payment collection described above are implemented.
  • the bus architecture (represented by the bus 700).
  • the bus 700 may include any number of interconnected buses and bridges.
  • the bus 700 will include one or more processors represented by the processor 702 and memory 704.
  • the various circuits of the memory are linked together.
  • the bus 700 can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, they will not be further described herein.
  • the bus interface 706 provides an interface between the bus 700 and the receiver 701 and the transmitter 703.
  • the receiver 701 and the transmitter 703 may be the same element, that is, a transceiver, providing a unit for communicating with various other devices on a transmission medium.
  • the processor 702 is responsible for managing the bus 700 and general processing, and the memory 704 can be used to store data used by the processor 702 when performing operations.
  • the present invention also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the aforementioned payment is realized Control method steps.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to work in a particular manner such that the instructions stored in the computer-readable memory produce a manufactured article including the instruction device, the instructions
  • the device implements the functions specified in one or more flowcharts and / or one or more blocks of the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing device, so that a series of steps can be performed on the computer or other programmable device to produce a computer-implemented process, which can be executed on the computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Databases & Information Systems (AREA)
  • Marketing (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Computational Linguistics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Tourism & Hospitality (AREA)
  • Human Resources & Organizations (AREA)
  • Game Theory and Decision Science (AREA)
  • Technology Law (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本说明书实施例提供了一种收款控制方法，考虑了在实际情况中，用户每次均摊收款的好友相似度很高，为了避免用户重复手动选取均摊好友，根据大数据收集和分析，自动生成一键均摊好友供用户选择，可快速确定均摊好友，提高均摊收款的效率和准确性。

Description

收款控制方法、装置、服务器及可读存储介质 技术领域
本说明书实施例涉及互联网技术领域，尤其涉及一种收款控制方法、装置、服务器及可读存储介质。
背景技术
随着互联网金融的发展，网络收款越来越普及。如何对收款过程进行有效控制，是网络金融需要考虑的一个技术问题。
发明内容
本说明书实施例提供及一种支付控制方法、装置、服务器及可读存储介质。
第一方面，本说明书实施例提供一种收款控制方法，用于对均摊收款的好友选取进行控制，所述方法包括：
获取用户发起的均摊收款订单，确定收款人数；
确定用户是否选择调用一键均摊好友，如果是，生成与所述收款人数对应的一键均摊好友列表，其中，基于预置时间段内所述用户的历史均摊收款订单，对用户行为累积数据进行收集和分析，确定所述一键均摊好友列表；
通过与用户交互，确定所述一键均摊好友列表是否与本次收款订单的好友匹配，如果匹配，则发起收款，如果不匹配，则对好友进行调整后发起收款。
第二方面，本说明书实施例提供一种收款控制装置，用于对均摊收款的好友选取进行控制，所述装置包括均摊收款确定单元、一键均摊好友调用单元、均摊好友调整单元和收款单元；其中：
所述均摊收款确定单元，用于获取用户发起的均摊收款订单，确定收款人数；
所述一键均摊好友调用单元，用于确定用户调用一键均摊好友时，生成与所述收款人数对应的一键均摊好友列表，其中，基于预置时间段内所述用户的历史均摊收款订单，对用户行为累积数据进行收集和分析，确定所述一键均摊好友列表；
所述均摊好友调整单元，用于通过与用户交互，确定所述一键均摊好友列表是否与 本次收款订单的好友匹配，如果匹配，则指示所述收款单元发起收款，如果不匹配，则对好友进行调整后指示所述收款单元发起收款。
第三方面，本说明书实施例提供一种服务器，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现上述任一项所述方法的步骤。
第四方面，本说明书实施例提供一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现上述任一项所述方法的步骤。
本说明书实施例有益效果如下：
本说明书实施例提供的收款控制方法，考虑了在实际情况中，用户每次AA收款的好友相似度很高，为了避免用户重复手动选取AA好友，根据大数据收集和分析，自动生成一键AA供用户选择，可快速确定AA好友，提高AA收款的效率和准确性，提升用户体验。另外，也对好友列表基于好友AA参与度进行了优化，可方便用户快速查找到AA好友。
附图说明
图1为本说明书实施例收款控制方法场景示意图；
图2为本说明书实施例第一方面提供的收款控制方法流程图；
图3为本说明书实施例第一方面提供的收款控制方法实例流程图；
图4为本说明书实施例第一方面提供的收款控制方法实例中一键均摊好友生成流程图；
图5为本说明书实施例第一方面提供的收款控制方法实例中优化通讯录生成流程图；
图6为本说明书实施例第二方面提供的收款控制装置结构示意图；
图7为本说明书实施例第三方面提供的服务器结构示意图。
具体实施方式
为了更好的理解上述技术方案，下面通过附图以及具体实施例对本说明书实施例的技术方案做详细的说明，应当理解本说明书实施例以及实施例中的具体特征是对本说明书实施例技术方案的详细的说明，而不是对本说明书技术方案的限定，在不冲突的情况 下，本说明书实施例以及实施例中的技术特征可以相互组合。
参见图1，为本说明书实施例收款控制方法场景示意图。场景包括收款操作平台10和收款控制平台20。收款操作平台10可以是各金融类APP或即时工具APP提供的平台，可以理解，收款操作平台10一般是位于用户终端(例如智能手机或pad等)。收款控制平台20是指对收款操作平台10进行控制的模块，可以集成在金融类APP或即时工具APP(即也位于用户终端)，也可以位于服务器端。本发明实施例中，特别地，对人均分担费用收款(均摊收款、AA收款)进行控制，即，收款控制平台20对收款操作平台10在均摊好友选取上进行快速匹配，从而提高整个均摊收款的效率。
第一方面，本说明书实施例提供一种收款控制方法，用于对均摊收款的好友选取进行控制，请参考图2，包括：
S201：获取用户发起的均摊收款订单，确定收款人数。
AA收款，意思是个人平均分担所需费用，本说明书实施例中也称为均摊收款。例如，几个好友一起旅行，旅行结束后均摊旅费，是一个典型的AA制例子。
目前很多即时通讯或金融类APP提供AA收款功能，用户进入AA收款界面后，填写收款金额和收款人数(还可以备注收款理由/明细)，APP可自动计算出人均均摊费用，但是却不能自动确定出本次AA收款的好友。如果用户手动选取好友，则比较繁琐。
S202：确定用户是否选择调用一键均摊好友，如果是，生成与收款人数对应的一键均摊好友列表，其中，基于预置时间段内用户的历史均摊收款订单，对用户行为累积数据进行收集和分析，确定一键均摊好友列表。
本发明实施例中，在收款控制平台20(参见图1)增加“一键均摊好友”功能，用户无需手动一个个添加AA好友，而是可以一键调用AA好友。
一键均摊好友，是指基于预置时间段内用户的历史均摊收款订单，对用户行为累积数据进行收集和分析，确定出的与本次AA人数相一致的一键均摊好友列表。
例如，本次AA收款人数为5(不包括用户自己)，则可以根据近一个月该用户AA收款的数据分析，确定出最有可能的5个好友(例如好友A、B、C、D、E)，作为上述一键均摊好友列表。
S203：通过与用户交互，确定一键均摊好友列表是否与本次收款订单的好友匹配，如果匹配，则发起收款，如果不匹配，则对好友进行调整后发起收款。
在确定出一键均摊好友列表之后，需要用户确认是否与实际情况吻合。如果一键均摊好友列表与本次收款订单的好友匹配，则发起收款，如果不匹配，则需要对好友进行调整至匹配再发起收款。
其中，对好友进行调整的方式可以有多种。
例如，由用户手动删除不匹配好友，然后向用户展示手动调整界面(优化通讯录)，用户从优化通讯录中增加缺少的好友。例如上述一键均摊好友列表包括好友A、B、C、D、E，经过用户确认发现好友B不匹配，则用户首先删除好友B，然后从优化通讯录中选择另一个好友，例如好友F，则最终的均摊好友包括A、C、D、E、F。
再如，还可以重新生成一键均摊好友，其中，重新生成的一键均摊好友是对一键均摊好友列表中好友优先级进行调整得到的。例如，一般情况下，在生成一键均摊好友时，是根据统计用户历史均摊收款订单中各个好友的均摊参与度确定的，即，哪个好友均摊参与度(参与AA频率)高，则其好友优先级高。但是实际情况中，可能存在某两个或多个好友的均摊参与度非常接近或相差不大的情况，在这种情况下，可以调整好友优先级，生成与前一次不同的一键均摊好友。例如，如前所述的第一次生成的均摊好友列表包括好友A、B、C、D、E，重新调整好友优先级生成的第二次均摊好友列表例如为好友A、C、D、E、F。在重新生成一键均摊好友之后，通过与用户交互，确定当前一键均摊好友列表是否与本次收款订单的好友匹配，如果匹配，则发起收款，如果不匹配，则确定是否再次生成一键均摊好友，或者用户手动调整好友，或者基于优化通讯录进行好友选取，直至好友匹配成功。
本发明实施例中，对传统的好友通讯录进行优化，称为优化通讯录。该优化通讯录是根据好友参与AA收款参与度得到的。例如，基于预置时间段内用户的历史均摊收款订单，对用户行为累积数据进行收集和分析，确定优化通讯录中各好友的排列顺序。
在前述步骤S202中，如果用户没有选择调用一键均摊好友，则可以向用户显示优化通讯录，确定用户在优化通讯录中选取的各个好友为本次收款订单的好友。由于该优化通信录是根据AA收款参与度对好友进行排序的，可方便用户快速找到AA收款对象。
参见图3，为本说明书实施例第一方面提供的收款控制方法实例流程图。在该实例中，详细给出AA收款的每一个步骤，以及具体介绍了一键均摊好友及优化通讯录的实现过程。
图3包括如下步骤：
S301：用户进入APP选择AA收款。
S302：用户填写AA收款订单相关信息，例如填写总金额、总人数、收款理由等；其中，一般情况下，用户填写的收款人数包括用户自己，便于计算出均摊费用，而本发明实施例中的收款人数不包括用户自己。
S303：生成AA收款订单(收款二维码)，主要是确定均摊费用，例如，总金额除以总人数得到均摊费用。
S304：用户选择AA方式，例如，AA方式包括扫码AA和好友AA两种，扫码AA即让每个好友当面扫描收款二维码，即可完成收款；好友AA即本说明书实施例所讨论的确定好友的方式，这种方式无需每个好友都在用户身边，特别适合好友不在场的情况。扫码AA执行S305；好友AA执行S306。
S305：通过各个好友扫码完成AA收款，然后结束整个流程。
S306：是否一键AA(一键均摊好友)？如果是，执行S307分支，如果不是，执行S311分支。
S307：生成一键AA好友列表。
S308：判断一键AA好友列表是否与实际AA好友匹配，如果匹配，则执行S309；如果不匹配，执行S310。
S309：发起AA收款，然后结束整个流程。
S310：选择手动调整好友还是自动调整好友？如果手动调整，则执行S311；如果自动调整，则返回执行S307，重新生成一键AA好友列表。
S311：从优化通讯录中选择好友，然后执行S309。
下面就一键AA及优化通讯录作进一步详细说明。
【一键AA】
用户行为累积，简言之，就是记录用户日常行为的点点滴滴；就以AA收款为例子，某个用户每发起一次AA收款，那么在宽表中以“我”这个用户为主体的AA收款笔数就+1，而AA的参与对象，称之为“累积客体”，每次该用户给其中某一位朋友A，那么以“我”为主体，A为客体的累积数据就+1；
下面用一个简单的例子来说明一下；
用户在1个月前发起了一笔AA，对象是A/B/C/D/E
用户在10天前发起了一笔AA，对象是E/F/G
用户在7天前发起了一笔AA，对象是B
用户在5天前发起了一笔AA，对象是C/G
用户在2天前发了一笔AA，对象是A/B/C/D/E/F/G/H
用户在昨天发了一笔AA，对象是B/X
用户在今天发了一笔AA，独享是A/B/C/D/E
然后可统计出，以该用户(例如“张三”)为累积主题的AA收款信息累积表如表1所示。
表1
累积对象 累积笔数 最近一次累积时间
A 3 今天
B 5 今天
C 4 今天
D 3 今天
E 4 今天
F 2 2天前
G 3 2天前
H 1 2天前
X 1 昨天
因此，这里每个累积对象的累积笔数和最近一次的累积时间，就可以成为判别这个对象和相关主体的密切程度的一个重要指标。以此为基础，可以添加多种变量，分别用以限定累积主体、累积客体、累积时间、累积方法等等，最终形成一套完善的大数据用户行为累积体系。
在实际情况中，一个人的“朋友圈”(“饭圈”等)其实基本是大致固定的，根据用户行为数据累积信息，就可以比较方便地获取到一个人可能发起的AA账单信息，流 程参见图4。
S401：对用户行为累积数据进行收集和分析，得到用户的均摊好友信息累积表(例如前述表1)。
S402：基于均摊好友信息累积表，是否可以确定出超过预定概率阈值的最大概率均摊对象人数，如果是，执行S403；否则执行S405。
例如，最近30天AA组合里最多且超过50％(预定概率阈值)的AA是一个5人组合，则最大概率均摊对象人数为5。如果最近30天AA组合里没有超过50％(预定概率阈值)的AA组合，则执行S405。
S403：判断最大概率均摊对象人数是否与本次订单的收款人数相一致，如果一致，则执行S404；如果不一致，执行S405。
仍如前例子，假设最近30天AA组合里最多且超过50％的AA是一个5人组合，而当前发起的AA人数是8人，则说明人数不匹配；如果当前发起的AA人数也是5人，则说明人数匹配，则执行将这个5人组合作为一键均摊好友列表。
S404：基于最大概率均摊对象人数对应的各个对象生成一键均摊好友列表。
S405：统计均摊信息累积表中各好友的均摊参与度，并根据均摊参与度从高至低选取出与本次订单的收款人数相一致的好友，作为一键均摊好友列表。
【优化通讯录】
一键AA收款的准确率可大为提高，如果通过一键AA还是无法准确命中，还提供了另外一种方式：即由用户选择好友收款，不过，针对这个选择好友的界面，也使用用户行为数据累积信息对它进行了改造。
参见图5，为优化通讯录生成流程图，包括：
S501：查询一段时间(例如90天)AA收款对象集合；
S502：获取各好友被AA的次数；
S503：获取各好友被AA的最近时间；
S504：获取各好友密切信息(例如最近聊天记录)；
其中，S502-S504的执行顺序不限。
S505：根据上述信息综合计算出各个好友的AA参与度；
S506：将通讯录中的好友按照AA参与度进行排序。
至此，以一个实际例子进行说明。
如果用户在今天发起了一个5人的AA，那么按照本说明书实施例的方法，执行下述判断和步骤：
(1)根据表1，发现在最近30天中，AA对象最多的组合是A/B/C/D/E，也刚好是5人，满足人数需求；
(2)但是这个组合出现次数是2次，总次数7次，2/7<50％,不满足直达一键AA条件；
(3)根据表1，密切度最高的5个人是A/B/C/D/E；
(4)输出给用户的AA收款信息对象是A/B/C/D/E；
(5)与用户交互后，如果不满足预期，用户点击选择朋友发起AA收款；
(6)在选择朋友界面，这几位朋友的排序如下：B-C-E-A-D-G-F-X-H。
可见，本说明书实施例提供的收款控制方法，考虑了在实际情况中，用户每次AA收款的好友相似度很高，为了避免用户重复手动选取AA好友，根据大数据收集和分析，自动生成一键AA供用户选择，可快速确定AA好友，提高AA收款的效率和准确性，提升用户体验。另外，也对好友列表基于好友AA参与度进行了优化，可方便用户快速查找到AA好友。
第二方面，基于同一发明构思，本说明书实施例提供一种收款控制装置，请参考图6，包括：均摊收款确定单元601、一键均摊好友调用单元602、均摊好友调整单元603和收款单元604；其中：
所述均摊收款确定单元601，用于获取用户发起的均摊收款订单，确定收款人数；
所述一键均摊好友调用单元602，用于确定用户调用一键均摊好友时，生成与所述收款人数对应的一键均摊好友列表，其中，基于预置时间段内所述用户的历史均摊收款订单，对用户行为累积数据进行收集和分析，确定所述一键均摊好友列表；
所述均摊好友调整单元603，用于通过与用户交互，确定所述一键均摊好友列表是否与本次收款订单的好友匹配，如果匹配，则指示所述收款单元604发起收款，如果不匹配，则对好友进行调整后指示所述收款单元604发起收款。
在一种可选方式中，所述装置还包括：
优化通讯录调用单元605，用于确定用户未选择调用一键均摊好友时，向用户显示优化通讯录，其中，基于预置时间段内所述用户的历史均摊收款订单，对用户行为累积数据进行收集和分析，确定所述优化通讯录中各好友的排列顺序；以及，确定用户在所述优化通讯录中选取的各个好友为本次收款订单的好友。
在一种可选方式中，所述均摊好友调整单元603具体用于：基于所述一键均摊好友，向用户展示手动调整界面，获取用户手动调整后的好友。
在一种可选方式中，所述均摊好友调整单元603向用户展示优化通讯录作为所述手动调整界面。
在一种可选方式中，所述均摊好友调整单元603具体用于：重新生成一键均摊好友，其中，重新生成的一键均摊好友是对所述一键均摊好友列表中好友优先级进行调整得到的。
在一种可选方式中，所述均摊好友调整单元603还用于：通过与用户交互，确定当前一键均摊好友列表是否与本次收款订单的好友匹配，如果匹配，则指示所述收款单元604发起收款，如果不匹配，则确定是否再次生成一键均摊好友，或者用户手动调整好友，或者基于优化通讯录进行好友选取，直至好友匹配成功。
在一种可选方式中，还包括：一键均摊好友生成单元606；
所述一键均摊好友生成单元606包括：
数据分析子单元6061，用于对用户行为累积数据进行收集和分析，得到所述用户的均摊好友信息累积表；
最大概率均摊对象人数确定子单元6062，用于基于所述均摊好友信息累积表，确定出超过预定概率阈值的最大概率均摊对象人数；
判断子单元6063，用于判断所述最大概率均摊对象人数是否与本次订单的收款人数相一致；
一键均摊好友列表确定子单元6064，如果所述最大概率均摊对象人数是否与本次订单的收款人数相一致，则基于所述最大概率均摊对象人数对应的各个对象生成所述一键均摊好友列表，如果不一致，则统计所述均摊信息累积表中各好友的均摊参与度，并根据均摊参与度从高至低选取出与本次订单的收款人数相一致的好友，作为所述一键 均摊好友列表。
在一种可选方式中，还包括：通讯录优化单元607，用于对用户行为累积数据进行收集和分析，得到所述用户的均摊好友信息累积表；以及，统计所述均摊信息累积表中各好友的均摊参与度，并根据均摊参与度从高至低，确定所述优化通讯录中各好友的排列顺序。
第三方面，基于与前述实施例中收款控制方法同样的发明构思，本发明还提供一种服务器，如图7所示，包括存储器704、处理器702及存储在存储器704上并可在处理器702上运行的计算机程序，所述处理器702执行所述程序时实现前文所述收款控制方法的步骤。
其中，在图7中，总线架构(用总线700来代表)，总线700可以包括任意数量的互联的总线和桥，总线700将包括由处理器702代表的一个或多个处理器和存储器704代表的存储器的各种电路链接在一起。总线700还可以将诸如***设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口706在总线700和接收器701和发送器703之间提供接口。接收器701和发送器703可以是同一个元件，即收发机，提供用于在传输介质上与各种其他装置通信的单元。处理器702负责管理总线700和通常的处理，而存储器704可以被用于存储处理器702在执行操作时所使用的数据。
第四方面，基于与前述实施例中收款控制方法的发明构思，本发明还提供一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现前文所述收款控制方法的步骤。
本说明书是参照根据本说明书实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的设备。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括 指令设备的制造品，该指令设备实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本说明书的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本说明书范围的所有变更和修改。
显然，本领域的技术人员可以对本说明书进行各种改动和变型而不脱离本说明书的精神和范围。这样，倘若本说明书的这些修改和变型属于本说明书权利要求及其等同技术的范围之内，则本说明书也意图包含这些改动和变型在内。

Claims (18)

  1. 一种收款控制方法，用于对均摊收款的好友选取进行控制，所述方法包括：
    获取用户发起的均摊收款订单，确定收款人数；
    确定用户选择调用一键均摊好友时，生成与所述收款人数对应的一键均摊好友列表，其中，基于预置时间段内所述用户的历史均摊收款订单，对用户行为累积数据进行收集和分析，确定所述一键均摊好友列表；
    通过与用户交互，确定所述一键均摊好友列表是否与本次收款订单的好友匹配，如果匹配，则发起收款，如果不匹配，则对好友进行调整后发起收款。
  2. 根据权利要求1所述的方法，所述方法还包括：
    确定用户未选择调用一键均摊好友时，向用户显示优化通讯录，其中，基于预置时间段内所述用户的历史均摊收款订单，对用户行为累积数据进行收集和分析，确定所述优化通讯录中各好友的排列顺序；
    确定用户在所述优化通讯录中选取的各个好友为本次收款订单的好友。
  3. 根据权利要求1或2所述的方法，在确定所述一键均摊好友列表与本次收款订单的好友不匹配时，所述对好友进行调整，包括：
    基于所述一键均摊好友，向用户展示手动调整界面，获取用户手动调整后的好友。
  4. 根据权利要求3所述的方法，所述向用户展示手动调整界面，包括：
    向用户展示优化通讯录作为所述手动调整界面。
  5. 根据权利要求1或2所述的方法，在确定所述一键均摊好友列表与本次收款订单的好友不匹配时，所述对好友进行调整，包括：
    重新生成一键均摊好友，其中，重新生成的一键均摊好友是对所述一键均摊好友列表中好友优先级进行调整得到的。
  6. 根据权利要求5所述的方法，在重新生成一键均摊好友之后，还包括：
    通过与用户交互，确定当前一键均摊好友列表是否与本次收款订单的好友匹配，如果匹配，则发起收款，如果不匹配，则确定是否再次生成一键均摊好友，或者用户手动调整好友，或者基于优化通讯录进行好友选取，直至好友匹配成功。
  7. 根据权利要求1-5任一项所述的方法，所述对用户行为累积数据进行收集和分析，确定所述一键均摊好友列表，包括：
    对用户行为累积数据进行收集和分析，得到所述用户的均摊好友信息累积表；
    基于所述均摊好友信息累积表，确定出超过预定概率阈值的最大概率均摊对象人数；
    判断所述最大概率均摊对象人数是否与本次订单的收款人数相一致，如果一致，则 基于所述最大概率均摊对象人数对应的各个对象生成所述一键均摊好友列表，如果不一致，则统计所述均摊信息累积表中各好友的均摊参与度，并根据均摊参与度从高至低选取出与本次订单的收款人数相一致的好友，作为所述一键均摊好友列表。
  8. 根据权利要求2所述的方法，所述对用户行为累积数据进行收集和分析，确定所述优化通讯录中各好友的排列顺序，包括：
    对用户行为累积数据进行收集和分析，得到所述用户的均摊好友信息累积表；
    统计所述均摊信息累积表中各好友的均摊参与度，并根据均摊参与度从高至低，确定所述优化通讯录中各好友的排列顺序。
  9. 一种收款控制装置，用于对均摊收款的好友选取进行控制，所述装置包括均摊收款确定单元、一键均摊好友调用单元、均摊好友调整单元和收款单元；其中：
    所述均摊收款确定单元，用于获取用户发起的均摊收款订单，确定收款人数；
    所述一键均摊好友调用单元，用于确定用户调用一键均摊好友时，生成与所述收款人数对应的一键均摊好友列表，其中，基于预置时间段内所述用户的历史均摊收款订单，对用户行为累积数据进行收集和分析，确定所述一键均摊好友列表；
    所述均摊好友调整单元，用于通过与用户交互，确定所述一键均摊好友列表是否与本次收款订单的好友匹配，如果匹配，则指示所述收款单元发起收款，如果不匹配，则对好友进行调整后指示所述收款单元发起收款。
  10. 根据权利要求9所述的装置，所述装置还包括：
    优化通讯录调用单元，用于确定用户未选择调用一键均摊好友时，向用户显示优化通讯录，其中，基于预置时间段内所述用户的历史均摊收款订单，对用户行为累积数据进行收集和分析，确定所述优化通讯录中各好友的排列顺序；以及，确定用户在所述优化通讯录中选取的各个好友为本次收款订单的好友。
  11. 根据权利要求9或10所述的装置，所述均摊好友调整单元具体用于：基于所述一键均摊好友，向用户展示手动调整界面，获取用户手动调整后的好友。
  12. 根据权利要求11所述的装置，所述均摊好友调整单元向用户展示优化通讯录作为所述手动调整界面。
  13. 根据权利要求9或10所述的装置，所述均摊好友调整单元具体用于：
    重新生成一键均摊好友，其中，重新生成的一键均摊好友是对所述一键均摊好友列表中好友优先级进行调整得到的。
  14. 根据权利要求13所述的装置，所述均摊好友调整单元还用于：通过与用户交互，确定当前一键均摊好友列表是否与本次收款订单的好友匹配，如果匹配，则指示所 述收款单元发起收款，如果不匹配，则确定是否再次生成一键均摊好友，或者用户手动调整好友，或者基于优化通讯录进行好友选取，直至好友匹配成功。
  15. 根据权利要求9-14任一项所述的装置，还包括：一键均摊好友生成单元；
    所述一键均摊好友生成单元包括：
    数据分析子单元，用于对用户行为累积数据进行收集和分析，得到所述用户的均摊好友信息累积表；
    最大概率均摊对象人数确定子单元，用于基于所述均摊好友信息累积表，确定出超过预定概率阈值的最大概率均摊对象人数；
    判断子单元，用于判断所述最大概率均摊对象人数是否与本次订单的收款人数相一致；
    一键均摊好友列表确定子单元，如果所述最大概率均摊对象人数是否与本次订单的收款人数相一致，则基于所述最大概率均摊对象人数对应的各个对象生成所述一键均摊好友列表，如果不一致，则统计所述均摊信息累积表中各好友的均摊参与度，并根据均摊参与度从高至低选取出与本次订单的收款人数相一致的好友，作为所述一键均摊好友列表。
  16. 根据权利要求10所述的装置，还包括：通讯录优化单元，用于对用户行为累积数据进行收集和分析，得到所述用户的均摊好友信息累积表；以及，统计所述均摊信息累积表中各好友的均摊参与度，并根据均摊参与度从高至低，确定所述优化通讯录中各好友的排列顺序。
  17. 一种服务器，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现权利要求1-8任一项所述方法的步骤。
  18. 一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现权利要求1-8任一项所述方法的步骤。
PCT/CN2019/089036 2018-08-13 2019-05-29 收款控制方法、装置、服务器及可读存储介质 WO2020034719A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
SG11202010617RA SG11202010617RA (en) 2018-08-13 2019-05-29 Payment collection control method and device, server, and computer-readable storage medium
EP19850319.5A EP3800603A4 (en) 2018-08-13 2019-05-29 PAYMENT COLLECTION CONTROL PROCEDURE AND DEVICE, SERVER AND READABLE STORAGE MEDIUM
US17/086,192 US11200547B2 (en) 2018-08-13 2020-10-30 Payment collection control method and device, server, and computer-readable storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810916993.5 2018-08-13
CN201810916993.5A CN109345219B (zh) 2018-08-13 2018-08-13 收款控制方法、装置、服务器及可读存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/086,192 Continuation US11200547B2 (en) 2018-08-13 2020-10-30 Payment collection control method and device, server, and computer-readable storage medium

Publications (1)

Publication Number Publication Date
WO2020034719A1 true WO2020034719A1 (zh) 2020-02-20

Family

ID=65294116

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/089036 WO2020034719A1 (zh) 2018-08-13 2019-05-29 收款控制方法、装置、服务器及可读存储介质

Country Status (6)

Country Link
US (1) US11200547B2 (zh)
EP (1) EP3800603A4 (zh)
CN (2) CN109345219B (zh)
SG (1) SG11202010617RA (zh)
TW (1) TWI766167B (zh)
WO (1) WO2020034719A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109345219B (zh) * 2018-08-13 2020-07-28 阿里巴巴集团控股有限公司 收款控制方法、装置、服务器及可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104717340A (zh) * 2013-12-13 2015-06-17 中国电信股份有限公司 提供拨号号码的方法和装置
CN106296158A (zh) * 2016-07-27 2017-01-04 努比亚技术有限公司 移动终端及支付方法
CN106686030A (zh) * 2015-11-09 2017-05-17 阿里巴巴集团控股有限公司 一种实现业务的方法及装置
CN109345219A (zh) * 2018-08-13 2019-02-15 阿里巴巴集团控股有限公司 收款控制方法、装置、服务器及可读存储介质

Family Cites Families (54)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6879691B1 (en) * 2000-05-12 2005-04-12 Bluetie, Inc. Information autocompletion system
US20040054592A1 (en) * 2002-09-13 2004-03-18 Konrad Hernblad Customer-based wireless ordering and payment system for food service establishments using terminals and mobile devices
US20060031510A1 (en) * 2004-01-26 2006-02-09 Forte Internet Software, Inc. Methods and apparatus for enabling a dynamic network of interactors according to personal trust levels between interactors
US7580363B2 (en) * 2004-08-16 2009-08-25 Nokia Corporation Apparatus and method for facilitating contact selection in communication devices
US8037421B2 (en) * 2005-10-11 2011-10-11 Research In Motion Limited System and method for organizing application indicators on an electronic device
US8370349B2 (en) * 2007-02-28 2013-02-05 Yahoo! Inc. Instant contact searching and presentation by category
US20090319425A1 (en) * 2007-03-30 2009-12-24 Obopay, Inc. Mobile Person-to-Person Payment System
US8495020B1 (en) * 2007-06-27 2013-07-23 ENORCOM Corporation Mobile information system
TWI431494B (zh) * 2007-09-21 2014-03-21 E Ten Information Sys Co Ltd Use color to identify contact person friendly methods, instant messaging systems and devices
US20090265429A1 (en) * 2008-04-22 2009-10-22 Amivox Limited Communications framework using hand held devices
US20110171934A1 (en) * 2008-07-30 2011-07-14 Sk Telecom Co., Ltd. Method of providing communication function for communication group, and mobile communication terminal and presence server for the same
US8498953B2 (en) * 2010-03-30 2013-07-30 Sap Ag Method for allocating trip sharing
US20120173396A1 (en) * 2010-12-30 2012-07-05 Paydivvy, Inc. Bill division and group payment systems and methods
US10078819B2 (en) * 2011-06-21 2018-09-18 Oath Inc. Presenting favorite contacts information to a user of a computing device
US20130054413A1 (en) * 2011-08-22 2013-02-28 American Express Travel Related Services Company Inc. Methods and systems for contactless payments
US9576284B2 (en) * 2011-09-29 2017-02-21 Paypal, Inc. Social proximity payments
US20130159173A1 (en) * 2011-12-19 2013-06-20 Sridhar Sivaraman Shared Mobile Payments
US8904689B2 (en) * 2012-12-26 2014-12-09 Theodosios Kountotsis Methods and systems for detecting a gun and/or bullet within one's vicinity via an electronic device
US20140241216A1 (en) * 2013-02-27 2014-08-28 Yi-Chuan Cheng Portable device with dynamic ranking module
US10282713B2 (en) * 2013-03-15 2019-05-07 Brandon Ham Bill splitting and payment system and method
US20150040027A1 (en) * 2013-07-31 2015-02-05 Yi-Chuan Cheng Portable Device with Handedness Switching Module
CN104144240B (zh) * 2013-09-24 2018-03-27 腾讯科技（深圳）有限公司 一种联系人管理方法及装置、终端设备
US9721314B2 (en) * 2013-10-28 2017-08-01 Square, Inc. Apportioning shared financial expenses
CN104636921B (zh) * 2013-11-06 2016-12-21 腾讯科技（深圳）有限公司 基于通信群的在线支付方法，支付***及服务器***
US10402899B2 (en) * 2013-11-20 2019-09-03 Capital One Services, Llc Shared expensive management
US20150156149A1 (en) * 2013-12-04 2015-06-04 At&T Mobility Ii Llc Method and apparatus for sharing content from third party websites via messaging
US9571427B2 (en) * 2013-12-31 2017-02-14 Google Inc. Determining strength of association between user contacts
US9830597B2 (en) * 2014-03-04 2017-11-28 Bank Of America Corporation Formation and funding of a shared token
US9710134B1 (en) * 2014-03-20 2017-07-18 Amazon Technologies, Inc. Smart contact lists
US10043184B2 (en) * 2014-05-30 2018-08-07 Paypal, Inc. Systems and methods for implementing transactions based on facial recognition
US9922094B1 (en) * 2014-06-18 2018-03-20 Symantec Corporation Sharing data based on user ranking
US20160019472A1 (en) * 2014-07-16 2016-01-21 TableDivide, Inc. System and method for organizing a group activity for multiple paying parties
US20160041982A1 (en) * 2014-08-05 2016-02-11 Facebook, Inc. Conditioned Search Ranking Models on Online Social Networks
US10152698B2 (en) * 2014-08-26 2018-12-11 Samsung Electronics Co., Ltd. System and method for mobile payments in a vehicle
US9396483B2 (en) * 2014-08-28 2016-07-19 Jehan Hamedi Systems and methods for determining recommended aspects of future content, actions, or behavior
KR20160060855A (ko) * 2014-11-20 2016-05-31 삼성전자주식회사 콘텐츠를 공유하는 방법 및 그 전자 장치
CN105654293B (zh) * 2014-12-03 2020-01-17 阿里巴巴集团控股有限公司 支付方法及装置
JP2016151785A (ja) * 2015-02-16 2016-08-22 Ｌｉｎｅ株式会社 情報処理システム及び情報処理方法
CN106296154B (zh) * 2015-06-11 2021-08-24 创新先进技术有限公司 事务处理方法和***
CN106330657B (zh) * 2015-06-19 2020-01-21 阿里巴巴集团控股有限公司 一种好友处理方法和装置
KR20170077425A (ko) * 2015-12-28 2017-07-06 삼성전자주식회사 전자 장치 및 전자 장치의 핸드오프를 이용한 결제 수행 방법
EP3371693B1 (en) * 2016-02-05 2021-06-16 Samsung Electronics Co., Ltd. Method and electronic device for managing operation of applications
US10187395B2 (en) * 2016-04-28 2019-01-22 Microsoft Technology Licensing, Llc Resource sharing and designation of permissions for other tenants and unregistered users of same tenant
CN107404500B (zh) * 2016-05-18 2020-07-03 阿里巴巴集团控股有限公司 群组通信方法、装置及移动终端
CN107545423A (zh) * 2016-06-24 2018-01-05 华为终端（东莞）有限公司 一种支付方法、支付终端及代付服务器
CN106651336A (zh) * 2016-09-20 2017-05-10 北京小米移动软件有限公司 收款方法和装置
CN106682890A (zh) * 2016-12-08 2017-05-17 腾讯科技（深圳）有限公司 多个用户账户之间进行业务数值转移的方法及装置
CN107045540A (zh) * 2017-02-14 2017-08-15 阿里巴巴集团控股有限公司 数据处理方法及装置、服务器和数据处理***
US20190279317A1 (en) * 2017-02-15 2019-09-12 Cherise Marissa Burton Travel Planning Resource Mobile Application
TWM548302U (zh) * 2017-06-12 2017-09-01 華南商業銀行股份有限公司 ***分帳系統
US10558673B2 (en) * 2017-07-12 2020-02-11 Facebook, Inc. Techniques for prospective contact ranking of address book entries
US10917180B2 (en) * 2018-07-24 2021-02-09 Comcast Cable Communications, Llc Controlling vibration output from a computing device
US20200159777A1 (en) * 2018-11-21 2020-05-21 International Business Machines Corporation Simplifying electronic communication based on dynamically structured contact entries
US20200334724A1 (en) * 2019-04-20 2020-10-22 Peter Garrett Peer-to-peer bill sharing payment application

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104717340A (zh) * 2013-12-13 2015-06-17 中国电信股份有限公司 提供拨号号码的方法和装置
CN106686030A (zh) * 2015-11-09 2017-05-17 阿里巴巴集团控股有限公司 一种实现业务的方法及装置
CN106296158A (zh) * 2016-07-27 2017-01-04 努比亚技术有限公司 移动终端及支付方法
CN109345219A (zh) * 2018-08-13 2019-02-15 阿里巴巴集团控股有限公司 收款控制方法、装置、服务器及可读存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3800603A4 *

Also Published As

Publication number Publication date
EP3800603A4 (en) 2021-08-04
CN112036854A (zh) 2020-12-04
CN109345219B (zh) 2020-07-28
US20210049564A1 (en) 2021-02-18
US11200547B2 (en) 2021-12-14
CN109345219A (zh) 2019-02-15
TWI766167B (zh) 2022-06-01
EP3800603A1 (en) 2021-04-07
SG11202010617RA (en) 2020-11-27
TW202014953A (zh) 2020-04-16

Similar Documents

Publication Publication Date Title
US11128582B2 (en) Emoji recommendation method and apparatus
CN105447604B (zh) 一种账户处理方法及装置
US20160012406A1 (en) Recharge Method, Recharge Terminal, and Recharge Server
WO2014070573A2 (en) System and method for generating subscriber churn predictions
WO2019196255A1 (zh) 电销时间段的选取方法、装置、终端设备及介质
JP6147433B2 (ja) ユーザとの自然会話能力を備えたエージェントシステム、エージェント制御方法、エージェント制御プログラム、及び記録媒体
US11372805B2 (en) Method and device for information processing
CN107248070A (zh) 聊天群预支付的方法及装置
EP3764303A1 (en) Information processing device, etc. for calculating prediction data
CN111459783B (zh) 应用程序优化方法、装置、电子设备及存储介质
CN110766389A (zh) 付款控制方法、支付控制方法及装置
CN109428910B (zh) 一种数据处理方法、装置及***
CN109597800B (zh) 一种日志分发方法及装置
EP3388956A1 (en) Media information display method, server, and data storage medium
TW201601086A (zh) 資訊推送方法及裝置
US20190220924A1 (en) Method and device for determining key variable in model
CN112967091A (zh) 营销服务事件的智能分发方法、***及存储介质
WO2020034719A1 (zh) 收款控制方法、装置、服务器及可读存储介质
WO2019136768A1 (zh) 基于区块链的挖矿方法、装置及计算机可读存储介质
CN115242745A (zh) 基于5g通信网络的短信推送***及方法
CN105848127B (zh) 一种精确补单方法和装置
CN113988559B (zh) 用于问卷投放的免打扰方法及装置
CN107301484B (zh) 一种监控点设置方法及装置
CN112862495A (zh) 交易数据风险控制方法、装置、计算机设备和存储介质
CN106920083B (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: 19850319

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019850319

Country of ref document: EP

Effective date: 20201229

NENP Non-entry into the national phase

Ref country code: DE