CN111555964A

CN111555964A - Group member management method, electronic device and storage medium

Info

Publication number: CN111555964A
Application number: CN202010366831.6A
Authority: CN
Inventors: 沈姿绮; 牛桂林
Original assignee: Netease Hangzhou Network Co Ltd
Current assignee: Netease Hangzhou Network Co Ltd
Priority date: 2020-04-30
Filing date: 2020-04-30
Publication date: 2020-08-18

Abstract

The application provides a group member management method, an electronic device and a storage medium, wherein the method comprises the following steps: providing a first member list on a group session interface of a terminal, wherein the first member list provides an invitation object to be joined into a group, and the invitation object to be joined into the group is an invitation object which does not respond to a first invitation request for joining the group; and responding to the first operation acted on the object to be invited to the group, and sending a second invitation request to the object to be invited to the group.

Description

Group member management method, electronic device and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a group member management method, an electronic device, and a storage medium.

Background

Most of the existing instant messaging software has the function of establishing a group, and after the group is established, all members joining the group can perform information interaction in the group. Currently, the way for a user to join a group includes: the group manager sends out group access invitation to some users, and the users join the group after agreeing to the invitation; or the user actively initiates a group application or responds to the invitation of other friends to generate the group application, and the user can join in the group after the group administrator agrees to the group application.

However, for the group administrator, after sending the invitation to join the group, if the other side does not process the invitation, the group list does not display the member, and at this time, the group administrator needs to compare the members in the invitation information with the members that have already joined the group to determine which members have not joined the group, and then send the invitation information again for the members, which is complicated and complicated in operation and low in efficiency.

It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.

Disclosure of Invention

In view of this, embodiments of the present application provide a group member management method, an electronic device, and a storage medium, so as to improve efficiency when a user initiates a group invitation again.

In a first aspect, an embodiment of the present application provides a method for managing group members, where the method includes:

providing a first member list on a group session interface of a terminal, wherein the first member list provides an invitation object to be joined into a group, and the invitation object to be joined into the group is an invitation object which does not respond to a first invitation request for joining the group;

and responding to the first operation acted on the object to be invited to the group, and sending a second invitation request to the object to be invited to the group.

Optionally, the providing the invitation object to enter the group by the first member list includes: and providing the invitation object to be entered into the group in the first member list according to the invitation object information to be entered into the group contained in the acquired group member information.

Optionally, the group member information is determined according to account authority information of the group logged in by the terminal, where the account authority information at least includes: the group administrator information comprises first group administrator information or second group administrator information.

Optionally, the group member information is according to the

The account authority information of the group logged by the terminal is determined to comprise:

if the account authority information for logging in the group is group administrator information, the group member information comprises information of an invitation object to be entered into the group;

otherwise, the group member information does not contain the information of the invitation object of the group to be entered.

Optionally, the method further comprises:

and if the group member information does not contain the information of the invitation object to enter the group, the first member list does not provide the invitation object to enter the group.

Optionally, the first invitation request to join the group comprises: the first invitation request is sent by a first group administrator or a second group administrator, wherein the first group administrator and the second group administrator correspond to the first group administrator information and the second group administrator information respectively.

Optionally, the information of the invitation object to enter the group includes information of an invitation object that does not respond to the first invitation request sent by a group administrator, where the group administrator includes the first group administrator and the second group administrator.

Optionally, the information of the invitation object to enter the group includes:

if the account authority information of the terminal login group is the information of the first group administrator, the invitation object information to be entered into the group is the invitation object information which does not respond to the first invitation request sent by the first group administrator;

if the account authority information of the terminal login group is the second group administrator information, the invitation object information to enter the group is the invitation object information which does not respond to the first invitation request sent by the second group administrator.

Optionally, the first member list provides a first control corresponding to the invitation object to enter a group;

the first operation of acting on the object to be joined group invitation is as follows:

a first operation acting on the first control.

Optionally, the first member list contains a first group, the first group comprising a collapsed state and an expanded display state;

the providing of the invitation object to be joined to the group by the first member list comprises:

and responding to a first operation acted on the first group, and switching the first group from a folded state to an expanded display state, wherein the first group displays the object to be invited into the group.

Optionally, the response comprises a consent invitation response, the first member list provides members who have joined the group, the method further comprising:

responding to an invitation agreement response made by the to-be-joined group invitation object to the first invitation request or the second invitation request, and switching the to-be-joined group invitation object to be a member which has joined the group.

Optionally, the response comprises a decline invitation response, the method further comprising:

and responding to a response of the invitation refusing response of the invitation object of the group to be entered to the first invitation request or the second invitation request, and deleting the invitation object of the group to be entered from the first member list.

Optionally, the first member list provides an application group entry object and an entered group member; the method further comprises the following steps:

and responding to a first operation acted on the application group object, and switching the application group object into an already-entered group member.

Optionally, the first member list provides a second control corresponding to the application group object;

the first operation acting on the application group object comprises:

a first operation acting on the second control.

Optionally, the method further comprises:

deleting the application-to-group object from the first member list in response to a first operation on the application-to-group object.

Optionally, the first member list provides a third control corresponding to the application group object;

the first operation acting on the application group object comprises:

a first operation acting on the third control.

Optionally, the method further comprises:

and responding to a second operation acted on the application group-entering object, wherein the first member list provides application information corresponding to the application group-entering object.

Optionally, the method further comprises:

responding to a second operation acted on the invitation object of the group to be entered, wherein the first member list provides invitation state information, and the invitation state information at least comprises the number of invitations corresponding to the invitation object of the group to be entered.

Optionally, the method further comprises:

responding to a third operation acted on the first member list, and determining an invitation object corresponding to the first invitation request sent by the first group administrator as a target invitation object from the invitation objects to be grouped;

and sending a second invitation request to the target invitation object.

In a second aspect, an embodiment of the present application provides a method for managing group members, where the method includes:

responding to a first operation acted on the object to be invited into the group, wherein the group session interface provides a first window;

and responding to the first operation acted on the first window, and sending a second invitation request to the object to be invited into the group.

Optionally, the group member information is determined according to account authority information of the group logged in by the terminal, where the account authority information at least includes: group administrator information or non-group administrator information, wherein the group administrator information comprises first group administrator information and second group administrator information.

Optionally, the determining, by the group member information according to the account authority information of the group logged in by the terminal, includes:

if the account authority information for logging in the group is the group administrator information, the group member information comprises information of an invitation object to enter the group;

Optionally, the method further comprises:

Optionally, the first member list provides a fourth control corresponding to the to-be-entered group invitation object;

a first operation acting on the fourth control.

Optionally, the first member list provides a first group, the first group comprising a collapsed state and an expanded display state;

the displaying the object to be invited to the group in the first group comprises:

Optionally, the response comprises a consent invitation response, the first member list provides members of the entered group, the method further comprising:

responding to an invitation agreement response made by the to-be-joined group invitation object to the first invitation request or the second invitation request, and switching the to-be-joined group invitation object to a joined group member.

Optionally, the first member list provides members who apply for group joining and have joined a group; the method further comprises the following steps:

responding to a first operation acted on the group application object, and providing a second window by the group session interface;

and responding to the first operation acted on the second window, and switching the object applying for group joining into a member of the group.

Optionally, the second window provides a second control;

the first operation on the second window comprises:

a first operation acting on the second control.

Optionally, the method further comprises:

responding to a first operation applied to the group object, and providing a second window by the group session interface;

and in response to a first operation on the second window, deleting the group application object from the first member list.

Optionally, the second window provides a third control;

the first operation on the second window comprises:

a first operation acting on the third control.

Optionally, the second window provides application information corresponding to the application group object.

Optionally, providing a fifth control for the application group object in the first member list;

the first operation acting on the application group object comprises:

a first operation acting on the fifth control.

Optionally, the method further comprises:

and sending a second invitation request to the target invitation object.

Optionally, the invitation request includes invitation information, and the invitation information is generated in a confirmation window in a typing or recording manner.

In a third aspect, an embodiment of the present application provides an electronic device, including: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating via the bus when the electronic device is running, the processor executing the machine-readable instructions to perform the steps of the method for managing group members according to any one of the first or second aspects.

In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to perform the steps of the group member management method according to any one of the first aspect or the second aspect.

The technical scheme provided by the embodiment of the application can have the following beneficial effects:

according to the group member management method, the electronic device and the storage medium provided by the application, after the first invitation request for joining the group is sent to the invitation object, if the invitation object does not respond to the first invitation request, the invitation object is used as the invitation object to be joined to the group and is displayed in the first member list provided by the group session interface of the terminal, so that the first member list can be used for knowing which invitation objects are not joined to the group, and the first operation can be performed on the invitation object to be joined to the group in the first member list so as to perform secondary invitation on the invitation object to be joined to the group. Compared with the sending mode in the prior art when the group invitation is initiated again, the operation is more convenient and faster, and the processing efficiency is improved.

In order to make the aforementioned objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.

Fig. 1 is a schematic flowchart of a management method for group members according to an embodiment of the present disclosure;

fig. 2 is a schematic flowchart of a management method for group members in another group according to an embodiment of the present application;

fig. 3 is a schematic diagram of a group session interface according to an embodiment of the present application;

fig. 4 is a schematic diagram of another group session interface provided in an embodiment of the present application;

fig. 5 is a schematic diagram of another group session interface provided in an embodiment of the present application;

fig. 6 is a schematic diagram of another group session interface provided in an embodiment of the present application;

fig. 7 is a schematic diagram of another group session interface provided in an embodiment of the present application;

fig. 8 is a schematic flowchart of a management method for group members according to a second embodiment of the present application;

fig. 9 is a schematic structural diagram of an electronic device according to a third embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present application without making any creative effort, shall fall within the protection scope of the present application.

In the related art, after establishing a group (e.g., a conference group, a live group, a chat group, etc.), a group administrator may send an invitation request to other users (e.g., friends) to join the other users in the group, if a user does not perform any operation on the invitation request, the user cannot join the group, and cannot be found in the group, and for the group administrator, the group administrator may initiate the invitation request to a plurality of users, if the group administrator wants to check an invitation object that is not joined to the group (i.e., the user that is referred to earlier), it is necessary to compare members in the invitation information with members that have already entered the group to determine which members have not entered the group, and if the group administrator wants to initiate a group invitation again to the user, it is necessary for the group administrator to first find the user (e.g., find the user from a friend list), the group invitation can then be initiated again to the user, thereby reducing the efficiency when the group invitation is initiated again to the user.

Based on the above problems, embodiments of the present application provide a group member management method, an electronic device, and a storage medium, so as to improve efficiency when a user initiates a group invitation again.

Example one

Fig. 1 is a schematic flowchart of a management method for group members according to an embodiment of the present application, and as shown in fig. 1, the management method for group members includes the following steps:

step 101, providing a first member list on a group session interface of a terminal, wherein the first member list provides a to-be-group invitation object, and the to-be-group invitation object is an invitation object which does not respond to a first invitation request for joining a group.

Specifically, after the group is established, a group session interface is displayed on the terminal, and the group session interface displays: the method comprises the following steps that a display area, an information input area, a friend list, a function key and the like of sent information can send a first invitation request for joining a group to an invitation object through a terminal, wherein the first invitation request comprises the following steps: determining an invitation object from a buddy list, and then sending a first invitation request to the invitation object for inviting the invitation object to join the group, wherein, when determining the invitation object, only one invitation object may be determined at a time, or a plurality of invitation objects may be determined at a time, if the invitation object does not respond to the first invitation request, and the invitation object does not join the group, in order to facilitate checking which invitation objects do not join the group, the invitation object needs to be taken as an invitation object to be joined to the group, and the invitation object is displayed in a first member list provided by a group session interface of the terminal, and the invitation object which does not join the group can be known through the first member list, for example: sending a first invitation request for inviting the invitation object 1, the invitation object 2 and the invitation object 3 to join the group by the terminal, if the invitation object 2 and the invitation object 3 do not respond to the first invitation request, taking the invitation object 2 and the invitation object 3 as invitation objects to be joined into the group, and displaying the invitation object 2 and the invitation object 3 as invitation objects to be joined into the group in a first member list.

It should be noted that the first member list may further include other information, such as: the user who has joined the group, the layout of the group conversation interface and the content displayed in the first member list can be set according to actual needs, and are not described in detail here.

And 102, responding to the first operation acted on the object to be invited to the group, and sending a second invitation request to the object to be invited to the group.

Specifically, after obtaining the first member list including the invitation objects to enter the group, it may be determined, through the first member list, which invitation objects do not respond to the first invitation request, that is: determining which invitation objects are not joined to the group through the first member list, and if it is desired to initiate a group invitation to an invitation object that is not joined to the group again, performing a first operation on the invitation object to be grouped provided by the first member list, for example: the invitation objects to be grouped provided in the first member list include an invitation object 1 to be grouped, an invitation object 2 to be grouped and an invitation object 3 to be grouped, if the invitation object 1 to be grouped and the invitation object 2 to be grouped are required to initiate group invitation again, a first operation can be performed on the invitation object 1 to be grouped and the invitation object 2 to be grouped in the first member list, or the first member list is also provided with a virtual key for initiating group invitation again for all the invitation objects to be grouped, if the invitation objects to be grouped are required to initiate group invitation again, the first operation can be performed on the virtual key, after the terminal responds to the first operation, a second invitation request is sent to the corresponding invitation object to be grouped, thereby realizing the purpose of initiating group invitation for the invitation object to be grouped again, compared with the sending mode when group invitation is initiated again in the prior art, the method and the device are beneficial to improving the efficiency when the group invitation is initiated again.

It should be noted that the first operation may include a click operation, for example: the object to be invited to the group to which the group invitation is to be entered is selected by a click operation, and then the request to be sent to the group invitation (i.e., the second invitation request) is determined by the click operation, or the virtual key is clicked to determine that the request to be sent to the group invitation (i.e., the second invitation request) is sent to all the objects to be invited to the group.

In one possible embodiment, the providing the to-group invitation object by the first member list includes: and providing the invitation object to be entered into the group in the first member list according to the invitation object information to be entered into the group contained in the acquired group member information.

Specifically, after the group is established, the server stores the group member information of the group, the object information of the group that has joined the group and the object information that has been invited but has not responded to the invitation (i.e., the object information of the invitation to group), in the server, the two object information may be marked by different marks, then the object information of the invitation to group is obtained by the mark, and then the terminal may determine the object of the invitation to group according to the object information of the invitation to group that is obtained from the server and display the object of the invitation to group in the first member list of the group session interface.

It should be noted that the above mentioned identifiers include: the nickname may be other information that can distinguish different objects, and the specific identifier may be set according to actual needs, and is not specifically limited herein.

In a possible embodiment, the group member information is determined according to account authority information of the terminal logging in the group, and the account authority information at least includes: the group administrator information comprises first group administrator information or second group administrator information.

Specifically, for a certain group, the group includes a group administrator and a non-group administrator, wherein the group administrator may be divided into first group administrator information and second group administrator information according to different administrative authorities, optionally, the group administrator includes a group owner and a common administrator other than the group owner, and the non-group administrator includes common members in the group; when a group member enters a group, account authority information of the group member needs to be acquired so as to judge whether the group member is a group administrator according to the account authority information, and only when the group member is the group administrator, group member information including information of an invitation object to enter the group is provided on a group session interface of a terminal, that is: only the group administrator can view the invitation to group object.

In a possible embodiment, when the step of determining the group member information according to the account permission information of the terminal logging in the group is executed, if the account permission information of the logging in the group is the first group administrator information or the second group administrator information, the group member information includes information of an invitation object to be entered into the group; otherwise, the group member information does not contain the information of the invitation object of the group to be entered.

Specifically, when a group member enters a group, account authority information of the group member in the group is determined to determine whether the group member is a group administrator or a non-group administrator, and if it is determined that the account authority information of the group member is the first group administrator information or the second group administrator information, it indicates that the group member has an administration authority for the group, in order to facilitate the group administrator to manage the group, group invitation object information to be entered needs to be added to the group member information corresponding to the group administrator, so that the group administrator knows an invitation object that does not respond to the first invitation request, and for the non-group administrator, because the non-group administrator does not have the administration authority for the group, the group invitation object information to be entered does not need to be added to the group member information corresponding to the non-group administrator.

In one possible implementation, if the group member information does not include information of an invitation to group object, the first member list does not provide the invitation to group object.

Specifically, the group session interfaces of the group administrator and the non-group administrator both provide the first member list, but the first member list in the group session interface of the group administrator includes the information of the invitation object to be grouped, and the first member list in the group session interface of the non-group administrator does not include the information of the invitation object to be grouped.

In one possible embodiment, the first invitation request to join the group includes: the first invitation request is sent by a first group administrator or a second group administrator, wherein the first group administrator and the second group administrator correspond to the first group administrator information and the second group administrator information respectively.

Specifically, the group administrator of the group can send a first invitation request, and send a second invitation request to the invitation object to be entered into the group when the invitation is not answered, where the group administrator includes the first group administrator or the second group administrator.

In one possible embodiment, the to-be-joined invitation object information includes invitation object information that is not in response to the first invitation request issued by a group administrator, the group administrator including the first group administrator and the second group administrator.

Specifically, whether a first group administrator (e.g., a group owner) or a second group administrator (e.g., a common administrator) may send a first invitation request to the invitation object, and whether the first invitation request is sent by administrator a or administrator B, as long as the invitation object does not respond to the first invitation request (e.g., the first invitation request is not seen or no processing is done after the first invitation request is seen), the invitation object information of the invitation object is used as the invitation object information of the group to be entered, and the invitation object of the group to be entered corresponding to the invitation object information of the group to be entered is displayed in the group session interface provided by all group administrators in the first member list, and all group administrators may subsequently process the invitation object of the group to be entered. For example, if the invitation object 1 does not respond to the first invitation request sent by the administrator a, the invitation object 1 will be displayed as the invitation object to enter the group on the terminal group session interfaces of the group administrator a and other group administrators except the group administrator a, and all the group administrators can make secondary invitations to the invitation object 1.

In one possible embodiment, the information of the to-be-joined group invitation object includes: if the account authority information of the terminal login group is the information of the first group administrator, the invitation object information to be entered into the group is the invitation object information which does not respond to the first invitation request sent by the first group administrator; if the account authority information of the terminal login group is the second group administrator information, the invitation object information to enter the group is the invitation object information which does not respond to the first invitation request sent by the second group administrator.

Specifically, a group may include a plurality of group administrators, each group administrator may send first invitation information to an invitation object, and in order to enable each group administrator to know information of the invitation object that does not respond to the first invitation request sent by the group administrator, it is necessary to display information of the invitation object to be entered into the group corresponding to the group administrator in a group session interface of the group administrator to provide a first member list, for example: the group administrator a sends a first invitation request to the invitation object 1, the invitation object 2 and the invitation object 3, wherein the invitation object 1 and the invitation object 2 do not respond to the first invitation request sent by the group administrator a, the group administrator B sends a first invitation request to the invitation object 4, the invitation object 5 and the invitation object 6, wherein the invitation object 5 and the invitation object 6 do not respond to the first invitation request sent by the group administrator B, the invitation object 1 and the invitation object 2 are displayed as group invitation object information to be entered corresponding to the group administrator a in a group session interface provision first member list of the group administrator, the invitation object 5 and the invitation object 6 are displayed as group invitation object information to be entered corresponding to the group administrator B in a group session interface provision first member list of the group administrator B, and by the above manner, for each group administrator, the group administrator can know the corresponding to-be-entered group invitation object, so that the information of the to-be-entered group invitation object can be effectively protected, and information leakage is prevented.

In one possible embodiment, the first member list provides a first control corresponding to the to-group invitation object; the step of executing the first operation on the object to be joined group invitation may be implemented by the first operation on the first control.

Specifically, each group invitation object to be entered provided by the first member list corresponds to a first control, if a group invitation is to be initiated again for a certain group invitation object to be entered, a first operation may be performed on the first control corresponding to the group invitation object to be entered, and after the first operation is responded, a second invitation request is sent to the group invitation object to be entered.

It should be noted that, the style of the first control may be set according to actual needs, and is not specifically limited herein, for example: the first control may also be a first object identifier, and may be implemented by a first operation on the first object identifier when the step of performing the first operation on the to-be-entered-group invitation object is performed.

In one possible embodiment, the first member list includes a first grouping, the first grouping including a collapsed state and an expanded display state; the providing of the invitation object to be joined to the group by the first member list comprises: and responding to a first operation acted on the first group, and switching the first group from a folded state to an expanded display state, wherein the first group displays the object to be invited into the group.

Specifically, in order to distinguish the invitation object to enter the group from other information in the first member list, a first group is set in the first member list, wherein the first group has two states: the group invitation object to enter is contained in the first group when the first group is in the folded state, at the moment, only one column including the first group is displayed in the first member list, but the group invitation object to enter is not displayed in the first group, after the first group is subjected to first operation, the first group can be switched from the folded state to the unfolded display state, and at the moment, the group invitation object to enter can be displayed in the first group.

In a possible embodiment, the response to the first invitation request or the second invitation request includes an invitation to agree, the members of the group that have joined are also provided in the first member list, and the invitation to join is switched to the members of the group that have joined in response to the invitation to agree made by the invitation to join to the first invitation request or the second invitation request.

Specifically, the first member list further displays members already joined to the group, and after the invitation agreement response made by the invitation object to join to the first invitation request or the second invitation request, the invitation object to join to the group indicates that the invitation object to join to the group agrees to join to the group, and at this time, the invitation object to join to the group in the first member list needs to be switched to a member already joined to the group, for example: and after the invitation agreement response of the invitation object to be joined to the first invitation request or the second invitation request is made by the invitation object to be joined to the group, replacing the identifier of the invitation object to be joined to the group from the first identifier to the second identifier.

In one possible embodiment, the response to the first invitation request or the second invitation request includes a decline invitation response, and the to-be-joined invitation object is deleted from the first member list in response to the decline invitation response made by the to-be-joined invitation object to the first invitation request or the second invitation request.

Specifically, if a waiting group invitation object responds to a refusal invitation made by the first invitation request or the second invitation request, it indicates that the waiting group invitation object explicitly refuses to join the group, and in order to facilitate the management of the group, the waiting group invitation object may be deleted from the first member list.

In one possible embodiment, the first member list provides an application group object and an already-grouped member; the method further comprises the following steps: and responding to a first operation acted on the application group object, and switching the application group object into an already-entered group member.

Specifically, in order to facilitate the group administrator to manage the group, the group member information corresponding to the group administrator includes not only the invitation object to enter the group, but also the information of the object to apply for entering the group and the information of the member to enter the group, the first member list provides not only the invitation object to enter the group, but also the object to apply for entering the group and the member to enter the group, the management of the members of three types can be realized through the first member list, and the group request of the object to apply for entering the group can be realized by performing the first operation on the object to apply for entering the group in the first member list, and after the group request of the object to apply for entering the group is agreed, the object to apply for entering the group is switched to the member to enter the group, for example: and after the group entry request of the group entry object is agreed, replacing the identifier of the group entry object from the third identifier into the second identifier.

In the method, the first member list can be used for knowing which group request applying for the group object is not processed, and the first member list can be used for performing the first operation on the group object applying for processing the group request applying for the group object.

In one possible embodiment, the first member list provides a second control corresponding to the application grouping object, and the step of executing the first operation on the application grouping object can be realized by the first operation on the second control.

Specifically, each application group-entering object provided by the first member list corresponds to one second control, if a group-entering request of a certain application group-entering object is required to be granted, the first operation can be performed on the second control corresponding to the application group-entering object so as to switch the application group-entering object to a member having entered the group.

It should be noted that the style of the second control may be set according to actual needs, and is not specifically limited herein.

In one possible embodiment, the application-to-group object is deleted from the first member list in response to a first operation on the application-to-group object.

Specifically, if the group administrator does not agree with the group entry request applied for the group entry object, the group entry request may be rejected, and the group entry object applied for the group entry object may be deleted from the first member list, so that the group administrator may manage other members.

In one possible embodiment, the first member list provides a third control corresponding to the application group object; the step of performing the first operation on the application group object may be performed by the first operation on the third control.

Specifically, each application group object provided by the first member list corresponds to a third control, if a group request of a certain application group object needs to be rejected, a first operation may be performed on the third control corresponding to the application group object, and after receiving the first operation, the application group object is deleted from the first member list.

The style of the third control element may be set according to actual needs, and is not specifically limited herein.

In one possible embodiment, the method further comprises: and responding to a second operation acted on the application group-entering object, wherein the first member list provides application information corresponding to the application group-entering object.

Specifically, the first member list further provides application information filled by each application group-entering object when the application group-entering object is applied for group entering, when no operation is performed on the application group-entering object, the application information is not displayed in the first member list, and the application information of the application group-entering object is displayed in the first member list after responding to a second operation (for example, responding to an operation that a user slides a mouse to a head portrait of the application group-entering object) applied to the application group-entering object.

The specific display mode of the application information may be set according to actual needs, and is not particularly limited herein.

In one possible embodiment, the method further comprises: responding to a second operation acted on the invitation object of the group to be entered, wherein the first member list provides invitation state information, and the invitation state information at least comprises the number of invitations corresponding to the invitation object of the group to be entered.

Specifically, the first member list further provides the number of invitations of each invitation object to enter the group, when no operation is performed on the invitation object to enter the group, the invitation state information is not displayed in the first member list, and the number of invitations of the invitation object to enter the group is displayed in the first member list after responding to a second operation (for example, responding to a user to slide a mouse onto a head portrait of the invitation object to enter the group or a sending control) acting on the invitation object to enter the group, so that the group administrator can know how many invitations are initiated on the invitation object to enter the group. Optionally, the number of invitations may also be differentiated by each group owner administrator, for example, administrator a invites 1 time, and administrator B invites 0 time. Therefore, when the group owner administrator makes the secondary invitation to the invitation object of the group to be entered, the group owner administrator can intuitively know whether other administrators have made the secondary invitation to the invitation object of the group to be entered, and repeated invitation is prevented from influencing user experience.

In a possible embodiment, fig. 2 is a schematic flowchart of a management method for group members in another group provided in an embodiment of the present application, and as shown in fig. 2, the method further includes the following steps:

step 201, responding to a third operation acting on the first member list, and determining an invitation object corresponding to the first invitation request sent by the first group administrator as a target invitation object from the invitation objects to enter the group.

Step 202, sending a second invitation request to the target invitation object.

Specifically, different group administrators correspond to different invitation objects to be joined, the invitation objects to be joined included in the first member lists corresponding to the different group administrators are the same, in order to enable the different group administrators to manage the corresponding invitation objects to be joined, after performing the third operation on the first member list, the invitation object to be joined corresponding to the group administrator is determined as the target invitation object from the invitation objects to be joined in the first member list, and then a second invitation request is sent to the determined target invitation object, for example: the group invitation objects to be entered corresponding to the group administrator A are a group invitation object 1 to be entered, a group invitation object 2 to be entered and a group invitation object 3 to be entered, the group invitation objects to be entered corresponding to the group administrator B are a group invitation object 4 to be entered, a group invitation object 5 to be entered and a group invitation object 6 to be entered, the group invitation objects to be entered included in the first member list of the group administrator A and the group administrator B are the group invitation object 1 to be entered to the group invitation object 6, the group invitation object 1 to be entered, the group invitation object 2 to be entered and the group invitation object 3 to be entered in the first member list are determined as target invitation objects in response to the third operation of the group administrator A on the first member list, the second invitation request corresponding to the group administrator A is sent to the target invitation object, the group administrator B responds to the third operation of the first member list, the group invitation object 4 to be entered in the first member list is sent, And the to-be-joined group invitation object 5 and the to-be-joined group invitation object 6 are determined as target invitation objects, and a second invitation request corresponding to the group administrator B is sent to the target invitation objects. Therefore, the group invitation objects to be entered corresponding to different group administrators can be quickly distinguished, so that the group administrators can quickly find the previously invited group invitation objects to be entered and invite the group invitation objects for the second time.

To further explain the above technical solutions, the following detailed description is made by using a specific implementation manner to describe the technical solution in the first embodiment, specifically, a current group administrator includes a group owner, an administrator 1 and an administrator 2, a group member a, a group member B and a group member C are members who have entered a group, fig. 3 is a schematic diagram of a group session interface provided in the first embodiment of the present application, as shown in fig. 3, the group session interface at least includes a first member list (currently displayed with the group administrator and members who have entered a group), an information input area (an area for inputting and sending information in the group), and an information display area (an area for displaying all information sent in the group), after the group owner sends a first invitation request to an invitation object 1 and an invitation object 2, if neither the invitation object 1 nor the invitation object 2 responds to the first invitation request, the invitation object 1 and the invitation object 2 are used as invitation objects to be entered into a group corresponding to a group owner, and the invitation object 1 and the invitation object 2 are displayed in a first member list of a group session interface corresponding to the group owner, fig. 4 is a schematic diagram of another group session interface provided in an embodiment of the present application, and as shown in fig. 4, in order to distinguish the invitation objects to be entered into the group, the invitation object 1 and the invitation object 2 are marked by using a first control as shown in fig. 4.

When the mouse is slid onto the inviting object 1 or the inviting object 2 in fig. 4, the number of invitations to the inviting object 1 or the inviting object 2 is displayed.

Fig. 5 is a schematic diagram of another group session interface provided in an embodiment of the present application, where after a first control of the invitation object 1 in fig. 4 is clicked, the interface shown in fig. 4 is switched to the interface shown in fig. 5 (a first window is added to fig. 5 as compared with fig. 4), a group owner may input a reason for group invitation in an information input box shown in fig. 5, and after a decision key in fig. 5 is clicked, a second invitation request is sent to the invitation object 1, and if the group owner clicks to cancel, the operation is abandoned this time.

If after the administrator 1 sends the first invitation request to the invitation object 3 and the invitation object 4, if neither the invitation object 3 nor the invitation object 4 responds to the first invitation request, the invitation object 3 and the invitation object 4 are taken as the invitation objects to be grouped corresponding to the administrator 1, the invitation object 3 and the invitation object 4 are displayed in the first member list of the group session interface corresponding to the administrator 1, and the invitation object 3 and the invitation object 4 are marked by using the first control.

The first member list corresponding to the group session interface of the group member A, the group member B and the group member C does not comprise the invitation object to enter the group.

After the invitation object 1 agrees with the second invitation request, the invitation object 1 agrees to join the group, and at this time, the first control of the invitation object 1 in the first member list corresponding to the group owner is deleted, so that the invitation object 1 is switched from the invitation object to be joined to the member of the joined group.

