WO2020078244A1 - 资源收取方法及装置 - Google Patents

资源收取方法及装置 Download PDF

Info

Publication number
WO2020078244A1
WO2020078244A1 PCT/CN2019/110267 CN2019110267W WO2020078244A1 WO 2020078244 A1 WO2020078244 A1 WO 2020078244A1 CN 2019110267 W CN2019110267 W CN 2019110267W WO 2020078244 A1 WO2020078244 A1 WO 2020078244A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource collection
resource
user
local user
group
Prior art date
Application number
PCT/CN2019/110267
Other languages
English (en)
French (fr)
Inventor
周凯
张黎黎
马颖男
Original Assignee
钉钉控股（开曼）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 钉钉控股（开曼）有限公司 filed Critical 钉钉控股（开曼）有限公司
Publication of WO2020078244A1 publication Critical patent/WO2020078244A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/04842—Selection of displayed objects or displayed text elements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/0482—Interaction with lists of selectable items, e.g. menus
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • 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

Definitions

  • One or more embodiments of this specification relate to the technical field of terminals, and in particular, to a resource collection method and device.
  • the implementation process of services often involves resource interactions, such as data resources, bandwidth resources, traffic resources, and credential resources, etc., so as to be suitable for corresponding types of business scenarios.
  • resource interactions such as data resources, bandwidth resources, traffic resources, and credential resources, etc.
  • user A provides resources to user B to complete related services.
  • these services can be combined so that a user can complete the combined service through its own resources, and the user can charge other users after the service is completed.
  • the corresponding resources can effectively improve the efficiency of business completion.
  • one or more embodiments of this specification provide a resource collection method and device.
  • a resource collection method including:
  • the resource collection object includes one or more associated users of the local user, the associated user includes at least one of the following: one or more group members selected from the organizational structure of the group to which the local user belongs 1. One or more group members selected from the group where the local user is located, and one or more contacts selected from the address book;
  • a resource collection method including:
  • an object configuration interface is displayed, and the object configuration interface includes an associated user of the local user;
  • the selected associated user in the object configuration interface is taken as a resource collection object, and a resource collection request is sent to the resource collection object to charge a set amount of resources from the resource collection object.
  • a resource collection method including:
  • a resource collection editing interface is displayed, and the resource collection editing interface includes object configuration options
  • a resource collection method including:
  • a resource collection method including:
  • the resource charging object includes multiple associated users of the local user, the multiple associated users belong to at least two user sets, wherein the user set includes at least one of the following: the local user's group Group members in the organization structure of the organization, group members in the group where the local user is located, and contacts in the address book;
  • a resource collection device including:
  • the determining unit determines a resource charging object, the resource charging object includes one or more associated users of the local user, and the associated user includes at least one of the following: one or more selected from the organizational structure of the group to which the local user belongs Group members, one or more group members selected from the group where the local user is located, and one or more contacts selected from the address book;
  • the sending unit sends a resource collection request to the resource collection object to charge the resource collection object with a set amount of resources.
  • a resource collection device including:
  • the first display unit displays the resource collection and editing interface, and the resource collection and editing interface includes object configuration options
  • a second display unit in response to a trigger operation on the object configuration option, displaying an object configuration interface, where the object configuration interface includes an associated user of the local user;
  • the sending unit takes the selected associated user in the object configuration interface as a resource collection object and sends a resource collection request to the resource collection object to charge the resource collection object with a set amount of resources.
  • a resource collection device including:
  • the first display unit displays the communication interface corresponding to the group
  • a second display unit when the resource collection function in the communication interface is triggered, a resource collection editing interface is displayed, and the resource collection editing interface includes object configuration options;
  • a third display unit in response to a trigger operation on the object configuration option, displaying an object configuration interface, where the object configuration interface includes group members of the group;
  • the sending unit sends a communication message including a resource collection request through a communication session corresponding to the group; wherein, the communication message is only visible to the group members selected as resource collection objects, or the communication message is available to all groups All members are visible but only the group members selected as resource collection targets can trigger.
  • a resource collection device including:
  • the sending unit sends a resource collection request to the resource collection object to charge the resource collection object with a set amount of resources.
  • a resource collection device including:
  • the determining unit determines a resource collection object, and the resource collection object includes multiple associated users of the local user, and the multiple associated users belong to at least two user sets, where the user set includes at least one of the following: the local end Group members in the organizational structure of the group to which the user belongs, group members in the group where the local user is located, and contacts in the address book;
  • the sending unit sends a resource collection request to the resource collection object to charge the resource collection object with a set amount of resources.
  • FIG. 1 is a schematic structural diagram of a resource collection system provided by an exemplary embodiment
  • FIG. 2 is a flowchart of a resource collection method provided by an exemplary embodiment
  • FIG. 3 is a flowchart of another resource collection method provided by an exemplary embodiment
  • FIG. 4 is a flowchart of yet another resource collection method provided by an exemplary embodiment
  • FIG. 5 is a schematic diagram of a collection management interface provided by an exemplary embodiment
  • FIG. 6 is a schematic diagram of a payment object selection interface provided by an exemplary embodiment
  • FIG. 7 is a schematic diagram of a collection event editing interface provided by an exemplary embodiment
  • FIG. 8 is a schematic diagram of a configuration reminder method provided by an exemplary embodiment
  • FIG. 9 is a schematic diagram of another payment event editing interface provided by an exemplary embodiment.
  • FIG. 10 is a schematic diagram of a payment configuration interface provided by an exemplary embodiment
  • FIG. 11 is a schematic diagram of a group communication session interface on the initiator side provided by an exemplary embodiment
  • FIG. 12 is a schematic diagram of a payment reminder to a payment object provided by an exemplary embodiment
  • FIG. 13 is a schematic diagram of a group communication session interface on a payment object side provided by an exemplary embodiment
  • FIG. 14 is a schematic diagram of a payment interface provided by an exemplary embodiment
  • 15 is a schematic diagram of a payment details interface provided by an exemplary embodiment
  • 16 is a schematic diagram of a personal communication session interface provided by an exemplary embodiment
  • FIG. 17 is a schematic diagram of an update collection management interface provided by an exemplary embodiment
  • FIG. 18 is a schematic diagram of creating a collection event in a group communication session interface provided by an exemplary embodiment
  • FIG. 19 is a schematic structural diagram of a device provided by an exemplary embodiment
  • 20 is a block diagram of a resource collection device provided by an exemplary embodiment
  • 21 is a block diagram of another resource collection device provided by an exemplary embodiment
  • FIG. 22 is a block diagram of yet another resource collection device provided by an exemplary embodiment.
  • the steps of the corresponding method are not necessarily performed in the order shown and described in this specification.
  • the method may include more or fewer steps than described in this specification.
  • the single step described in this specification may be decomposed into multiple steps for description in other embodiments; and the multiple steps described in this specification may also be combined into a single step in other embodiments description.
  • FIG. 1 is a schematic structural diagram of a resource collection system provided by an exemplary embodiment. As shown in FIG. 1, the system may include a server 11, a network 12, and several electronic devices, such as a mobile phone 13, a mobile phone 14, a mobile phone 15, and so on.
  • the server 11 may be a physical server containing an independent host, or the server 11 may be a virtual server hosted by a host cluster. During the running process, the server 11 can run a server-side program of an application to be implemented as a server of the application. In the technical solutions of one or more embodiments of this specification, the server 11 can cooperate with the clients running on the mobile phones 13-15 to implement the resource collection solution.
  • Mobile phones 13-15 are just one type of electronic devices that users can use. In fact, users obviously can also use electronic devices such as the following types: tablet devices, notebook computers, PDAs (Personal Digital Assistants), wearable devices (such as smart glasses, smart watches, etc.), etc. Various embodiments do not limit this.
  • the electronic device can run a client-side program of an application to be a client of the mobile group office platform.
  • the client application can be pre-installed on the electronic device, so that the client can be started and run on the electronic device; of course, when using an online "client” such as HTML5 technology, there is no need to The client can be obtained and run by installing the corresponding application program on the electronic device.
  • the network 12 for interaction between the mobile phones 13-15 and the server 11 may include various types of wired or wireless networks.
  • the network 12 may include a Public Switched Telephone Network (PSTN) and the Internet.
  • PSTN Public Switched Telephone Network
  • FIG. 2 is a flowchart of a resource collection method provided by an exemplary embodiment. As shown in FIG. 2, this method is applied to electronic devices (such as mobile phones 13 to 15 shown in FIG. 1, etc.), and may include the following steps:
  • Step 202 Determine the resource collection target.
  • the local user can charge a set amount of resources from the resource charging object through the technical solution of this specification.
  • the local user can provide physical or virtual goods to the resource collection object and charge the resource equivalent to the resource collection object; for example, the local user can advance a set amount for the resource collection object in advance Resources, and then collect the set amount of resources from the resource collection object; of course, the local user can also collect the set amount of resources from the resource collection object for other reasons, and this specification does not limit this.
  • the resource charging object may include an associated user of the local user, that is, a user who is associated with the local user.
  • the associated user may include a contact selected by the local user from the address book (in-app address book and / or local address book of the electronic device); for another example, the associated user may include the local user from the group where the user is located Selected group members; for another example, the associated users may include group members selected by the local user from the organizational structure of the group to which they belong. In short, as long as the local user can learn about the associated user, he can add it as a resource collection target.
  • the number of resource collection objects may be one or more, depending on the actual needs and conditions of the local user.
  • the multiple associated users may belong to at least two user sets, where the user set includes at least one of the following One: The group members in the organizational structure of the group to which the local user belongs, the group members in the group where the local user is located, and the contacts in the address book, etc. This manual does not limit this.
  • the local user when the client of the application is running on the electronic device, the local user can implement the technical solution of this specification through the resource collection function provided by the client.
  • the application can provide one or more trigger portals for the resource charging function, such as independent trigger portals or built-in trigger portals.
  • the local user when the local user triggers the above resource collection function through an independent triggering portal, the local user can select all associated users as the resource collection object.
  • the resource collection function is triggered in the group where the local user is located, all group members except the local user can be added as resource collection objects, or the local user can select among the group members , And add one or more group members selected by the local user as resource collection objects.
  • Step 204 Send a resource collection request to the resource collection object to charge the resource collection object with a set amount of resources.
  • the resource collection request can set the resource amount for the resource collection object (that is, the set amount above), and the resource collection object can trigger the resource collection request And quickly provide a set amount of resources to local users.
  • the resource collection request can serve as a reminder to the resource collection object, which helps to improve the resource collection efficiency.
  • a communication session message including the resource collection request can be sent through the communication session between the local user and the resource collection object, so that the resource collection object can be received and viewed Arrive at the communication session message, and provide the set amount of resources to the local user by triggering the communication session message, so that the local user can smoothly charge the set amount of resources.
  • a reminder message including the resource charging request may be sent to the resource charging object based on the name of the local user.
  • the reminder message is different from the communication session message and is specifically used to realize the reminder function.
  • the reminder intensity of the above communication session message can enable the resource charging object to view the resource charging request as soon as possible and provide a set amount of resources.
  • the reminder message may include one or more of in-app messages, short messages, and voice announcement messages after the phone is connected. This specification does not limit this.
  • the resource collection request may be sent through the above-mentioned communication session message and reminder message at the same time.
  • the set amount may be the average amount of resources to be collected set by the local user to the average amount after each resource collection object. Taking resources as money for example, the total amount of resources to be collected is the total amount of money to be received m.
  • the set amount may be a set amount for each resource charging object for the local user; in other words, the set amount corresponding to each resource charging object may be independent of each other.
  • the resource collection request may include remark information added by the local user, so that the local user and the resource collection object can understand the relevant information of the resource collection request. On the one hand, it can be distinguished from other resource collection requests. On the one hand, it can help the resource collection object determine whether to trigger a response to the resource collection request.
  • the remark information may include the reason for collecting the resource required by the resource collection request, the method for setting the amount, and the basis for setting the amount. The disclosure does not limit this.
  • the local user can be provided with alternative options, so that the selected alternative can be quickly added as remark information; or, the local user can set custom remark information.
  • the local user may be shown the status of the resources provided by each resource charging object for the set amount of resources.
  • the local user may be presented with a provision status similar to "XXX paid" to indicate that the resource collection target "XXX" has provided a corresponding set amount of resources.
  • a local user may be presented with a provision status similar to "x charged, remaining y not charged", indicating that there are x resource charging objects that have provided a corresponding set amount of resources and y resource charging objects The corresponding set amount of resources has not been provided.
  • a summary interface may be displayed to a local user.
  • the summary interface may include all resource collection objects, a set amount corresponding to each resource collection object, and whether each resource collection object has provided a corresponding set amount Resources etc.
  • a resource collection reminder message may be automatically sent to resource collection objects that do not provide the set amount of resources on a regular basis to remind them to provide related resources as soon as possible.
  • the sending cycle of the resource collection reminder message can be the default cycle or a custom cycle set for the user at the end. This specification does not limit this.
  • a resource collection reminder message in response to a trigger operation by a local user, may be sent to a resource collection object that does not provide the set amount of resources. For example, for resource collection objects that have not yet provided the set amount of resources, corresponding reminder options may be shown; when a certain reminder option is selected, it may be determined that the local user has implemented a trigger operation on the corresponding resource collection object, A resource collection reminder message needs to be sent to the resource collection object.
  • the resource collection function of the resource collection request may be automatically terminated to avoid repeated resource provision. loss.
  • the resource collection function of the resource collection request may be automatically terminated after the validity period of the resource collection request has passed.
  • the validity period can be the default duration, or a custom duration set by the local user.
  • the resource collection function of the resource collection request may be actively terminated. For example, when most resources are charged, the local user can stop charging the remaining resources based on the termination instruction.
  • the resource includes a general equivalent; or, the resource may include any other type of entity or virtual item, which is not limited in this specification.
  • FIG. 3 is a flowchart of another resource collection method provided by an exemplary embodiment. As shown in FIG. 3, this method is applied to electronic devices (such as mobile phones 13-15 shown in FIG. 1), and may include the following steps:
  • step 302 a resource collection and editing interface is displayed, and the resource collection and editing interface includes object configuration options.
  • step 304 in response to the triggering operation on the object configuration option, an object configuration interface is displayed, and the object configuration interface includes an associated user of the local user.
  • the local user can charge a set amount of resources from the resource charging object through the technical solution of this specification.
  • the local user can provide physical or virtual goods to the resource collection object and charge the resource equivalent to the resource collection object; for example, the local user can advance a set amount for the resource collection object in advance Resources, and then collect the set amount of resources from the resource collection object; of course, the local user can also collect the set amount of resources from the resource collection object for other reasons, and this specification does not limit this.
  • the resource charging object may include an associated user of the local user, that is, a user who is associated with the local user.
  • the associated user may include a contact selected by the local user from the address book (in-app address book and / or local address book of the electronic device); for another example, the associated user may include the local user from the group where the user is located Selected group members; for another example, the associated users may include group members selected by the local user from the organizational structure of the group to which they belong. In short, as long as the local user can learn about the associated user, he can add it as a resource collection target.
  • the number of resource collection objects may be one or more, depending on the actual needs and conditions of the local user.
  • the local user when the client of the application is running on the electronic device, the local user can implement the technical solution of this specification through the resource collection function provided by the client.
  • the application can provide one or more trigger portals for the resource charging function, such as the independent trigger portal in this embodiment (different from the built-in trigger portal, etc.); when the local user triggers the above through the independent trigger portal In the resource collection function, the local user can select all associated users as the resource collection object.
  • Step 306 Select the associated user selected in the object configuration interface as a resource collection object, and send a resource collection request to the resource collection object to charge the resource collection object with a set amount of resources.
  • the resource collection request can set the resource amount for the resource collection object (that is, the set amount above), and the resource collection object can trigger the resource collection request And quickly provide a set amount of resources to local users.
  • the resource collection request can serve as a reminder to the resource collection object, which helps to improve the resource collection efficiency.
  • a communication session message including the resource collection request can be sent through the communication session between the local user and the resource collection object, so that the resource collection object can be received and viewed Arrive at the communication session message, and provide the set amount of resources to the local user by triggering the communication session message, so that the local user can smoothly charge the set amount of resources.
  • a reminder message including the resource charging request may be sent to the resource charging object based on the name of the local user.
  • the reminder message is different from the communication session message and is specifically used to realize the reminder function
  • the reminder intensity of the above communication session message can enable the resource charging object to view the resource charging request as soon as possible and provide a set amount of resources.
  • the reminder message may include one or more of in-app messages, short messages, and voice announcement messages after the phone is connected. This specification does not limit this.
  • the resource collection request may be sent through the above-mentioned communication session message and reminder message at the same time.
  • the set amount may be the average amount of resources to be collected set by the local user to the average amount after each resource collection object. Taking resources as money for example, the total amount of resources to be collected is the total amount of money to be received m.
  • the set amount may be a set amount for each resource charging object for the local user; in other words, the set amount corresponding to each resource charging object may be independent of each other.
  • the resource collection request may include remark information added by the local user, so that the local user and the resource collection object can understand the relevant information of the resource collection request. On the one hand, it can be distinguished from other resource collection requests. On the one hand, it can help the resource collection object determine whether to trigger a response to the resource collection request.
  • the remark information may include the reason for collecting the resource required by the resource collection request, the method for setting the amount, and the basis for setting the amount. The disclosure does not limit this. Among them, you can provide alternatives to local users, so that the selected alternatives can be quickly added as remarks; or, local users can set custom remarks.
  • the local user may be shown the status of the resources provided by each resource charging object for the set amount of resources.
  • the local user may be presented with a provision status similar to "XXX paid" to indicate that the resource collection target "XXX" has provided a corresponding set amount of resources.
  • a local user may be presented with a provision status similar to "x charged, remaining y not charged", indicating that there are x resource charging objects that have provided a corresponding set amount of resources and y resource charging objects The corresponding set amount of resources has not been provided.
  • a summary interface may be displayed to a local user.
  • the summary interface may include all resource collection objects, a set amount corresponding to each resource collection object, and whether each resource collection object has provided a corresponding set amount Resources etc.
  • a resource collection reminder message may be automatically sent to resource collection objects that do not provide the set amount of resources on a regular basis to remind them to provide related resources as soon as possible.
  • the sending cycle of the resource collection reminder message can be the default cycle or a custom cycle set for the user at the end. This specification does not limit this.
  • a resource collection reminder message in response to a trigger operation by a local user, may be sent to a resource collection object that does not provide the set amount of resources. For example, for resource collection objects that have not yet provided the set amount of resources, corresponding reminder options may be shown; when a certain reminder option is selected, it may be determined that the local user has implemented a trigger operation on the corresponding resource collection object, A resource collection reminder message needs to be sent to the resource collection object.
  • the resource collection function of the resource collection request may be automatically terminated to avoid repeated resource provision. loss.
  • the resource collection function of the resource collection request may be automatically terminated after the validity period of the resource collection request has passed.
  • the validity period can be the default duration, or a custom duration set by the local user.
  • the resource collection function of the resource collection request may be actively terminated. For example, when most resources are charged, the local user can stop charging the remaining resources based on the termination instruction.
  • FIG. 4 is a flowchart of yet another resource collection method provided by an exemplary embodiment. As shown in FIG. 4, this method is applied to electronic devices (such as mobile phones 13 to 15 shown in FIG. 1, etc.), and may include the following steps:
  • Step 402 displaying the communication interface corresponding to the group.
  • Step 404 When the resource collection function in the communication interface is triggered, a resource collection editing interface is displayed, and the resource collection editing interface includes object configuration options.
  • Step 406 In response to the trigger operation on the object configuration option, display an object configuration interface, where the object configuration interface includes group members of the group.
  • the local user can charge a set amount of resources from the resource charging object through the technical solution of this specification.
  • the local user can provide physical or virtual goods to the resource collection object and charge the resource equivalent to the resource collection object; for example, the local user can advance a set amount for the resource collection object in advance Resources, and then collect the set amount of resources from the resource collection object; of course, the local user can also collect the set amount of resources from the resource collection object for other reasons, and this specification does not limit this.
  • the resource charging object may include an associated user of the local user, that is, a user who is associated with the local user.
  • the associated user may include a contact selected by the local user from the address book (in-app address book and / or local address book of the electronic device); for another example, the associated user may include the local user from the group where the user is located Selected group members; for another example, the associated users may include group members selected by the local user from the organizational structure of the group to which they belong. In short, as long as the local user can learn about the associated user, he can add it as a resource collection target.
  • the number of resource collection objects may be one or more, depending on the actual needs and conditions of the local user.
  • the local user when the client of the application is running on the electronic device, the local user can implement the technical solution of this specification through the resource collection function provided by the client.
  • the application may provide one or more trigger portals for the resource charging function, such as the trigger portal built into the group in this embodiment. If the resource collection function is triggered in the group where the local user is located, all group members except the local user can be added as resource collection objects, or the local user can select among the group members, and One or more group members selected by the local user are added as resource collection targets.
  • Step 408 Send a communication message including a resource collection request through the communication session corresponding to the group; wherein the communication message is only visible to the group members selected as resource collection objects, or the communication message is available to all groups All members are visible but only the group members selected as resource collection targets can trigger.
  • any group member when a communication message can be triggered for any group member, it can be understood that: any group member can provide a set amount of resources to the local user through the communication message; and when the communication message is not available for any group member When triggered, it can be understood that any group member cannot provide a set amount of resources to the local user through the communication message. For example, any group member does not respond after clicking the communication message, or the group member only clicks the communication message. You can view the total amount of resources to be collected, the set amount corresponding to each resource collection object, and the resource provision status of each resource collection object (provided or not yet provided), but any group member cannot provide resources by itself.
  • the resource collection request can set the resource amount for the resource collection object (that is, the set amount above), and the resource collection object can trigger the resource collection request And quickly provide a set amount of resources to local users.
  • the resource collection request can serve as a reminder to the resource collection object, which helps to improve the resource collection efficiency.
  • a reminder message including the resource charging request may be sent to the resource charging object based on the name of the local user.
  • the reminder message is different from the communication session message and is specifically used to realize the reminder function
  • the reminder intensity of the above communication session message can enable the resource charging object to view the resource charging request as soon as possible and provide a set amount of resources.
  • the reminder message may include one or more of in-app messages, short messages, and voice announcement messages after the phone is connected. This specification does not limit this.
  • the resource collection request may be sent through the above-mentioned communication session message and reminder message at the same time.
  • the set amount may be the average amount of resources to be collected set by the local user to the average amount after each resource collection object. Taking resources as money for example, the total amount of resources to be collected is the total amount of money to be received m.
  • the set amount may be a set amount for each resource charging object for the local user; in other words, the set amount corresponding to each resource charging object may be independent of each other.
  • the resource collection request may include remark information added by the local user, so that the local user and the resource collection object can understand the relevant information of the resource collection request. On the one hand, it can be distinguished from other resource collection requests. On the one hand, it can help the resource collection object determine whether to trigger a response to the resource collection request.
  • the remark information may include the reason for collecting the resource required by the resource collection request, the method for setting the amount, and the basis for setting the amount. The disclosure does not limit this.
  • the local user can be provided with alternative options, so that the selected alternative can be quickly added as remark information; or, the local user can set custom remark information.
  • the local user may be shown the status of the resources provided by each resource charging object for the set amount of resources.
  • the local user may be presented with a provision status similar to "XXX paid" to indicate that the resource collection target "XXX" has provided a corresponding set amount of resources.
  • a local user may be presented with a provision status similar to "x charged, remaining y not charged", indicating that there are x resource charging objects that have provided a corresponding set amount of resources and y resource charging objects The corresponding set amount of resources has not been provided.
  • a summary interface may be displayed to a local user.
  • the summary interface may include all resource collection objects, a set amount corresponding to each resource collection object, and whether each resource collection object has provided a corresponding set amount Resources etc.
  • a resource collection reminder message may be automatically sent to resource collection objects that do not provide the set amount of resources on a regular basis to remind them to provide related resources as soon as possible.
  • the sending cycle of the resource collection reminder message can be the default cycle or a custom cycle set for the user at the end. This specification does not limit this.
  • a resource collection reminder message in response to a trigger operation by a local user, may be sent to a resource collection object that does not provide the set amount of resources. For example, for resource collection objects that have not yet provided the set amount of resources, corresponding reminder options may be shown; when a certain reminder option is selected, it may be determined that the local user has implemented a trigger operation on the corresponding resource collection object, A resource collection reminder message needs to be sent to the resource collection object.
  • the resource collection function of the resource collection request may be automatically terminated to avoid repeated resource provision. loss.
  • the resource collection function of the resource collection request may be automatically terminated after the validity period of the resource collection request has passed.
  • the validity period can be the default duration, or a custom duration set by the local user.
  • the resource collection function of the resource collection request may be actively terminated. For example, when most resources are charged, the local user can stop charging the remaining resources based on the termination instruction.
  • an enterprise communication APP client can be run on the mobile phone used by user A.
  • the enterprise communication APP client can realize the payment collection function, so that user A initiates payment collection to other users, or user A can The payment request initiated by the user responds and pays.
  • FIG. 5 is a schematic diagram of a collection management interface provided by an exemplary embodiment; the enterprise communication APP client may present a collection management interface 500 as shown in FIG. 5 on the mobile phone, so that user A can Manage your own collection events.
  • the collection management interface 500 may display the "receipt balance" of the user A, that is, the user A's account balance in the "corporate communication app", such as "66.66 yuan” shown in FIG. 5.
  • the collection management interface 500 can display the total number and total amount of payments received by user A in history, such as "26 pens” and “1666.66 yuan” shown in FIG. 5.
  • the collection management interface 500 may include tabs such as "I initiated” and "I participated” to record the collection events initiated or participated by user A, respectively; wherein, the collection events initiated by user A It is used to collect money from other users, and the collection event that User A participates in is used to pay money to other users. User A can switch between different tabs according to his own viewing needs.
  • the collection events initiated by user A are displayed in reverse order from top to bottom according to the occurrence time; for example, in “2018-09-16 "12:32" initiated the collection event, the total amount required to be collected is 360 yuan, and there are still 2 people who have not paid the relevant payment, so the status of the collection event is "receiving”; for example, in " In the collection event initiated at 13:15, 2018-09-12, user A notes the collection event as "lunch", which is different from the default “collection", so that other users can quickly understand the related events of the collection event The reason is that the total amount of money required for the collection event is 180 yuan, and all payments have been received, so the status of the collection event is "collected”; for example, in “2018-09-06 18: 33 ”In the collection event initiated, the total amount of money required is 240 yuan. Although there is still one person who has not paid the relevant amount, due to the validity period of the collection event
  • the collection management interface 500 includes an initiation collection option 501, and user A can create and initiate a new collection event by triggering the initiation collection option 501.
  • FIG. 6 is a schematic diagram of a collection object selection interface provided by an exemplary embodiment; in response to user A ’s trigger operation on the above-mentioned initiating payment option 501, the enterprise communication APP client may show user A as shown in FIG. 6 The payment object selection interface 600 is displayed to select the payment object of the payment event to be created.
  • any user who has any association with user A may be selected as the above-mentioned collection object.
  • the collection object may include the "corporate communication app friend" shown in FIG. 6, that is, a user who has a friend relationship with the user A in the "corporate communication app”; for another example, the collection object may include the one shown in FIG.
  • the payment object may include the "Group”, that is, the group that user A is in the "corporate communication app", user A can select any group, add all group members of the group as the recipient of the payment, or user A can further The group members of the group are filtered so that some of the group members are added as collection objects, where the group can be an internal group of user A ’s group “enterprise AA”, between enterprise AA and other enterprises This group does not limit cooperation groups, external groups that are not related to the enterprise AA; for example, the recipients may include employees of the enterprise AA, even if these employees and the user A are not "friends of enterprise communication APP" , There is no contact information in the "Mobile Address Book” and it is not in the same group as User A, but by showing the organization structure of the enterprise AA in the payment object selection interface 600, User A can be in the organization Any employee in the AA
  • FIG. 7 is a schematic diagram of a collection event editing interface provided by an exemplary embodiment. After user A confirms the desired payment object in the payment object selection interface 600, he can switch to the payment event editing interface 700 shown in FIG. 7 by triggering the determination option shown in FIG. Edit the collection event.
  • the collection event editing interface 700 may include a total amount configuration option 701, and the user A may fill in the total amount of money to be received, such as 300 yuan.
  • the collection event editing interface 700 may include a total number of people configuration option 702, which may show the total number of collection objects selected by user A through the collection object selection interface 600, such as "15 people" shown in FIG. 7; of course, user A You can also re-enter the payment object selection interface 600 by triggering the total number of people configuration option 702 to edit the payment object.
  • the collection event editing interface 700 may include a remarks editing option 703, and user A may fill in the remark information of the collection event that needs to be created, so that the collection object can clearly understand the relevant information of the collection event. For example, when user A advances the lunch fee, user A can add the note information as "lunch" through the note editing option 703, so that the recipient object understands that the payment event is to charge the lunch fee.
  • pre-defined alternative remark information can also be shown in remark editing option 703, such as "meal”, “party”, “water and electricity bill” and other common remark information, and can also be calculated
  • User A customizes the remark information to be filled in, and adds the remark information with high frequency to user A's personalized common remark information and displays it as the above alternative remark information, so that user A can quickly add remark information that meets his needs.
  • the collection event editing interface 700 may include a type switching option 704, so that after the collection event is created, a collection request message can be sent to the collection object based on the conventional message type or reminder message type.
  • the type switching option 704 When the type switching option 704 is in the closed state shown in FIG. 7, the enterprise communication APP client may send a payment request message according to a conventional message type, for example, the conventional message type may include an instant messaging message type.
  • FIG. 8 is a schematic diagram of a configuration reminder method provided by an exemplary embodiment; when the type switching option 704 is in an open state as shown in FIG.
  • the enterprise communication APP client may show multiple alternative sending methods, For example, “in-app”, “SMS”, “phone”, etc .;
  • the message type corresponding to the "in-app” method is the instant messaging type, that is, the recipient of the payment can receive the instant messaging type in the enterprise communication APP client Reminder message, the reminder message contains the payment request, of course, the reminder message based on the instant messaging type and the conventional message have a different display form, so that the reminder message can still play a better reminder effect, assist the recipient quickly Payment;
  • the message type corresponding to the "SMS” method is the SMS type, that is, the recipient can receive a reminder message of the SMS type, and the reminder message contains the payment request;
  • the message type corresponding to the "Phone” method is the call type, that is, receiving
  • the payment object can receive the phone call request and listen to the call voice related to the payment request after being connected.
  • User A can choose to use multiple types of reminder messages at the same time to improve the reminder level of the recipient, and this manual does
  • the user A may choose to send a payment request message to the payment recipient based on the regular message type and the reminder message type at the same time, which is not limited in this specification. Specifically, after the user A opens the type switching option 704 and selects the type of reminder message to be adopted, the enterprise communication APP client will send a payment request message to the payment recipient based on the conventional message type and the reminder message type, respectively.
  • the enterprise communication APP client can automatically calculate the payment required for each collection object, that is, FIG. 7-
  • the "per capita payment” shown in 8 for example, when the total amount is 300 yuan and the total number of people is 15, the per capita payment is 20 yuan.
  • the collection event editing interface 700 may include a payment method switching option 705, which may be used to switch the payment method, so that the enterprise communication APP client calculates the payment required by each payment object in different ways. For example, FIG.
  • FIG. 9 is a schematic diagram of another collection event editing interface provided by an exemplary embodiment; in response to the user A triggering the payment mode switching option 705, the enterprise communication APP client can switch to the collection event editing Interface 900, the collection event editing interface 900 is distinguished from the use of per capita payment as the payment required for each payment object in Figure 7-8, and user A configures the payment required for each payment object separately .
  • FIG. 10 is a schematic diagram of a payment configuration interface provided by an exemplary embodiment.
  • the enterprise communication APP client can switch to the payment configuration interface 1000 as shown in FIG. 10, and the user A sets its own for each payment object
  • the amount of money to be paid is 20 yuan, while user C and user F are 10 yuan.
  • the collection event editing interface 900 may include a remarks editing option 902, which is equivalent to the remarks editing option 703 in the collection event editing interface 700, which will not be repeated here.
  • the collection event editing interface 900 may include a type switching option 903, which is equivalent to the type switching option 704 in the collection event editing interface 700, which will not be repeated here.
  • the collection event editing interface 900 may include a payment method switching option 704, so that user A can switch to the payment method shown in FIGS. 7-8 according to this, that is, by setting the total amount and total number of people to determine The amount of money to be paid by each recipient.
  • FIG. 11 is a schematic diagram of a group communication session interface on an initiator side provided by an exemplary embodiment. Assuming that the payment objects selected by user A are all in the same created group "Eat on Time”, after User A creates the corresponding payment event through Figure 7-8 or Figure 9, you can "Eat on Time” through this group
  • the corresponding communication session sends a corresponding payment request, for example, the enterprise communication APP client can display the group communication session interface 1100 shown in FIG. 11 to user A, which contains the payment request message 1101 corresponding to the sent payment request .
  • FIG. 12 is a schematic diagram of a payment notification to a payment object provided by an exemplary embodiment.
  • the electronic communication device client used by the user C can run the enterprise communication APP client, and the enterprise communication APP client can show the communication entry list interface 1200 shown in FIG. 12 to the user C.
  • the communication entry list interface 1200 is used to display each communication An interface entry corresponding to a session.
  • the interface entry is used to enter a communication session interface corresponding to a communication session.
  • the interface entry 1201 is used to enter the group communication session interface 1100 shown in FIG.
  • the interface entrance 1201 occupies a certain display area on the communication entrance list interface 1200, and the display area can display an avatar, name, preview content of the latest communication message of the group, and the communication message And other information. Then, when receiving the above payment request message 1101 sent by user A, the interface entrance 1201 can display the corresponding preview content as "you need to pay 10.00 yuan", etc., and can indicate the preview through "[Bill to be paid]”
  • the communication message corresponding to the content belongs to the type of "bill", that is, "receipt request”.
  • the interface entry 1201 may display a digital identifier "1", indicating that there is still an unread message, and the value of the digital identifier may vary with the number of unread messages.
  • FIG. 13 is a schematic diagram of a group communication session interface on a payment object side provided by an exemplary embodiment.
  • the group communication session interface 1300 shown in FIG. 13 can be switched to.
  • the group communication session interface 1300 may show a payment request message 1301, corresponding to the above payment request message 1101 sent by the user A, for the user C to make payment for the money received by the user A.
  • FIG. 14 is a schematic diagram of a payment interface provided by an exemplary embodiment; in response to the user C triggering the payment request message 1301, the user may switch to the payment interface 1400 shown in FIG.
  • the initiator of the payment request is user A, the note is “lunch”, and the payment to be paid is 10 yuan, and user C only needs to click the "pay now” option to trigger the payment operation, which is used by user C to user A Pay 10 yuan.
  • the group communication session interface 1300 may include a payment prompt box 1302, which is fixedly displayed above the interface, and the payment prompt box 1302 is displayed suspended in the communication session message in the group communication session interface 1300 Above, even if the payment request message 1301 scrolls out of the screen of the electronic device used by user C due to other communication session messages, it will not affect the display of the payment prompt box 1302, which can prevent user C from ignoring the receipt The payment request message 1301 causes user A to fail to receive the payment. By triggering the payment prompt box 1302, it is also possible to switch to the payment interface 1400 to complete the payment, which will not be repeated here.
  • user A may receive a corresponding payment completion prompt.
  • a payment completion prompt message 1102 may be displayed on the group communication session interface 1100 to indicate that user C has completed the payment; similarly, when other payment recipients complete the payment, the group communication session interface 1100 may also A corresponding prompt message can be shown.
  • the group communication session interface 1100 may also display a remaining money reminder message 1103, indicating the amount of money that has not yet been collected from all the money to be collected in the collection request message 1101; for example, after user C completes the payment, due to User A itself does not need to actually perform the payment operation, so user B and users D to F have not yet completed the payment, so the content of the remaining money reminder message 1103 may include "you still have 4 uncollected payments.”
  • the enterprise communication APP client may display the payment details interface 1500 shown in FIG. 15 to address the payment situation Show details.
  • the payment details interface 1500 can display the paid and unpaid status of the collection event, for example, user A and user C belong to “paid”, and user B and users D to F belong to unpaid , And can show the amount of money corresponding to each payment object.
  • a reminder option 1501 can be shown in the payment details interface 1500, so that user A can quickly target the payment object that has not yet completed the payment (user B and users D to F) send reminder messages to remind them to complete the payment as soon as possible.
  • the payment details interface 1500 may include a stop payment option 1502, and user A may trigger the stop payment option 1502 to make the payment request message received by the payment object (such as the payment request message 1301) ),
  • the payment prompt box (such as the payment prompt box 1302) is invalid, then the payment objects such as user B and users D to F that have not yet completed the payment will not be able to complete the payment by triggering the payment request message or the payment prompt box, and user A Nor can it continue to complete the collection through the collection event corresponding to the collection details interface 1500 unless user A recreates a new collection event.
  • 16 is a schematic diagram of a personal communication session interface provided by an exemplary embodiment; taking user C as an example, an enterprise communication APP client can initiate a payment request through a communication session between user A and user C, such as The corresponding payment request message 1601 may be displayed in the communication session interface 1600. Similar to the above embodiment, user C can obtain the prompt shown in FIGS. 12-13 and complete the payment, while user A can view the payment completion prompt message 1602 and the remaining amount prompt message 1603, which is equivalent to the above payment completion prompt The message 1102 or the remaining money reminder message 1103 will not be repeated here.
  • FIG. 17 is a schematic diagram of an update collection management interface provided by an exemplary embodiment.
  • the collection management interface 1700 may update and display the corresponding event information 1701.
  • the event information 1701 may include: The collection event is initiated at "2018-09-19 13:32", The total amount of money required to be collected is 100 yuan.
  • User A notes the collection event as "lunch”, which is different from the default "collection", and there are still 4 people who have not paid the relevant payment, so the status of the collection event is "Under payment”.
  • FIG. 18 is a schematic diagram of creating a collection event in a group communication session interface provided by an exemplary embodiment.
  • the function option window at the bottom can be invoked by triggering the " ⁇ +" mark, and the function option window contains function options corresponding to several functions , For user A to select and trigger.
  • the collection creation function can be triggered so that the enterprise communication APP client can switch to the collection event editing interface 700 shown in FIGS.
  • FIG. 19 is a schematic structural diagram of a device provided by an exemplary embodiment. Please refer to FIG. 19.
  • the device includes a processor 1902, an internal bus 1904, a network interface 1906, a memory 1908, and a non-volatile memory 1910. Of course, it may include hardware required for other services.
  • the processor 1902 reads the corresponding computer program from the non-volatile memory 1910 into the memory 1908 and then runs it to form a resource collection device at a logical level.
  • one or more embodiments of this specification do not exclude other implementations, such as logic devices or a combination of hardware and software, etc., that is to say, the execution body of the following processing flow is not limited to each
  • the logic unit may also be a hardware or logic device.
  • the resource collection device shown in FIG. 19 may include:
  • the determination unit 2001 determines the resource collection target
  • the sending unit 2002 sends a resource collection request to the resource collection object to charge the resource collection object with a set amount of resources.
  • the resource charging object includes: one or more associated users of the local user.
  • the associated users include at least one of the following:
  • the resource collection object includes multiple associated users of the local user, and the multiple associated users belong to at least two user sets, where the user set includes at least one of the following: the organizational structure of the group to which the local user belongs Group members in the group, group members in the group where the local user is located, and contacts in the address book.
  • the determining unit 2001 is specifically used to:
  • the sending unit 2002 is specifically used to:
  • the set amount is the average amount of resources to be collected set by the end user to the average amount after each resource collection object;
  • the set amount is the amount set by the local user for each resource collection object.
  • the resource charging request includes remark information added by the local user.
  • Optional also includes:
  • the display unit 2003 displays the supply status of each resource collection object to the set amount of resources.
  • Optional also includes:
  • the reminder unit 2004 periodically or in response to the trigger operation of the local user, sends a resource collection reminder message to the resource collection object that does not provide the set amount of resources.
  • Optional also includes:
  • Termination unit 2005 after the resource collection request has been triggered by the resource collection object to provide the set amount of resources, the validity period of the resource collection request has expired, or the termination instruction issued by the local user is received, then terminate The resource collection function of the resource collection request.
  • the resource includes a general equivalent; or, the resource may include any other type of entity or virtual item, which is not limited in this specification.
  • the resource collection device shown in FIG. 19 may include:
  • the first display unit 2101 displays an resource collection and editing interface, and the resource collection and editing interface includes object configuration options;
  • the second display unit 2102 in response to the trigger operation on the object configuration option, displays an object configuration interface, where the object configuration interface includes an associated user of the local user;
  • the sending unit 2103 takes the selected associated user in the object configuration interface as a resource collection object, and sends a resource collection request to the resource collection object to charge the resource collection object with a set amount of resources.
  • the resource collection device shown in FIG. 19 may include:
  • the first display unit 2201 displays the communication interface corresponding to the group
  • the second display unit 2202 when the resource collection function in the communication interface is triggered, displays a resource collection editing interface, the resource collection editing interface includes object configuration options;
  • a third display unit 2203 in response to a trigger operation on the object configuration option, displaying an object configuration interface, where the object configuration interface includes group members of the group;
  • the sending unit 2204 sends a communication message including a resource collection request through a communication session corresponding to the group; wherein, the communication message is only visible to the group members selected as resource collection objects, or the communication message is available to all groups Group members are visible but only group members selected as resource collection targets can trigger.
  • the system, device, module or unit explained in the above embodiments may be specifically implemented by a computer chip or entity, or by a product having a certain function.
  • a typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email sending and receiving device, and a game control Desk, tablet computer, wearable device, or any combination of these devices.
  • the computer includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.
  • processors CPUs
  • input / output interfaces output interfaces
  • network interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-permanent memory, random access memory (RAM) and / or non-volatile memory in computer-readable media, such as read only memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
  • RAM random access memory
  • ROM read only memory
  • flash RAM flash memory
  • Computer-readable media including permanent and non-permanent, removable and non-removable media, can store information by any method or technology.
  • the information may be computer readable instructions, data structures, modules of programs, 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 technologies, read-only compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, Magnetic cassette tapes, magnetic disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices.
  • computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.
  • first, second, third, etc. may use the terms first, second, third, etc. to describe various information, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as second information, and similarly, the second information may also be referred to as first information.
  • word "if” as used herein may be interpreted as "when” or “when” or “in response to a determination”.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Human Computer Interaction (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本说明书一个或多个实施例提供一种资源收取方法及装置，该方法可以包括：确定资源收取对象，所述资源收取对象包括本端用户的一个或多个关联用户，所述关联用户包括以下至少之一：从本端用户所属团体的组织架构中选取的一个或多个团体成员、从本端用户所处群组中选取的一个或多个群组成员、从通讯录中选取的一个或多个联系人；向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。

Description

资源收取方法及装置
本申请要求2018年10月17日递交的申请号为201811207191.3、发明名称为“资源收取方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本说明书一个或多个实施例涉及终端技术领域，尤其涉及一种资源收取方法及装置。
背景技术
在相关技术中，业务的实现过程往往涉及资源交互，比如数据资源、带宽资源、流量资源、凭证资源等，以适用于相应类型的业务场景。例如，用户A通过向用户B提供资源，以完成相关业务。再例如，对于多个用户分别参与的多个业务，可以对这些业务进行合并，使得某一用户可以通过自身拥有的资源来完成合并后的业务，并在业务完成后由该用户向其他用户收取相应的资源，从而能够有效提升业务的完成效率。
发明内容
有鉴于此，本说明书一个或多个实施例提供一种资源收取方法及装置。
为实现上述目的，本说明书一个或多个实施例提供技术方案如下：
根据本说明书一个或多个实施例的第一方面，提出了一种资源收取方法，包括：
确定资源收取对象，所述资源收取对象包括本端用户的一个或多个关联用户，所述关联用户包括以下至少之一：从本端用户所属团体的组织架构中选取的一个或多个团体成员、从本端用户所处群组中选取的一个或多个群组成员、从通讯录中选取的一个或多个联系人；
向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
根据本说明书一个或多个实施例的第二方面，提出了一种资源收取方法，包括：
展示资源收取编辑界面，所述资源收取编辑界面包含对象配置选项；
响应于对所述对象配置选项的触发操作，展示对象配置界面，所述对象配置界面中包含本端用户的关联用户；
将所述对象配置界面中被选取的关联用户作为资源收取对象，并向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
根据本说明书一个或多个实施例的第三方面，提出了一种资源收取方法，包括：
展示群组对应的通讯界面；
当所述通讯界面中的资源收取功能被触发时，展示资源收取编辑界面，所述资源收取编辑界面包含对象配置选项；
响应于对所述对象配置选项的触发操作，展示对象配置界面，所述对象配置界面中包含所述群组的群组成员；
通过所述群组对应的通讯会话发送包含资源收取请求的通讯消息；其中，所述通讯消息仅对被选取为资源收取对象的群组成员可见，或者所述通讯消息对所有群组成员均可见但仅被选取为资源收取对象的群组成员可触发。
根据本说明书一个或多个实施例的第四方面，提出了一种资源收取方法，包括：
确定资源收取对象；
向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
根据本说明书一个或多个实施例的第五方面，提出了一种资源收取方法，包括：
确定资源收取对象，所述资源收取对象包括本端用户的多个关联用户，所述多个关联用户属于至少两个用户集合，其中，所述用户集合包括以下至少之一：本端用户所属团体的组织架构中的团体成员、本端用户所处群组中的群组成员、通讯录中的联系人；
向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
根据本说明书一个或多个实施例的第六方面，提出了一种资源收取装置，包括：
确定单元，确定资源收取对象，所述资源收取对象包括本端用户的一个或多个关联用户，所述关联用户包括以下至少之一：从本端用户所属团体的组织架构中选取的一个或多个团体成员、从本端用户所处群组中选取的一个或多个群组成员、从通讯录中选取的一个或多个联系人；
发送单元，向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
根据本说明书一个或多个实施例的第七方面，提出了一种资源收取装置，包括：
第一展示单元，展示资源收取编辑界面，所述资源收取编辑界面包含对象配置选项；
第二展示单元，响应于对所述对象配置选项的触发操作，展示对象配置界面，所述对象配置界面中包含本端用户的关联用户；
发送单元，将所述对象配置界面中被选取的关联用户作为资源收取对象，并向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
根据本说明书一个或多个实施例的第八方面，提出了一种资源收取装置，包括：
第一展示单元，展示群组对应的通讯界面；
第二展示单元，当所述通讯界面中的资源收取功能被触发时，展示资源收取编辑界面，所述资源收取编辑界面包含对象配置选项；
第三展示单元，响应于对所述对象配置选项的触发操作，展示对象配置界面，所述对象配置界面中包含所述群组的群组成员；
发送单元，通过所述群组对应的通讯会话发送包含资源收取请求的通讯消息；其中，所述通讯消息仅对被选取为资源收取对象的群组成员可见，或者所述通讯消息对所有群组成员均可见但仅被选取为资源收取对象的群组成员可触发。
根据本说明书一个或多个实施例的第九方面，提出了一种资源收取装置，包括：
确定单元，确定资源收取对象；
发送单元，向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
根据本说明书一个或多个实施例的第十方面，提出了一种资源收取装置，包括：
确定单元，确定资源收取对象，所述资源收取对象包括本端用户的多个关联用户，所述多个关联用户属于至少两个用户集合，其中，所述用户集合包括以下至少之一：本端用户所属团体的组织架构中的团体成员、本端用户所处群组中的群组成员、通讯录中的联系人；
发送单元，向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
附图说明
图1是一示例性实施例提供的一种资源收取系统的架构示意图；
图2是一示例性实施例提供的一种资源收取方法的流程图；
图3是一示例性实施例提供的另一种资源收取方法的流程图；
图4是一示例性实施例提供的又一种资源收取方法的流程图；
图5是一示例性实施例提供的一种收款管理界面的示意图；
图6是一示例性实施例提供的一种收款对象选择界面的示意图；
图7是一示例性实施例提供的一种收款事件编辑界面的示意图；
图8是一示例性实施例提供的一种配置提醒方式的示意图；
图9是一示例性实施例提供的另一种收款事件编辑界面的示意图；
图10是一示例性实施例提供的一种款项配置界面的示意图；
图11是一示例性实施例提供的一种发起方侧的群组通讯会话界面的示意图；
图12是一示例性实施例提供的一种向收款对象进行收款提示的示意图；
图13是一示例性实施例提供的一种收款对象侧的群组通讯会话界面的示意图；
图14是一示例性实施例提供的一种付款界面的示意图；
图15是一示例性实施例提供的一种收款详情界面的示意图；
图16是一示例性实施例提供的一种个人通讯会话界面的示意图；
图17是一示例性实施例提供的一种更新收款管理界面的示意图；
图18是一示例性实施例提供的一种在群组通讯会话界面中创建收款事件的示意图；
图19是一示例性实施例提供的一种设备的结构示意图；
图20是一示例性实施例提供的一种资源收取装置的框图；
图21是一示例性实施例提供的另一种资源收取装置的框图；
图22是一示例性实施例提供的又一种资源收取装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本说明书一个或多个实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本说明书一个或多个实施例的一些方面相一致的装置和方法的例子。
需要说明的是：在其他实施例中并不一定按照本说明书示出和描述的顺序来执行相应方法的步骤。在一些其他实施例中，其方法所包括的步骤可以比本说明书所描述的更多或更少。此外，本说明书中所描述的单个步骤，在其他实施例中可能被分解为多个步骤进行描述；而本说明书中所描述的多个步骤，在其他实施例中也可能被合并为单个步骤进行描述。
图1是一示例性实施例提供的一种资源收取系统的架构示意图。如图1所示，该系统可以包括服务器11、网络12、若干电子设备，比如手机13、手机14和手机15等。
服务器11可以为包含一独立主机的物理服务器，或者该服务器11可以为主机集群承载的虚拟服务器。在运行过程中，服务器11可以运行某一应用的服务器侧的程序，以实现为该应用的服务端。而在本说明书一个或多个实施例的技术方案中，可由服务器11通过与手机13-15上运行的客户端进行配合，以实现资源收取方案。
手机13-15只是用户可以使用的一种类型的电子设备。实际上，用户显然还可以使用诸如下述类型的电子设备：平板设备、笔记本电脑、掌上电脑(PDAs，Personal Digital Assistants)、可穿戴设备(如智能眼镜、智能手表等)等，本说明书一个或多个实施例并不对此进行限制。在运行过程中，该电子设备可以运行某一应用的客户端侧的程序，以实现为该移动化团体办公平台的客户端。
需要指出的是：客户端的应用程序可以被预先安装在电子设备上，使得该客户端可以在该电子设备上被启动并运行；当然，当采用诸如HTML5技术的在线“客户端”时，无需在电子设备上安装相应的应用程序，即可获得并运行该客户端。
而对于手机13-15与服务器11之间进行交互的网络12，可以包括多种类型的有线或无线网络。在一实施例中，该网络12可以包括公共交换电话网络(Public Switched Telephone Network，PSTN)和因特网。
图2是一示例性实施例提供的一种资源收取方法的流程图。如图2所示，该方法应用于电子设备(例如图1所示的手机13～15等)，可以包括以下步骤：
步骤202，确定资源收取对象。
在一实施例中，本端用户通过本说明书的技术方案可以向资源收取对象收取设定数额的资源。例如，本端用户可以向该资源收取对象提供了实体或虚拟类型的货品，并向资源收取对象收取对等的资源；再例如，本端用户可以预先替该资源收取对象垫付了设定数额的资源，并在此后向资源收取对象收取该设定数额的资源；当然，本端用户还可以基于其他原因而向该资源收取对象收取设定数额的资源，本说明书并不对此进行限制。
在一实施例中，所述资源收取对象可以包括本端用户的关联用户，即与该本端用户存在关联的用户。例如，关联用户可以包括本端用户从通讯录(应用内通讯录和/或电子设备的本地通讯录)中选取的联系人；再例如，关联用户可以包括本端用户从自身所处群组中选取的群组成员；又例如，关联用户可以包括本端用户从自身所属团体的组织架构中选取的团体成员。总之，只要本端用户能够获知该关联用户，即可将其添加为资源收取对象。
在一实施例中，资源收取对象的数量可以为一个或多个，这取决于本端用户的实际需求和状况。例如，当资源收取对象的数量为多个时，即资源收取对象包括本端用户的多个关联用户，该多个关联用户可以属于至少两个用户集合，其中，所述用户集合包括以下至少之一：本端用户所属团体的组织架构中的团体成员、本端用户所处群组中的群组成员、通讯录中的联系人等，本说明书并不对此进行限制。
在一实施例中，电子设备上运行应用的客户端时，本端用户可以通过该客户端所提供的资源收取功能，实现本说明书的技术方案。该应用可以提供针对该资源收取功能的一个或多个触发入口，比如独立触发入口或内置于群组中的触发入口等。
例如，当本端用户通过独立触发入口触发上述的资源收取功能时，本端用户可以对所有的关联用户进行选择，以作为资源收取对象。再例如，若在本端用户所处的群组中触发资源收取功能，可以将除本端用户之外的所有群组成员添加为资源收取对象，或者可由本端用户在群组成员中进行选择，并将本端用户选取的一个或多个群组成员添加为资源收取对象。
步骤204，向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
在一实施例中，通过向资源收取对象发送资源收取请求，使得资源收取请求中可以针对资源收取对象设定资源的数额(即上述的设定数额)，且资源收取对象可以通过触发资源收取请求而快速地向本端用户提供设定数额的资源。同时，本端用户向资源收取对象发送资源收取请求时，该资源收取请求可以起到对资源收取对象的提醒作用，有助于提升资源收取效率。
在一实施例中，可以基于本端用户的名义，通过本端用户与所述资源收取对象之间的通讯会话，发送包含所述资源收取请求的通讯会话消息，使得资源收取对象可以接收和查看到该通讯会话消息，并通过触发该通讯会话消息而向本端用户提供该设定数额的资源，使得本端用户顺利收取该设定数额的资源。
在一实施例中，可以基于本端用户的名义向所述资源收取对象发送包含所述资源收取请求的提醒消息，该提醒消息区别于通讯会话消息，专门用于实现提醒作用，可以实现高于上述通讯会话消息的提醒强度，可使资源收取对象尽快查看到资源收取请求、提供设定数额的资源。其中，提醒消息可以包括应用内消息、短信、电话接通后的语音播报消息等形式中的一种或多种，本说明书并不对此进行限制。
在一实施例中，可以同时通过上述的通讯会话消息和提醒消息发送资源收取请求。
在一实施例中，所述设定数额可以为本端用户设定的待收取资源总额平均至每一资源收取对象后的平均数额。以资源为款项为例，待收取资源总额为待收款总额m，当资源收取对象的数量为n时，设定数额为平均数额m/n；更为具体地，如果m＝100、n＝5，那么设定数额为100/5＝20。
在一实施例中，所述设定数额可以为本端用户分别针对每一资源收取对象设定的数额；换言之，各个资源收取对象对应的设定数额可以相互独立。
在一实施例中，资源收取请求中可以包含本端用户添加的备注信息，以便于本端用户和资源收取对象了解该资源收取请求的相关信息，一方面可以区分于其他的资源收取请求，另一方面可以帮助资源收取对象确定是否对该资源收取请求进行触发响应。例如，备注信息可以包括该资源收取请求所需收取资源的事由、数额设定方式、数额设定依据等，本公开并不对此进行限制。其中，可以向本端用户提供备选项，使得被选中的备选项可以被快速添加为备注信息；或者，本端用户可以设置自定义的备注信息。
在一实施例中，可以向本端用户展示各个资源收取对象对所述设定数额的资源的提供状况。例如，可以向本端用户展示类似于“XXX已支付”的提供状况，以表明资源收取对象“XXX”已经提供了相应的设定数额的资源。再例如，可以向本端用户展示类似于“已收取x笔，剩余y笔未收取”的提供状况，表明已有x个资源收取对象提供了相应的设定数额的资源、y个资源收取对象尚未提供相应的设定数额的资源。又例如，可以向本端用户展示汇总界面，该汇总界面中可以包括所有资源收取对象、每一资源收取对象对应的设定数额，以及每一资源收取对象是否已经提供了相应的设定数额的资源等。
在一实施例中，可以定期自动向未提供所述设定数额的资源的资源收取对象发送资源收取提醒消息，以提醒其尽快提供相关资源。资源收取提醒消息的发送周期可以为默认周期，也可以为本端用户设置的自定义周期，本说明书并不对此进行限制。
在一实施例中，可以响应于本端用户的触发操作，向未提供所述设定数额的资源的资源收取对象发送资源收取提醒消息。例如，针对尚未提供所述设定数额的资源的资源收取对象，可以示出相应的提醒选项；当某一提醒选项被选取时，可以确定本端用户对相应的资源收取对象实施了触发操作，需要向该资源收取对象发送资源收取提醒消息。
在一实施例中，可以在所述资源收取请求已被所述资源收取对象触发以提供所述设定数额的资源后，自动终止所述资源收取请求的资源收取作用，避免重复提供资源而造成损失。
在一实施例中，可以在所述资源收取请求的有效期已过后，自动终止所述资源收取请求的资源收取作用。其中，有效期可以为默认时长，或者本端用户设置的自定义时长。
在一实施例中，可以在接收到本端用户发出的终止指令后，主动终止所述资源收取请求的资源收取作用。譬如，在收取了大部分资源的情况下，本端用户可以基于该终止指令而停止收取剩余资源。
在一实施例中，所述资源包括一般等价物；或者，所述资源可以包括其他任意类型的实体或虚拟物品，本说明书并不对此进行限制。
图3是一示例性实施例提供的另一种资源收取方法的流程图。如图3所示，该方法应用于电子设备(例如图1所示的手机13～15等)，可以包括以下步骤：
步骤302，展示资源收取编辑界面，所述资源收取编辑界面包含对象配置选项。
步骤304，响应于对所述对象配置选项的触发操作，展示对象配置界面，所述对象配置界面中包含本端用户的关联用户。
在一实施例中，本端用户通过本说明书的技术方案可以向资源收取对象收取设定数额的资源。例如，本端用户可以向该资源收取对象提供了实体或虚拟类型的货品，并向资源收取对象收取对等的资源；再例如，本端用户可以预先替该资源收取对象垫付了设定数额的资源，并在此后向资源收取对象收取该设定数额的资源；当然，本端用户还可以基于其他原因而向该资源收取对象收取设定数额的资源，本说明书并不对此进行限制。
在一实施例中，所述资源收取对象可以包括本端用户的关联用户，即与该本端用户存在关联的用户。例如，关联用户可以包括本端用户从通讯录(应用内通讯录和/或电子设备的本地通讯录)中选取的联系人；再例如，关联用户可以包括本端用户从自身所处群组中选取的群组成员；又例如，关联用户可以包括本端用户从自身所属团体的组织架构中选取的团体成员。总之，只要本端用户能够获知该关联用户，即可将其添加为资源收取对象。
在一实施例中，资源收取对象的数量可以为一个或多个，这取决于本端用户的实际需求和状况。
在一实施例中，电子设备上运行应用的客户端时，本端用户可以通过该客户端所提供的资源收取功能，实现本说明书的技术方案。该应用可以提供针对该资源收取功能的一个或多个触发入口，比如本实施例中的独立触发入口(区别于内置于群组中的触发入 口等)；当本端用户通过独立触发入口触发上述的资源收取功能时，本端用户可以对所有的关联用户进行选择，以作为资源收取对象。
步骤306，将所述对象配置界面中被选取的关联用户作为资源收取对象，并向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
在一实施例中，通过向资源收取对象发送资源收取请求，使得资源收取请求中可以针对资源收取对象设定资源的数额(即上述的设定数额)，且资源收取对象可以通过触发资源收取请求而快速地向本端用户提供设定数额的资源。同时，本端用户向资源收取对象发送资源收取请求时，该资源收取请求可以起到对资源收取对象的提醒作用，有助于提升资源收取效率。
在一实施例中，可以基于本端用户的名义，通过本端用户与所述资源收取对象之间的通讯会话，发送包含所述资源收取请求的通讯会话消息，使得资源收取对象可以接收和查看到该通讯会话消息，并通过触发该通讯会话消息而向本端用户提供该设定数额的资源，使得本端用户顺利收取该设定数额的资源。
在一实施例中，可以基于本端用户的名义向所述资源收取对象发送包含所述资源收取请求的提醒消息，该提醒消息区别于通讯会话消息，专门用于实现提醒作用，可以实现高于上述通讯会话消息的提醒强度，可使资源收取对象尽快查看到资源收取请求、提供设定数额的资源。其中，提醒消息可以包括应用内消息、短信、电话接通后的语音播报消息等形式中的一种或多种，本说明书并不对此进行限制。
在一实施例中，可以同时通过上述的通讯会话消息和提醒消息发送资源收取请求。
在一实施例中，所述设定数额可以为本端用户设定的待收取资源总额平均至每一资源收取对象后的平均数额。以资源为款项为例，待收取资源总额为待收款总额m，当资源收取对象的数量为n时，设定数额为平均数额m/n；更为具体地，如果m＝100、n＝5，那么设定数额为100/5＝20。
在一实施例中，所述设定数额可以为本端用户分别针对每一资源收取对象设定的数额；换言之，各个资源收取对象对应的设定数额可以相互独立。
在一实施例中，资源收取请求中可以包含本端用户添加的备注信息，以便于本端用户和资源收取对象了解该资源收取请求的相关信息，一方面可以区分于其他的资源收取请求，另一方面可以帮助资源收取对象确定是否对该资源收取请求进行触发响应。例如，备注信息可以包括该资源收取请求所需收取资源的事由、数额设定方式、数额设定依据等，本公开并不对此进行限制。其中，可以向本端用户提供备选项，使得被选中的 备选项可以被快速添加为备注信息；或者，本端用户可以设置自定义的备注信息。
在一实施例中，可以向本端用户展示各个资源收取对象对所述设定数额的资源的提供状况。例如，可以向本端用户展示类似于“XXX已支付”的提供状况，以表明资源收取对象“XXX”已经提供了相应的设定数额的资源。再例如，可以向本端用户展示类似于“已收取x笔，剩余y笔未收取”的提供状况，表明已有x个资源收取对象提供了相应的设定数额的资源、y个资源收取对象尚未提供相应的设定数额的资源。又例如，可以向本端用户展示汇总界面，该汇总界面中可以包括所有资源收取对象、每一资源收取对象对应的设定数额，以及每一资源收取对象是否已经提供了相应的设定数额的资源等。
在一实施例中，可以定期自动向未提供所述设定数额的资源的资源收取对象发送资源收取提醒消息，以提醒其尽快提供相关资源。资源收取提醒消息的发送周期可以为默认周期，也可以为本端用户设置的自定义周期，本说明书并不对此进行限制。
在一实施例中，可以响应于本端用户的触发操作，向未提供所述设定数额的资源的资源收取对象发送资源收取提醒消息。例如，针对尚未提供所述设定数额的资源的资源收取对象，可以示出相应的提醒选项；当某一提醒选项被选取时，可以确定本端用户对相应的资源收取对象实施了触发操作，需要向该资源收取对象发送资源收取提醒消息。
在一实施例中，可以在所述资源收取请求已被所述资源收取对象触发以提供所述设定数额的资源后，自动终止所述资源收取请求的资源收取作用，避免重复提供资源而造成损失。
在一实施例中，可以在所述资源收取请求的有效期已过后，自动终止所述资源收取请求的资源收取作用。其中，有效期可以为默认时长，或者本端用户设置的自定义时长。
在一实施例中，可以在接收到本端用户发出的终止指令后，主动终止所述资源收取请求的资源收取作用。譬如，在收取了大部分资源的情况下，本端用户可以基于该终止指令而停止收取剩余资源。
图4是一示例性实施例提供的又一种资源收取方法的流程图。如图4所示，该方法应用于电子设备(例如图1所示的手机13～15等)，可以包括以下步骤：
步骤402，展示群组对应的通讯界面。
步骤404，当所述通讯界面中的资源收取功能被触发时，展示资源收取编辑界面，所述资源收取编辑界面包含对象配置选项。
步骤406，响应于对所述对象配置选项的触发操作，展示对象配置界面，所述对象配置界面中包含所述群组的群组成员。
在一实施例中，本端用户通过本说明书的技术方案可以向资源收取对象收取设定数额的资源。例如，本端用户可以向该资源收取对象提供了实体或虚拟类型的货品，并向资源收取对象收取对等的资源；再例如，本端用户可以预先替该资源收取对象垫付了设定数额的资源，并在此后向资源收取对象收取该设定数额的资源；当然，本端用户还可以基于其他原因而向该资源收取对象收取设定数额的资源，本说明书并不对此进行限制。
在一实施例中，所述资源收取对象可以包括本端用户的关联用户，即与该本端用户存在关联的用户。例如，关联用户可以包括本端用户从通讯录(应用内通讯录和/或电子设备的本地通讯录)中选取的联系人；再例如，关联用户可以包括本端用户从自身所处群组中选取的群组成员；又例如，关联用户可以包括本端用户从自身所属团体的组织架构中选取的团体成员。总之，只要本端用户能够获知该关联用户，即可将其添加为资源收取对象。
在一实施例中，资源收取对象的数量可以为一个或多个，这取决于本端用户的实际需求和状况。
在一实施例中，电子设备上运行应用的客户端时，本端用户可以通过该客户端所提供的资源收取功能，实现本说明书的技术方案。该应用可以提供针对该资源收取功能的一个或多个触发入口，比如本实施例中内置于群组中的触发入口等。若在本端用户所处的群组中触发资源收取功能，可以将除本端用户之外的所有群组成员添加为资源收取对象，或者可由本端用户在群组成员中进行选择，并将本端用户选取的一个或多个群组成员添加为资源收取对象。
步骤408，通过所述群组对应的通讯会话发送包含资源收取请求的通讯消息；其中，所述通讯消息仅对被选取为资源收取对象的群组成员可见，或者所述通讯消息对所有群组成员均可见但仅被选取为资源收取对象的群组成员可触发。
在一实施例中，当通讯消息对任一群组成员可触发时，可以理解为：该任一群组成员可以通过该通讯消息向本端用户提供设定数额的资源；而当通讯消息对任一群组成员不可触发时，可以理解为：该任一群组成员无法通过该通讯消息向本端用户提供设定数额的资源，比如该任一群组成员点击该通讯消息后没有反应，或者该任一群组成员点击通讯消息后仅能够查看待收取资源的总额、各个资源收取对象对应的设定数额、各个资 源收取对象的资源提供情况(已提供或尚未提供等)，但该任一群组成员自身并不能够提供资源。
在一实施例中，通过向资源收取对象发送资源收取请求，使得资源收取请求中可以针对资源收取对象设定资源的数额(即上述的设定数额)，且资源收取对象可以通过触发资源收取请求而快速地向本端用户提供设定数额的资源。同时，本端用户向资源收取对象发送资源收取请求时，该资源收取请求可以起到对资源收取对象的提醒作用，有助于提升资源收取效率。
在一实施例中，可以基于本端用户的名义向所述资源收取对象发送包含所述资源收取请求的提醒消息，该提醒消息区别于通讯会话消息，专门用于实现提醒作用，可以实现高于上述通讯会话消息的提醒强度，可使资源收取对象尽快查看到资源收取请求、提供设定数额的资源。其中，提醒消息可以包括应用内消息、短信、电话接通后的语音播报消息等形式中的一种或多种，本说明书并不对此进行限制。
在一实施例中，可以同时通过上述的通讯会话消息和提醒消息发送资源收取请求。
在一实施例中，所述设定数额可以为本端用户设定的待收取资源总额平均至每一资源收取对象后的平均数额。以资源为款项为例，待收取资源总额为待收款总额m，当资源收取对象的数量为n时，设定数额为平均数额m/n；更为具体地，如果m＝100、n＝5，那么设定数额为100/5＝20。
在一实施例中，所述设定数额可以为本端用户分别针对每一资源收取对象设定的数额；换言之，各个资源收取对象对应的设定数额可以相互独立。
在一实施例中，资源收取请求中可以包含本端用户添加的备注信息，以便于本端用户和资源收取对象了解该资源收取请求的相关信息，一方面可以区分于其他的资源收取请求，另一方面可以帮助资源收取对象确定是否对该资源收取请求进行触发响应。例如，备注信息可以包括该资源收取请求所需收取资源的事由、数额设定方式、数额设定依据等，本公开并不对此进行限制。其中，可以向本端用户提供备选项，使得被选中的备选项可以被快速添加为备注信息；或者，本端用户可以设置自定义的备注信息。
在一实施例中，可以向本端用户展示各个资源收取对象对所述设定数额的资源的提供状况。例如，可以向本端用户展示类似于“XXX已支付”的提供状况，以表明资源收取对象“XXX”已经提供了相应的设定数额的资源。再例如，可以向本端用户展示类似于“已收取x笔，剩余y笔未收取”的提供状况，表明已有x个资源收取对象提供了相应的设定数额的资源、y个资源收取对象尚未提供相应的设定数额的资源。又例如，可 以向本端用户展示汇总界面，该汇总界面中可以包括所有资源收取对象、每一资源收取对象对应的设定数额，以及每一资源收取对象是否已经提供了相应的设定数额的资源等。
在一实施例中，可以定期自动向未提供所述设定数额的资源的资源收取对象发送资源收取提醒消息，以提醒其尽快提供相关资源。资源收取提醒消息的发送周期可以为默认周期，也可以为本端用户设置的自定义周期，本说明书并不对此进行限制。
在一实施例中，可以响应于本端用户的触发操作，向未提供所述设定数额的资源的资源收取对象发送资源收取提醒消息。例如，针对尚未提供所述设定数额的资源的资源收取对象，可以示出相应的提醒选项；当某一提醒选项被选取时，可以确定本端用户对相应的资源收取对象实施了触发操作，需要向该资源收取对象发送资源收取提醒消息。
在一实施例中，可以在所述资源收取请求已被所述资源收取对象触发以提供所述设定数额的资源后，自动终止所述资源收取请求的资源收取作用，避免重复提供资源而造成损失。
在一实施例中，可以在所述资源收取请求的有效期已过后，自动终止所述资源收取请求的资源收取作用。其中，有效期可以为默认时长，或者本端用户设置的自定义时长。
在一实施例中，可以在接收到本端用户发出的终止指令后，主动终止所述资源收取请求的资源收取作用。譬如，在收取了大部分资源的情况下，本端用户可以基于该终止指令而停止收取剩余资源。
为了便于理解，以企业即时通讯应用“企业通讯APP”为例，针对用户之间的收款过程，对本说明书一个或多个实施例的技术方案进行说明。
以用户A为例，在用户A使用的手机上可以运行有企业通讯APP客户端，该企业通讯APP客户端可以实现收款功能，使得用户A向其他用户发起收款，或者由用户A对其他用户发起的收款请求进行响应、付款。例如，图5是一示例性实施例提供的一种收款管理界面的示意图；企业通讯APP客户端可以在手机上呈现出如图5所示的收款管理界面500，使得用户A可以对与自身相关的收款事件进行管理。
在一实施例中，收款管理界面500可以展示用户A的“收款余额”，即该用户A在“企业通讯APP”中的账户余额，比如图5所示的“66.66元”。收款管理界面500可以展示用户A在历史上一共收到的付款笔数和总额，比如图5所示的“26笔”和“1666.66元”。
在一实施例中，收款管理界面500可以包括“我发起的”和“我参与的”等标签页，以分别记录用户A发起或参与的收款事件；其中，用户A发起的收款事件用于向其他用户收取款项，而用户A参与的收款事件用于向其他用户支付款项，用户A可以根据自身的查看需求，在不同标签页之间进行切换。例如，在图5所示的“我发起的”标签页下，采用列表形式、按照发生时间从上至下倒序排列展示了用户A所发起的收款事件；比如，在“2018-09-16 12:32”发起的收款事件中，所需收取的款项总额为360元，且尚存在2人未支付相关款项，因而该收款事件的状态为“收款中”；再比如，在“2018-09-12 13:15”发起的收款事件中，用户A将该收款事件备注为“午饭”、区别于默认的“收款”，以便于其他用户快速了解该收款事件的相关事由等，该收款事件所需收取的款项总额为180元，且已收到所有款项，因而该收款事件的状态为“已收齐”；又比如，在“2018-09-06 18:33”发起的收款事件中，所需收取的款项总额为240元，虽然尚存在1人未支付相关款项，但由于该收款事件的有效期限(从创建时刻开始的默认时长，或者用户A自定义的时长)已过，因而该收款事件的状态为“已过期”。
在一实施例中，收款管理界面500包括发起收款选项501，用户A可以通过触发该发起收款选项501而创建、发起新的收款事件。图6是一示例性实施例提供的一种收款对象选择界面的示意图；响应于用户A对上述发起收款选项501的触发操作，企业通讯APP客户端可以向用户A展示出如图6所示的收款对象选择界面600，以选取即将创建的收款事件的收款对象。
在一实施例中，任何与用户A存在任意关联的用户，均可以被选取为上述的收款对象。例如，收款对象可以包括图6所示的“企业通讯APP好友”，即在“企业通讯APP”中与该用户A存在好友关系的用户；再例如，收款对象可以包括图6所示的“手机通讯录”，由“企业通讯APP”在用户A的授权下从其使用的手机上的“通讯录”应用中所读取；又例如，收款对象可以包括图6所示的“已有的群”，即用户A在“企业通讯APP”中所处的群组，用户A可以选取任一群组、将该群组的所有群组成员均添加为收款对象，或者用户A可以进一步对该群组的群组成员进行筛选、使得部分群组成员被添加为收款对象，其中该群组可以为用户A的所属团体“企业AA”的内部群组、企业AA与其他企业之间的合作群组、与企业AA无关的外部群组等，本说明书并不对此进行限制；还例如，收款对象可以包括企业AA的员工，即便这些员工与用户A之间并非“企业通讯APP好友”、在“手机通讯录”中不存在其联系人信息、并未与用户A处于同一群 组中，但是通过在收款对象选择界面600中示出该企业AA的组织架构，用户A就可以在该组织架构中查找到该企业AA中的任一员工，从而选择为收款对象。此外，收款对象选择界面600可以按照最近联系时刻、联系次数、联系频率等，示出用户A的常用联系人，比如图6所示的用户B、用户C、用户D等，用户A同样可以将常用联系人选取为收款对象。
图7是一示例性实施例提供的一种收款事件编辑界面的示意图。用户A在收款对象选择界面600中确认所需选择的收款对象后，可以通过触发如图6所示的确定选项而切换至如图7所示的收款事件编辑界面700，以针对该收款事件进行编辑。
在一实施例中，收款事件编辑界面700可以包括总金额配置选项701，用户A可以填写待收款项的总金额，比如300元。收款事件编辑界面700可以包括总人数配置选项702，可以示出用户A通过收款对象选择界面600选取的收款对象的总人数，比如图7所示的“15人”；当然，用户A还可以通过触发该总人数配置选项702，重新进入收款对象选择界面600，以针对收款对象进行编辑。可见，虽然上述实施例中是首先进入收款对象选择界面600对收款对象进行选择，然后进入收款事件编辑界面700，但实际上也可以首先进入收款事件编辑界面700，然后通过总人数配置选项702进入收款对象选择界面600、以针对收款对象进行编辑，本说明书并不对此进行限制。
在一实施例中，收款事件编辑界面700可以包括备注编辑选项703，用户A可以填写所需创建的收款事件的备注信息，以便收款对象能够清楚地了解该收款事件的相关信息。比如，当用户A垫付了午饭费用时，用户A可以通过备注编辑选项703添加备注信息为“午饭”，使得收款对象了解该收款事件是为了收取午饭费用。除了用户A自定义填写备注信息之外，备注编辑选项703中还可以示出预定义的备选备注信息，比如“聚餐”、“聚会”、“水电费”等常用备注信息，还可以通过统计用户A自定义填写的备注信息，将填写频率高的备注信息添加为用户A个性化的常用备注信息、展示为上述的备选备注信息，便于用户A快速添加符合自身需求的备注信息。
在一实施例中，收款事件编辑界面700可以包括类型切换选项704，使得收款事件被创建后，可以基于常规消息类型或提醒消息类型向收款对象发送收款请求消息。当类型切换选项704处于图7所示的关闭状态时，企业通讯APP客户端可以按照常规消息类型发送收款请求消息，比如该常规消息类型可以包括即时通讯消息类型。图8是一示例性实施例提供的一种配置提醒方式的示意图；当类型切换选项704处于如图8所示的开启状态时，企业通讯APP客户端可以示出备选的多种发送方式，比如“应用内”、“短 信”、“电话”等；其中，“应用内”方式对应的消息类型为即时通讯消息类型，即收款对象可以在企业通讯APP客户端中收到即时通讯消息类型的提醒消息，该提醒消息中包含收款请求，当然基于即时通讯消息类型的提醒消息与常规消息具有差异化的展示形式，使得提醒消息仍然能够起到更佳的提醒效果，协助收款对象快速付款；“短信”方式对应的消息类型为短信类型，即收款对象可以收到短信类型的提醒消息，该提醒消息中包含收款请求；“电话”方式对应的消息类型为通话类型，即收款对象可以收到电话呼叫请求，并在接通后收听到与收款请求相关的通话语音。用户A可以选择同时采用多种类型的提醒消息，以提升对收款对象的提醒等级，本说明书并不对此进行限制。
在一实施例中，用户A可以选择同时基于常规消息类型和提醒消息类型向收款对象发送收款请求消息，本说明书并不对此进行限制。具体的，在用户A开启类型切换选项704并选取所需采用的提醒消息类型后，企业通讯APP客户端会分别基于常规消息类型和提醒消息类型向收款对象发送收款请求消息。
在如图7-8所示的收款事件编辑界面700中，通过配置总金额和总人数，使得企业通讯APP客户端可以自动计算出每一收款对象所需支付的款项，即图7-8所示的“人均收款”，比如当总金额为300元、总人数为15人时，人均收款为20元。在一实施例中，收款事件编辑界面700可以包括收款方式切换选项705，可以用于切换收款方式，使得企业通讯APP客户端通过不同方式计算各个收款对象所需支付的款项。例如，图9是一示例性实施例提供的另一种收款事件编辑界面的示意图；响应于用户A对收款方式切换选项705的触发操作，企业通讯APP客户端可以切换至收款事件编辑界面900，该收款事件编辑界面900区别于图7-8中采用人均收款作为每一收款对象所需支付的款项，而由用户A分别针对每一收款对象配置所需支付的款项。
在一实施例中，图10是一示例性实施例提供的一种款项配置界面的示意图。当用户A触发收款事件编辑界面900中的款项编辑选项901时，企业通讯APP客户端可以切换至如图10所示的款项配置界面1000，并由用户A分别针对每一收款对象设置其所需支付的款项的数额，比如用户A、用户B、用户D、用户E等均为20元，而用户C和用户F为10元。
在一实施例中，收款事件编辑界面900可以包括备注编辑选项902，相当于收款事件编辑界面700中的备注编辑选项703，此处不再赘述。
在一实施例中，收款事件编辑界面900可以包括类型切换选项903，相当于收款事件编辑界面700中的类型切换选项704，此处不再赘述。
在一实施例中，收款事件编辑界面900可以包括收款方式切换选项704，使得用户A可以据此切换至图7-8所示的收款方式，即通过设置总金额和总人数而确定每一收款对象所需支付的款项的数额。
图11是一示例性实施例提供的一种发起方侧的群组通讯会话界面的示意图。假定用户A选取的收款对象均处于同一已创建的群组“按时吃饭”，在用户A通过图7-8或图9创建了相应的收款事件后，可以通过该群组“按时吃饭”对应的通讯会话发送相应的收款请求，比如企业通讯APP客户端可以向用户A展示如图11所示的群组通讯会话界面1100，其中包含已发送的收款请求对应的收款请求消息1101。
以作为收款对象的用户C为例，图12是一示例性实施例提供的一种向收款对象进行收款提示的示意图。用户C使用的电子设备上可以运行企业通讯APP客户端，该企业通讯APP客户端可以向用户C展示出如图12所示的通讯入口列表界面1200，该通讯入口列表界面1200用于展示各个通讯会话对应的界面入口，该界面入口用于进入通讯会话对应的通讯会话界面，比如界面入口1201用于进入图11所示的对应于群组“按时吃饭”的群组通讯会话界面1100。
在一实施例中，界面入口1201在通讯入口列表界面1200上占用了一定的展示区域，该展示区域可以展示群组“按时吃饭”的头像、名称、最近一条通讯消息的预览内容、该通讯消息的发生时刻等信息。那么，当收到用户A发送的上述收款请求消息1101时，界面入口1201可以展示出相应的预览内容为“你需支付10.00元”等，并且可以通过“[待支付账单]”表明该预览内容对应的通讯消息属于“账单”、即“收款请求”类型的消息。当该通讯消息尚未被读取时，界面入口1201中可以示出数字标识“①”，表明尚存在一条未读消息，且该数字标识的数值可随未读消息的数量而变化。
图13是一示例性实施例提供的一种收款对象侧的群组通讯会话界面的示意图。响应于用户C对界面入口1201的触发操作，可以切换至如图13所示的群组通讯会话界面1300。在一实施例中，群组通讯会话界面1300可以示出收款请求消息1301，对应于用户A发出的上述收款请求消息1101，以供用户C对用户A所收款项进行付款。例如，图14是一示例性实施例提供的一种付款界面的示意图；响应于用户C对收款请求消息1301的触发操作，可以切换至如图14所示的付款界面1400，可以查看到收款请求的发起者为用户A、备注为“午饭”、待支付款项为10元，而用户C只需要点击“立即支付”选项即可触发支付操作，该支付操作用于由用户C向用户A支付10元。
在一实施例中，群组通讯会话界面1300可以包括支付提示框1302，该支付提示框 1302固定显示于界面上方，并且该支付提示框1302悬浮显示于群组通讯会话界面1300中的通讯会话消息之上，使得即便收款请求消息1301由于其他通讯会话消息而滚动至用户C所使用的电子设备的屏幕之外，也不会影响对该支付提示框1302的显示，可以避免用户C忽略掉收款请求消息1301而造成用户A收款失败。通过对支付提示框1302进行触发，同样可以切换至付款界面1400以完成付款，此处不再赘述。
在一实施例中，当用户C完成支付后，用户A可以收到相应的支付完成提示。例如图11所示，群组通讯会话界面1100中可以示出支付完成提示消息1102，以表明用户C已经完成支付；类似地，当其他收款对象完成支付后，群组通讯会话界面1100中也可以示出相应的提示消息。此外，群组通讯会话界面1100还可以示出剩余款项提示消息1103，表明在收款请求消息1101所需要收取的所有款项中，尚未完成收取的款项数量；比如，在用户C完成支付后，由于用户A自身不需要真的实施支付操作，因而还剩下用户B、用户D～F未完成支付，因而剩余款项提示消息1103的内容可以包括“你还有4笔未收齐的收款”。
图15是一示例性实施例提供的一种收款详情界面的示意图。响应于用户A对收款请求消息1101、支付完成提示消息1102或剩余款项提示消息1103的触发操作，企业通讯APP客户端可以展示如图15所示的收款详情界面1500，以针对收款情况进行详情展示。例如图15所示，收款详情界面1500可以分别针对收款事件的已支付、未支付情况进行展示，比如用户A自己和用户C属于“已支付”、用户B和用户D～F属于未支付，并且可以分别示出各个收款对象对应的款项数额。
在一实施例中，针对尚未完成支付的收款对象，收款详情界面1500中可以示出提醒选项1501，使得用户A可以通过触发该提醒选项1501而快速针对尚未完成支付的收款对象(用户B和用户D～F)发送提醒消息，以提醒其尽快完成支付。
在一实施例中，收款详情界面1500可以包括停止收款选项1502，用户A可以通过触发该停止收款选项1502，使得收款对象所接收到的收款请求消息(如收款请求消息1301)、支付提示框(如支付提示框1302)失效，那么用户B和用户D～F等尚未完成支付的收款对象将无法通过触发该收款请求消息或支付提示框而完成支付，而用户A也无法继续通过收款详情界面1500对应的收款事件完成收款，除非用户A重新创建新的收款事件。
在一实施例中，用户A在创建收款事件时，收款对象并不一定来源于同一群组，那么企业通讯APP客户端可以分别通过用户A与每一收款对象之间的通讯会话，向相应的 收款对象发起收款请求。图16是一示例性实施例提供的一种个人通讯会话界面的示意图；以用户C为例，企业通讯APP客户端可以通过用户A与用户C之间的通讯会话发起收款请求，比如在个人通讯会话界面1600中可以示出对应的收款请求消息1601。与上述实施例相类似的，用户C可以获得如图12-13所示的提示并完成支付，而用户A可以查看到支付完成提示消息1602和剩余款项提示消息1603，相当于上述的支付完成提示消息1102或剩余款项提示消息1103，此处不再一一赘述。
图17是一示例性实施例提供的一种更新收款管理界面的示意图。针对用户A创建的收款事件，收款管理界面1700中可以更新展示出对应的事件信息1701，该事件信息1701可以包括：收款事件的发起时刻为“2018-09-19 13:32”，所需收取的款项总额为100元，用户A将该收款事件备注为“午饭”、区别于默认的“收款”，且尚存在4人未支付相关款项，因而该收款事件的状态为“收款中”。
除了通过在收款管理界面500中通过发起收款选项501而创建收款事件之外，企业通讯APP还可以提供其他的功能入口，以由用户A创建收款事件。例如，图18是一示例性实施例提供的一种在群组通讯会话界面中创建收款事件的示意图。如图18所示，在群组“按时吃饭”的群组通讯会话界面1800中，通过触发“○+”标识可以唤出底部的功能选项窗口，该功能选项窗口中包含若干功能对应的功能选项，以供用户A进行选择和触发。例如，当用户A触发功能选项1801后，可以触发收款创建功能，使得企业通讯APP客户端可以切换至如图7-8的收款事件编辑界面700或如图9所示的收款事件编辑界面900；同时，由于在群组“按时吃饭”的群组通讯会话界面1800中触发功能选项1801，因而此时创建的收款事件的收款对象必须为该群组“按时吃饭”的群组成员。
图19是一示例性实施例提供的一种设备的示意结构图。请参考图19，在硬件层面，该设备包括处理器1902、内部总线1904、网络接口1906、内存1908以及非易失性存储器1910，当然还可能包括其他业务所需要的硬件。处理器1902从非易失性存储器1910中读取对应的计算机程序到内存1908中然后运行，在逻辑层面上形成资源收取装置。当然，除了软件实现方式之外，本说明书一个或多个实施例并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
在一实施例中，请参考图20，在软件实施方式中，图19所示的资源收取装置可以包括：
确定单元2001，确定资源收取对象；
发送单元2002，向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
可选的，所述资源收取对象包括：本端用户的一个或多个关联用户。
可选的，所述关联用户包括以下至少之一：
从本端用户所属团体的组织架构中选取的一个或多个团体成员、从本端用户所处群组中选取的一个或多个群组成员、从通讯录中选取的一个或多个联系人。
可选的，资源收取对象包括本端用户的多个关联用户，所述多个关联用户属于至少两个用户集合，其中，所述用户集合包括以下至少之一：本端用户所属团体的组织架构中的团体成员、本端用户所处群组中的群组成员、通讯录中的联系人。
可选的，所述确定单元2001具体用于：
在本端用户所处的群组中触发资源收取功能；
将除本端用户之外的所有群组成员添加为资源收取对象；或者，将本端用户选取的一个或多个群组成员添加为资源收取对象。
可选的，所述发送单元2002具体用于：
通过本端用户与所述资源收取对象之间的通讯会话，发送包含所述资源收取请求的通讯会话消息；
或者，向所述资源收取对象发送包含所述资源收取请求的提醒消息。
可选的，
所述设定数额为本端用户设定的待收取资源总额平均至每一资源收取对象后的平均数额；
或者，所述设定数额为本端用户分别针对每一资源收取对象设定的数额。
可选的，资源收取请求中包含本端用户添加的备注信息。
可选的，还包括：
展示单元2003，展示各个资源收取对象对所述设定数额的资源的提供状况。
可选的，还包括：
提醒单元2004，定期或响应于本端用户的触发操作，向未提供所述设定数额的资源的资源收取对象发送资源收取提醒消息。
可选的，还包括：
终止单元2005，在所述资源收取请求已被所述资源收取对象触发以提供所述设定数额的资源、所述资源收取请求的有效期已过或接收到本端用户发出的终止指令后，终止 所述资源收取请求的资源收取作用。
可选的，所述资源包括一般等价物；或者，所述资源可以包括其他任意类型的实体或虚拟物品，本说明书并不对此进行限制。
在一实施例中，请参考图21，在软件实施方式中，图19所示的资源收取装置可以包括：
第一展示单元2101，展示资源收取编辑界面，所述资源收取编辑界面包含对象配置选项；
第二展示单元2102，响应于对所述对象配置选项的触发操作，展示对象配置界面，所述对象配置界面中包含本端用户的关联用户；
发送单元2103，将所述对象配置界面中被选取的关联用户作为资源收取对象，并向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
在一实施例中，请参考图22，在软件实施方式中，图19所示的资源收取装置可以包括：
第一展示单元2201，展示群组对应的通讯界面；
第二展示单元2202，当所述通讯界面中的资源收取功能被触发时，展示资源收取编辑界面，所述资源收取编辑界面包含对象配置选项；
第三展示单元2203，响应于对所述对象配置选项的触发操作，展示对象配置界面，所述对象配置界面中包含所述群组的群组成员；
发送单元2204，通过所述群组对应的通讯会话发送包含资源收取请求的通讯消息；其中，所述通讯消息仅对被选取为资源收取对象的群组成员可见，或者所述通讯消息对所有群组成员均可见但仅被选取为资源收取对象的群组成员可触发。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机，计算机的具体形式可以是个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件收发设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任意几种设备的组合。
在一个典型的配置中，计算机包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介 质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带、磁盘存储、量子存储器、基于石墨烯的存储介质或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在本说明书一个或多个实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本说明书一个或多个实施例。在本说明书一个或多个实施例和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本说明书一个或多个实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本说明书一个或多个实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
以上所述仅为本说明书一个或多个实施例的较佳实施例而已，并不用以限制本说明书一个或多个实施例，凡在本说明书一个或多个实施例的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本说明书一个或多个实施例保护的范围之内。

Claims (26)

  1. 一种资源数据处理方法，其特征在于，包括：
    确定资源收取对象，所述资源收取对象包括本端用户的一个或多个关联用户，所述关联用户包括以下至少之一：从本端用户所属团体的组织架构中选取的一个或多个团体成员、从本端用户所处群组中选取的一个或多个群组成员、从通讯录中选取的一个或多个联系人；
    向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
  2. 根据权利要求1所述的方法，其特征在于，所述确定资源收取对象，包括：
    在本端用户所处的群组中触发资源收取功能；
    将除本端用户之外的所有群组成员添加为资源收取对象；或者，将本端用户选取的一个或多个群组成员添加为资源收取对象。
  3. 根据权利要求1所述的方法，其特征在于，所述向所述资源收取对象发送资源收取请求，包括：
    通过本端用户与所述资源收取对象之间的通讯会话，发送包含所述资源收取请求的通讯会话消息；
    或者，向所述资源收取对象发送包含所述资源收取请求的提醒消息。
  4. 根据权利要求1所述的方法，其特征在于，
    所述设定数额为本端用户设定的待收取资源总额平均至每一资源收取对象后的平均数额；
    或者，所述设定数额为本端用户分别针对每一资源收取对象设定的数额。
  5. 根据权利要求1所述的方法，其特征在于，资源收取请求中包含本端用户添加的备注信息。
  6. 根据权利要求1所述的方法，其特征在于，还包括：
    展示各个资源收取对象对所述设定数额的资源的提供状况。
  7. 根据权利要求6所述的方法，其特征在于，还包括：
    定期或响应于本端用户的触发操作，向未提供所述设定数额的资源的资源收取对象发送资源收取提醒消息。
  8. 根据权利要求1所述的方法，其特征在于，还包括：
    在所述资源收取请求已被所述资源收取对象触发以提供所述设定数额的资源、所述 资源收取请求的有效期已过或接收到本端用户发出的终止指令后，终止所述资源收取请求的资源收取作用。
  9. 根据权利要求1所述的方法，其特征在于，所述资源包括一般等价物。
  10. 一种资源数据处理方法，其特征在于，包括：
    确定资源收取对象，所述资源收取对象包括本端用户的多个关联用户，所述多个关联用户属于至少两个用户集合，其中，所述用户集合包括以下至少之一：本端用户所属团体的组织架构中的团体成员、本端用户所处群组中的群组成员、通讯录中的联系人；
    向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
  11. 一种资源收取方法，其特征在于，包括：
    确定资源收取对象；
    向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
  12. 一种资源收取方法，其特征在于，包括：
    展示群组对应的通讯界面；
    当所述通讯界面中的资源收取功能被触发时，展示资源收取编辑界面，所述资源收取编辑界面包含对象配置选项；
    响应于对所述对象配置选项的触发操作，展示对象配置界面，所述对象配置界面中包含所述群组的群组成员；
    通过所述群组对应的通讯会话发送包含资源收取请求的通讯消息；其中，所述通讯消息仅对被选取为资源收取对象的群组成员可见，或者所述通讯消息对所有群组成员均可见但仅被选取为资源收取对象的群组成员可触发。
  13. 一种资源收取方法，其特征在于，包括：
    展示资源收取编辑界面，所述资源收取编辑界面包含对象配置选项；
    响应于对所述对象配置选项的触发操作，展示对象配置界面，所述对象配置界面中包含本端用户的关联用户；
    将所述对象配置界面中被选取的关联用户作为资源收取对象，并向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
  14. 一种资源收取装置，其特征在于，包括：
    确定单元，确定资源收取对象，所述资源收取对象包括本端用户的一个或多个关联 用户，所述关联用户包括以下至少之一：从本端用户所属团体的组织架构中选取的一个或多个团体成员、从本端用户所处群组中选取的一个或多个群组成员、从通讯录中选取的一个或多个联系人；
    发送单元，向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
  15. 根据权利要求14所述的装置，其特征在于，所述确定单元具体用于：
    在本端用户所处的群组中触发资源收取功能；
    将除本端用户之外的所有群组成员添加为资源收取对象；或者，将本端用户选取的一个或多个群组成员添加为资源收取对象。
  16. 根据权利要求14所述的装置，其特征在于，所述发送单元具体用于：
    通过本端用户与所述资源收取对象之间的通讯会话，发送包含所述资源收取请求的通讯会话消息；
    或者，向所述资源收取对象发送包含所述资源收取请求的提醒消息。
  17. 根据权利要求14所述的装置，其特征在于，
    所述设定数额为本端用户设定的待收取资源总额平均至每一资源收取对象后的平均数额；
    或者，所述设定数额为本端用户分别针对每一资源收取对象设定的数额。
  18. 根据权利要求14所述的装置，其特征在于，资源收取请求中包含本端用户添加的备注信息。
  19. 根据权利要求14所述的装置，其特征在于，还包括：
    展示单元，展示各个资源收取对象对所述设定数额的资源的提供状况。
  20. 根据权利要求19所述的装置，其特征在于，还包括：
    提醒单元，定期或响应于本端用户的触发操作，向未提供所述设定数额的资源的资源收取对象发送资源收取提醒消息。
  21. 根据权利要求14所述的装置，其特征在于，还包括：
    终止单元，在所述资源收取请求已被所述资源收取对象触发以提供所述设定数额的资源、所述资源收取请求的有效期已过或接收到本端用户发出的终止指令后，终止所述资源收取请求的资源收取作用。
  22. 根据权利要求14所述的装置，其特征在于，所述资源包括一般等价物。
  23. 一种资源数据处理装置，其特征在于，包括：
    确定单元，确定资源收取对象，所述资源收取对象包括本端用户的多个关联用户，所述多个关联用户属于至少两个用户集合，其中，所述用户集合包括以下至少之一：本端用户所属团体的组织架构中的团体成员、本端用户所处群组中的群组成员、通讯录中的联系人；
    发送单元，向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
  24. 一种资源收取装置，其特征在于，包括：
    确定单元，确定资源收取对象；
    发送单元，向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
  25. 一种资源收取装置，其特征在于，包括：
    第一展示单元，展示群组对应的通讯界面；
    第二展示单元，当所述通讯界面中的资源收取功能被触发时，展示资源收取编辑界面，所述资源收取编辑界面包含对象配置选项；
    第三展示单元，响应于对所述对象配置选项的触发操作，展示对象配置界面，所述对象配置界面中包含所述群组的群组成员；
    发送单元，通过所述群组对应的通讯会话发送包含资源收取请求的通讯消息；其中，所述通讯消息仅对被选取为资源收取对象的群组成员可见，或者所述通讯消息对所有群组成员均可见但仅被选取为资源收取对象的群组成员可触发。
  26. 一种资源收取装置，其特征在于，包括：
    第一展示单元，展示资源收取编辑界面，所述资源收取编辑界面包含对象配置选项；
    第二展示单元，响应于对所述对象配置选项的触发操作，展示对象配置界面，所述对象配置界面中包含本端用户的关联用户；
    发送单元，将所述对象配置界面中被选取的关联用户作为资源收取对象，并向所述资源收取对象发送资源收取请求，以向所述资源收取对象收取设定数额的资源。
PCT/CN2019/110267 2018-10-17 2019-10-10 资源收取方法及装置 WO2020078244A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811207191.3A CN111061408A (zh) 2018-10-17 2018-10-17 资源收取方法及装置
CN201811207191.3 2018-10-17

Publications (1)

Publication Number Publication Date
WO2020078244A1 true WO2020078244A1 (zh) 2020-04-23

Family

ID=70283222

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/110267 WO2020078244A1 (zh) 2018-10-17 2019-10-10 资源收取方法及装置

Country Status (2)

Country Link
CN (1) CN111061408A (zh)
WO (1) WO2020078244A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113411193B (zh) * 2021-06-11 2023-04-21 维沃移动通信有限公司 消息发送方法、装置、电子设备和可读存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101079133A (zh) * 2006-06-29 2007-11-28 腾讯科技（深圳）有限公司 批量支付系统及批量支付方法
CN105550860A (zh) * 2015-12-11 2016-05-04 小米科技有限责任公司 支付方法及装置
CN105719135A (zh) * 2015-12-31 2016-06-29 杨川林 基于手机的多人群组资金收入支付方法
US20160314132A1 (en) * 2012-11-08 2016-10-27 Socialtopias, Llc Method and apparatus for providing map functionality indicating occupancy of entities
CN106682890A (zh) * 2016-12-08 2017-05-17 腾讯科技（深圳）有限公司 多个用户账户之间进行业务数值转移的方法及装置
CN107038561A (zh) * 2016-11-30 2017-08-11 阿里巴巴集团控股有限公司 一种业务数据处理方法、装置及客户端

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102932238B (zh) * 2012-11-13 2016-06-29 华为技术有限公司 群组消息的提醒方法和设备
US10235663B2 (en) * 2013-11-06 2019-03-19 Tencent Technology (Shenzhen) Company Limited Method, system and server system of payment based on a conversation group
CN104702420B (zh) * 2015-02-26 2018-05-08 小米科技有限责任公司 信息生成方法及装置
CN107404500B (zh) * 2016-05-18 2020-07-03 阿里巴巴集团控股有限公司 群组通信方法、装置及移动终端
CN106980967A (zh) * 2017-03-29 2017-07-25 北京小米移动软件有限公司 付款处理方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101079133A (zh) * 2006-06-29 2007-11-28 腾讯科技（深圳）有限公司 批量支付系统及批量支付方法
US20160314132A1 (en) * 2012-11-08 2016-10-27 Socialtopias, Llc Method and apparatus for providing map functionality indicating occupancy of entities
CN105550860A (zh) * 2015-12-11 2016-05-04 小米科技有限责任公司 支付方法及装置
CN105719135A (zh) * 2015-12-31 2016-06-29 杨川林 基于手机的多人群组资金收入支付方法
CN107038561A (zh) * 2016-11-30 2017-08-11 阿里巴巴集团控股有限公司 一种业务数据处理方法、装置及客户端
CN106682890A (zh) * 2016-12-08 2017-05-17 腾讯科技（深圳）有限公司 多个用户账户之间进行业务数值转移的方法及装置

Also Published As

Publication number Publication date
CN111061408A (zh) 2020-04-24

Similar Documents

Publication Publication Date Title
US10572098B2 (en) Sharing location information during a communication session
US20220014488A1 (en) Information processing method, apparatus, device, and storage medium
US10127544B2 (en) Sending and receiving payments using a message system
WO2018223869A1 (zh) 任务提醒方法及装置、提醒消息的生成和展示方法及装置
TW201915701A (zh) 訊息展示方法及裝置
WO2022152191A1 (zh) 消息展示方法及装置
US10410241B1 (en) Swipe screen advertisement metrics and tracking
AU2012327213A1 (en) Creating and discovering real-time conversations
JP2018512647A (ja) メッセージおよび支払キューを使用した支払の送信、受信および更新の促進
WO2011109636A2 (en) A system, method and computer program product for a dating decision process
US11943310B2 (en) Performing operations based upon activity patterns
WO2018223860A1 (zh) 活动提醒方法、活动提醒消息生成方法及装置
WO2019062587A1 (zh) 任务生成方法及装置
TW201907326A (zh) 資訊的展示方法及裝置
WO2018147741A1 (en) System and device for personal messaging
TW201830305A (zh) 事件處理方法及裝置
TW202016809A (zh) 資源收取方法及裝置
WO2022012394A1 (zh) 电子红包的相关信息展示、发送、接收方法、装置及设备
WO2020078244A1 (zh) 资源收取方法及装置
WO2018223858A1 (zh) 团队配置方法、团队配置方案的分享方法及装置
WO2019015507A1 (zh) 通讯方法及装置
CN106170805B (zh) 组的跨客户端集成
US8666360B2 (en) Contact communication tracking system
US20230412552A1 (en) Messaging protocol to faciliate demand-based messaging
WO2019184742A1 (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: 19873658

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

Country of ref document: EP

Kind code of ref document: A1