CN115706719A - Information interaction method and device and electronic equipment - Google Patents

Information interaction method and device and electronic equipment Download PDF

Info

Publication number
CN115706719A
CN115706719A CN202210352728.5A CN202210352728A CN115706719A CN 115706719 A CN115706719 A CN 115706719A CN 202210352728 A CN202210352728 A CN 202210352728A CN 115706719 A CN115706719 A CN 115706719A
Authority
CN
China
Prior art keywords
team
group
information
members
displaying
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210352728.5A
Other languages
Chinese (zh)
Inventor
赵立悦
沈博文
刘洪泽
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Zitiao Network Technology Co Ltd
Original Assignee
Beijing Zitiao Network Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Zitiao Network Technology Co Ltd filed Critical Beijing Zitiao Network Technology Co Ltd
Priority to PCT/CN2022/109962 priority Critical patent/WO2023011521A1/en
Publication of CN115706719A publication Critical patent/CN115706719A/en
Priority to US18/408,064 priority patent/US20240146564A1/en
Pending legal-status Critical Current

Links

Images

Abstract

The embodiment of the disclosure discloses an information interaction method, an information interaction device and electronic equipment. The method comprises the following steps: displaying a team identification on the information interaction interface; wherein the team indicated by the team identification has an associated set of team members; displaying at least one group associated with the team indicated by the team identification; wherein a group of the at least one group includes at least a portion of the members of the set of team members. Displaying a team identification on the information interaction interface; wherein the team indicated by the team identification has an associated set of team members; displaying at least one group associated with the team indicated by the team identification; the group in at least one group at least comprises part of members in the team member set, so that the information of the group related to the team is displayed and managed by taking the team as a unit, and the information in the team is conveniently aggregated and communicated in the team member set. Helping to reduce interference to non-team members.

Description