If an object applying for joining a group exists, the object is taken as an object applying for group joining, the object applying for group joining is displayed in a first member list corresponding to a group administrator, and meanwhile, a second control is used for marking the object applying for group joining, fig. 6 is a schematic diagram of another group session interface provided in the embodiment of the present application, as shown in fig. 6, if the object applying for group joining includes an object applying for group 1 and an object applying for group 2, an object applying for group 1 and an object applying for group 2 are displayed in the first member list, and then, the second control is used for marking partial tables of the object applying for group 1 and the object applying for group 2.

Any group administrator can operate the second controls of the application group object 1 and the application group object 2 to approve the application for group of the application group object 1 and the application group object 2, or reject the application for group of the application group object 1 and the application group object 2, taking the second control of the application group object 1 as an example, fig. 7 is a schematic diagram of another group session interface provided in the first embodiment of the application, after clicking the second control of the application group object 1, the displayed group session interface is as shown in fig. 7 (in comparison with fig. 6, fig. 7 adds a second window), after clicking the group administrator clicks the ok button, the group administrator indicates that the group administrator approves the application group object 1 to join the group, at this time, the second control of the application group object 1 is deleted, so that the application group object 1 is switched from the application group object to the member already joined the group, after clicking the reject key, the group administrator indicates that the group administrator rejects the application of the group entry object 1 to join the group, and at this time, the application of the group entry object 1 needs to be deleted from the first member list, where fig. 7 may also display application information (i.e., a reason for joining the group) of the application of the group entry object 1 to join the group.

And the first list corresponding to the non-group administrator does not display the object applied for group entry.

Example two

Fig. 8 is a schematic flowchart of a management method for group members according to a second embodiment of the present application, and as shown in fig. 8, the method includes the following steps:

step 801, providing a first member list on a group session interface of a terminal, where the first member list provides an invitation object to enter a group, where the invitation object to enter the group is an invitation object that does not respond to a first invitation request to join the group.

Step 802, responding to a first operation acting on the invitation object to enter the group, wherein the group session interface provides a first window;

step 803, responding to the first operation acting on the first window, and sending a second invitation request to the object to be invited to the group.

In a possible embodiment, the determining of the group member information according to the account authority information of the terminal logging in the group includes:

In one possible embodiment, the method further comprises:

In one possible embodiment, the information of the to-be-joined group invitation object includes:

In one possible embodiment, the first member list provides a fourth control corresponding to the to-group invitation object;

a first operation acting on the fourth control.

In one possible embodiment, the first member list provides a first grouping, the first grouping including a collapsed state and an expanded display state;

In one possible embodiment, the response includes an invitation to agree response, the first member list provides members of the entered group, the method further comprising:

In one possible embodiment, the response includes a decline invitation response, the method further including:

In one possible embodiment, the first member list provides members who apply for group entry objects and have joined a group; the method further comprises the following steps:

In one possible embodiment, the second window provides a second control;

the first operation on the second window comprises:

a first operation acting on the second control.

In one possible embodiment, the method further comprises:

In one possible embodiment, the second window provides a third control;

the first operation on the second window comprises:

a first operation acting on the third control.

In a possible embodiment, the second window provides application information corresponding to the application group object.

In one possible embodiment, a fifth control is provided for the application to group object in the first member list;

the first operation acting on the application group object comprises:

a first operation acting on the fifth control.

In one possible embodiment, the method further comprises:

and sending a second invitation request to the target invitation object.

In one possible embodiment, the invitation request contains invitation information that is generated by typing or recording in the confirmation window (i.e., the first window).

Specifically, the invitation information may be generated in the confirmation window by typing or recording when the invitation request is sent to the invitation object, and a specific implementation manner of the invitation information is not specifically limited herein.

Regarding the related principles of the second embodiment, reference may be made to the related description of the first embodiment, and the detailed description thereof is omitted here.

According to the group member management method provided by the application, after a first invitation request for joining a group is sent to an invitation object, if the invitation object does not respond to the first invitation request, the invitation object is used as a to-be-joined invitation object and is displayed in a first member list provided by a group session interface of a terminal, so that which invitation objects are not joined into the group can be known through the first member list, and a first operation can be performed on the to-be-joined invitation object in the first member list so as to perform secondary invitation on the to-be-joined invitation object. Compared with the sending mode in the prior art when the group invitation is initiated again, the operation is more convenient and faster, and the processing efficiency is improved.

EXAMPLE III

Fig. 9 is a schematic structural diagram of an electronic device according to a third embodiment of the present application, including: a processor 901, a storage medium 902 and a bus 903, where the storage medium 902 stores machine readable instructions executable by the processor 901, when the electronic device runs the above group member management method, the processor 901 and the storage medium 902 communicate with each other through the bus 903, and the processor 901 executes the machine readable instructions to execute the group member management method according to the first embodiment or the second embodiment.

For the specific implementation steps and principles, reference is made to the description of the first embodiment, which is not repeated herein.

Example four

An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the method for managing group members in the first embodiment or the second embodiment is performed.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments provided in the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus once an item is defined in one figure, it need not be further defined and explained in subsequent figures, and moreover, the terms "first", "second", "third", etc. are used merely to distinguish one description from another and are not to be construed as indicating or implying relative importance.

Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present application, and are used for illustrating the technical solutions of the present application, but not limiting the same, and the scope of the present application is not limited thereto, and although the present application is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope disclosed in the present application; such modifications, changes or substitutions do not depart from the spirit and scope of the present disclosure, which should be construed in light of the above teachings. Are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for managing members of a group, the method comprising:

2. The method of claim 1, wherein providing a to-group invitation object with the first member list comprises: and providing the invitation object to be entered into the group in the first member list according to the invitation object information to be entered into the group contained in the acquired group member information.

3. The method according to claim 2, wherein the group member information is determined according to account authority information of the terminal logging in the group, and the account authority information at least comprises: the group administrator information comprises first group administrator information or second group administrator information.

4. The method of claim 3, wherein the determining of the group member information according to the account authority information of the terminal logging in the group comprises:

5. The method of claim 2, further comprising:

6. The method of claim 3, wherein the first invitation request to join the group comprises: the first invitation request is sent by a first group administrator or a second group administrator, wherein the first group administrator and the second group administrator correspond to the first group administrator information and the second group administrator information respectively.

7. The method of claim 6, wherein the to-be-joined invitation object information comprises invitation object information that is not responsive to the first invitation request issued by a group administrator, the group administrator comprising the first group administrator and the second group administrator.

8. The method of claim 6, wherein the information of the to-be-entered group invitation object comprises:

9. The method of claim 1, wherein the first member list provides a first control corresponding to the to-group invitation object;

a first operation acting on the first control.

10. The method of claim 1, wherein the first member list comprises a first group comprising a collapsed state and an expanded display state;

11. The method of claim 1, wherein the response includes an invitation to agree response, wherein the first member list provides members that have joined the group, and wherein the method further comprises:

12. The method of claim 1, wherein the response comprises a decline invitation response, and wherein the method further comprises:

13. The method of claim 1, wherein the first member list provides an application group object and an already-in-group member; the method further comprises the following steps:

14. The method of claim 13, wherein the first member list provides a second control corresponding to the application group object;

the first operation acting on the application group object comprises:

a first operation acting on the second control.

15. The method of claim 13, further comprising:

16. The method of claim 15, wherein the first member list provides a third control corresponding to an application group object;

the first operation acting on the application group object comprises:

a first operation acting on the third control.

17. The method of claim 13, further comprising:

18. The method of claim 1, further comprising:

19. The method according to claim 6 or 7, characterized in that the method further comprises:

and sending a second invitation request to the target invitation object.

20. A method for managing members of a group, the method comprising:

21. The method of claim 20, wherein providing a to-group invitation object with the first member list comprises: and providing the invitation object to be entered into the group in the first member list according to the invitation object information to be entered into the group contained in the acquired group member information.

22. The method according to claim 21, wherein the group member information is determined according to account authority information of the terminal logging in the group, and the account authority information at least includes: the group administrator information comprises first group administrator information or second group administrator information.

23. The method of claim 22, wherein the determining of the group member information according to the account authority information of the terminal logging in the group comprises:

24. The method of claim 21, further comprising:

25. The method of claim 22, wherein the first invitation request to join the group comprises: the first invitation request is sent by a first group administrator or a second group administrator, wherein the first group administrator and the second group administrator correspond to the first group administrator information and the second group administrator information respectively.

26. The method of claim 25, wherein the to-be-joined invitation object information comprises invitation object information that is not responsive to the first invitation request issued by a group administrator, the group administrator comprising the first group administrator and the second group administrator.

27. The method of claim 25, wherein the information of the to-be-entered group invitation object comprises:

28. The method of claim 20, wherein the first member list provides a fourth control corresponding to the to-group invitation object;

a first operation acting on the fourth control.

29. The method of claim 20, wherein the first member list provides a first group, the first group comprising a collapsed state and an expanded display state;

30. The method of claim 20, wherein the response includes an invitation to agree response, wherein the first member list provides members of an entered group, and wherein the method further comprises:

31. The method of claim 20, wherein the response comprises a decline invitation response, and wherein the method further comprises:

32. The method of claim 20, wherein the first member list provides members who apply for group entry objects and have joined a group; the method further comprises the following steps:

33. The method of claim 32, wherein the second window provides a second control;

the first operation on the second window comprises:

a first operation acting on the second control.

34. The method of claim 32, further comprising:

35. The method of claim 34, wherein the second window provides a third control;

the first operation on the second window comprises:

a first operation acting on the third control.

36. The method of any one of claims 32-35, wherein the second window provides application information corresponding to the application group object.

37. The method of claim 32, wherein a fifth control is provided for the application group object in the first member list;

the first operation acting on the application group object comprises:

a first operation acting on the fifth control.

38. The method of claim 20, further comprising:

39. The method of claim 25 or 26, further comprising:

and sending a second invitation request to the target invitation object.

40. The method of claim 20, wherein the invitation request includes invitation information, and wherein the invitation information is generated by typing or recording in a confirmation window.

41. An electronic device, characterized in that the electronic device comprises: processor, memory storing a computer program executable by the processor, the computer program when executed by the processor performing the method of managing group members according to any one of claims 1 to 40.

42. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, performs a method of managing group members according to any one of claims 1 to 40.