CN111726321A

CN111726321A - Public account management method, communication group interaction method, corresponding device and system

Info

Publication number: CN111726321A
Application number: CN201910209205.3A
Authority: CN
Inventors: 林苏芝
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2019-03-19
Filing date: 2019-03-19
Publication date: 2020-09-29
Also published as: WO2020187058A1

Abstract

The invention discloses a public account management method, a communication group interaction method, a corresponding device and a corresponding system. The public account management method comprises the following steps: in response to an account creation request of an application member for creating a common account for a communication group to which the application member belongs, checking the authority corresponding to the application member; and under the condition that the audit confirms that the application member is authorized to create the public account, creating the public account for the communication group. Therefore, the common account is quickly and conveniently created for the communication group, and technical support is provided for common maintenance, management and supervision of the common account by each member of the communication group.

Description

Public account management method, communication group interaction method, corresponding device and system

Technical Field

The present disclosure relates to the field of internet technologies, and in particular, to a communication group interaction method, apparatus, system, computing device, and storage medium.

Background

At present, with the rapid development of scientific technology, more and more people use terminal equipment, more and more functions are provided by the terminal equipment, and different people can also realize communication and/or information sharing through the terminal equipment.

However, in some group (e.g., two or more people) scenarios, such as some real-time updated accounts, synchronous sharing of information cannot be completely achieved, and usually one of the users (e.g., an administrator or other designated user) maintains, updates, and shares information related to the updated account with other members of the group. In these cases, other members of the community do not have the authority to operate the account, and cannot actively know the update condition of the account in real time, and the common maintenance, management and supervision of the account by the members of the community cannot be realized.

Thus, there is a need for a more convenient community interaction scheme to provide technical support for better enabling the corporate members' co-maintenance and administration of accounts to be managed.

Disclosure of Invention

The purpose of the disclosure is to provide a more convenient public account management scheme and a communication group interaction scheme, so as to provide technical support for better realizing the common maintenance, management and supervision of the public accounts bound with the communication group by group members.

According to an aspect of the present disclosure, there is provided a common account management method including: in response to an account creation request of an application member for creating a common account for a communication group to which the application member belongs, checking the authority corresponding to the application member; and under the condition that the audit confirms that the application member is authorized to create the public account, creating the public account for the communication group.

Optionally, on a server or a device accessible by the server, a member list of the communication group and/or first authorization information for the communication group is recorded, the first authorization information being used to define an object or an audit rule having a right to create a common account for the communication group, and wherein the right corresponding to the application member is audited based on the member list and/or the first authorization information.

Optionally, the step of auditing the rights corresponding to the member comprises: auditing whether the application member is a specific object with the authority of creating a community account for the communication group; and/or forwarding the account creation request to at least one designated object and auditing whether the account creation request is granted via the at least one designated object based on feedback from the designated object in response to the account creation request; and/or forwarding the account creation request to other members of the communication group and auditing whether the account creation request is granted by most or all members of the communication group based on feedback from the other members in response to the account creation request.

Optionally, the method may further include: recording, on a server or a device accessible to the server, an identifier of the application member, an identifier of an account administrator of the public account, and/or second authorization information for the public account in association with the public account, wherein the account administrator and/or the second authorization information are set by the application member and/or a group administrator of the communication group, and the second authorization information is used for respectively defining the authority of the members of the communication group to perform interactive operation on various accounts of the public account.

Optionally, a group account interface is respectively provided on the interactive interfaces of the communication group, the group account interface corresponds to the common account, and the method further includes: responding to an account interoperation request of a member of the communication group to realize account inquiry or use of the member for the public account, wherein the account interoperation request is issued in response to the member interoperating with a group account interface displayed on the interactive interface.

Optionally, the server maintains a plurality of common accounts corresponding to the communication group; a plurality of group account interfaces are respectively provided on the interactive interfaces of the communication group, and the plurality of group account interfaces respectively correspond to the plurality of common accounts.

Optionally, the specific object includes at least one of: a group administrator; at least one secondary administrator designated by the group administrator; members of the communication group belonging to the group having the operation level of creating the group account; and a designated object outside the communication group having a common account authority for the communication group.

Optionally, the specified object includes at least one of: a group administrator; a manager of a department or organization to which the communication group belongs; a guardian of a member of the communication group.

According to another aspect of the present disclosure, there is also provided a public account management method, including: responding to the interactive operation of an application member on a group account creation interface displayed on the interactive interface of the communication group, and sending an account creation request to a server by the electronic equipment of the application member; in response to an account creation request for creating a common account for a communication group to which an application member belongs, the server audits the authority corresponding to the application member; and under the condition that the audit confirms that the application member is authorized to create the public account, creating the public account for the communication group.

Optionally, the method may further include: providing a group account interface on an interactive interface of the communication group, the group account interface corresponding to the common account; and operating the public account in response to an interaction between a member and the group account interface.

According to another aspect of the present disclosure, there is also provided a communication group interaction method, including: providing a group account interface on an interactive interface of the communication group, the group account interface corresponding to a common account bound with the communication group; and operating the public account in response to an interaction between a member and the group account interface.

Optionally, the group account interface includes at least one of a first interface, a second interface, a third interface, a fourth interface, and a fifth interface, and the step of enabling account interaction of the member with respect to the public account in response to interaction between the member and the group account interface includes at least one of: creating the public account in response to a first interaction between a member and the first interface; in response to a second interaction operation between the member and the second interface, implementing a transfer operation from the member's personal account to the public account; responding to a third interactive operation between the member and the third interface, and realizing an outward payment or roll-out operation of the public account; in response to a fourth interaction operation between the member and the fourth interface, implementing a viewing operation of the member on account information of the public account, wherein the account information is output to the member; responding to a fifth interactive operation between the members and the fifth interface, and realizing balance return operation of the public account, wherein all or part of the balance of the public account is divided into a plurality of shares according to a preset or appointed balance return rule, and the shares are transferred to the personal accounts of the at least two members respectively.

Optionally, the at least two members each have permission to perform various interactions with the group account interface; or the at least two members are respectively set with the authority to execute various interactive operations.

Optionally, the group administrator has the right to perform the first interactive operation; and/or setting, by a group administrator, members of the communication group having the right to perform the first interactive operation; and/or the account administrator has the right to perform the third and/or fifth interoperation; and/or setting, by an account administrator, members of the communication group having a right to perform the second and/or fourth interoperation; and/or setting the balance return rule by an account administrator, wherein the group administrator is one of the at least two members, and the account administrator comprises a group administrator and/or a member designated by the group administrator and/or a member creating the common account.

Optionally, an authority mode setting interface is provided for the account administrator, and is used for selecting an authority mode from a plurality of preset authority modes.

Optionally, the account information includes at least one of: account balance, account two-dimensional code, income detail and expenditure detail.

Optionally, a plurality of group account interfaces are respectively provided on the interactive interfaces of the communication group, and the plurality of group account interfaces correspond to a plurality of common accounts bound with the communication group.

According to another aspect of the present disclosure, there is also provided a community interaction method, the community comprising at least two members, the method comprising: respectively providing a group account interface on the group interaction interfaces of the at least two members, wherein the group account interfaces correspond to the same group account; and in response to an interaction between a member and the community account interface, implementing an account interaction of the member for the community account.

According to another aspect of the present disclosure, there is also provided a communication group interaction system, the communication group comprising at least two members, the system comprising a server and electronic devices of the members, wherein the server maintains a common account bound to the communication group; a group account interface is respectively provided on the interactive interfaces of the communication groups of the electronic devices of the at least two members, wherein the group account interface corresponds to a common account bound with the communication groups; in response to an interaction between a member and the group account interface, the member's electronic device sends an account interaction request to the server to enable account interaction of the member for the common account request.

Optionally, the account interaction comprises at least one of: creating the public account; a transfer operation from the member's personal account to the public account; external payment or roll-out operation of the public account; viewing operation of account information of the public account; and the balance of the public account is returned, wherein all or part of the balance of the public account is divided into a plurality of shares according to a preset or appointed balance return rule and is respectively transferred into the personal accounts of the at least two members.

Optionally, recording a list of members of the communication group in association with the common account on the server or a device accessible to the server; the server receives an account interaction operation request from the electronic equipment of the member in the member list and executes the account interaction operation.

Optionally, the at least two members each have permission to perform various interactions with the group account interface; or the member list comprises authorization information used for respectively limiting the authority of the at least two members to execute the account interactive operation of the corresponding type.

Optionally, the method further comprises: recording, on the server or a device accessible to the server, an identifier of a member creating the public account in association with the public account.

Optionally, the server maintains a plurality of common accounts belonging to the communication group; a plurality of group account interfaces are respectively provided on the interactive interfaces of the communication groups of the electronic devices of the at least two members, and the plurality of group account interfaces respectively correspond to the plurality of common accounts.

According to another aspect of the present disclosure, there is also provided a community interaction system, the community comprising at least two members, the system comprising a server and electronic devices of the members, wherein the server maintains community accounts belonging to the community; respectively providing community account interfaces on community interaction interfaces of the electronic devices of the at least two members, wherein the community account interfaces correspond to the community accounts; in response to an interaction between a member and the community account interface, the electronic device of the member sends an account interaction operation request to the server to realize the account interaction operation of the member for the community account request.

According to another aspect of the present disclosure, there is also provided a common account management apparatus including: the auditing device is used for responding to an account establishing request of an application member for establishing a common account for a communication group to which the application member belongs, and auditing the authority corresponding to the application member; and the account creating device is used for creating a common account for the communication group under the condition that the application member is checked and determined to have the right to create the common account.

According to another aspect of the present disclosure, there is also provided a communication group interaction apparatus, the communication group including at least two members, the apparatus including: the group account interface device is used for providing a group account interface on an interactive interface of the communication group, and the group account interface corresponds to a common account bound with the communication group; and the interaction device is used for responding to the interaction operation between the member and the group account interface and realizing the account interaction operation of the member aiming at the public account.

Optionally, the group account interface provided by the group account interface device includes at least one of a first interface, a second interface, a third interface, a fourth interface, and a fifth interface, and the interaction device is configured to implement at least one of the following: creating the public account in response to a first interaction between a member and the first interface; in response to a second interaction operation between the member and the second interface, implementing a transfer operation from the member's personal account to the public account; responding to a third interactive operation between the member and the third interface, and realizing an outward payment or roll-out operation of the public account; in response to a fourth interaction operation between the member and the fourth interface, implementing a viewing operation of the member on account information of the public account, wherein the account information is output to the member; and responding to a fifth interactive operation between the members and the fifth interface, and realizing balance return operation of the public account, wherein all or part of the balance of the public account is divided into a plurality of shares according to a preset or appointed balance return rule, and the shares are transferred to the personal accounts of the at least two members respectively.

According to another aspect of the present disclosure, there is also provided a community interaction apparatus, the community comprising at least two members, the apparatus comprising: the community account interface device is used for respectively providing community account interfaces on community interaction interfaces of the at least two members, and the community account interfaces correspond to the same community account; and the interaction device is used for responding to the interaction operation between the members and the community account interface and realizing the account interaction operation of the members aiming at the community account.

According to another aspect of the present disclosure, there is also provided a computing device comprising: a processor; and a memory having executable code stored thereon, which when executed by the processor, causes the processor to perform the method as described above.

According to another aspect of the present disclosure, there is also provided a non-transitory machine-readable storage medium having stored thereon executable code, which when executed by a processor of an electronic device, causes the processor to perform the method as described above.

Therefore, in a community scene such as a communication group, the public account can be created for the communication group by providing the group account interface, and each member of the communication group can realize the account interactive operation of the public account bound with the communication group through the group account interface, so as to provide technical support for better realizing the common maintenance, management and supervision of each group member on the public account. The interaction scheme may be applicable to group interaction in any scenario, including but not limited to monetary accounts, points accounts, token accounts, group chat accounts, and the like.

Drawings

The above and other objects, features and advantages of the present disclosure will become more apparent by describing in greater detail exemplary embodiments thereof with reference to the attached drawings, in which like reference numerals generally represent like parts throughout.

FIG. 1 shows a schematic diagram of a community interaction system, according to one embodiment of the present disclosure.

Fig. 2-7 show examples of interfaces in a working group scenario based on instant messaging APP.

FIG. 8 shows a flow diagram of a community interaction method according to one embodiment of the present disclosure.

FIG. 9 shows a schematic block diagram of a community interaction device 900 according to one embodiment of the present disclosure.

FIG. 10 shows a schematic structural diagram of a computing device according to an embodiment of the invention.

Detailed Description

Preferred embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the preferred embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

As described above, in some group scenes in the prior art, synchronous sharing of accounts among group members cannot be achieved, other members of a group do not have the authority to operate the accounts, and cannot actively know the update condition of the accounts in real time, and common maintenance, management and supervision of the group members on the accounts cannot be achieved.

In view of the above, the present disclosure provides a group interaction scheme, which provides a group account interface, conveniently creates a group account for the group, enables each member in the group to conveniently implement account interaction with the group account, and provides technical support for implementing common maintenance, management and administration of the group account by each member of the group.

In the disclosed embodiments, a "community" is a collective concept with respect to individuals, which may include two or more individual members that are united or organized for a common purpose, benefit, or entertainment, etc., and each individual member may have some associative or interactive relationship with each other. Also, individual members of the community may enable various interactions based on the electronic device and/or the communication network.

The community interaction scheme of the present disclosure may be applicable in any community scenario, including but not limited to work scenarios (e.g., enterprise groups, department groups, small groups, etc.), private scenarios (e.g., class groups, family groups, friend groups, etc.), or other scenarios where social relationships exist. It may be based on instant messaging applications, or may be based on third party payment platforms, or may be based on other social modalities. The group accounts involved therein may include, without limitation, monetary accounts, points accounts, token accounts, and the like. In some cases, the community may be, for example, a communication group including, but not limited to, an instant messaging group, a mail group, and the like, to which the present disclosure is not limited.

In the embodiment of the present disclosure, the community may be, for example, a small community including 2-5 members, a large community including, for example, 15-20 members, or a huge community including more members. In some complex situations, the community may also include multiple sub-communities. Also, for different application scenarios, a community may correspond to a single community account, or may correspond to multiple community accounts, or a community account may include multiple sub-accounts. For example, some groups may be relatively simple in terms of expense items and expense types, and may simply create a group account. However, some large or ultra-large groups are complicated in terms of expense items and expense types, the account expenses cannot be made clear by creating one group account, and a plurality of group accounts may be created and maintained separately or a plurality of sub-group accounts may be created under the created group account, accordingly. The present disclosure does not set any limit to the form of the group and the group account.

In the disclosed example, different members of the community may each have different member roles, and different members may each have different account operating permissions that determine the permissions that the members are granted to perform some interactions, particularly account interactions. The account operation authority can be represented by whether an interface corresponding to the account interactive operation is displayed on an interactive interface of the member or whether the member can perform the account interactive operation on the interface corresponding to the account interactive operation displayed on the interactive interface. The member role and the operation authority thereof (which may include the initial account operation authority) may be set for the member when the member joins the group, or the operation authority of the member may be updated along with the change of time or the change of the member role. Thus, technical support is conveniently provided for enabling the common maintenance and management of the community accounts by all members of the community.

It should be understood that the communication group interaction scheme of the present disclosure is an application example of the community interaction scheme of the present disclosure, which is applicable to the communication group, and the communication group interaction scheme may also be applicable to other community interaction scenarios. And some terms referred to therein, such as "group account" and "common account", "group" and "communication group", etc., may be regarded as the same concept, and the present disclosure will not be distinguished one by one in the following description.

In the disclosed embodiment, all account interaction operations involving the community account (including operations to create the community account and operations to query or use the community account, etc.) may be notified to all members of the community, for example, in the form of a message. In different application scenarios, the form of the message or the message notification may be different, and the form of the message or the message notification may also be set by the community members according to a preset form or a customized form. Therefore, all members of the community can clearly know the real-time dynamic of the community account, so as to better realize the common maintenance, management and supervision of the community account by each member.

Different contents can be displayed aiming at different member roles, different interfaces or functions and the like. "different" can be embodied in the presentation form of the content, such as text form, voice form, picture form, or a combination thereof; the communication group can also be embodied in specific display content, for example, the roles of the members in the communication group or the head images of the members can be displayed in the displayed message content; and displaying a member role corresponding to the account interactive operation corresponding to the content, which is not limited by the disclosure. The details will be described below with reference to the drawings and examples. The community interaction scheme of the present disclosure will be described in detail with reference to the drawings and the embodiments, and further, a "communication group" is taken as an example of a community and a specific application scenario is taken as an example to describe the community interaction scheme of the present disclosure in more detail.

Community interaction scheme

FIG. 1 shows a schematic diagram of a community interaction system, according to one embodiment of the present disclosure. The community of the present disclosure may be a community (e.g., a communication group), and the community may include at least two members, each member having a corresponding electronic device, and may implement a corresponding community interaction through their respective electronic devices and communication networks. In the communication group interaction example, the community interaction system may also be referred to as a communication group interaction system.

As shown in fig. 1, the system may include a server 20 and electronic devices 10_1, 10_2, … …, 10_ N of the at least two members.

Where electronic device 10 is any suitable electronic device operable to perform network access. Preferably, for example, it may be a portable electronic device including, but not limited to, a smart phone, tablet, or other portable client. The electronic device 10 can transmit and receive information to and from the server 20 via the network 40. Electronic devices (e.g., between 10_1 and 10_2 or 10_ N) may also communicate with each other via network 40.

The server 20 is any server capable of providing information required for an interactive service through a network.

Network 40 may be a network for information transfer in a broad sense and may include one or more communication networks such as a wireless communication network, the internet, a private network, a local area network, a metropolitan area network, a wide area network, or a cellular data network, among others.

It should be noted that the underlying concepts of the exemplary embodiments of the present invention are not altered if additional modules are added or removed from the illustrated environments.

And, one or a part of the mobile terminals will be selected from the following description to be described (for example, the electronic device 10-1), but it will be understood by those skilled in the art that the above-mentioned 1 … N terminals are intended to represent a large number of terminals existing in a real network, and the single server 20 shown is intended to represent the operation of the server related to the technical aspect of the present invention. The detailed description of a particular numbered mobile terminal and a single server is for convenience of description at least and does not imply any limitation as to the type or location of the mobile terminal and the server.

In the disclosed example, corresponding interfaces can be respectively provided on the community interaction interface, and various interactions can be realized through the interfaces. The interfaces can allow various interactive operations, and the interfaces can be preset with interface functions or interface use modes.

In particular, in the community account scenario, for example, an operation of creating a community account, an operation of transferring from a member's individual account to the community account, an operation of external payment or transfer of the community account, an operation of viewing account information of the community account, and an operation of returning a balance of the community account may be included. Corresponding to different functions, corresponding names can be given to the interfaces respectively so as to be convenient for distinguishing, such as an account creating interface, a transfer-in interface, a payment interface, a viewing interface, a balance returning interface and the like.

In the disclosed example, different interfaces may be displayed on different interactive interfaces, and different interfaces may be opened at different time stages to provide relevant services based on the interfaces to members.

For example, in a community account scenario, members may be provided with a community account creation interface prior to community account creation that only allows for interactive operations such as creating a community account. After the group account is created, a plurality of interfaces, such as the above-mentioned transfer-in interface, transfer-out interface, viewing interface, balance return interface, etc., are provided for the members to conveniently inquire or use the group account (or may be named as a first interface, a second interface, a third interface, a fourth interface, etc., respectively, and the naming mode is not limited). Based on the interface, the members with the operation authority can conveniently create the group account, and the corresponding members can jointly realize the common maintenance and supervision of the group account.

In the disclosed example, different members in the community may have different member roles, respectively, and different members may have different operational rights, respectively. The operation authority may include a general operation authority for the interface control, and may also include an account operation authority for an account function implementation corresponding to the interface control. The operation authority determines whether a certain interface is displayed to the member, whether the member can operate the certain interface, whether the member can perform account interactive operation on the certain interface, and the like. The operation authority can be set by an administrator or an account administrator or a designated object, and can also be applied by a member and authorized after the application is passed. The authorization information of the member for the operation authority of different interactive operations may be determined and recorded when the member joins the community, may be determined and recorded when the community account is created, and may also be changed and updated in real time as time or settings or authorization changes, which is not limited by the present disclosure.

According to authorized operation authority of different users in the community, only the interface related to authorized operation of the users can be displayed on the corresponding account interactive interface, and the interface corresponding to unauthorized operation of the users is not displayed. Alternatively, all members of the community may be presented with a plurality of interfaces corresponding to various interactive operations, respectively, and among them, according to the granted operation authority of different members in the community, the interface with the operation authority may be made operable on its corresponding account interactive interface, while the interface without the operation authority may not be operable. Still alternatively, all members of the community may be respectively presented with a plurality of interfaces corresponding to various interactive operations, and in which, according to the granted account operation authority for the community account for different members in the community, the interface with the account operation authority may be made directly operable on its corresponding account interactive interface, while the interface without the account operation authority may apply whether it is authorized to be operable.

Creating a group account

In one embodiment, the community account interface may include a first interface (which may also be referred to as an account creation interface) that may correspond to operations to create a community account. Wherein, some members may be granted the authority to create the group account, and the account creation interfaces may be respectively provided on the group interaction interfaces of the electronic devices of the members, so that the members may implement the creation of the group account through the interaction operation with the account creation interface corresponding to the function of creating the group account. In other embodiments, the community account interface may be provided on the community interaction interfaces of the electronic devices of all the community members, respectively, and the members having the authority to create the community account may perform an interaction operation on the community account interface, while the members not having the authority to create the community account may not perform an interaction operation on the community account interface.

The member having the right to create the community account may be a specific object. For example, the group account authority may include a specific member in the group (e.g., a group creator or a group administrator), a core participating member or an assistant administrator designated by the group administrator, some members with higher activity coefficient in the group, a team belonging to a member with an operation level for creating a group account, or a designated object outside the group having the authority to create a group account for the group, such as a group administrator, an administrator of a department or an organization of the group, a guardian of a member in the group, and the like, which is not limited by the present disclosure.

The members can be respectively given corresponding member roles in the community, and for different member roles, the interaction operation rights of the members in the community are different. In this case, the management level can also be divided for different member roles, and the member roles can have operation levels suitable for the management levels. Under different community scenes, the roles of the members can be determined in different modes, and the corresponding operation authorities of the members can also be determined in different modes.

For example, in some work scenarios, a member's role may be determined based on its business position, department of ownership, social position, social role, and the like. Further, different member roles may correspond to different management levels, which may correspond to different operational rights. For example, for a leader of an enterprise, a financial manager is at a higher management level in some enterprise groups and accordingly has higher operation authority, the group account creation can be applied. While the general staff members for the enterprise are at a lower level of management with correspondingly lower operational rights and no rights to apply for the creation of a group account. In some private scenarios, however, any member of the community may have the right to create a community account.

In the case where it is desired to create a community account for the community, members (or other objects) may interact with a community account creation interface displayed on an interactive interface of the community displayed on their electronic devices to request the creation of a corresponding community account for the community to which they belong. The member who initiated the application may also be referred to as an "application member," among other things, to distinguish it from other members of the community.

The electronic device of the application member may send an account creation request to the server in response to the interaction. The server may decide whether to create a community account for the community in response to an account creation request from the electronic device of the application member.

In one embodiment, the server may respond to an account creation request for an application member to create a community account (or common account) for its affiliated community (or communication group), review permissions corresponding to the application member, and create a community account (or common account) for the community (or communication group) if the review determines that the application member is authorized to create the community account (or common account).

In which the authority of the application member can be audited from a number of aspects.

For example, it may include auditing whether the applying member is a specific object having a right to create a community account; reviewing whether the application is approved by a designated object or other member of the community; checking whether the application meets preset checking rules; whether the purpose of applying for the group account is reasonable can be checked; checking whether the target use of the desired created group account is reasonable and legal; checking whether a bank account associated with the group account expected to be created for the application is a designated bank account; auditing account credits, and the like. The information required to be audited can be obtained when the application member submits the application, and can be selected or input by the application member.

In different application scenarios, the auditing process for the permissions of the application members may be different.

For example, in some scenarios, any member of the community has the right to create a community account. When the member applies for creating the group account, the group account related to the group where the member is located can be created immediately, and account information is perfected, such as binding a bank card, associating a payment account, setting a payment password, paying a quota once/every day, and the like, so that the created group account can be put into use.

For example, in some scenarios, only some members of the community, or other particular objects, all have the right to create a community account. The auditing process may, for example, audit whether the application member has the creation authority.

Specifically, a list of members of the community and/or first authorization information for the community defining object information or audit rules having a right to create a community account for the community may be recorded on the server or a device accessible to the server. Wherein the member list may include the first authorization information. After receiving an account creation request from an application member, the server may review the authority corresponding to the application member based on the member list and/or the first authorization information. The account creation request may include an identifier of the application member, and the server may determine whether the application member has the creation authority by looking up whether the object information defined in the authorization information and having the authority to create the community account for the community includes the identifier of the application member.

Alternatively, in response to the account creation request, the server may also obtain identity information of the application member from its memory or a device accessible to the server, such as department where the member is located, member position, account usage, account management accountant, member's top leader, and the like, and determine whether the application member has creation authority by reviewing the identity information of the member, member role in the community, or other information.

As another example, the review process may also include whether the application was approved by most or all members of the community. The specific auditing process can be determined according to the role of the member, for example, under the condition that the administrator initiates the application, whether the approval of most members is passed can be audited; in case the application is initiated by other members, it can be checked whether the consent of all members has been passed.

For example, the server may forward the account creation request to other members of the communication group to consult all other members as to whether the application is approved and obtain feedback from the other members in response to the account creation request. The feedback may include, for example, whether the member agrees to the application of the application member to create the community account or other feedback. Based on the other members' feedback in response to the account creation request, the server may, for example, count the number of members whose feedback approves the application and review whether the account creation request was approved by most members (e.g., half members or two-thirds of the total number of members) or all members of the communication group. The server may determine that the application has passed its audit with the consent of most or all of the members.

In some scenarios, for example, audit rules may also be preset, which may include, for example, group attributes (e.g., group type, student group, adult group, or other group, etc.) and corresponding audit conditions, such as whether or not approval is granted via at least one specified object. For communities with different community attributes, the permissions corresponding to the application members can be checked based on corresponding checking rules respectively. Ball

In one embodiment, for a student community, the at least one designated object may be a guardian of a student member. For a work party, the at least one designated object may be a party to a manager of the department or organization or a higher level manager or financial manager, etc. The designated object may be provided by a member or the account number of the designated object is tied to the community account or to the account number association of the community member. Moreover, the body attribute may be determined based on the group name, basic information of the group members (e.g., age, school, company, personal profile, etc.), etc., and the disclosure is not limited thereto and will not be described in detail.

The server may forward the account creation request to at least one designated object and obtain feedback of the designated object in response to the account creation request. The feedback may include, for example, whether the at least one specified subject agrees to an application by the application member for creation of a community account. Based on the feedback, the server may audit whether the account creation request was granted via the at least one designated object. And determining that the application has passed the audit if the at least one designated subject agrees.

In other embodiments, the feedback may further include, for example, a recommendation of the quota for the group account created by the application member applied by the designated subject or other members, a private account provided by the designated subject (for example, for a student group, a guardian of the designated subject may provide a personal private account as a private account of a student member, and transfer charges from the private account to the group account when, for example, the student makes a payment), and the like, which is not limited by the disclosure.

When the permission of the application member passes the permission review, for example, under the condition that the permissions of the application member all meet preset conditions in multiple aspects, the permission of the application member is determined to be authorized to create the group account through the review, and at this time, the group account can be created for the group to which the application member belongs.

And when the audit is not passed, for example, when any aspect does not meet the preset condition, determining that the audit is not passed, at this time, returning the application, and providing the reason why the application is not passed to the application member, for example, the application member does not have the creation authority, the application is not approved by most members, the application is not approved by a specified object, or any other aspect does not meet the application condition. And, the members or objects with creation authority, the conditions that any aspect should meet, and the like can be informed to the application members when the application is returned, thereby facilitating the efficient creation of the community account.

Thus, a member may request the creation of a community account corresponding to the community through interaction with an account creation interface, which may correspond to the community account. The server may create the community account in response to an account creation request issued by an interaction between the member and the community account interface to create the community account.

Querying or using community accounts

In one embodiment, after the team account is created, the application member or other members with associated account management authority (e.g., a community manager) may be further refined to further refine the relevant settings for the community account. For example, a group bank card is bound for the group account, account management members capable of managing the group account are set, operation rights of the respective group members for the group account are set, and the like.

Accordingly, the related information of the above-described setting for the group account can also be recorded. For example, an identifier of the application member, an identifier of an account administrator of the public account, and/or second authorization information for the public account is recorded in association with the public account on a server or a device accessible to the server. The account administrator and/or the second authorization information are set by the application member and/or the group administrator of the communication group, and the second authorization information is used for respectively limiting the authority of the members of the communication group for various account interactive operations of the common account. From this first or second authorization information, the server 20 can clearly understand which interactions of the members in the community are allowed and which interactions are not.

Wherein, these information can also be recorded and stored in association with the member list or the first authorization information, etc. which have been recorded and stored as described above, and in some cases, can also be used to update the information such as the member list or the first authorization information. Thereby, subsequent community account maintenance and management is facilitated.

After the community account creation is complete and/or the account information is completed, the community account can be used by the members. The functions of some of the group account interfaces corresponding to the group account are turned on, and at the same time, the server 20 may maintain the group account.

In one embodiment, these community account interfaces may be provided separately on the interactive interfaces of the community of the member's electronic devices. All interfaces corresponding to the community accounts can be displayed on the community interaction interface of the member, and the interface with the operation authority can be operated according to the operation authority of the member, so that the interface without the operation authority can not be operated (such as a gray control). Or some interfaces with the operation authority can be displayed on the community interaction interface according to the operation authority of the member. The present disclosure is not so limited.

In this way, through the plurality of interfaces provided on the community interactive interface of the member and/or the setting of the operation authority of the provided interfaces, the member can know that the interactive operation corresponding to the interfaces can be executed by the member, and the interactive operation corresponding to the interface which is not provided cannot be executed by the member.

Each member of the community may interact with the community accounts as previously described to enable account queries or uses by the members against the community account. In response to an interaction between a member and the community account interface, the member's electronic device may send an account interaction request to the server.

The server may implement account interactions of the members for the community account request in response to the received account interaction request. Moreover, all of the account interaction operations related to the community account in the embodiments of the present disclosure may be presented in the interactive interface of the community. Messages displayed in the community interaction interface corresponding to account interactions involving the community account may be presented in different forms. For example, different content may be presented for different member roles, different community interfaces, or functions.

Wherein, the group account interface can comprise different interfaces corresponding to different account interactive operations so as to respectively realize different interactive functions.

For example, the group account interface may include a second interface, which may correspond to a transfer-in operation. The server may enable a transfer operation from the member's personal account to the community account in response to a second interaction operation between the member and the second interface.

For example, the group account interface may include a third interface, which may correspond to roll-outs. The server may implement an outbound payment or roll-out operation for the group account in response to a third interaction between the member and the third interface.

For example, the group account interface may include a fourth interface, which may correspond to a viewing operation. The server may implement a viewing operation of the account information of the community account by the member in response to a fourth interaction operation between the member and the fourth interface, wherein the account information is output to the member. Wherein the account information may include at least one of: account balance, account two-dimensional code, income detail and expenditure detail.

For example, the group account interface may include a fifth interface, which may correspond to a balance return operation. The server may implement a balance return operation for the community account in response to a fifth interaction between a member and the fifth interface. Wherein, the whole or part of the balance of the group account can be divided into a plurality of shares according to a preset or appointed balance return rule, and the shares are respectively transferred into the personal accounts of the at least two members.

Therefore, through the interface, technical support can be conveniently provided for realizing the common maintenance and management of all members in the community to the community account. It should be understood that the different account interactions and the interfaces respectively corresponding to the different account interactions as described above are illustrative examples of the community account interface of the present disclosure, and are not limiting of the interactions and/or interfaces of the present disclosure, including but not limited to the above examples. In the disclosed example, each member of the community may have the authority to perform various interactive operations on the community account interface. Alternatively, the authority for performing various interactive operations may be set for different members in the group, and the interactive operations authorized by different members in the group may not be identical.

The interfaces of the present disclosure as described above relating to the community accounts may be collectively referred to as the community account interface, and different interfaces may be implemented at different time periods or corresponding to different functions and may be named as different names. Different interfaces may correspond to different account interactions. Different interfaces can be displayed at different time periods, and different interfaces can be displayed on the same interactive interface or different interactive interfaces.

The above-described authorization of the operation authority of each member of the community may be set by the community manager and/or the member who creates the account at the time of initially creating the community group or at the time of initially creating the community account. For example, a member having a right to perform creation of a group account (i.e., a first interactive operation) in the group may be set by the group administrator, and a member having a right to perform the above-described transfer operation (i.e., a second interactive operation) and/or viewing operation (i.e., a fourth interactive operation) in the group may also be set by the group administrator. Alternatively, the authorization of the operation authority of each member in the community may also be automatically set according to the organizational structure status of the member in the community, which is not limited by the present disclosure.

In addition, the created community accounts may have account administrators for ease of management. The account administrator may be, for example, a community administrator and/or a member designated by the community administrator and/or a member who created the community account (i.e., an application member as described above). The account administrator may take on the primary administrative position of the community account management, e.g., the account administrator may have the authority to perform some payout type operations of the community account, such as an outward payment or roll-out operation and/or a balance return operation of the community account. The account administrator may also set some spending rules in the community scenario, such as balance return rules.

Any member of the group can perform transfer operation from the individual account to the group account, and can also perform viewing operation on the account information of the group account, so as to conveniently submit the group payment and/or view the group account balance detail in real time.

For account security, in an embodiment, the members in the community having the right to perform the above transfer operation and/or view operation may also be set by the account administrator, which is not limited by the present disclosure. The account administrator can be provided with an authority mode setting interface, and based on the authority mode setting interface, the account administrator can select an authority mode from a plurality of preset authority modes so as to respectively set account authorities of different members in a group.

Additionally, in one example of the present disclosure, the community may also have multiple community accounts.

Specifically, for example, a plurality of account creation interfaces may be respectively provided on the community interaction interface, the plurality of account creation interfaces may be respectively used to create a plurality of community accounts corresponding to the community, and the plurality of community accounts may be respectively used to achieve different account purposes or account management. These multiple community accounts may be created by the same or different member applications. The multiple account creation interfaces, the multiple group account interfaces respectively corresponding to the multiple account creation interfaces, and the implementation of the interaction operation between the group members and the multiple group account interfaces are the same as or similar to the case of one group account described above, and are not described herein again. In that

In other embodiments, one or more sub-accounts may also be opened for the created group account, different sub-accounts may be respectively used to implement different account purposes or account management (for example, for a sub-team of the group), each sub-account may also correspond to multiple sub-account interfaces, which is convenient for implementing, for example, query or use of the sub-account by a member of the sub-team, and specific implementation may refer to the above, and is not described herein again.

The community interaction scheme of the present disclosure may be applicable in any community scenario, including but not limited to work scenarios (e.g., business groups, department groups, small groups, etc.), private scenarios (e.g., class groups, student groups, parent groups, family groups, friend groups, etc.), or other scenarios where social relationships exist. The payment system can be based on an instant messaging application program, a third-party payment platform and other social application programs. The group accounts involved therein may include, without limitation, monetary accounts, points accounts, token accounts, and the like. In some cases, the community may be, for example, a communication group including, but not limited to, an instant messaging group, a mail group, and the like, to which the present disclosure is not limited.

Instant messaging group interaction scheme

For better understanding of the technical solution of the present disclosure, the community interaction scheme of the present disclosure will be described below with reference to the example of the interaction interface in the instant messaging APP based instant messaging group scene, based on the application scene of the community of the instant messaging APP communication group. It should be understood that the instant messaging group based communication group interaction scheme of the present disclosure is an application example of the group interaction scheme of the present disclosure, to which the group interaction scheme as described above is applicable, and the instant messaging group interaction scheme may also be applicable in other group interaction scenarios, and some terms referred to therein, such as "group" and "communication group", "group account" and "public account", "group account interface" and "group account interface", etc., may be regarded as the same concept, and the detailed description and distinction thereof are not repeated below. And some of these details may be referred to in the relevant description above.

The communication group interaction scheme may be implemented by a communication group interaction system, which may include a server and electronic devices of at least two members included in the communication group, and an interface corresponding to a group account may be displayed on an interaction interface of the electronic devices of the members, and the members in the group may create the group account through the interface or use the created group account, similar to or the same as the above-described group interaction system.

For example, as shown in FIG. 2, in an internal workgroup with a group name of "Miximex UXD", the current group chat interface 200 displays chat content from member A, B or C at different times along with some basic information about member A, B, C (e.g., the head portrait, nickname, etc. of member A-Amiri, shown at 201, member B-Peter, shown at 202, and member C, alice, shown at 203, respectively).

At this point, a member D in the group (which may be the group administrator, a member designated by the group administrator, or any member in the group) enters the group settings interface 300 shown in FIG. 3 by clicking on the "group settings" control 204 in the upper right-hand corner of the chat interface 200. At the group setting interface, some interfaces such as "group announcement", "picture", "file", "link", "search", "group sport", "live playback", "group vault 301", and the like are provided to the group members. The group vault interface 301 is a group account interface corresponding to the communication group.

The member D may enter the group vault interface 400 as shown in fig. 4A by clicking on the group vault interface 301 without previously creating a public account corresponding to the communication group. At the group vault interface 400, member D may apply for the creation of a public account corresponding to the group "mizexime UXD" by clicking on the "open group vault" control 401. The electronic device of the member D may send an account creation request to the server in response to the click operation, so that the server can check the authority of the member D.

In one embodiment, the server may check whether member D has creation rights by accessing the group member list of the group and the associated authorization information recorded in its memory. When member D has the creation rights, the server may also forward the request to other members of the group, such as message 206 shown in fig. 4B, to consult whether other members of the group (e.g., member E) approve the account creation request of member D (e.g., "approve watt open group vault").

The server may obtain feedback on other members regarding the account creation request, such as agreement (yes) or disagreement (no), and may count the number of members who agree to the application. If most (e.g., half or two-thirds) members of the group have agreed to the application, then it is determined that member D is authorized to create a common account, i.e., a group account, for the group. The server may maintain a common account bound to the communication group. The group account maintained by the server may be a virtual account maintained by itself, or a bank account mediated by the server, which is not limited in this disclosure.

At the same time, a message 205 that member D (member D nickname is watt) has opened the group vault function is displayed in the group chat interface 200 of all group members as shown in fig. 5A, and all members in the group can see the opened message of the group vault function on their corresponding group chat interfaces. Therefore, the group members can conveniently know the real-time dynamic state of the public account.

All account interactive operations related to the group account in the embodiment of the present disclosure can be displayed on the chat interface of the communication group. Also, messages displayed in the group chat interface 200 corresponding to account interactions involving a common account may be presented in different forms. For example, different content may be presented for different member roles, different group interfaces, or functions, and the content or form of the message 205 presented may be different.

"different" can be embodied in the presentation form of the content, such as text form, voice form, picture form, or a combination thereof; the communication group can also be embodied in specific display content, for example, the roles of the members in the communication group or the head images of the members can be displayed in the displayed message content; and displaying a member role corresponding to the account interactive operation corresponding to the content, which is not limited by the disclosure. For example, when a member performs an account interaction operation, the message displayed on the group chat interface may be a relatively simple prompt message, a prompt message with a role of the member added, or a balance prompt message sent by the member in the form of sending chat content, for example. In addition, the member user may also customize the display content/switch, etc. to set the attribute information such as the form of the message that the member user desires to display, which is not limited in this disclosure.

For example, the message 205 presented on the group chat interface may be the more compact prompt message "Watt open group vault function" 205 shown in FIG. 5A, a prompt message such as the member role of member D added to create a public account shown in FIG. 5B, e.g., "group Administrator (or other role) -Watt open group vault function" 205, or a message 205 shown in the form of a chat message issued by member D, e.g., as shown in FIG. 5C, including member D's avatar, nickname, etc.

It should be understood that the messages related to the interaction of the public account illustrated in fig. 5A-5C are only illustrative examples and are not limiting, and the present disclosure is not limited to the presentation form and specific presentation content of the messages related to the public account. And the illustrated presentation of messages is equally applicable to other account interactions in the process of querying or using the common account or other account interactions involving the common account.

After the group account is created, that is, the group vault function is turned on, a group account interface may be provided on an interactive interface of a communication group of the electronic devices of the group members, respectively, where the group account interface corresponds to a common account bound to the communication group. Based on these group account interfaces, group members may enable common maintenance of group accounts. In one embodiment, these group account interfaces may be displayed on the same interactive interface, such as group account details interface 600.

For example, any member of the group may enter the group vault account details interface 600 by clicking successively on the "group settings" interface 204 in the upper right hand corner of the group chat interface 200 shown in fig. 2, and the "group vault" interface 301 of the group settings interface 300 shown in fig. 3, in order for the member to query or use the common account conveniently. In other embodiments, the "group vault" interface may also be provided on a group chat interface, such as the "group vault" interface 207 shown in FIG. 6A, where a member may access the group account details interface 600 by clicking on the interface 207.

Here account details interface 600 may provide some group account interfaces such as account balance (element) 601, payment code 602, debit code 609, my to do up interface 603, red parcel interface 604, cash up interface 605, transfer interface 606, and detail interface 607, among others. By interacting with the accounts between these interfaces, members of the group can conveniently initiate queries or use against the group account. In response to the interaction between the member and the group account interface, the electronic device of the member may send an account interaction operation request to the server to implement the account interaction operation of the member with respect to the group account request, and implement the common administration and maintenance of the group account (i.e., the group vault).

For example, the group members can conveniently transfer the amount to the group vault through the 'I want to pay' interface to pay the group fee. And paying out a team based on a 'payment code' and the like, such as buying a gift, buying a birthday cake, gathering a meal for payment and the like, so as to maintain the team cohesion and enrich the work and life. The members in the group can also check the income and expenditure details of the group account in real time based on the detail interface, so that all the members in the group can realize the common management and monitoring of the group account. Members with operational privileges may also manage the group of accounts based on "transfer," "cash out," etc.

According to the preset member role or member authorization information or the difference of the positions of different members in the group organization structure, the operation authority of different members on the provided account interface is not completely the same, and the group account detail interfaces 600 displayed to the members are not completely the same.

For example, only the interface that the member has operating rights may be displayed to the member at the account details interface 600. For example, for a member at the lowest level of operational privileges (having only the privilege to query and transfer to a group account), the member is provided with a group account details interface 600 as shown in fig. 6B, the member may view the balance 601 of the group account, may query the balance details of the group account via a "details" interface 607, or may transfer a fee from his private account to the group account via a "cash register" interface 609 or a "i'm to pay" interface 603.

Alternatively, an interface corresponding to the full functionality of the group account may be displayed to the member at the account details interface 600. An interface in the account details interface 600 displayed on the member's device is operable when the member has operational rights to that interface. While an interface in the account details interface 600 displayed on the member's device is inoperable when the member has no operational rights for that interface. It will be appreciated that in one embodiment, when a member has no operational rights to an interface, the interface may appear as a grayscale control at the group vault account details interface 600 opened by the member to indicate that the control is not currently operational.

Alternatively, an interface corresponding to the full functionality of the group account may be displayed to the member at the account details interface 600. When a member does not have the account interactive operation execution right on a certain interface, when the member clicks the interface, the member can also be provided with an 'application right' interface, so that the member can obtain the operation authorization of the account interactive operation corresponding to the interface.

The interface provided on the account details interface 600 may be pre-set with the interface usage or may be set by the member.

For example, the "i want to pay" interface may be preset (or set by the member) to a periodic rated charge pay mode. After being authorized by the member, the server may transfer a predetermined amount (e.g., 20 dollars) from the member's private account to the group account at a predetermined time (e.g., 9:00 a day in the morning, or 1 day a month, etc.). Wherein the private account and/or the group account are accounts commonly maintained by the server. For another example, the "detail" interface may be preset (or set by a member) to a mode of periodically reporting receipt and payment details or receipt and payment summaries for a predetermined period of time. For example, the server reports to all group members on a set predetermined date (e.g., 15 days per month) the income and/or payment details or the total amount of the balance between the last 15 days to the present 15 days.

The account details interface 600 shown in FIG. 6C is the account details interface 600 corresponding to the member of the group (e.g., the group administrator or account administrator) having the highest authorization level, all of which are operational, who may transfer charges into the group account via, for example, the "I am to pay" interface 603; some detailed revenues and payouts for the group of accounts may also be viewed through the "details" interface 607; the merchant may also be paid via a pay code 602, sending a red envelope to some members of the community via a "red envelope" interface 604; transfer some of the charges of the group account to a bank account (which may be a bank account associated with the group account or a private bank account or other bank account for a member) through the "cash out" interface 605; transfer to a private account of a member of the community via a "transfer" interface 606, and so on.

In other embodiments, any member of the group may be presented with an account details interface 600 as shown in FIG. 6C, where the interface in which the member does not have operational privileges is displayed as a grayscale control. For the general member, it may be presented with an account details interface 600 as shown in fig. 6B, providing interfaces such as account balance (element) 601, my to do up interface 603, and details interface 607, all members in the group having operational rights. While some interfaces, such as those corresponding to account payout scenarios, such as pay codes 602, "red parcel" interface 604, "cash-out" interface 605, "transfer" interface 606, etc., may be displayed only on the group account details interface 600 of a designated member having operational privileges (e.g., a member designated by a group administrator and/or account administrator and/or group administrator/account administrator). Moreover, the interfaces displayed on the group account detail interface 600 of the present disclosure may also be freely combined according to the member authority, which is not limited by the present disclosure.

By way of example, when any member of the group, such as member D, wishes to view details of the charges with the group account, member D may by clicking on details control 607 as shown in FIG. 6C, and thereafter presenting details page 610 as shown in FIG. 6D to the user. On the detail page 610, a plurality of items of the receipt and payment details related to the common account and related information may be displayed in the form of items, for example, and total income and total expenditure within a predetermined time range (for example, one day, one month, or one year) may be displayed. The displayed content of the entry may be different according to the balance information related to different balance behaviors, for example, the displayed content may be displayed according to the transaction types (including all transaction types, red envelope, transfer, group collection, two-dimensional code payment, recharge, cash withdrawal, refund, merchant consumption, etc.), the balance time, member identification (for example, displayed in the case that the balance behaviors occur in a public account and a personal account of the member), and the like, or only some main contents of the balance details may be displayed.

For example, referring to fig. 6D, the detail page 610 illustrates a number of balance detail entries for a common account bound to the communication group in january of 2019, shown by "all deal type". The revenue entry 611 is a red envelope that member B of the communication group transfers from his personal account (e.g., change account) to the public account on 25/2019 for a total of 200 dollars. The revenue entry 612 is the account administrator for the communication group paying 10 dollars to the merchant in 2019 payments by scanning the two-dimensional code on month 1, 21, 12: 55. Revenue entry 613 is for the account administrator for the communication group to transfer 20 dollars to member a in 2019, 1 month, 15 days 18: 35. The revenue entry 614 is that the account administrator for the communication group paid cake merchant a 80 dollars on 1 month 13 days 15:10 2019. The revenue entry 615 is that a member of the communication group paid 300 dollars from their b bank account to the public account on 12 th 1 month in 2019. It should be understood that for purposes of illustration, only a few entries of the detail page are shown schematically and the full detail page is not shown here. When the detail page 610 shown in fig. 6B is opened by the member D, the member D may further click one of the receipt and payment detail entries, so that the bill detail page corresponding to the receipt and payment detail entry may be entered, where the bill detail page includes more detailed desired information of the receipt and payment detail entry, such as current state (completion, failure, duration, and the like), transaction time, payment method, transaction order number, identification of both parties of the transaction, and details thereof are not described herein.

When any member of the group, for example member D, wishes to issue a red envelope at the communication group, member D may enter a red envelope page 620 as shown in fig. 6E by selecting the red envelope control 604 as shown in fig. 6C (or member D may also select the "red envelope" function directly on the group chat interface, although the present disclosure is not limited to the form of entering the red envelope interface).

In the red package page 620, some interactive controls may be provided to the member so that the member can set the red package that the member desires to issue and some basic information of the red package by clicking on the relevant control. Such as the type of red envelope (e.g., spelled sign-up red envelope, exclusive red envelope, etc.), the number of red envelopes, the total amount, the individual red envelope amounts, the payment method (source of the funding account used for payment), the time of delivery, red envelope remark information (e.g., blessing words or reminder remarks), etc. Wherein a member of the group (e.g., a group administrator or an account administrator) having group account payout rights may select the group account as a payment source for paying the red envelope. And other members who do not have the group account payout authority may not select the group account as the payment source for paying the red envelope. It should be understood that, for different types of red-packs, the interaction controls specifically related to setting the properties of the red-packs may not be identical, and the disclosure is not limited thereto.

After the member setting is completed, the member can submit confirmation to issue the red packet by clicking the 'red packet control', and the related server can execute the interactive operation corresponding to the red packet. The server of the present disclosure may forward the "red envelope" request to the origin server of the payment source selected by the member, with the origin server performing the transfer of the charge corresponding to the amount of the red envelope to the other account. With the group account as the payment source, an operation of transferring the fee corresponding to the amount of the bonus money from the group account to another account is performed by a server that maintains the group account.

Similar to the red parcel interface, some interactive controls or interfaces may also be provided for the member in the corresponding interface for implementing functions such as cash withdrawal, transfer and the like, so that the member can set some information related to the cash withdrawal or transfer behavior thereof, such as a payee account, cash withdrawal/transfer amount, payment method, payment time, remark information and the like, by clicking the relevant control or interface.

Thus, in some team payout scenarios, for example, an account administrator may implement payout management for a common account by presenting a payment code to a merchant. In the expense scenario that transfer to other members in the group, red package, or cash out to a specific account is required, the account administrator may respectively implement the payment by clicking on the interface with operability such as "red package" interface 604, "cash out" interface 605, "transfer" interface 606, which is not described in detail herein.

Meanwhile, all account interactions involving the common account can be notified to all members of the communication group, for example, in the form of messages, or to other designated objects outside the communication group. In different scenarios, the message notification form and the notified message content may be different and may also be set via the member. For example, in an instant messaging group scenario, all account interactions involving the group account may be exposed on a group chat interface or in the form of application notifications to designated objects belonging to the same application as the group. In the mail group scenario, all account interactions involving the group account can be notified to group members or other objects by way of mail.

Returning to the instant messenger APP based example of the present disclosure, similar to the messages 205 shown in fig. 5A-5C, each time a change occurs in the group account (e.g., revenue or expense occurs), a corresponding message may be displayed in the group chat interface 200, such as a credit message 207 "edward deposits 30 dollars in the group fund" shown in fig. 7. Therefore, all members in the group can check the balance change of the group account in real time and monitor the balance detail of the group account in real time.

Therefore, by combining the interaction interfaces under the instant messaging APP working community scene as shown in fig. 2 to fig. 7, the community interaction scheme of the present disclosure is described in detail, and by providing the community account interface, each member can implement account interaction operation with the community account through the community account interface, so as to provide technical support for better implementing common maintenance, management and supervision of accounts by each community member. The group interaction scheme can be applied to group interaction in any scene, and can be a work scene or a private scene, and can include but is not limited to a money account, a point account, a token account, a group chat account and the like.

Method or apparatus

The community interaction scheme of the present disclosure as described above may also be implemented as a community interaction method, which may be implemented by a community interaction apparatus. FIG. 8 shows a flow diagram of a community interaction method according to one embodiment of the present disclosure. FIG. 9 shows a schematic block diagram of a community interaction device 900 according to one embodiment of the present disclosure.

As shown in fig. 8, in step S810, a community account interface may be provided on the community interaction interfaces of the at least two members, respectively, for example, by the community account interface device 910 shown in fig. 9, where the community account interfaces correspond to the same community account. Wherein a community may comprise at least two members.

In step S820, account interaction operation of the member with respect to the community account may be implemented, for example, by the interaction device 920 shown in fig. 9, in response to interaction operation between the member and the community account interface.

In the communication group application scenario, the group account interface device 910 may be a group account interface device 910, and in step S810, the group account interface device 910 may provide a group account interface (i.e., a group account interface) on an interactive interface of the communication group, where the group account interface corresponds to a common account (i.e., a group account) bound to the communication group. In step S820, the interaction device 920 may implement account interaction of the member with respect to the public account in response to interaction between the member and the group account interface.

Optionally, the community account interface may include at least one of a first interface, a second interface, a third interface, a fourth interface, and a fifth interface, and the interaction means may be capable of implementing an account interaction operation for the community account by the member in response to an interaction operation between the member and the community account interface, and the step of implementing an account interaction operation for the community account by the member may include at least one of: creating the community account in response to a first interaction between a member and the first interface; and/or in response to a second interaction operation between a member and the second interface, implementing a transfer operation from the member's personal account to the community account; and/or in response to a third interaction between a member and the third interface, implementing an outbound payment or roll-out operation for the group account; and/or in response to a fourth interaction operation between a member and the fourth interface, implementing a viewing operation of the member on account information of the community account, wherein the account information is output to the member; and/or responding to a fifth interactive operation between the members and the fifth interface to realize the balance return operation of the group account, wherein all or part of the balance of the group account is divided into a plurality of shares according to a preset or appointed balance return rule and is transferred to the personal accounts of the at least two members respectively. Optionally, the at least two members each have a right to perform various interactive operations on the community account interface; or the at least two members are respectively set with the authority to execute various interactive operations.

Optionally, the community manager has the right to perform the first interactive operation; and/or setting, by a community administrator, members of the community having the right to perform the first interactive operation; and/or the account administrator has the right to perform the third and/or fifth interoperation; and/or setting, by an account administrator, members of the community having a right to perform the second and/or fourth interactive operations; and/or setting the balance return rule by an account administrator, wherein the community administrator is one of the at least two members, and the account administrator comprises a community administrator and/or a member designated by the community administrator and/or a member creating the community account.

Optionally, the account administrator may be provided with an authority mode setting interface, and the authority mode setting interface may be used to select an authority mode from a plurality of preset authority modes.

Optionally, the account information may include at least one of: account balance, account two-dimensional code, income detail and expenditure detail.

Optionally, a plurality of community account interfaces may be respectively provided on the community interaction interfaces of the at least two members, the plurality of community account interfaces respectively corresponding to a plurality of community accounts belonging to the community.

Communication group interaction scheme

The community interaction scheme as described above may be implemented as a communication group interaction scheme implemented in a communication group application scenario, which is briefly described below, and the specific implementation details thereof are the same as or similar to the scheme of the community interaction system as described above, and refer to the related description above.

In one embodiment, the communication group interaction scheme may be implemented by a communication group interaction system. The communication group interaction system can comprise a server and electronic equipment of members, wherein the server maintains a common account bound with the communication group; a group account interface is respectively provided on the interactive interfaces of the communication groups of the electronic devices of the at least two members, wherein the group account interface corresponds to a common account bound with the communication groups; in response to an interaction between a member and the group account interface, the member's electronic device sends an account interaction request to the server to enable account interaction of the member for the common account request.

Optionally, the account interaction comprises at least one of: creating the public account;

a transfer operation from the member's personal account to the public account; external payment or roll-out operation of the public account; viewing operation of account information of the public account; and the balance of the public account is returned, wherein all or part of the balance of the public account is divided into a plurality of shares according to a preset or appointed balance return rule and is respectively transferred into the personal accounts of the at least two members.

Optionally, an identifier of a member creating the public account may also be recorded in association with the public account on the server or a device accessible to the server.

In one embodiment, the communication group interaction scheme may be implemented as a communication group interaction method implemented by a communication group interaction apparatus.

In particular, a group account interface may be provided on an interactive interface of the communication group, for example, by a group account interface device, the group account interface corresponding to a common account bound to the communication group. The interaction device may operate on the public account in response to an interaction between a member and the group account interface.

Optionally, the group account interface provided by the group account interface device may include at least one of a first interface, a second interface, a third interface, a fourth interface, and a fifth interface, and the interaction device may implement at least one of the following: in response to an interaction between a member and the group account interface, the step of enabling account interaction by the member with respect to the common account includes at least one of: creating the public account in response to a first interaction between a member and the first interface; in response to a second interaction operation between the member and the second interface, implementing a transfer operation from the member's personal account to the public account; responding to a third interactive operation between the member and the third interface, and realizing an outward payment or roll-out operation of the public account; in response to a fourth interaction operation between the member and the fourth interface, implementing a viewing operation of the member on account information of the public account, wherein the account information is output to the member; responding to a fifth interactive operation between the members and the fifth interface, and realizing balance return operation of the public account, wherein all or part of the balance of the public account is divided into a plurality of shares according to a preset or appointed balance return rule, and the shares are transferred to the personal accounts of the at least two members respectively.

Common account management

The department involved in community/public account creation may also be implemented as a public account management scheme.

In one embodiment, the common account management method may be implemented by a server.

Specifically, the server can respond to an account creation request of an application member for creating a common account for a communication group to which the application member belongs, and check the authority corresponding to the application member; and under the condition that the audit confirms that the application member is authorized to create the public account, creating the public account for the communication group.

Optionally, on a server or a device accessible by the server, a member list of the communication group and/or first authorization information for the communication group is recorded, the first authorization information being used to define an object or an audit rule having a right to create a common account for the communication group, and wherein the server may audit the right corresponding to the application member based on the member list and/or the first authorization information.

Optionally, the server may further record, on a server or a device accessible to the server, an identifier of the application member, an identifier of an account administrator of the public account, and/or second authorization information for the public account in association with the public account, where the account administrator and/or the second authorization information are set by the application member and/or a group administrator of the communication group, and the second authorization information is used to respectively define the authority of the members of the communication group to interact with various accounts of the public account.

In one embodiment, the common account management method may be implemented by a system.

Specifically, in response to an interactive operation of an application member on a group account creation interface displayed on an interactive interface of the communication group, the electronic device of the application member sends an account creation request to a server; in response to an account creation request for creating a common account for a communication group to which an application member belongs, the server audits the authority corresponding to the application member; and under the condition that the audit confirms that the application member is authorized to create the public account, creating the public account for the communication group.

Optionally, a group account interface may be provided on an interactive interface of the communication group, the group account interface corresponding to the common account; and operating the public account in response to an interaction between a member and the group account interface.

The specific implementation details can be referred to the above related description, and are not repeated herein.

[ calculating device ]

Referring to fig. 10, the computing device 1000 includes a memory 1010 and a processor 1020.

The processor 1020 may be a multi-core processor or may include multiple processors. In some embodiments, processor 1020 may include a general-purpose host processor and one or more special purpose coprocessors such as a Graphics Processor (GPU), Digital Signal Processor (DSP), or the like. In some embodiments, processor 1020 may be implemented using custom circuits, such as an Application Specific Integrated Circuit (ASIC) or a Field Programmable Gate Array (FPGA).

The memory 1010 may include various types of storage units, such as system memory, Read Only Memory (ROM), and permanent storage. Wherein the ROM may store static data or instructions that are needed by the processor 1020 or other modules of the computer. The persistent storage device may be a read-write storage device. The persistent storage may be a non-volatile storage device that does not lose stored instructions and data even after the computer is powered off. In some embodiments, the persistent storage device employs a mass storage device (e.g., magnetic or optical disk, flash memory) as the persistent storage device. In other embodiments, the permanent storage may be a removable storage device (e.g., floppy disk, optical drive). The system memory may be a read-write memory device or a volatile read-write memory device, such as a dynamic random access memory. The system memory may store instructions and data that some or all of the processors require at runtime. Further, the memory 1010 may include any combination of computer-readable storage media, including various types of semiconductor memory chips (DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), magnetic and/or optical disks, among others. In some embodiments, memory 1010 may include a removable storage device that is readable and/or writable, such as a Compact Disc (CD), a read-only digital versatile disc (e.g., DVD-ROM, dual layer DVD-ROM), a read-only Blu-ray disc, an ultra-density optical disc, a flash memory card (e.g., SD card, min SD card, Micro-SD card, etc.), a magnetic floppy disc, or the like. Computer-readable storage media do not contain carrier waves or transitory electronic signals transmitted by wireless or wired means.

The memory 1010 has stored thereon processable code that, when processed by the processor 1020, causes the processor 1020 to perform the community interaction methods described above.

The community interaction method, apparatus, system according to the present invention have been described in detail above with reference to the accompanying drawings.

Furthermore, the method according to the invention may also be implemented as a computer program or computer program product comprising computer program code instructions for carrying out the above-mentioned steps defined in the above-mentioned method of the invention.

Alternatively, the invention may also be embodied as a non-transitory machine-readable storage medium (or computer-readable storage medium, or machine-readable storage medium) having stored thereon executable code (or a computer program, or computer instruction code) which, when executed by a processor of an electronic device (or computing device, server, etc.), causes the processor to perform the steps of the above-described method according to the invention.

Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems and methods according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Having described embodiments of the present invention, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen in order to best explain the principles of the embodiments, the practical application, or improvements made to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A method of common account management, comprising:

in response to an account creation request of an application member for creating a common account for a communication group to which the application member belongs, checking the authority corresponding to the application member;

and under the condition that the audit confirms that the application member is authorized to create the public account, creating the public account for the communication group.

2. The method according to claim 1, characterized in that on a server or a device accessible by the server, a list of members of the communication group and/or first authorization information for the communication group defining objects or audit rules with the right to create a common account for the communication group is recorded,

and wherein the rights corresponding to the application member are audited based on the member list and/or the first authorization information.

3. The method of claim 2, wherein the step of reviewing the permissions corresponding to the member comprises:

auditing whether the application member is a specific object with the authority of creating a community account for the communication group; and/or

Forwarding the account creation request to at least one designated object and auditing whether the account creation request is approved via the at least one designated object based on feedback of the designated object in response to the account creation request; and/or

Forwarding the account creation request to other members of the communication group, and auditing whether the account creation request is approved by most or all members of the communication group based on feedback from the other members in response to the account creation request.

4. The method of claim 1, further comprising:

recording, on a server or a device accessible to the server, an identifier of the application member, an identifier of an account administrator of the public account, and/or second authorization information for the public account in association with the public account,

the account administrator and/or the second authorization information are set by the application member and/or the group administrator of the communication group, and the second authorization information is used for respectively limiting the authority of the members of the communication group for various account interactive operations of the common account.

5. The method of claim 1, wherein a group account interface is provided on each of the interactive interfaces of the communication group, the group account interface corresponding to the common account, and the method further comprises:

responding to an account interoperation request of a member of the communication group to enable account inquiry or use of the member against the common account,

the account interaction request is issued in response to the member's account interaction with a group account interface displayed on the interaction interface.

6. The method of claim 1, wherein the server maintains a plurality of common accounts corresponding to the communication group;

a plurality of group account interfaces are respectively provided on the interactive interfaces of the communication group, and the plurality of group account interfaces respectively correspond to the plurality of common accounts.

7. The method of claim 3, wherein the specific object comprises at least one of:

a group administrator;

at least one secondary administrator designated by the group administrator;

members of the communication group belonging to the group having the operation level of creating the group account; and

and a designated object outside the communication group, wherein the designated object has the public account authority for the communication group.

8. The method of claim 3, wherein the designated object comprises at least one of:

a group administrator;

a manager of a department or organization to which the communication group belongs;

a guardian of a member of the communication group.

9. A method of common account management, comprising:

responding to the interactive operation of an application member on a group account creation interface displayed on the interactive interface of the communication group, and sending an account creation request to a server by the electronic equipment of the application member;

in response to an account creation request for creating a common account for a communication group to which an application member belongs, the server audits the authority corresponding to the application member; and

10. The method of claim 9, further comprising:

providing a group account interface on an interactive interface of the communication group, the group account interface corresponding to the common account; and

and responding to account interaction operation between members and the group account interface, and operating the public account.

11. The method according to claim 9, characterized in that on a server or a device accessible by the server, a list of members of the communication group and/or first authorization information for the communication group defining objects or audit rules with the right to create a common account for the communication group is recorded,

12. The method of claim 11, wherein the step of reviewing the rights corresponding to the member comprises:

13. A communication group interaction method, comprising:

providing a group account interface on an interactive interface of the communication group, the group account interface corresponding to a common account bound with the communication group; and

14. The method of claim 13, wherein the group account interface comprises at least one of a first interface, a second interface, a third interface, a fourth interface, and a fifth interface, and wherein the act of operating on the common account in response to the interaction between the member and the group account interface comprises at least one of:

creating the public account in response to a first interaction between a member and the first interface;

in response to a second interaction operation between the member and the second interface, implementing a transfer operation from the member's personal account to the public account;

responding to a third interactive operation between the member and the third interface, and realizing an outward payment or roll-out operation of the public account;

in response to a fourth interaction operation between the member and the fourth interface, implementing a viewing operation of the member on account information of the public account, wherein the account information is output to the member;

responding to a fifth interactive operation between the members and the fifth interface, and realizing balance return operation of the public account, wherein all or part of the balance of the public account is divided into a plurality of shares according to a preset or appointed balance return rule, and the shares are transferred to the personal accounts of the at least two members respectively.

15. The method of claim 14,

the at least two members each having the authority to perform various interactions with the group account interface; or

And the at least two members are respectively set with the authority for executing various interactive operations.

16. The method of claim 15,

the group administrator has the authority to execute the first interactive operation; and/or

Setting, by a group administrator, members of the communication group having a right to perform the first interactive operation; and/or

The account administrator has the right to perform the third interactive operation and/or the fifth interactive operation; and/or

Setting, by an account administrator, members of the communication group having a right to perform the second and/or fourth interoperation; and/or

The balance return rule is set by the account administrator,

wherein the group administrator is one of the at least two members and the account administrator comprises a group administrator and/or a member designated by a group administrator and/or a member creating the common account.

17. The method of claim 15,

and providing an authority mode setting interface for the account administrator, wherein the authority mode setting interface is used for selecting an authority mode from a plurality of preset authority modes.

18. The method of claim 14,

the account information includes at least one of: account balance, account two-dimensional code, income detail and expenditure detail.

19. The method according to any one of claims 13-18,

providing a plurality of group account interfaces on the interactive interfaces of the communication group respectively, wherein the plurality of group account interfaces correspond to a plurality of public accounts bound with the communication group.

20. A community interaction method, said community comprising at least two members, the method comprising:

respectively providing a group account interface on the group interaction interfaces of the at least two members, wherein the group account interfaces correspond to the same group account; and

and responding to the interaction operation between the member and the community account interface to operate the community account.

21. A communication group interaction system, said communication group comprising at least two members, characterized in that the system comprises a server and electronic devices of the members, wherein,

the server maintaining a common account bound to the communication group;

a group account interface is respectively provided on the interactive interfaces of the communication groups of the electronic devices of the at least two members, wherein the group account interface corresponds to a common account bound with the communication groups;

in response to an interaction between a member and the group account interface, the member's electronic device sends an account interaction request to the server to enable account interaction of the member for the common account request.

22. The system of claim 21, wherein the account interaction comprises at least one of:

creating the public account;

a transfer operation from the member's personal account to the public account;

external payment or roll-out operation of the public account;

viewing operation of account information of the public account; and

and (3) balance returning operation of the public account, wherein all or part of the balance of the public account is divided into a plurality of shares according to a preset or appointed balance returning rule and the shares are respectively transferred into the personal accounts of the at least two members.

23. The system of claim 22, wherein the list of members of the communication group is recorded in association with the common account on the server or a device accessible to the server;

the server receives an account interaction operation request from the electronic equipment of the member in the member list and executes the account interaction operation.

24. The system of claim 23,

The member list includes authorization information for respectively defining the authority of the at least two members to perform the corresponding type of account interaction.

25. The system of claim 22, further comprising:

recording, on the server or a device accessible to the server, an identifier of a member creating the public account in association with the public account.

26. The system according to any of claims 21-25, wherein said server maintains a plurality of common accounts belonging to said communication group;

a plurality of group account interfaces are respectively provided on the interactive interfaces of the communication groups of the electronic devices of the at least two members, and the plurality of group account interfaces respectively correspond to the plurality of common accounts.

27. A community interaction system, said community comprising at least two members, characterized in that the system comprises a server and electronic devices of the members, wherein,

the server maintaining a community account belonging to the community;

respectively providing community account interfaces on community interaction interfaces of the electronic devices of the at least two members, wherein the community account interfaces correspond to the community accounts;

in response to an interaction between a member and the community account interface, the electronic device of the member sends an account interaction operation request to the server to realize the account interaction operation of the member for the community account request.

28. A public account management apparatus, comprising:

the auditing device is used for responding to an account establishing request of an application member for establishing a common account for a communication group to which the application member belongs, and auditing the authority corresponding to the application member;

and the account creating device is used for creating a common account for the communication group under the condition that the application member is checked and determined to have the right to create the common account.

29. An apparatus for communication group interaction, the communication group comprising at least two members, the apparatus comprising:

the group account interface device is used for providing a group account interface on an interactive interface of the communication group, and the group account interface corresponds to a common account bound with the communication group; and

and the interaction device is used for responding to the interaction operation between the members and the group account interface and operating the public account.

30. The apparatus of claim 29, wherein the group account interface provided by the group account interface apparatus comprises at least one of a first interface, a second interface, a third interface, a fourth interface, and a fifth interface,

the interaction means is for implementing at least one of:

in response to a fourth interaction operation between the member and the fourth interface, implementing a viewing operation of the member on account information of the public account, wherein the account information is output to the member; and

31. An apparatus for community interaction, said community comprising at least two members, the apparatus comprising:

the community account interface device is used for respectively providing community account interfaces on community interaction interfaces of the at least two members, and the community account interfaces correspond to the same community account; and

and the interaction device is used for responding to the interaction operation between the members and the community account interface and operating the community account.

32. A computing device, comprising:

a processor; and

a memory having executable code stored thereon, which when executed by the processor, causes the processor to perform the method of any of claims 1-20.

33. A non-transitory machine-readable storage medium having stored thereon executable code, which when executed by a processor of an electronic device, causes the processor to perform the method of any of claims 1-20.