Information interaction method and device and electronic equipment
Technical Field
The present disclosure relates to the field of internet technologies, and in particular, to an information interaction method and apparatus, and an electronic device.
Background
Through the instant messaging application, the user can perform information interaction with the contact person in real time. The contacts may include single contacts as well as group contacts. The group contact at least comprises two contacts.
The information flow display interface of the instant messaging application can display single chat information of information interaction between a user and a single contact person and/or group chat information of information interaction between the user and a group chat contact person.
Disclosure of Invention
This disclosure is provided to introduce concepts in a simplified form that are further described below in the detailed description. This disclosure is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
The embodiment of the disclosure provides an information interaction method, an information interaction device and electronic equipment.
In a first aspect, an embodiment of the present disclosure provides an information interaction method, where the method includes: displaying a team identification on the information interaction interface; wherein the team indicated by the team identification has an associated set of team members; displaying at least one group associated with a team indicated by the team identification; wherein a group of the at least one group includes at least a portion of the team members of the set of team members.
In a second aspect, an embodiment of the present disclosure provides an information interaction method, where the method includes: displaying a team identifier on the information interaction interface; the team indicated by the team identification has an associated team member set, the team is associated with at least one type of information communication entity, and the information communication entity is used for information interaction among team members; controlling the information interaction authority in the information communication entity based on the team member set of the team
In a third aspect, an embodiment of the present disclosure provides an information interaction apparatus, where the apparatus includes: the first display unit is used for displaying the team identification on the information interaction interface; wherein the team indicated by the team identification has an associated set of team members; a second display unit for displaying at least one group associated with the team indicated by the team identification; wherein a group of the at least one group includes at least a portion of the team members of the set of team members.
In a fourth aspect, an embodiment of the present disclosure provides an information interaction apparatus, where the apparatus includes: the third display unit is used for displaying the team identification on the information interaction interface; the team indicated by the team identification has an associated team member set, the team is associated with at least one type of information communication entity, and the information communication entity is used for information interaction among team members; and the control unit is used for controlling the information interaction authority in the information communication entity based on the team member set of the team.
In a fifth aspect, an embodiment of the present disclosure provides an electronic device, including: one or more processors; a storage device, configured to store one or more programs, which when executed by the one or more processors, cause the one or more processors to implement the information interaction method according to the first aspect or the second aspect.
In a sixth aspect, the disclosed embodiments provide a computer readable medium, on which a computer program is stored, which when executed by a processor, implements the steps of the information interaction method according to the first aspect or the second aspect.
According to the information interaction method, the information interaction device and the electronic equipment, the team identification is displayed on the information interaction interface; wherein the team indicated by the team identification has an associated set of team members; displaying at least one group associated with a team indicated by the team identification; the group in the at least one group at least comprises part of members in the team member set, so that the information of the group related to the team is displayed and managed by taking the team as a unit, and the information in the team is convenient to be limited to the team member set for communication. Helping to reduce interference to non-team members. In addition, the team members can know the information carried by the information communication entity in the team in real time, and the information transparency in the team is facilitated. The problems of reducing information interference and improving information transparency can be considered to a certain extent.
Drawings
The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale.
FIG. 1 is a flow diagram of some embodiments of an information interaction method according to the present disclosure;
FIG. 1A is a schematic view of a team information display area displaying information;
FIG. 2 is a schematic flow diagram of creating a team in the embodiment shown in FIG. 1;
FIG. 3 is a schematic diagram of an application scenario of an information interaction method provided by an embodiment of the present disclosure;
FIG. 4 is a flow diagram of additional embodiments of information interaction methods according to the present disclosure;
FIG. 5 is a schematic block diagram of one embodiment of an information-interacting device, according to the present disclosure;
FIG. 6 is a schematic block diagram of one embodiment of an information interaction device according to the present disclosure;
FIG. 7 is an exemplary system architecture to which the information interaction method of one embodiment of the present disclosure may be applied;
fig. 8 is a schematic diagram of a basic structure of an electronic device provided according to an embodiment of the present disclosure.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
The term "including" and variations thereof as used herein is intended to be open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
Referring to fig. 1, a flow diagram of one embodiment of an information interaction method according to the present disclosure is shown. The information interaction method as shown in fig. 1 includes the following steps:
step 101, displaying a team identification on an information interaction interface; wherein the team indicated by the team identification has an associated set of team members.
The information interaction interface can be an information interaction interface of an instant messaging application. A team logo may be displayed on the information interaction interface.
The team identification may be used to indicate a team. The team identification may include, but is not limited to, text, symbols, pictures, and the like. The team identification of different teams may be different.
The team member set may be a member set formed by all members of a team. For example, when a team includes 2 members, the team member set is a member set consisting of 2 members, and when the team includes 100 members, the team member set is a member set consisting of 100 members. Team members here may include users.
Step 102, displaying at least one group associated with the team indicated by the team identification; wherein a group of the at least one group includes at least a portion of the members of the set of team members.
The team indicated by the team identification may be associated with at least one group.
The group here may be a group in an instant messaging application. A group may be a tool for information interaction of group members.
A group here may be associated with a set of group members. The set of group members includes at least one group member. The group members may be team members.
In some application scenarios, the at least one group may be displayed with a display of team identification. For example, a user performs a selection operation on the first identifier associated with a team displayed in the information interaction interface, a team identifier of the team may be displayed in the information interaction interface, and at least one group associated with the team is displayed in a display area corresponding to the team.
In other application scenarios, the at least one group may be displayed upon receiving a group instruction to display team associations. For example, a user may perform a selection operation on a team filtering tag associated with a team displayed in the information interaction interface, and a team identification of the team may be displayed in the information interaction interface. After the user performs selection operation on the team identification, at least one group associated with the team can be displayed in the information interaction interface.
Optionally, the team is associated with a team filter tag. Before the team identification is displayed on the information interaction interface, the information interaction method further comprises the following steps:
firstly, displaying a team screening label on an information interaction interface;
secondly, when the team screening label is selected, displaying a team identification on an information interaction interface.
The team screening tags may also be associated with other teams.
In these alternative implementations, team information for a plurality of teams may be associated with the team selection tab in the information interaction interface while the team selection tab is selected, the team information including a team identification.
The other teams and the team can be sequentially arranged in the information interaction interface according to a preset ordering rule. For example, the team identifiers are arranged according to the sequence created by other teams and the team, or the names of the team identifiers of other teams and the team are arranged.
In some embodiments, the step 101 comprises: displaying a team identification in a conversation flow on the information interaction interface with the selected team screening label; the step 102 includes: displaying information of the associated groups in the conversation flow in close proximity to the team identification; or, in response to a team identifier in the conversation flow being triggered, displaying information of the associated respective group next to the team identifier.
In some optional implementation manners, the information interaction method further includes: when the team screening tag is selected, displaying information of a group associated with a team in a conversation flow in an information interaction interface; when the screening labels except the team screening label on the information interaction interface are selected, displaying the information of the group related to the team in the conversation flow displayed in the information interaction interface; wherein the session flow is used for displaying single chat session information and group session information.
In these optional implementations, the group associated with the team can be displayed in the information interaction interfaces of the team filtering tags, and can also be displayed in the information interaction interfaces of other filtering tags, which is helpful for the user to browse the information of the group associated with the team in real time.
In some optional implementations, when a filtering tag other than the team filtering tag on the information interaction interface is selected, the information of the group associated with the team displayed in the conversation flow includes a team indication identifier for indicating that the group is associated with a team.
The team indication mark may include, but is not limited to, at least one of the following: characters, letters, symbols, pictures. The team indicator may be displayed around the target group identifier or may be displayed as a background to the group identifier of the group with which the team is associated.
For example, where the team indicator includes the word "team," the team indicator may be displayed around the group indicator of the group associated with the team to indicate that the group is a group associated with the team.
In these optional implementation manners, when the information of the group associated with the team is displayed on the display interface displaying the information flow corresponding to the other filtering tags, the group may be quickly identified as the group associated with the team according to the team indication identifier.
Further, the team indication mark may include a first indication mark indicating a team associated with the group.
The first indicator may include, but is not limited to: words, letters, symbols, and/or pictures. The first indicator may include, for example, team identification information of a team associated with the target group, such as an icon, name, etc. of the associated team.
Therefore, the user can conveniently and quickly identify which team the target group is associated with on an information flow display interface of other non-team interactive information. Helping the user to determine whether to process the messages within the target group as quickly as possible.
In some optional implementations, a set of group members of a group of the at least one group is consistent with the set of team members.
In these application scenarios, the group member sets of the groups are consistent with the team member set. That is, each team member may also be a member of the group of groups at the same time. Each group member of each group is also a team member.
In these application scenarios, the set of team members is consistent with the group members, who may view information within the group in each group.
In some alternative implementations, the at least one group includes: a group whose set of group members is consistent with the set of team members, and a group whose set of group members is a proper subset of the set of team members.
In these application scenarios, the set of group members of the partial group may coincide with the set of team members in the at least one group. The set of group members of the partial group is a proper subset of the set of team members.
The above-mentioned group member set of the partial groups being a proper subset of the team member set means that all the group members in the group member set are team members, and the partial team members in the team member set are not the group members of these groups.
In these alternative implementations, the group associated with the team may have groups for which the set of group members may be consistent with the set of team members, or groups for which the set of group members is smaller than the set of team members. In these alternative implementations, messages within any group are viewed only within the scope of the team members, thereby limiting the boundaries of information diffusion to within the scope of the team members.
In yet other alternative implementations, the at least one group includes: the set of group members is a group of a subset of the set of team members, and the set of group members includes groups of at least some members of the set of team members and members outside the team.
In these application scenarios, the group member set is a group of a subset of the team member set, and includes a group of which the group member set is consistent with the team member set, and the group member set is a group of a proper subset of the team member set.
In these application scenarios, at least one group also includes groups in which some of the group members are members outside the team. Some of the group members of these groups may be team members.
In these alternative implementations, the group associated with the team may include a group in which some group members are members other than the team member, and diversity of the group may be implemented.
In some optional implementation manners, the at least one group displayed on the information interaction interface is a group with visible permission for a current user who logs in the information interaction interface. Wherein, the group that the current user has the visible right includes: the current user is a group of group members, and the current user is not a group member but has a visible right to the current user.
In these alternative implementations, the current user is a group of its group members, and the current user may browse the information of these groups. The information of the group may include, for example, a group identifier of the group, information flow in the group, and the like.
For groups for which the current user is not a member, but has visible rights to the current user, the current user can browse the information of the groups in the information interaction interface. The information of the groups may comprise, for example, group identifications of the groups, so that the user can determine whether to join the group according to the group identifications. In some embodiments, the group which has the visible right opened to the current user and is not a group member of the current user may have a group entry displayed according to the user operation, so that the user can initiate a group entry operation according to the group identifier, thereby joining the group.
Further optionally, the partial group of the at least one group is invisible to users without visible rights.
In these alternative implementations, for at least one group that is currently having visible rights, some of these groups are not visible to users that do not have visibility.
For a portion of the at least one group, the portion of the group may be invisible to a portion of the users. Some of the users here may be team members of a team. For the part of the group, the group information of the part of the group cannot be seen by the users without the visible right. The group information privacy is favorably realized, and meanwhile, aiming at preset team members which are not members of the group, the information such as the group identification of the group is displayed, so that the team members can conveniently determine whether to join the group according to the group identification.
In some optional implementation manners, a first reminding manner is adopted as a default for the message reminding manner of at least a part of the at least one group, wherein the group member sets of the part of the groups are all consistent with the team member set, and the message reminding frequency corresponding to the first reminding manner is lower than a preset reminding threshold.
The reminding threshold value can be 1 time/day and the like. The preset reminding threshold may be set according to a specific application scenario, and is not limited herein. As an illustrative illustration, the first reminding manner here is, for example, a reminding manner of closing the message notification.
When the message notification is closed and the group receives a new message, the group does not send a prompt message of receiving the new message to the user. When the user selects to browse the messages of the group, the user can browse the unread messages.
In these optional implementations, the at least part of the group is a first reminding manner by default. The interference brought to the user by prompting the new message to the user when the group receives the new message can be reduced.
Further optionally, the information interaction method further includes: and changing the first reminding mode into a second reminding mode according to the replacement operation of the current user logging in the information interaction interface on the message reminding mode, wherein the message reminding frequency of the second reminding mode is higher than the message reminding frequency corresponding to the first reminding mode.
As an illustrative illustration, the second reminding manner here is, for example, a reminding manner of opening a message notification.
In these optional implementation manners, the current user may change the message reminding manner of one or more groups to the second reminding manner according to the own requirement. After the group adopts the second reminding mode, the current user can receive the notification for indicating that the group receives the new message at a higher frequency. In order to alert the current group of receipt of a new message.
In the information interaction method provided by the embodiment, the team identification is displayed on the information interaction interface; wherein the team indicated by the team identification has an associated set of team members; displaying at least one group associated with a team indicated by the team identification; the group in the at least one group at least comprises part of members in the team member set, so that the information of the group related to the team is displayed and managed by taking the team as a unit, and the information in the team is convenient to be limited to the team member set for communication. Helping to reduce interference to non-team members. In addition, the team members can know the information carried by the information communication entity in the team in real time, and the information transparency in the team is facilitated. The problems of reducing information interference and improving information transparency can be considered to a certain extent.
In some optional implementations of this embodiment, the association relationship between the group and the team in the at least one group may be edited, and the association relationship between the group and the team may be changed by the editing operation.
That is, the association relationship between the group and the team in the at least one group is not constant. The association relationship may be changed by an editing operation of the user.
Further, the editing operation includes: and establishing an association relationship and/or releasing the association relationship.
It is understood that the user who edits the association relationship may be a user with a preset authority among the team members. The preset authority may include, for example: group-to-group association editing rights, group creation rights, deletion rights, and the like.
In these optional implementations, the user may conveniently change the association relationship between the group and the team through the editing operation on the association relationship.
In some alternative implementations, the team identification is displayed in a first display sub-area of the team information display area. The team information display area further comprises a second display sub-area, and the second display sub-area is used for displaying the extension identification. The team information display area may be a display area of team information in an information flow. For example, may be part of the area in the information stream display area. The team information display area may be information that displays a team logo, an extension logo, and a partial message of the team.
Referring to FIG. 1A, FIG. 1A shows a schematic view of a team information display area. As shown, the team information display area may display a team logo 111, an extension logo 112, and information "message B" of a partial message of a team.
The team identification may include, but is not limited to: graphics, image identification, and/or text identification.
As in fig. 1A, the team id includes a graphic id 113 and a text id "team one".
An extension identifier, which is an identifier displayed in the team information display area for indicating an actionable item of the team. The extension identifies "…" as shown in fig. 1A.
In some application scenarios, the team identifier is displayed in a first display sub-area of a team information display area, which also includes a second display sub-area. The second display sub-area is used for displaying the extension identification. The information interaction method further comprises the following steps:
displaying a team setting entry in response to receiving a first trigger operation executed by a current user on the first display subarea; or
And displaying the team setting entry in response to receiving a second trigger operation executed by the current user on the second display subarea.
The team setting inlet comprises an editing operation inlet used for editing the association relationship between the group and the graph pair.
As shown in FIG. 1A, the team information display area includes a first display sub-area 114 and a second display sub-area 115. The team logo 111 is displayed in the first display sub-area 114. The extension indicator 112 is displayed in the second display sub-region 115.
If the current user performs the first trigger operation on the first display sub-area 114, the team setup portal may be displayed.
The first trigger operation may include a click operation performed by a mouse auxiliary button.
As an implementation manner, the first trigger operation here may also be a touch operation performed on the first display sub-area for more than a preset time period, and the like. In these implementations, the electronic device for displaying team information has a touch screen, and receives a first trigger operation through the touch screen.
If the current user performs a second trigger operation on the second display sub-region 115, a team setup portal may be displayed.
The second triggering operation may include performing a click operation through a main button of the mouse.
As an implementation manner, the second trigger operation may be a conventional touch operation performed on the second display sub-area, or the like. In these implementations, the electronic device for displaying team information has a touch screen.
In the application scenes, the team setting entrance is displayed to the user in different modes, so that the user can conveniently set a team by using the team setting entrance.
Specifically, the team setting portal may include a portal set by a team member, a portal for editing an association relationship between a group and a team, and the like.
The entry of the editing operation for editing the association relationship between the group and the team comprises a group adding option. And entering a group adding window by executing triggering operation on the group adding option.
In some optional implementations, the team identification is displayed in a team information display area of the team. The editing operation includes establishing an association. The association relationship between the groups and the teams is established based on the following steps:
and 11, receiving a first preset operation executed by a current user on the team information display area, and displaying a group addition option for indicating to add a group associated with a team.
And step 12, displaying a group adding window according to the received selection operation executed on the group adding option.
And step 13, associating the target group with the team indicated by the team identification according to the target group determination operation executed by the user in the group adding window.
Further optionally, the target group determining operation may include: selecting an existing group, and/or a new group.
That is, an existing group may be selected as a group associated with a team, or a group associated with a team may be newly created.
In some application scenarios, the group addition option displayed in step 11 above includes adding an existing group option.
In these application scenarios, the step 12 includes: displaying an existing group list according to the received selection operation executed on the added existing group option; the existing group list includes at least one existing group. The step 13 includes: and determining at least one target group according to the selection operation of the user on the existing group list, and establishing the association relationship between the target group and the team.
Optionally, the existing group list includes: the current user is a first group of a group owner or a group manager; alternatively, the current user is a first type group of a group owner or a group administrator, and the current user is a second type group of a group member other than the group owner or the group administrator.
Further optionally, when the existing group list includes a second type of group in which the current user is a group member but not a group owner or a group manager, the determining at least one target group according to a selection operation performed by the user on the existing group list, and establishing an association relationship between the target group and the team includes: when a user performs selection operation on a second group in the existing group list, sending a request message to a group owner or an administrator of the second group owner; the request message is used for requesting to associate the second group with a team; in response to confirmation information agreeing to associate the second type group with the team, the second type group is determined as the target group.
In these application scenarios, the existing group may be a group associated with a current user who logs in the information interaction interface, and if the target group indicated by the operation is a first-class group, the first-class group may be associated with a team by initiating an operation to associate the target group with the team according to the current user.
If the target group indicated by the operation is a second-type group, when the current user initiates an operation of associating one or more second-type groups with a team, request information for associating the second-type groups with the team can be sent to a group or an administrator of the one or more second-type groups. After receiving the confirmation information of the group of the one or more second-type groups or the administrator, the group of the one or more second-type groups is determined as a target group, and further, an association relationship between the target group and the team can be established.
In these alternative implementations, the current user is provided with a channel to associate existing groups with teams. The method provides convenience for the current user to establish the association relationship between the existing group and the team.
In some optional implementation manners, the determining at least one target group according to the selection operation performed by the user on the existing group list, and establishing the association relationship between the target group and the team may include the following steps:
step 131, if the target group includes an out-of-team group member other than the team member, moving the out-of-team group member out of the target group to obtain a first target group.
Step 132, establishing an association relationship between the first target group of the members who move out of the team and the team; or showing inquiry information about whether the out-of-team member is added as a team member, responding to confirmation operation made by the current user based on the inquiry information, establishing an association relationship between the target group and the team, and adding the out-of-team member to the team.
In these alternative implementations, it is determined whether there are non-team members in the target group before associating the existing target group with the team. If it is determined that there are non-team members in the target group, the non-team members in the target group can be moved out of the group to obtain a first target group. It will be appreciated that the identity of the first target group may still be the same as the identity of the original target group. Only the group members of the first target group have changed.
In another implementation, after the current user confirms, non-team members in the target group may also be added to the team member set, so that the members of the target group are consistent with the team member set, and it is ensured that the range of information interaction is limited within the scope of the team members.
By establishing the association relationship between the first target group and the team, the group members of the first target group associated with the team are all team members. Thereby allowing team information to be propagated only between team members. The privacy of the team information can be improved.
Optionally, the determining at least one target group according to the selection operation performed by the user on the existing group list, and establishing the association relationship between the target group and the team may further include the following steps:
step 133, if the team member includes an out-of-group member other than the target group member, adding the out-of-group member to the group member set of the first target group to obtain a second target group.
Step 134, establishing an association relationship between the second target group and the team.
In these alternative implementations, if the set of group members of the first target group obtained in step 132 does not include a portion of team members, the portion of team members may be added to the set of group members of the first target group. It is understood that the group id of the second target group may be the same as the first target group id, and only the group members are changed.
In these optional implementation manners, a team member is added to the group member set of the first target group, and the obtained group member set of the second target group is the same as the team member set. Team members may be facilitated to browse the group messages of the second target group.
In other application scenarios, the group addition option displayed in step 11 above includes a new group option.
In these application scenarios, the step 12 includes: displaying a group creation window for creating a group according to the received selection operation executed on the newly-created group option, wherein the group creation window comprises a candidate group member list; the step 13 includes: determining a newly-built group member according to the selection operation executed by the user in the candidate group member list; and creating a new group comprising the members of the new group, and associating the new group serving as a target group with the team.
The list of candidate group members may include a team member list and/or a non-team member list.
Alternatively, a team member list may be displayed in a first area of the group creation window and a non-team member list may be displayed in a second area.
The non-team member list includes at least one non-team member user. The team member list includes at least one team member.
In these application scenarios, a group new window is provided. In the group new building window, the group member of the created group can be selected from a plurality of group members of the group, so that the newly built group member can be controlled, and the situation that non-group members are added into the group due to misoperation is avoided.
In some optional implementations, the information interaction method further includes: and determining the group type of the target group according to the group type setting operation executed by the user on the target group.
Wherein the group type setting operation performed on the target group includes: a selection operation performed by the user on the displayed at least one candidate group type option; or a group type input operation performed by the user on the target group.
In some application scenarios, the target group is an existing group. When the existing group is determined as the target group, a group type option may be presented. The group type options include different group type options. For example, the group type selection item includes a topic group type selection item and a general group type selection item that does not define a topic. The topic group type option is used for indicating that the group mainly carries out focused communication aiming at one or a plurality of specific topics; .
The user may determine the target group type of the target group in the presented group type options.
That is, the existing group non-topic group type options and the team establish an association relationship; when the existing group is determined as the target group and the association relationship is established with the team, the group type of the existing group can be modified.
In other application scenarios, the target group is a new group. In these application scenarios, the group type selection item may be set in the group creation window where the new group is created. When a user creates a new group, the group type of the new group is determined through the group type option.
In addition, the user can also set the group type of the target group through a group type input operation.
In these optional implementations, the user may modify or set the group type of the target group through the group type setting operation, so as to provide more group setting functions for the user, thereby improving the user experience.
In some optional implementations, the editing operation includes releasing the association between the group and the team, and the association between the group and the team may be released based on the following steps:
and 14, according to the received association releasing operation of the target group, releasing the association relation between the team and the target group, and reserving the target group session.
Optionally, the maintaining the target group session includes: and displaying the session information of the target group in a group information display interface in the information interaction interface.
In these alternative implementations, the target group session may still be retained after the target group is disassociated from the team. The group members of the target group can browse the information in the target group so that the group members can search the historical information. The reserved group session can also reserve the information interaction function of the group members, and the members in the group can continue to perform information interaction through the reserved group session.
Further optionally, the step 14 comprises the following sub-steps:
first, receiving a second preset operation executed by a current user on a target group associated with a team, and displaying an association relation removing selection item for indicating to remove the association relation with the team.
Secondly, according to the received selection operation executed on the incidence relation removing selection item, the incidence relation between the target group and the team is removed.
In these alternative implementations, a portal is provided that facilitates disassociation of the target group from the team.
In some optional implementations, the group type of the target group associated with the team is a first type group; after the incidence relation between the target group and the team is removed, the group type of the target group is set as a second type; wherein the first type group is a group associated with a team, and the second type group is a group not associated with a team.
In these alternative implementations, the plurality of groups of current users may include a first type group and a second type group. The first type group may be a group associated with a team. The second type of group may be a group that is not currently associated with a team. After a group of a first type is disassociated from a team, the group may be changed from the first type to a second type. Further, a group of a second type may change the type of the group from the second type to the first type after being associated with a team.
In some optional implementation manners, the information interaction method further includes: if the information interaction interface displays information flow of non-team information, information of a first type group is displayed in the information flow displayed on the interaction interface, the information of the first type group comprises team association information, and the team association information is used for indicating that the group is associated with the team.
In these alternative implementations, the user may select to display team interaction information in the information interaction interface. Information of at least a part of the group associated with the team may be displayed in the interaction information of the team. In addition, the user may also select to display information streams corresponding to other filtering tags besides the team filtering tag in the information interaction interface, for example, to display information streams including single chat information and/or group chat information. In the information interaction interface, the information of the first type group can also be displayed. The information of the first type group includes team association information. The team association information is used to indicate that the first type group is associated with a team. The team association information includes a team sub-identification.
Therefore, in the information interaction interface for displaying the information flow of the non-team information, the latest information of the team group related to the team can be browsed, the channel for finding the new information is expanded, and whether the team is the first type group or the second type group can be quickly identified according to the team related information carried by the team.
Further optionally, in the information interaction interface for information flow of non-team information, the displayed information of the first type group includes a team portal; the information interaction method further comprises the following steps: and entering an information interaction interface of a team associated with the first type group according to the selection operation of the user on the team entrance of the first type group.
In these alternative implementations, the team portal for each first-type group may be displayed within the display area of the information for that first-type group. The team portal may be displayed as graphics, text, etc.
The user may perform a selection operation on a team portal of a first type group. After receiving the selection operation of the user on the team entrance, the information interaction interface of the team associated with the first type group can be entered. That is, the information interactive interface is switched from the information flow displaying the non-team information to the information interactive interface displaying the team information.
In these alternative implementations, team portals are provided in the first type group to facilitate users entering team interaction information from an information flow of non-team information. For example, by providing a team portal in the information flow of the non-team information by a group associated to a team, it is possible to facilitate a user to quickly switch to an information display page or area where the corresponding team is located through the portal.
In some optional implementations, the at least one group includes a first group having a set of group members that is the same as the set of team members; the group members of the first group change synchronously as the set of team members changes to keep both members consistent.
Here, the set of group members of the first group changes synchronously with changes in the set of team members, including: when a new team member is added to the team member set, the new team member is correspondingly added to the group member set of the first group as a group member. When the team member set deletes an existing team member, the existing team member is also deleted from the group member set of the first group.
In this way, the set of group members of the first group may be made consistent with the set of team members.
In some alternative implementations, the first group is configured to send notification messages regarding team-level events for the team, or notification messages associated with the team itself. The notification messages regarding team-level events for a team include one or more of the following:
creating a new notification message of the team;
notification messages of change events of team information;
modifying the notification message of the team member authority;
a notification message of the association relationship is established between the existing group and the team;
a team member change notification message;
notification messages dismissed by the team.
The notification message of the new team can be a notification message created by the team. Notification messages of change events of team information, including but not limited to: team identification change, team name change, change of team introduction information of the team. Team member change notification messages, including notification messages of team member increase or decrease.
In these alternative implementations, the system level notification message may be sent in a first group. The user may browse to these system level messages in the first group. At the same time, because the set of group members of the first group is consistent with the set of team members, the team members may browse to these system level notification messages from the messages of the first group. So that system level messages can be transmitted to all team members.
The first group may not be top displayed if there is a new system level message in the first group.
In some alternative implementations, the first group is automatically generated with the creation of a team.
In these alternative implementations, the first group may be generated at the same time as the team is created. In this way, team members may receive a system notification message at a first time in the first group.
Further optionally, no affiliation disassociation portal is provided for disassociating the first group from an affiliation between the first group and the team and/or no group disassociation portal is provided for disassociating the first group during the presence of the team.
In some optional implementations, the information interaction method further includes: after the teams are disbanded, the first group is disbanded, or the first group is changed from a first type to a second type. Wherein the first type group is a group associated with a team and the second type group is a group not associated with a team.
In these alternative implementations, the first group may be dismissed, or the group type altered, after the team is dismissed. As the first type group associated with the team changes to a second type group not associated with the team.
In these alternative implementations, the first group cannot be disassociated from the team or disassociated during the existence of the team. It may be ensured that team members use the first group to obtain notification messages during the team's existence.
In some optional implementations, the at least one group includes at least one second group, the group member set of the second group being the same as the team member set, the second group being created based on the team member set after the team is created, or the second group being associated with the team after being created.
In these alternative implementations, the second group may be created after team creation. For example, after team creation, group creation is selected in a setup page of the team. And after receiving the selection operation of the group creation, displaying a group creation window. The group creation window may display a set of team members. A set of team members may be selected as a set of group members for the second group, thereby creating the second group. It is understood that the number of the second groups may include more than one. Each second group may include a group identification. The group identification may include, but is not limited to, text, symbols, graphics, and/or pictures.
In some application scenarios, the second group may also be created outside of the team. Or the second group is an existing group. In these application scenarios, the second group and the team may be associated according to the association relationship established between the second group and the team by the user. While the second group is associated with the team, non-team members of the group members of the second group may be moved out of the second group while non-group members of the team members are added as group members of the second group. Such that the set of group members of the second group is consistent with the set of team members.
Further optionally, the set of group members of the second group changes synchronously as the set of team members changes; and the set of team members changes synchronously as the set of group members of the second group changes.
That is, the group members of the second group are linked with the team members in both directions to ensure that the team member set is consistent with the second group members.
The second group may be, for example, a project progress communication group for disclosing a progress of a certain development project. Alternatively, the second group may be a food communication group.
In some optional implementations, the method further includes: and the message reminding mode of the at least one second group is a first reminding mode by default, and the message reminding frequency corresponding to the first reminding mode is lower than a preset reminding threshold value.
The reminding threshold value can be 1 time/day and the like. The preset reminding threshold may be set according to a specific application scenario, and is not limited herein. As an illustrative illustration, the first reminding manner here is, for example, a reminding manner of closing the message notification.
When the message notification is closed and the group receives a new message, the prompt information of receiving the new message may not be sent to the user. When the user selects to browse the messages of the group, the user can browse the unread messages.
In these optional implementations, the at least part of the group is a first reminding manner by default. The interference to the user caused by sending the prompt new message to the user when the second group receives the new message can be reduced.
Further optionally, the information interaction method further includes: and changing the first reminding mode into a second reminding mode according to the replacement operation of the current user logging in the information interaction interface on the message reminding mode, wherein the message reminding frequency of the second reminding mode is higher than the message reminding frequency corresponding to the first reminding mode.
As an illustrative illustration, the second reminding manner here is, for example, a reminding manner of opening a message notification. That is to say, the current user may change the reminding mode of the second group, and the user may set the message reminding mode of the second group.
In some optional implementations, the at least one group includes at least one third group, the set of team members of the third group being a proper subset of the set of team members; the third group is created based on a set of team members after the team is created, or the third group is associated with the team after being created; the identification information of the third group is visible to team members other than the third group member.
Further, messages in the third group are not visible to team members other than the third group member.
In these alternative implementations, the group members of the third group may be team members. Some team members of the team may not be group members of the third group. The team member may browse to the identification information of the third group in the team's information interaction interface. But cannot see messages within the third group. That is, the user may perceive that the third group exists, but cannot see the messages within the third group.
On one hand, the method is helpful for users to know the team information composition, and on the other hand, the method can ensure that the messages in the third group are not leaked.
In some optional implementations, the at least one group includes at least one fourth group, the set of team members of the fourth group being a proper subset of the set of team members; the fourth group's identification information is not visible to team members outside the fourth group constituent members.
In these alternative implementations, team members outside the fourth group may not be aware of the presence of the fourth group, and thus privacy of messages within the fourth group may be ensured. The fourth group can be used for information communication with higher confidentiality.
In some optional implementations, the group has a first set of group management functions before or after being disassociated with the team, and the group has a second set of group management functions after being associated with the team, wherein the second set of group management functions has fewer management function items than the first set of group management functions.
Further, the information interaction method further includes: after the group is associated with the team, merging at least one management function of the first group management function set to at least one management function of a team or adding to a management function set of the team; and processing the first group management function set as follows to obtain a second group management function set: deleting the at least one management function, or setting the at least one management function of the first group to a disabled state.
Further optionally, the merging at least one management function of the first group management function set into at least one management function of a team comprises: and expanding the objects managed by the at least one first management function of the team to include the first group, wherein the transaction management range of the at least one first management function item of the team can cover the transaction management range covered by the combined management function in the first group management function set.
In these alternative implementations, the first management function of the first group is merged with the first management function of the team, and the merged first management function is a management function of the team. In addition, the original partial group management function of the first group may also be added to the group management function of the team, becoming a team management function.
The first management function may be, for example, a group deletion function of the first group. The group management function added to the team group management function may be, for example, a group member addition or deletion management function of the first group, the second group.
In these optional implementation manners, the management function of the group and the team management function are combined into the management function of the team, or part of the management function of the group is added to the management function of the group, so that if the group is managed through the management function, the group needs to be managed through the management function of the team, which is beneficial to controlling the group, so as to ensure that the information of the group is not leaked.
Referring to FIG. 2, there is shown a schematic flow diagram of the creation of a team in the embodiment shown in FIG. 1.
As shown in fig. 2, the team is created based on the following steps:
step 201, receiving a team creating instruction, wherein the team creating instruction comprises team identification and team member information.
The team creating command may be issued by a user in a preset team creating window. The team creation instructions may include a team identification and team member information. The team identification includes, but is not limited to, text, graphics, symbols, and/or pictures. The team member information may include a set of team members. The team member set may include at least one team member.
Further, the step 201 may include the following sub-steps:
in sub-step 2011, a team creation window is displayed according to a team creation operation initiated by the user, and the team creation window includes a team name information input window and a team member setting window.
In the information interaction interface, a team creation selection item for instructing team creation may be included. When a user performs a selection operation on a team creation selection item, the user may be considered to initiate a team creation operation. The team creation window may be displayed according to the above-described team creation operation.
And a substep 2012, receiving the team name input by the preset user in the team name information input window.
And a substep 2013 of receiving team member information of the team to be created, which is set in the team member setting window by the user.
Setting the team member information here may include inputting information of the team member in the team member setting window, or selecting a team member in a candidate team member list displayed in the team member setting window.
The candidate team members may be contacts of the user. Or other users pushed by the server side.
Through the sub-steps 2011 to 2013, the team identification and the team member information included in the team creation instruction can be received.
Step 202 creates the team based on the team identification and the team member information.
A team can be newly created through the above steps 201 to 202. Multiple team members in a team may not belong to the same group before the team.
After the team is newly created, a first group of teams is automatically generated. The set of group members of the first group is consistent with a set of team members of the team.
Further, after a team is established, a second group, a third group, a fourth group, etc. associated with the team may be generated based on the team members.
In detail, please refer to the description of the first group, the second group, the third group, and the fourth group, which are not repeated herein.
In the manner shown in fig. 2, a new team is implemented.
In still other embodiments, the team in the embodiment shown in FIG. 1 is generated based on the following steps: and generating a team based on the information of the existing group according to the preset group attribute change operation executed by the user on the existing group.
The preset group attribute changing operation is used for indicating the change of the existing group from the group attribute to the team attribute
In these alternative implementations, existing groups may be upgraded to teams through property changes.
Specifically, the generating a team based on the information of the existing group includes: taking the existing group member set as a team member set to generate a team; changing the existing group to a group associated with a team.
That is, when an existing group is upgraded to a team, a team member set of the existing group may be used as a team member set to generate a team. The team identification of the team may be the same as the group identification of the existing group described above. Further, the existing group may be changed to a group associated with a team.
By upgrading the group to a team, the method of team creation is expanded.
In some alternative implementations, the default pattern of team identifications for the team created according to the embodiment shown in FIG. 2 is different from the default pattern of group identifications.
In these alternative implementations, the team may be a team created by creating an instruction according to a team, or a team obtained by changing a group to a team by changing a group property.
In these alternative implementations, the created default pattern of team identifications for the team is distinct from the default pattern of group identifications for the group.
Patterns of team or group logos include, but are not limited to, at least one of: graphics, images, and background colors.
Here, by setting the default pattern of the team logo to be different from the default icon of the group logo, it is helpful for the user to quickly recognize whether one logo is the logo of the team or the logo of the group through the pattern.
In some optional implementation manners, the information interaction method further includes the following steps:
first, the pattern edit portal for the team logo is displayed.
The team logo pattern editing entry can be displayed on a team creation page of a creation team, and can also be accessed through a team setting entry. The above team setting entry display may refer to relevant parts of this specification, and will not be described herein.
And secondly, displaying team identification pattern editing items according to the received trigger operation executed on the pattern editing entry.
The team identification pattern edit item includes, but is not limited to, at least one of: a graphic or image entry, a text color setting, and a background color setting.
And finally, determining the team identification pattern according to the pattern editing operation executed by the user on the team identification pattern editing item.
In these alternative implementations, the user may edit the pattern of the team logo, thereby enabling personalized setting of the team logo.
In some optional implementations, the team setup portal further includes a team member change portal. The information interaction method further comprises the following steps:
displaying a team member change page according to a trigger operation executed by a user on a team member change entrance; adding new team members added through the team member change page to team members, or removing team members deleted through the team member change page from a team member set.
As an illustrative illustration, the team member change portal may be a portal to add a team member. The user may click on the add team member portal, thereby displaying a team member change page. The team member change page here may be a page for adding a team member. The user may perform an add team member operation in the page for the add team member, such as selecting a target contact from a plurality of contacts as a team member to be added and aggregating the team member to be added.
As another illustrative example, the team member change entry may also be a delete team member entry. The user may click on the delete team members entry, thereby displaying a team members delete page. All team members can be displayed in the team member deletion page, a user can determine a target team member to be deleted through selection operation, and the target team member is moved out of the team member set according to subsequent operation.
As another illustrative illustration, a team member change page is entered through a team member change portal, the team member change page providing an add team member option and a delete team member option. And executing corresponding operation on the team member adding option to further add a new team member for the team. The selected team member is then removed from the set of team members by performing a corresponding operation on the delete team member option.
In some application scenarios, the team setting portal may further include an exit team portal, a dissolve team portal, and a management team portal.
The team exit page of the exiting team can be entered through the exiting team entrance. And exiting the team through corresponding operation executed on the team exit page.
The team dispute page of the dispute team can be entered through the dispute team entrance. The team is dismissed by corresponding operations performed on the dismissal page in question.
Through the management team portal, a team management page for the management team may be accessed. In these application scenarios, the logged-on user may be a user of the team members who has administrative privileges. The user can manage the authority of the team members through the team management page.
In some optional implementation manners, the information interaction method further includes: in response to receiving a request for a first user to exit a team member, the first user is moved out of the team and a group associated with the team.
In these alternative implementations, the user may apply for a quit from the team. The first user who applies for the exit from the team can be removed from the team member set according to the application of the user. At the same time, the first user is removed from the group set of groups associated with the team. In this way, the first user may successfully exit the team. Through the implementation, a convenient way for the user to exit the team is provided.
In some optional implementations, the information interaction method further includes: according to the received command for resolving the team, the association relationship between the team and each associated group is released
In these alternative implementations, the association relationship between the team and each association group can be released by resolving the instructions of the team. Groups may change from a first type of group associated with a team to a second type of group that has no association with the team. The group data of each group can be reserved, and the information interaction function in the group can also be reserved.
Through the alternative implementation modes, a mode of knowing about the team is provided, and the team is convenient to manage by a user.
In some alternative implementations, the at least one group includes the first group and other groups; the first group is used for sending team-level system notification messages; the information interaction method also comprises the following steps:
first, in response to a team-level event occurring, a corresponding notification message is sent in a first group.
Secondly, in response to an event occurrence at a group level, a corresponding notification message is transmitted in the corresponding group, and when the event at the group level satisfies a first predetermined condition, the corresponding notification message is transmitted in the first group.
In these alternative implementations, the team-level events include: change events of team information. Team information changes include, but are not limited to: changes in team name, changes in team identification, changes in team membership, changes in team association groups, changes in team referral information, etc. These team-level events may be sent as system-level system notification messages within the first group. When the user selects to browse the messages of the first group, the system notification messages can be browsed one by one.
In addition, for a group-level event occurrence, a corresponding notification message may be sent at the corresponding group. For example, the other groups may include a fourth group with stronger privacy, for example. The group level event may be, for example, a message sent by a member of the fourth group in the fourth group. The message may be sent to group members of a fourth group in the fourth group.
The first predetermined condition may be, for example, a group member change, a group identification change, or the like.
In some optional implementations, the information interaction method further includes: and if the notification message meets the second preset condition, setting the group for sending the notification message at the top of the conversation flow.
Further, the second preset condition includes at least one of: the notification message is a notification message of a newly-built team; the notification message is a team information change notification message, the notification message is a notification message associated with an existing group and a team, and the notification message is a notification message of team dispersion.
In these alternative implementations, the message satisfying the second preset condition may be regarded as an important message. Upon receiving important messages, the group that will send the notification message may be set top in the conversation flow to enable the user to quickly browse through the important messages. In one embodiment, the group used to present the team-level system notification messages may be a default group that is automatically generated as the team is created.
In some optional implementation manners of this embodiment, the information interaction method further includes: displaying at least one other information communication entity associated with the team indicated by the team identification; wherein the at least one other information communication entity comprises one or more of the following: documents, calendars, meetings.
In these alternative implementations, in addition to being associated with a group, the team is also associated with other information communication entities. The user can conveniently browse the information carried by other communication entities in the team.
In some embodiments, a team is constructed by selecting a set of users, such as a group of people, and determining the selected set of users as a set of team members of the team, the set of team members may be utilized to construct information and permission boundaries for the team such that the information and permission boundaries for the team are relatively stable. One or more information communication entities of the same type or different types can be mounted or associated under the team, and team members can perform information interaction through the information communication entities, so that information transparency can be maintained to the maximum extent in the team. In some embodiments, the authority control is performed on the information communication in the team based on the team member set, in other words, when the authority control is performed on the information interaction in the information communication entity, the team member set information of the team is also referred to, so that the problem of information opaqueness caused by that the information in the information communication entity can only be transferred in the information communication entity is avoided, for example, the problem of information opaqueness caused by that the information of a group can only be checked in the group is solved, or the risk of divulgence and the like caused by that the information transfer condition of the information communication entity is too loose is avoided.
In some embodiments, by being assisted by preset notification logic, the transparency of information in a team can be improved, and meanwhile, the team members are not disturbed excessively. For example, in a default communication group associated with a team, only messages meeting preset conditions are notified in the default communication group, or messages related to the team themselves adopt a first notification mode, but messages not directly related to the team themselves or messages in an information communication entity of the team adopt a second notification mode, and the notification intensity of the first notification mode is higher than that of the second notification mode. In some embodiments, team members may also actively boost the message notification strength of one or more information communication entities, thereby facilitating the team members to actively discover information.
Please refer to fig. 3, which illustrates a schematic diagram of an application scenario provided in this embodiment. As shown in FIG. 3, a plurality of filter tags may be displayed in the information interaction interface 30. For example, the message filtering tab "message" and the team filtering tab "team" are displayed in the first area 31 of the information interactive interface 30. The user may perform a selection operation on the team filter tab "team" to display team information for a plurality of teams associated with the team filter tab in the second area 32 of the information interaction interface. For example, the second area 32 may display a team identification of team 1, a team identification of team 2. At least one group associated with the team may be displayed in the second area 32 of the information. Such as displaying group 11 and group 12 associated with team 1. Group 21 associated with team 2.
In addition, the user can also execute operations of creating a team and deleting a team in the second area.
Taking team 1 as an example, the team 1 may have a team member set, the group 11 may have a group member set 111, and the group 12 may have a group member set 121. The group 11 may be the first group established at the time of team 1 creation. The group member set 111 of group 11 is consistent with the team member set and is bi-directionally coordinated. Team level system messages for team 1 may be sent at group 11. In addition, the message in the group 11 satisfying the preset first predetermined condition may also be sent in the group 11. The group member set of group 12 may be a subset of team 1. The group 12 may be a second group, a third group, etc.
A user may add a group member q to the group 12. When a user adds a group member q to the group 12, the group member q may be added as a team member at the same time.
In addition, the user may also choose to associate an existing group s with team 1 in the information interaction interface 30. In associating existing group s with team 1, non-team 1 group member f in existing group s may be deleted from the set of group members, and then the existing group s with the non-team member removed may be associated with the team. Or, when the existing group s is associated with the team 1, inquiring the user whether the user agrees to add the group member f of the non-team 1 in the existing group s as a team member, and after the user confirms the agreement, adding the group member f as a team member and associating the existing group s with the team.
Please refer to fig. 4, which shows a flowchart of some embodiments of the information interaction method provided in the present embodiment. As shown in fig. 4, the information interaction method includes the following steps:
step 401, displaying a team identification on an information interaction interface; the team indicated by the team identification has an associated team member set, the team is associated with at least one type of information communication entity, and the information communication entity is used for information interaction among team members.
The at least one type of information communication entity includes one or more of the following: group, calendar, document, meeting. Including one or more of the following:
that is, the teams may associate groups, calendars, documents, and/or meetings.
The information communication entity can be used for information interaction among team members. A team member may associate a set of team members.
Step 402, controlling information interaction authority in the information communication entity based on the team member set of the team.
For example, the information interaction in the information communication entity can be performed only among the team members. The team outsiders do not interact with information in the information communication entities associated with the team.
In some optional implementation manners, the controlling the information interaction authority in the information communication entity includes: and controlling the information interaction authority in the information communication entity based on a first authority system of a team and a second authority system of the information communication entity.
The first authority system includes, but is not limited to, a team management function set of a team, such as increase and decrease of team members, circulation conditions of information, and the like. The second authority system includes, but is not limited to, a set of management functions of the information communication entity, such as increase and decrease of members in the information communication entity, authority of the members, information circulation conditions, and the like.
The group can be managed through the management function set of the team, so that the aim of controlling the information interaction authority in the information communication entity is fulfilled.
Further optionally, the above first authority system based on the team and the second authority system based on the information communication entity control the information interaction authority in the information communication entity, including: adding at least one original management function of the information communication entity before being associated with the team to a management function item set of the team, or combining the at least one original management function with the management function of the team; and deleting the at least one management function from the management function set of the information communication entity or setting the at least one management function to be in a failure state.
Taking a communication entity as a group for example, after the group and the team establish an association relationship, merging at least one original management function of the group before the group establishes the association relationship with the team into at least one management function of the team or adding the original at least one management function into a management function set of the team; and processing the first group management function set as follows to obtain a second group management function set: deleting the at least one management function, or setting the at least one management function of the first group to a disabled state.
Said merging at least one management function of said first set of group management functions to at least one management function of a team, comprising: and expanding the objects managed by the at least one first management function of the team to include the first group, wherein the transaction management range of the at least one first management function item of the team can cover the transaction management range covered by the combined management function in the first group management function set.
Such as team dismissal, to cover group dismissal.
By combining the management function of the information communication entity and the team management function into the team management function, or adding part of the management function of the information communication entity to the group management function, if the group is managed through the management function item, the team management function is needed to be realized, which is beneficial to controlling the information communication entity, so as to ensure that the information carried by the information communication entity is not leaked.
In some other application scenarios, the information communication entity includes an instant message communication group, and the controlling of the information interaction authority in the information communication entity includes:
there is a linkage between the change in the set of team members and the change in the set of members of the associated at least one instant messaging group.
In these alternative implementations, the messaging group is associated with a set of group members. The set of group members may be a subset of the set of team members.
In order to control the information interaction authority in the information communication entity, the team member set can be changed, and linkage exists between the change of the group members of the at least one instant message communication group.
Specifically, the group member set of the instant messaging communication group changes synchronously with the change of the team member set; and the set of team members changes synchronously with changes in the set of group members of the instant messaging group.
When a new team member is added to the team member set, the group member set of the instant messaging communication group correspondingly adds the new team member to be a group member. When a team member set deletes an existing team member, the existing team member is also deleted from the group member set of the instant messaging group. If a new group member is added to the group member set of the instant messaging communication group, the new group member is also added to the group member set. If a group member is deleted from the set of group members of the instant messaging group, the group member deleted from the group is also deleted from the team members.
By linking the change of the team member set with the change of the group member set of the instant message communication group, the team member set can be kept consistent with the group member set of the instant message communication group, and the team member can browse the communication message of the instant message communication group at any time. Therefore, the communication messages in the instant message communication group are limited to be visible to team members, and the safety of the communication messages of the instant message communication group can be improved.
In some optional implementations, the information communication entity includes a default information communication entity; the default information communication entity is generated at the same time of team creation.
The information communication entities include, but are not limited to: group, calendar, document, meeting. The conference includes real-time or non-real-time voice and/or video conference communication channels, such as voice chat room, real-time voice or video conference, live broadcast room, etc.
In these optional implementation manners, the default information communication entity is generated at the same time of team creation, so that team members can bear communication information of the team members through the default information communication entity when the team is created.
In the related art, instant messaging applications are used as main tools for cooperative work, and various information required by work pushing is distributed in various group chat and cloud documents. The information in the group chat can be updated in real time, and the real-time updated group chat information can cause disturbance to the user. Therefore, it is desirable for the user to have a compromise of "information transparency + low interference", i.e., "want to know information and worry about reminding of all information too much to disturb".
In the information interaction method provided by the embodiment, the team identification is displayed on the information interaction interface; the team indicated by the team identification has an associated team member set, the team is associated with at least one type of information communication entity, and the information communication entity is used for information interaction among team members; the team member set based on the team controls the information interaction authority in the information communication entity, so that the communication of messages in the team member set is realized, the interference to non-team members can be reduced, the team members can timely know the information carried by the information communication entity in the team, and the information transparence in the team is realized. The problems of reducing information interference and improving information transparence are considered to a certain extent.
With further reference to fig. 5, as an implementation of the method shown in the above-mentioned figures, the present disclosure provides an embodiment of an information interaction apparatus, which corresponds to the method embodiment shown in fig. 1, and which can be applied in various electronic devices.
As shown in fig. 5, the information interaction apparatus of the present embodiment includes: a first display unit 501 and a second display unit 502. The first display unit 501 is configured to display a team identifier on an information interaction interface; wherein the team indicated by the team identification has an associated set of team members; a second display unit 502 for displaying at least one group associated with the team indicated by the team identification; wherein a group of the at least one group includes at least a portion of the members of the set of team members.
In this embodiment, specific processing of the first display unit 501 and the second display unit 502 of the information interaction apparatus and technical effects thereof can refer to related descriptions of step 101 and step 102 in the corresponding embodiment of fig. 1, which are not repeated herein.
In some optional implementations, the information interaction apparatus further includes a filtering identifier changing unit (not shown in the figure). The screening identification changing unit is used for: receiving a change operation executed by a user on at least one target session, wherein the change operation is used for changing the screening identification corresponding to the target session, and changing the screening identification corresponding to the at least one target session into a first target screening identification indicated by the change operation.
In some optional implementations, a set of group members of a group of the at least one group is consistent with the set of team members; alternatively, the at least one group comprises: a group whose group member set is consistent with the team member set, and a group whose group member set is a proper subset of the team member set; alternatively, the at least one group comprises: the set of group members is a group of a subset of the set of team members, and the set of group members includes groups of at least some members of the set of team members and members outside the team.
In some optional implementations, the at least one displayed group is a group for which a current user logged in the information interaction interface has a visible right; wherein, the group that the current user has the visible right includes: the group in which the current user is a group member, and the group in which the current user is not a group member but has a visible right to the current user.
In some alternative implementations, a portion of the groups in the at least one group are not visible to users having no visible rights.
In some optional implementation manners, a first reminding manner is adopted as a default for the message reminding manner of a part of the at least one group, wherein the group member sets of the part of the group are all consistent with the team member set, and the message reminding frequency corresponding to the first reminding manner is lower than a preset reminding threshold value
In some optional implementations, the information interaction apparatus further includes a message notification attribute changing unit (not shown in the figure). The message notification attribute changing unit is configured to: and changing the first reminding mode into a second reminding mode according to the replacement operation of the current user logging in the information interaction interface on the message reminding mode, wherein the message reminding frequency of the second reminding mode is higher than the message reminding frequency corresponding to the first reminding mode.
In some optional implementations, the association relationship between a part of the at least one group and the team may be performed by an editing operation, by which the association relationship between the group and the team is altered.
In some optional implementations, the editing operation includes: and establishing an association relationship and/or releasing the association relationship.
In some optional implementations, the team identifier is displayed in a team information display area of the team, the editing operation includes establishing an association relationship, and the information interaction unit further includes an association relationship establishing unit (not shown in the figure). The association relationship establishing unit is used for: establishing an association relationship between the group and the team based on the following steps: receiving a first preset operation executed by a current user on the team information display area, and displaying a group addition option for indicating addition of a group associated with a team; displaying a group adding window according to the received selection operation executed on the group adding option; and associating the target group with the team indicated by the team identification according to the target group determination operation executed by the user in the group adding window.
In some optional implementations, the target group determination operation includes: selecting an existing group, and/or a new group.
In some optional implementations, the association relationship establishing unit is further configured to: determining the type of a target group according to group type setting operation executed by a user on the target group; wherein the content of the first and second substances,
the group type setting operation performed on the target group includes: a selection operation performed by the user on the displayed at least one candidate group type option; or a group type input operation performed by the user on the target group.
In some optional implementations, the group addition option includes adding an existing group option; the association relationship establishing unit is further configured to: displaying an existing group list according to the received selection operation executed on the added existing group option; the existing group list comprises at least one existing group; the associating the target group with the team indicated by the team identifier according to the target group determination operation executed by the user in the group adding window includes: and determining at least one target group according to the selection operation of the user on the existing group list, and establishing the association relationship between the target group and the team.
In some optional implementations, the association relationship establishing unit is further configured to: if the target group comprises an out-of-team member except the team member, moving the out-of-team member out of the target group to obtain a first target group; establishing an association between the first target group of the removed out-of-team members and the team; or, showing inquiry information about whether the out-of-team member is added as a team member, responding to confirmation operation made by the current user based on the inquiry information, establishing an association relationship between the target group and the team, and adding the out-of-team member to the team; if the team members comprise members outside the group except the target group members, adding the members outside the group to the group member set of the first target group to obtain a second target group; establishing an association relationship between the second target group and the team.
In some optional implementations, the existing group list includes: the current user is a first group of a group owner or a group manager; alternatively, the current user is a first type group of a group owner or a group administrator, and the current user is a second type group of a group member other than the group owner or the group administrator.
In some optional implementations, when the existing group list includes a second type group in which the current user is a group member but not a group owner or a group manager, the association relationship establishing unit is further configured to: when a user performs selection operation on a second group in the existing group list, sending a request message to a group owner or an administrator of the second group owner; the request message is used for requesting to associate the second group with a team; in response to the confirmation information agreeing to associate the second type group with the team, the second type group is determined to be the target group owner.
In some optional implementations, the group addition option includes a new group option; the association relationship establishing unit is further configured to: displaying a group creation window for creating a group according to the received selection operation executed on the newly-created group option, wherein the group creation window comprises a candidate group member list; the associating the target group with the team indicated by the team identifier according to the target group determination operation executed by the user in the group adding window includes: determining a newly-built group member according to the selection operation executed by the user in the candidate group member list; and creating a new group comprising the members of the new group, and associating the new group with the team.
In some optional implementations, the list of candidate group members includes a team member list and/or a non-team member list.
In some optional implementations, the first display unit 501 is further configured to: displaying the team screening label on the information interaction interface; and when the team screening label is selected, displaying a team identifier on an information interaction interface.
In some optional implementations, the second display unit 501 is further configured to: when the team screening tag is selected, displaying information of a group associated with a team in a conversation flow in an information interaction interface; when the screening labels except the team screening label on the information interaction interface are selected, displaying the information of the group related to the team in the conversation flow displayed in the information interaction interface; wherein the session flow is used for displaying single chat session information and group session information.
In some optional implementations, when a filtering tag other than the team filtering tag on the information interaction interface is selected, the information of the group associated with the team displayed in the conversation flow includes a team indication identifier for indicating that the group is associated with a team.
In some optional implementations, the team indicator includes a first indicator for indicating a team with which the group is associated.
In some alternative implementations, the editing operation includes disassociating the group from the team. The information interaction device also comprises a library association relationship releasing unit (not shown in the figure) which is used for releasing the association relationship between the group and the team based on the following steps: and according to the received association releasing operation of the target group, releasing the association relation between the team and the target group, and reserving the target group session.
In some optional implementations, reserving the target group session includes: and displaying the information of the target group in a group information display interface in the information interaction interface.
In some optional implementations, the association releasing unit is further configured to: receiving a second preset operation executed by the current user on a target group associated with the team, and displaying an association relation removing selection item for indicating to remove the association relation with the team; and according to the received selection operation performed on the association relation removing selection item, removing the association relation between the target group and the team.
In some alternative implementations, the group type of the target group associated with the team is a first type group; the information interaction device further includes a first-type setting unit (not shown in the figure) for: after the incidence relation between a target group and a team is released, setting the group type of the target group as a second type; wherein the first type group is a group associated with a team, and the second type group is a group not associated with a team.
In some optional implementations, wherein in the information interaction interface for information flow of non-team information, the displayed first type group of information includes a team portal; the second display unit 502 is further configured to: and entering an information interaction interface of a team associated with the first type group according to the selection operation of the user on the team entrance of the first type group.
In some optional implementations, the at least one group includes a first group having a set of group members that is the same as the set of team members; the group members of the first group change synchronously as the set of team members changes to keep both members consistent.
In some optional implementations, the first group is to send system level notification messages about teams, including any one or more of the following:
creating a new notification message of the team;
modifying the notification message of the team basic information;
modifying the notification message of the team member authority;
a notification message of the association relationship is established between the existing group and the team;
a team member change notification message;
notification messages dismissed by the team.
In some alternative implementations, the first group is automatically generated as a team is created.
In some alternative implementations, no affiliation disassociation portal is provided for disassociating the first group from a team and/or no group disassociation portal is provided for disassociating the first group during the presence of the team.
In some optional implementations, the information interaction apparatus further includes a first type setting unit (not shown in the figure), and the first type setting unit is configured to: after the teams are disbanded, the first group is disbanded, or the first group is changed from a first type to a second type. Wherein the first type group is a group associated with a team and the second type group is a group not associated with a team.
In some optional implementations, the at least one group includes at least one second group, the group member set of the second group being the same as the team member set, the second group being created based on the team member set after the team is created, or the second group being associated with the team after being created.
In some alternative implementations, the set of group members of the second group changes synchronously as the set of team members changes; and the set of team members changes synchronously as the set of group members of the second group changes.
In some optional implementation manners, the message reminding manner of the at least one second group is a first reminding manner by default, and a message reminding frequency corresponding to the first reminding manner is lower than a preset reminding threshold.
In some optional implementations, the at least one group includes at least one third group, the set of team members of the third group being a proper subset of the set of team members; the third group is created based on a set of team members after the team is created, or the third group is associated with the team after being created; the identification information of the third group is visible to team members other than the third group member.
In some alternative implementations, messages in the third group are not visible to team members other than the third group member.
In some optional implementations, the at least one group includes at least one fourth group, the set of team members of the fourth group being a proper subset of the set of team members; the fourth group's identification information is not visible to team members outside the fourth group constituent members.
In some optional implementations, the group has a first set of group management functions before or after being disassociated with the team, and the group has a second set of group management functions after being associated with the team, wherein the second set of group management functions has fewer management function items than the first set of group management functions.
In some optional implementations, the information interaction apparatus further includes a function item management unit (not shown in the figure). The function item management unit is configured to: after the group is associated with the team, merging at least one management function of the first group management function set to at least one management function of a team or adding to a management function set of the team; and processing the first group management function set as follows to obtain the second group management function set: deleting the at least one management function, or setting the at least one management function of the first group to a disabled state.
In some optional implementations, the function item management unit is further to: expanding the objects managed by the at least one first management function of the team to include the objects managed by the at least one first management function of the team, wherein the transaction management scope of the at least one first management function item of the team can cover the transaction management scope covered by the merged management function in the first group management function set.
In some optional implementations, the information interaction device further includes a team creation unit (not shown in the figures). The team creating unit creates a team based on the steps of: receiving a team creating instruction, wherein the team creating instruction comprises team identification and team member information; and creating the team according to the team identification and the team member information.
In some optional implementations, the team creation unit is further to: displaying a team establishing window according to team establishing operation initiated by a user, wherein the team establishing window comprises a team name information input window and a team member setting window; receiving a team name input by the preset user in the team name information input window; and receiving team member information of a team to be created, which is set in the team member setting window by the user.
In some optional implementations, the team creation unit is further to: a team is created based on the following steps: generating a team based on the information of the existing group according to the preset group attribute change operation executed by a user on the existing group; (ii) a And the preset group attribute changing operation is used for indicating that the existing group is changed from the group attribute to the team attribute.
In some optional implementations, the team creation unit is further to: taking the existing group member set as a team member set to generate a team; changing the existing group to a group associated with a team.
In some alternative implementations, the created default pattern of team identifications for the team is different from the default pattern of group identifications.
In some optional implementations, the information interaction apparatus further includes a member changing unit (not shown in the figure). The member changing unit is configured to: in response to receiving a request for a first user to exit a team member, the first user is moved out of the team and a group associated with the team.
In some optional implementations, the information interaction device further includes a team dissembling unit (not shown in the figures). The team dispersing unit is used for: and according to the received command for resolving the team, releasing the association relationship between the team and each associated group.
In some alternative implementations, the at least one group includes the first group and other groups; the first group is used for sending team-level system notification messages; the information interaction device further comprises a message notification unit (not shown in the figure). The message notification unit is used for: in response to a team-level event occurrence, sending a corresponding notification message in the first group; in some alternative implementations, the message notification unit is further configured to, in response to an event at a group level occurring, send a corresponding notification message in the corresponding group, and when the event at the group level satisfies a first predetermined condition, send the corresponding notification message in the first group: and if the notification message meets the second preset condition, setting the group for sending the notification message at the top of the conversation flow.
In some optional implementations, the second preset condition includes at least one of: the notification message is a notification message of a newly-built team; the notification message is a team information change notification message, the notification message is a notification message associated with an existing group and a team, and the notification message is a notification message of team dispersion.
In some alternative implementations, the team-level events include: a change event of team information, the change of team information comprising: changes in team name, identification, and team referral information.
In some optional implementations, the second display unit 502 is further configured to: displaying at least one other information communication entity associated with the team indicated by the team identification; wherein the at least one other information communication entity comprises one or more of: documents, calendars, meetings.
In some optional implementations, the displaying the team identification on the information interaction interface includes: displaying a team identifier in a conversation flow on an information interaction interface; the second display unit 502 is further configured to: displaying information of the associated groups in the conversation flow in close proximity to the team identification; or, in response to a team identifier in the conversation flow being triggered, displaying information of the associated respective group next to the team identifier.
In some optional implementations, the team logo is displayed in a first display sub-area of a team information display area, and the team information display area further includes a second display sub-area, and the second display sub-area is used for displaying an extension logo; and the second display unit 502 is further configured to:
displaying a team setting entry in response to receiving a first trigger operation executed by a current user on the first display subarea; or
Displaying a team setting entrance in response to receiving a second trigger operation executed by a current user on the second display subarea; wherein
The team setting inlet comprises an inlet used for editing the editing operation of the association relationship between the groups and the teams.
With further reference to fig. 6, as an implementation of the method shown in the above-mentioned figures, the present disclosure provides an embodiment of an information interaction apparatus, which corresponds to the method embodiment shown in fig. 1, and which can be applied in various electronic devices.
As shown in fig. 6, the information interaction apparatus of the present embodiment includes: a third display unit 601 and a control unit 602. The third display unit 601 is configured to display a team identifier on the information interaction interface; the team indicated by the team identification has an associated team member set, the team is associated with at least one type of information communication entity, and the information communication entity is used for information interaction among team members; a control unit 602, configured to control information interaction permissions in the information communication entity based on the team member set of a team.
In this embodiment, specific processing of the third display unit 601 and the control display unit 602 of the information interaction apparatus and technical effects thereof can refer to related descriptions of step 601 and step 602 in the corresponding embodiment of fig. 3, which are not described herein again.
In some optional implementations, the control unit 602 is further configured to: and controlling the information interaction authority in the information communication entity based on a first authority system of a team and a second authority system of the information communication entity.
In some optional implementations, the control unit 602 is further configured to: adding at least one original management function of the information communication entity before being associated with the team to a management function item set of the team, or combining the at least one original management function with the management function of the team; and deleting the at least one management function from the management function set of the information communication entity or setting the at least one management function to be in a failure state.
In some optional implementations, the information communication entity includes an instant message communication group, and the control unit 602 is further configured to: controlling a linkage relationship between the change in the set of team members and the change in the set of group members of the associated at least one instant messaging group.
In some optional implementations, the information communication entity includes a default information communication entity; the default information communication entity is generated at the same time of team creation.
In some optional implementations, the information communication entity includes one or more of the following: group, calendar, document, meeting.
Referring to fig. 7, fig. 7 illustrates an exemplary system architecture to which the information interaction method of one embodiment of the present disclosure may be applied.
As shown in fig. 7, the system architecture may include terminals 701, 702, 703, a network 704, and a server 705. The network 704 serves to provide a medium for communication links between the terminals 701,702, 703 and the server 705. Network 704 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
Terminals 701, 702, 703 may interact with a server 705 over a network 704 to receive or send messages and the like. The terminals 701, 702, 703 may have various client applications installed thereon, such as a web browser application, a search-type application, and a news-information-type application. The client applications in the terminals 701, 702, and 703 may receive the instruction of the user, and complete corresponding functions according to the instruction of the user, for example, display an information stream of the instant messaging application according to the instruction of the user.
The terminals 701, 702, 703 may be hardware or software. When the terminals 701, 702, 703 are hardware, they may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III, motion Picture Experts compression standard Audio Layer 3), MP4 players (Moving Picture Experts Group Audio Layer IV, motion Picture Experts compression standard Audio Layer 4), laptop portable computers, desktop computers, and the like. When the terminals 701, 702, 703 are software, they can be installed in the electronic devices listed above. It may be implemented as multiple pieces of software or software modules (e.g., software or software modules used to provide distributed services) or as a single piece of software or software module. And is not particularly limited herein.
The server 705 may provide various services such as receiving information sent by the terminals 701, 702, 703 and forwarding the information to other terminals.
It should be noted that the information interaction method provided by the embodiment of the present disclosure may be executed by a terminal, and accordingly, the information interaction apparatus may be disposed in the terminals 701, 702, and 703. In addition, the information interaction method provided by the embodiment of the present disclosure may also be executed by the server 705, and accordingly, the information interaction apparatus may be disposed in the server 705.
It should be understood that the number of terminals, networks, and servers in fig. 7 is merely illustrative. There may be any number of terminals, networks, and servers, as desired for an implementation.
Referring now to fig. 8, shown is a schematic diagram of an electronic device (e.g., the terminal device or the server in fig. 7) suitable for use in implementing embodiments of the present disclosure. The terminal device in the embodiments of the present disclosure may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a vehicle terminal (e.g., a car navigation terminal), and the like, and a stationary terminal such as a digital TV, a desktop computer, and the like. The electronic device shown in fig. 8 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 8, an electronic device may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 801 that may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 802 or a program loaded from a storage means 808 into a Random Access Memory (RAM) 803. In the RAM803, various programs and data necessary for the operation of the electronic apparatus 800 are also stored. The processing apparatus 801, the ROM 802, and the RAM803 are connected to each other by a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.
Generally, the following devices may be connected to the I/O interface 805: input devices 806 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, or the like; output devices 807 including, for example, a Liquid Crystal Display (LCD), speakers, vibrators, and the like; storage 808 including, for example, magnetic tape, hard disk, etc.; and a communication device 809. The communication means 809 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. While fig. 8 illustrates an electronic device having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication means 809, or installed from the storage means 808, or installed from the ROM 802. The computer program, when executed by the processing apparatus 801, performs the above-described functions defined in the methods of the embodiments of the present disclosure.
It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.
The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: displaying a team identification on the information interaction interface; wherein the team indicated by the team identification has an associated set of team members; displaying at least one group associated with a team indicated by the team identification; wherein a group of the at least one group includes at least a portion of the members of the set of team members. Or
Displaying a team identification on the information interaction interface; the team indicated by the team identification has an associated team member set, the team is associated with at least one type of information communication entity, and the information communication entity is used for information interaction among team members; and controlling the information interaction authority in the information communication entity based on the team member set of the team.
Computer program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including but not limited to an object oriented programming language such as Java, smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. 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.
The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of an element does not in some cases constitute a limitation on the element itself.
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems on a chip (SOCs), complex Programmable Logic Devices (CPLDs), and the like.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.
Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims (51)

1. An information interaction method comprises the following steps:
displaying a team identification on the information interaction interface; wherein the team indicated by the team identification has an associated set of team members;
displaying at least one group associated with a team indicated by the team identification; wherein a group of the at least one group includes at least a portion of the members of the set of team members.
2. The method of claim 1, wherein,
a set of group members of a group of the at least one group is consistent with the set of team members;
alternatively, the at least one group comprises: a group whose group member set is consistent with the team member set, and a group whose group member set is a proper subset of the team member set;
alternatively, the at least one group comprises: the set of group members is a group of a subset of the set of team members, and the set of group members includes groups of at least some members of the set of team members and members outside the team.
3. The method of claim 1, wherein the at least one displayed group is a group for which a current user logged into the information interaction interface has visible rights;
wherein, the group that the current user has the visible right includes: the group with the current user as a group member and the group with the current user not as a group member but opening visible permission to the current user; a partial group of the at least one group is invisible to users without visible rights.
4. The method of claim 1, wherein associations between a portion of said at least one group and said teams can be edited, whereby said associations between said groups and said teams are altered.
5. The method of claim 4, wherein the team identification is displayed on a team information display area of a team, the editing operation comprising establishing an association relationship, the association relationship between the group and the team established based on the steps of:
receiving a first preset operation executed by a current user on the team information display area, and displaying a group addition option for indicating to add a group associated with a team;
displaying a group adding window according to the received selection operation executed on the group adding option;
and associating the target group with the team indicated by the team identification according to the target group determination operation executed by the user in the group adding window.
6. The method of claim 5, wherein the method comprises:
determining the type of a target group according to group type setting operation executed by a user on the target group; wherein the content of the first and second substances,
the group type setting operation performed on the target group includes: a selection operation performed by the user on the displayed at least one candidate group type option; or a group type input operation performed by the user on the target group.
7. The method of claim 5, wherein,
the group addition option comprises adding an existing group option;
the displaying a group adding window according to the received selection operation executed on the group adding option comprises: displaying an existing group list according to the received selection operation executed on the added existing group option; the existing group list comprises at least one existing group;
the associating the target group with the team indicated by the team identifier according to the target group determination operation executed by the user in the group adding window includes: and determining at least one target group according to the selection operation of the user on the existing group list, and establishing the association relationship between the target group and the team.
8. The method of claim 7, wherein said determining at least one target group according to the selection operation performed by the user on the existing group list, and establishing an association between the target group and the team comprises:
if the target group comprises the members of the team outside the team, moving the members of the team outside the team out of the target group to obtain a first target group, and establishing an association relationship between the first target group of the members of the team outside the team and the team; or, showing inquiry information about whether the out-of-team member is added as a team member, responding to confirmation operation made by the current user based on the inquiry information, establishing an association relationship between the target group and the team, and adding the out-of-team member to the team; and
if the team members comprise members outside the group except the target group members, adding the members outside the group to the group member set of the first target group to obtain a second target group; establishing an association between the second target group and the team.
9. The method of claim 7, wherein the existing group list comprises:
the current user is a first group of a group owner or a group manager;
alternatively, the first and second electrodes may be,
a first type group in which the current user is a group owner or a group administrator, and a second type group in which the current user is a group member but not a group owner or a group administrator.
10. The method of claim 9, wherein, when the existing group list includes a second type of group for which the current user is a group member but not a group owner or a group manager,
the determining at least one target group according to the selection operation executed by the user on the existing group list, and the establishing of the association relationship between the target group and the team comprises:
when a user performs selection operation on a second group in the existing group list, sending a request message to a group owner or an administrator of the second group owner; the request message is used for requesting to associate the second group with a team;
in response to confirmation information agreeing to associate the second type group with the team, the second type group is determined as the target group.
11. The method of claim 5, wherein,
the group adding option comprises a new group option;
the displaying a group addition window according to the received selection operation executed on the group addition option comprises: displaying a group creation window for creating a group according to the received selection operation executed on the newly-created group option, wherein the group creation window comprises a candidate group member list;
the associating the target group with the team indicated by the team identifier according to the target group determination operation executed by the user in the group adding window includes: determining a newly-built group member according to the selection operation executed by the user in the candidate group member list; and creating a new group comprising the new group members, and associating the new group with the team.
12. The method of claim 1, wherein prior to displaying the team identification on the information interaction interface, the method further comprises:
displaying a team screening label on the information interaction interface;
and when the team screening label is selected, displaying a team identifier on an information interaction interface.
13. The method of claim 12, wherein the method further comprises:
when the team screening tag is selected, displaying information of a group associated with a team in a conversation flow in an information interaction interface; and
when the screening labels except the team screening label on the information interaction interface are selected, displaying the information of the group associated with the team in the conversation flow displayed in the information interaction interface; wherein the session flow is used for displaying single chat session information and group session information.
14. The method of claim 13, wherein, when a filter tab other than the team filter tab on the information interaction interface is selected, the information of the team associated group displayed in the conversation flow includes a team indicator indicating that the group is associated with a team.
15. The method of claim 4, wherein the editing operation comprises disassociating a group from the team, the disassociation between the group and the team based on:
and according to the received association releasing operation of the target group, releasing the association relation between the team and the target group, and reserving the target group session.
16. The method of claim 1, wherein the at least one group includes a first group having a set of group members that is the same as the set of team members; the group members of the first group change synchronously as the set of team members changes to keep both members consistent.
17. The method of claim 16, wherein the first group is to send system level notification messages on teams, including any one or more of:
creating a new notification message of the team;
modifying the notification message of the team basic information;
modifying the notification message of the team member authority;
a notification message of the association relationship is established between the existing group and the team;
a team member change notification message;
notification messages dismissed by the team.
18. The method of claim 16, wherein the first group is automatically generated with the creation of a team.
19. The method of claim 16, wherein no affiliation disassociation portal is provided for disassociating first groups from teams and/or no group disassociation portal is provided for disassociating first groups during the presence of the team.
20. The method of claim 19, wherein the method further comprises: after the teams are disbanded, the first group is disbanded, or the first group is changed from a first type to a second type. Wherein the first type group is a group associated with a team and the second type group is a group not associated with a team.
21. The method of claim 1, wherein the at least one group includes at least one second group, the group member set of the second group being the same as the team member set, the second group being created based on the team member set after the team is created or the second group being associated with the team after being created.
22. The method of claim 21, wherein,
the set of group members of the second group changes synchronously as the set of team members changes; and
the set of team members changes synchronously as the set of group members of the second group changes.
23. The method according to claim 1, wherein a first reminding mode is adopted as a default for the message reminding mode of the at least one second group, and a message reminding frequency corresponding to the first reminding mode is lower than a preset reminding threshold.
24. The method of claim 1, wherein the at least one group includes at least one third group whose set of team members is a proper subset of the set of team members; the third group is created based on a set of team members after the team is created or the third group is associated with the team after being created; the identification information of the third group is visible to team members other than the third group member.
25. The method of claim 1, wherein the at least one group includes at least one fourth group whose set of team members is a proper subset of the set of team members; the fourth group's identification information is not visible to team members outside the fourth group constituent members.
26. The method of claim 1, wherein the group has a first set of group management functions before an association is established with the team or after a disassociation is made with the team, the group has a second set of group management functions after an association is established with the team, wherein,
management function items in the second set of group management functions are less than management function items in the first set of group management functions.
27. The method of claim 26, wherein the method further comprises:
after the group is associated with the team, merging at least one management function of the first group management function set to at least one management function of a team or adding to a management function set of the team; and processing the first group management function set as follows to obtain the second group management function set: deleting the at least one management function, or setting the at least one management function of the first group to a disabled state.
28. The method of claim 1, wherein the team is created based on the steps of:
receiving a team creating instruction, wherein the team creating instruction comprises team identification and team member information;
creating the team according to the team identification and the team member information;
wherein the receiving a team creation instruction comprises:
displaying a team establishing window according to team establishing operation initiated by a user, wherein the team establishing window comprises a team name information input window and a team member setting window;
receiving the team name input by the preset user in the team name information input window;
and receiving team member information of a team to be created, which is set in the team member setting window by the user.
29. The method of claim 1, wherein the team is created based on the steps of:
generating a team based on the information of the existing group according to the preset group attribute change operation executed by a user on the existing group; and the preset group attribute changing operation is used for indicating that the existing group is changed from the group attribute to the team attribute.
30. The method of claim 29, wherein generating a team based on the existing group of information comprises: taking the existing group member set as a team member set to generate a team; changing the existing group to a group associated with a team.
31. The method of one of claims 28-30, wherein the created default pattern of team identification of the team is different from the default pattern of group identification.
32. The method of claim 1, wherein the method further comprises:
in response to receiving a request for a first user to exit a team member, the first user is moved out of the team and a group associated with the team.
33. The method of claim 1, wherein the method further comprises:
and according to the received command for resolving the team, releasing the association relationship between the team and each associated group.
34. The method of claim 1, wherein the at least one group comprises a first group and other groups; the first group is used for sending team-level system notification messages; and the method further comprises:
in response to a team-level event occurrence, sending a corresponding notification message in the first group;
the method includes the steps of responding to the occurrence of an event at a group level, sending a corresponding notification message in a corresponding group, and sending the corresponding notification message in a first group when the event at the group level meets a first preset condition.
35. The method of claim 34, wherein the method further comprises:
and if the notification message meets the second preset condition, setting the group for sending the notification message at the top in the conversation flow.
36. The method of claim 35, wherein the second predetermined condition comprises at least one of:
the notification message is a notification message of a newly-built team; the notification message is a team information change notification message; the notification message is a notification message associated with an existing group and a team; the notification message is a notification message disassembled by a team.
37. The method of claim 34, wherein the team-level events include:
a change event of team information, the change of team information comprising: changes in team name, identification, and team referral information.
38. The method as recited in claim 1, wherein the method further comprises:
displaying at least one other information communication entity associated with the team indicated by the team identification;
wherein the at least one other information communication entity comprises one or more of: documents, calendars, meetings.
39. The method of claim 1, wherein said displaying a team identification on an information interaction interface comprises: displaying a team identifier in a conversation flow on an information interaction interface;
the displaying at least one group associated with the team indicated by the team identification comprises: displaying information of the associated groups in the conversation flow in close proximity to the team identification; or, in response to a team identifier in the conversation flow being triggered, displaying information of the associated respective group next to the team identifier.
40. The method of claim 1, wherein the team logo is displayed in a first display sub-area of a team information display area, the team information display area further comprising a second display sub-area for displaying an extension logo; and
the method further comprises the following steps:
displaying a team setting entry in response to receiving a first trigger operation executed by a current user on the first display subarea; or
Displaying a team setting entrance in response to receiving a second trigger operation executed by a current user on the second display subarea; wherein
The team setting inlet comprises an inlet used for editing the editing operation of the association relationship between the groups and the teams.
41. The method of claim 40, wherein,
the team setup portal further comprises a team member change portal:
displaying a team member change page according to a trigger operation executed by a user on a team member change entrance; adding new team members added through the team member change page to team members, or removing team members deleted through the team member change page from a team member set.
42. An information interaction method comprises the following steps:
displaying a team identification on the information interaction interface; the team indicated by the team identification has an associated team member set, the team is associated with at least one type of information communication entity, and the information communication entity is used for information interaction among team members;
and controlling the information interaction authority in the information communication entity based on the team member set of the team.
43. The method of claim 42, wherein the controlling of the information interaction authority in the information communication entity comprises:
and controlling the information interaction authority in the information communication entity based on a first authority system of a team and a second authority system of the information communication entity.
44. The method of claim 43, wherein the controlling of the information interaction rights in the information communication entity based on a first rights system of the team and a second rights system of the information communication entity comprises:
adding at least one original management function of the information communication entity before being associated with the team to a management function item set of the team, or combining the at least one original management function with the management function of the team; and deleting the at least one management function from the management function set of the information communication entity or setting the at least one management function to be in a failure state.
45. The method of claim 42 or 43, wherein the messaging entity comprises an instant messaging group, and the controlling of the message interaction rights in the messaging entity comprises:
there is a linkage between the change in the set of team members and the change in the set of group members of the associated at least one instant messaging group.
46. The method of claim 42, wherein the messaging entity comprises a default messaging entity;
the default information communication entity is generated at the same time of team creation.
47. The method of claim 42, wherein the information communication entity includes one or more of: group, calendar, document, meeting.
48. An information interaction device, comprising:
the first display unit is used for displaying the team identification on the information interaction interface; wherein the team identification indicates that the team has an associated set of team members;
a second display unit for displaying at least one group associated with the team indicated by the team identification; wherein a group of the at least one group includes at least a portion of the members of the set of team members.
49. An information interaction device, comprising:
the third display unit is used for displaying the team identification on the information interaction interface; the team indicated by the team identification has an associated team member set, the team is associated with at least one type of information communication entity, and the information communication entity is used for information interaction among team members;
and the control unit is used for controlling the information interaction authority in the information communication entity based on the team member set of the team.
50. An electronic device, comprising:
one or more processors;
a storage device to store one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method recited in any one of claims 1-47.
51. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 47.
CN202210352728.5A 2021-08-06 2022-03-31 Information interaction method and device and electronic equipment Pending CN115706719A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2022/109962 WO2023011521A1 (en) 2021-08-06 2022-08-03 Information interaction methods and apparatus, and electronic device
US18/408,064 US20240146564A1 (en) 2021-08-06 2024-01-09 Method and apparatus for information interaction, and electronic device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110905719X 2021-08-06
CN202110905719 2021-08-06

Publications (1)

Publication Number Publication Date
CN115706719A true CN115706719A (en) 2023-02-17

Family

ID=85181403

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210352728.5A Pending CN115706719A (en) 2021-08-06 2022-03-31 Information interaction method and device and electronic equipment

Country Status (1)

Country Link
CN (1) CN115706719A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116520996A (en) * 2023-07-03 2023-08-01 南京维赛客网络科技有限公司 Group tour method, system and storage medium under same channel scene

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116520996A (en) * 2023-07-03 2023-08-01 南京维赛客网络科技有限公司 Group tour method, system and storage medium under same channel scene

Similar Documents

Publication Publication Date Title
US20170168692A1 (en) Dual-Modality Client Application
CN112311754B (en) Interaction method and device and electronic equipment
JP2023527250A (en) Video processing method, apparatus, electronic equipment and computer readable storage medium
US11310295B1 (en) Integrated workspace on a communication platform
US20230319001A1 (en) Snippet(s) of content associated with a communication platform
US11652858B2 (en) Integration of communication platform functionality with a third-party application
US20220353129A1 (en) Channel generation in a communication platform
CN113609834A (en) Information processing method, device, equipment and medium
KR20150138514A (en) Method and device for tagging chatting message
CN113222549A (en) Information interaction method, device and system and electronic equipment
CN115706719A (en) Information interaction method and device and electronic equipment
WO2023011528A1 (en) Information interaction method and apparatus, and electronic device
CN112306595A (en) Interaction method and device and electronic equipment
CN110704151A (en) Information processing method and device and electronic equipment
CN115578020A (en) Subtask creation method, device, equipment and medium
CN115270734A (en) Message processing method, device, equipment and medium based on session
CN115237533A (en) Information display method, device, equipment and medium
WO2023011521A1 (en) Information interaction methods and apparatus, and electronic device
CN114827060A (en) Interaction method and device and electronic equipment
CN115061601A (en) Electronic document processing method and device, terminal and storage medium
WO2024087533A1 (en) Expression image sharing method and apparatus, computer device, and storage medium
US20230394440A1 (en) Generating collaborative documents for virtual meetings in a communication platform
US11190368B1 (en) Real time data update for channel preview
US11784955B1 (en) Virtual space server redundancy across geographic regions
US11848904B2 (en) Sharing custom history in multi-party direct message

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination