[go: up one dir, main page]

WO2018196739A1 - 即时通信群组的管理方法和装置 - Google Patents

即时通信群组的管理方法和装置 Download PDF

Info

Publication number
WO2018196739A1
WO2018196739A1 PCT/CN2018/084229 CN2018084229W WO2018196739A1 WO 2018196739 A1 WO2018196739 A1 WO 2018196739A1 CN 2018084229 W CN2018084229 W CN 2018084229W WO 2018196739 A1 WO2018196739 A1 WO 2018196739A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
read
message
condition
mandatory
Prior art date
Application number
PCT/CN2018/084229
Other languages
English (en)
French (fr)
Inventor
柳林东
Original Assignee
阿里巴巴集团控股有限公司
柳林东
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司, 柳林东 filed Critical 阿里巴巴集团控股有限公司
Priority to KR1020197018217A priority Critical patent/KR102248393B1/ko
Priority to JP2019534784A priority patent/JP6918116B2/ja
Priority to EP18790640.9A priority patent/EP3544229B1/en
Priority to ES18790640T priority patent/ES2875793T3/es
Priority to PL18790640T priority patent/PL3544229T3/pl
Publication of WO2018196739A1 publication Critical patent/WO2018196739A1/zh
Priority to US16/440,834 priority patent/US10686615B2/en
Priority to PH12019501485A priority patent/PH12019501485A1/en
Priority to US16/901,959 priority patent/US20200313917A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H04L12/1822—Conducting the conference, e.g. admission, detection, selection or grouping of participants, correlating users to one or more conference sessions, prioritising transmission
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method and an apparatus for managing an instant communication group.
  • Group chat technology allows users in the same group in real life to gather and share information, such as classmates and company groups.
  • group chat application there are often simple multi-person conversations, such as temporarily pulling several colleagues into a group to talk about key issues.
  • the probability of such groups being used again is low, resulting in the server maintaining many such "zombie groups", increasing the complexity of group management and being prone to errors.
  • the present application provides a method and apparatus for managing an instant messaging group.
  • a method for managing an instant communication group comprising:
  • the group dissolving condition is met, the group is dismissed based on the preset policy.
  • a management device for an instant communication group comprising:
  • a read-only determination unit that determines a mandatory read message in the group session message
  • the condition determining unit determines whether the group dissolving condition is satisfied according to the reading condition of the read-read message
  • the group dissolving unit if the group dissolving condition is satisfied, dissolves the group based on the preset policy.
  • the present application can determine whether the group dissolving condition is met according to the reading condition of the read-read message in the group, and when the group dissolving condition is met, the group is dissolved based on the preset policy, thereby dissolving
  • a large number of "zombie groups" reduce the complexity of group management, and at the same time release resources such as storage and processing on the server side.
  • FIG. 1 is a schematic flowchart diagram of a method for managing an instant messaging group according to an exemplary embodiment of the present application.
  • FIG. 2 is a schematic diagram of a group session interface according to an exemplary embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a pre-set policy-based disbanding group according to an exemplary embodiment of the present application.
  • FIG. 4 is a structural diagram of a management apparatus for an instant communication group according to an exemplary embodiment of the present application.
  • FIG. 5 is a block diagram of an apparatus for managing an instant messaging group according to an exemplary embodiment of the present application.
  • first, second, third, etc. may be used in this application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information without departing from the scope of the present application.
  • second information may also be referred to as the first information.
  • word "if” as used herein may be interpreted as "when” or “when” or “in response to a determination.”
  • FIG. 1 is a schematic flowchart diagram of a method for managing an instant messaging group according to an exemplary embodiment of the present application.
  • the method for managing an instant messaging group can be applied to an instant messaging server, including the following steps:
  • Step 101 Determine a mandatory message in the group session message.
  • the present application can perform determination and subsequent follow-up only for the temporary group. Dissolution process.
  • the group creator can select the type of the group when creating the group, such as: creating a "fixed group” or creating a "temporary group”; in addition, for the fixed group that has been created, the group owner or the administrator You can also change the type of a fixed group to a temporary group by setting options; of course, for the created temporary group, you can also modify its type to a fixed group by setting options.
  • the mandatory read message is usually marked by a group member having authority, such as a group owner or an administrator.
  • a group member having authority such as a group owner or an administrator.
  • the group can trigger the marking of the mandatory message by clicking, double-clicking, long pressing, etc., for example, the group owner may wish all group members Messages that are read are marked as read-only messages.
  • the group owner client can send the tag event to the server.
  • the tag event carrying the group session message identifier can be sent to the server, and the server can receive the message according to the message.
  • the tag event determines the corresponding group session message as a mandatory message.
  • Step 102 Determine, according to the reading condition of the mandatory read message, whether the group dissolving condition is met.
  • the server can count the reading of the read-read message, and the reading usually includes: read or unread.
  • the server may detect the reading status of the read message by each group member, and then determine whether the group satisfies the group dissolving condition according to the reading condition of the read message in the group member. The detection of the reading situation can be implemented by using an implementation solution in the related art, which is not repeatedly described herein.
  • the group dissolving condition may be a default default condition, or may be personalized by the group owner or the administrator as needed.
  • Step 103 If the group dissolving condition is met, the group is dismissed based on the preset policy.
  • the present application can determine whether the group dissolving condition is met according to the reading condition of the read-read message in the group, and when the group dissolving condition is met, the group is dissolved based on the preset policy, thereby dissolving
  • a large number of "zombie groups" reduce the complexity of group management, and at the same time release resources such as storage and processing on the server side.
  • a group member having authority such as a group owner or an administrator, can set an upper limit number of required messages as needed. For example, if Xiaobai establishes a temporary group to release an important message to a group member, Xiaobai can set the upper limit of the number of mandatory messages to 1, and after sending the important message, The important messages are marked as mandatory messages. It should be noted that the upper limit of the number of mandatory read messages in the present application is not fixed. Before the temporary group is dissolved, Xiaobai can modify the upper limit of the number of read-only messages according to actual needs. limit.
  • the server can detect the reading status of the mandatory message by each group member based on the white flag event.
  • the server when the server determines that the mandatory read message has been read by all group members, it may be determined that the temporary group satisfies the group dissolving condition, and then the temporary group may be dismissed based on the preset policy.
  • the server when the server determines that the mandatory read message has been read by all group members, and the release duration of the read-read message has reached the first duration, it may be determined that the temporary group satisfies the group dissolving condition. And, in turn, the temporary group can be dissolved based on a preset policy.
  • the first duration may be defined in advance by white, or may be a default default value, such as: 1 day, 3 days, and the like. Taking 1 day as an example, when the server determines that the mandatory read message has been read by all group members, and the published duration of the mandatory read message has reached 24 hours, the temporary group can be dismissed based on the preset policy.
  • the group member before the release duration of the mandatory read message reaches the first duration, the group member may also perform related discussions in the temporary group, and White may also reset the upper limit of the number of read-read messages as needed. To achieve more flexibility and better user experience.
  • the server determines that the mandatory read message is not read by all group members, but the release duration of the mandatory read message has reached the second duration, it may be determined that the temporary group satisfies the group dissolving condition. And, in turn, the temporary group can be dissolved based on a preset policy.
  • the second duration may be defined in advance by white, or may be a default default value, such as 15 days, 30 days, etc., and the second duration is usually greater than the foregoing first duration. Taking 15 days as an example, when the server determines that the mandatory read message has not been read by all the group members, and the release duration of the read-read message has reached 15 days, the temporary group can be dissolved based on the preset policy.
  • the temporary group can be dissolved based on the preset policy.
  • the server when the server determines that the number of group members who have read the read-read message reaches a preset ratio, it may be determined that the temporary group satisfies the group dissolving condition, and then the user may be dissolved based on the preset policy.
  • the preset ratio may also be set by white, such as: 80%, 90%, and the like. For example, if the temporary group has 10 group members, after the server determines that the 8 members have read the required message, the temporary group can be dissolved based on the preset policy. In an actual application, such an implementation may be combined with the first duration and the second duration as a criterion for determining the group dissolving condition.
  • the server may determine that the number of read-only messages in the temporary group has reached the upper limit of the read-read message, and then Determine whether the group dissolving condition is met based on the reading of all mandatory messages.
  • the server may determine the group dissolution condition when it determines that the number of mandatory messages in the temporary group reaches three. For example, if the three mandatory reading messages have been read by all group members, it can be determined that the temporary group satisfies the group dissolution condition; if the three mandatory reading messages have been read by all group members, and the publishing time The latest mandatory message has been published for 24 hours, and it can be determined that the temporary group satisfies the group dissolution condition; if at least one of the three mandatory messages is not read by all the group members, and The release time of the latest read-only message has reached 15 days, and it can be determined that the temporary group satisfies the group dissolution condition, etc., and the present application will not be repeated here.
  • the group when it is determined that the temporary group satisfies the group dissolving condition, the group may be dismissed based on the preset policy.
  • the preset policy can be set by a developer.
  • the server may immediately dismiss the temporary group. Specifically, all the information related to the temporary group may be deleted, such as a group identifier, a group member information, a group session message, and the like.
  • dissolving the group based on the preset policy may include the following steps:
  • Step 301 Send a hidden notification to the client, so that the client hides the group in the group list.
  • the server when determining that the temporary group satisfies the group dissolving condition, the server may first send a hidden notification to the client, and after receiving the hidden notification, the client may hide the temporary group in the group list. group. In this way, for the group members of the temporary group, the temporary group cannot be seen in the group list, and the interference of the temporary group that has not been used is avoided.
  • Step 302 Dissolve the group when the hidden duration of the group reaches a third duration.
  • the server may dismiss the temporary group when it is determined that the hiding of the temporary group reaches the third duration.
  • the third duration may be set by a developer, such as: 20 days, 30 days, and the like.
  • the server may first send a hidden notification to the client of each group member of the temporary group, the client.
  • the terminal can in turn hide the temporary group in the group list.
  • the server can dissolve the temporary group at 18 o'clock on March 21, 2017.
  • the white client may be notified to display the temporary group, and if it is determined that the temporary group has a new one, Reading the message cancels the dissolution of the temporary group.
  • the query can be performed by querying the temporary group. For example, Xiaobai can enter the group name of the temporary group to query. The server notifies the white client to display the temporary group. Based on the found temporary group, Xiaobai can send the mandatory message again, and can also modify the upper limit of the mandatory message.
  • the server determines that a new mandatory message appears in the temporary group, the disbanding of the temporary group may be cancelled, and when the number of mandatory messages of the temporary group reaches the upper limit of the number of mandatory reading messages again, It is determined whether the temporary group satisfies the group dissolving condition according to the reading condition of all the necessary read messages, and the present application will not repeat them here.
  • the present application gives the user a certain buffer time and is more flexible before dissolving the group that satisfies the group dissolving condition.
  • the present application also provides an embodiment of the management device of the instant messaging group.
  • Embodiments of the management device of the instant messaging group of the present application can be applied to a server or server cluster deployed by a service provider.
  • the device embodiment may be implemented by software, or may be implemented by hardware or a combination of hardware and software.
  • the processor of the server in which it is located reads the corresponding computer program instructions in the non-volatile memory into the memory.
  • FIG. 4 a hardware structure diagram of a server where the management device of the instant messaging group of the present application is located, except for the processor, memory, network interface, and non-volatile shown in FIG.
  • the server where the device is located in the embodiment is usually based on the actual function of the server, and may also include other hardware, which will not be described again.
  • FIG. 5 is a block diagram of an apparatus for managing an instant messaging group according to an exemplary embodiment of the present application.
  • the management apparatus 400 of the instant messaging group can be applied to the server shown in FIG. 4, and includes: a mandatory reading determining unit 401, a condition determining unit 402, and a group dissolving unit 403.
  • the mandatory reading determining unit 401 determines a mandatory read message in the group session message.
  • the condition determining unit 402 determines whether the group dissolving condition is satisfied according to the reading condition of the read-only message
  • the group dissolving unit 403 if the group dissolving condition is satisfied, dismisses the group based on the preset policy.
  • condition determining unit 402 determines that the group dissolving condition is satisfied when the mandatory reading message has been read by all group members.
  • condition determining unit 402 determines that the group dissolving condition is satisfied when the mandatory read message has been read by all group members, and the release duration of the read-read message has reached the first duration.
  • condition determining unit 402 determines that the group dissolving condition is satisfied when the mandatory reading message is not read by all group members, but the publishing duration of the mandatory reading message has reached the second duration.
  • condition determining unit 402 determines that the group dissolving condition is satisfied when the number of group members who have read the mandatory message reaches a preset ratio.
  • condition determining unit 402 further obtains a predefined number of mandatory read message upper limit, and when the number of mandatory read messages in the group session message has reached the upper limit of the read-read message, according to all Read the reading of the message to determine if the group dissolution condition is met.
  • the number of the mandatory read message upper limit is set by the group owner or the administrator.
  • the group dissolving unit 403 sends a hidden notification to the client, so that the client hides the group in the group list; when the hidden time of the group reaches the third duration, the group is dismissed .
  • the group dissolving unit 403 notifies the client to display the group if the query command from the group owner or the administrator is received before the hidden time of the group reaches the third time period; When it is determined that a new mandatory message appears in the group, the dissolution of the group is cancelled.
  • the group is a temporary group.
  • the mandatory message is marked by a group owner or an administrator.
  • the device embodiment since it basically corresponds to the method embodiment, it can be referred to the partial description of the method embodiment.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the objectives of the present application. Those of ordinary skill in the art can understand and implement without any creative effort.
  • the system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.
  • a typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, and a game control.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Information Transfer Between Computers (AREA)
  • Communication Control (AREA)

Abstract

本申请提供一种即时通信群组的管理方法和装置。所述方法包括：确定群组会话消息中的必读消息；根据所述必读消息的阅读情况，确定是否满足群组解散条件；若满足群组解散条件，则基于预设的策略解散该群组。本申请可以根据群组中必读消息的阅读情况确定是否满足群组解散条件，并在满足该群组解散条件时，基于预设的策略解散该群组，从而解散大量的"僵尸群"，降低群组管理的复杂度，同时还可以释放服务端的存储、处理等各项资源。

Description

即时通信群组的管理方法和装置 技术领域
本申请涉及通信技术领域，尤其涉及一种即时通信群组的管理方法和装置。
背景技术
随着互联网技术的广泛发展，即时通信技术给人们的工作与生活带来了各种便利。从早期的ICQ以及OICQ(今日广泛使用的QQ)到如今更新一代的微信以及钉钉等，即时通信技术正在不断地向着更加便利用户的方向演进。
很多即时通信都支持群聊技术，群聊技术可以允许在现实生活中处于同一集体的用户聚集在一起进行信息的交互与分享，比如：同学群、公司群等。在目前的群聊应用中，经常会出现一些简易性的多人会话，比如：临时将几个同事拉到一个群中说一下关键问题。然而，这类群后续再被使用的概率很低，导致服务端要维护很多这样的“僵尸群”，增加了群管理的复杂度，并且容易出错。
发明内容
有鉴于此，本申请提供一种即时通信群组的管理方法和装置。
具体地，本申请是通过如下技术方案实现的：
一种即时通信群组的管理方法，所述方法包括：
确定群组会话消息中的必读消息；
根据所述必读消息的阅读情况，确定是否满足群组解散条件；
若满足群组解散条件，则基于预设的策略解散该群组。
一种即时通信群组的管理装置，所述装置包括：
必读确定单元，确定群组会话消息中的必读消息；
条件判断单元，根据所述必读消息的阅读情况，确定是否满足群组解散条件；
群组解散单元，若满足群组解散条件，则基于预设的策略解散该群组。
由以上描述可以看出，本申请可以根据群组中必读消息的阅读情况确定是否满足群组解散条件，并在满足该群组解散条件时，基于预设的策略解散该群组，从而解散大量的“僵尸群”，降低群组管理的复杂度，同时还可以释放服务端的存储、处理等各项资源。
附图说明
图1是本申请一示例性实施例示出的一种即时通信群组的管理方法的流程示意图。
图2是本申请一示例性实施例示出的一种群组会话界面示意图。
图3是本申请一示例性实施例示出的一种基于预设的策略解散群组的流程示意图。
图4是本申请一示例性实施例示出的一种用于即时通信群组的管理装置的一结构图。
图5是本申请一示例性实施例示出的一种即时通信群组的管理装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本申请相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本申请的一些方面相一致的装置和方法的例子。
在本申请使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本申请。在本申请和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本申请可能采用术语第一、第二、第三等来描述各种信 息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本申请范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
图1是本申请一示例性实施例示出的一种即时通信群组的管理方法的流程示意图。
请参考图1，所述即时通信群组的管理方法可以应用在即时通信服务端，包括有以下步骤：
步骤101，确定群组会话消息中的必读消息。
在本实施例中，由于“公司群”、“同学群”等很多群组是长期存在的群组，并没有解散的必要，所以本申请可以仅针对临时群组执行必读消息的确定以及后续的解散流程。具体地，群创建者可以在创建群组的时候选择群组的类型，比如：创建“固定群组”还是创建“临时群组”；此外，针对已创建的固定群组，群主或者管理员也可以通过设置选项将固定群组的类型修改为临时群组；当然，针对已创建的临时群组，也可以通过设置选项将其类型修改为固定群组。
在本实施例中，所述必读消息通常由群主、管理员等有权限的群组成员标记。请参考图2的示例，群主在通过客户端发布一条群组会话消息后，可以通过点击、双击、长按等操作触发对必读消息的标记，比如：群主可以将希望所有群组成员都阅读的消息标记为必读消息。群主将某条消息标记为必读消息后，群主客户端可以将该标记事件发送给服务端，比如：可发送携带群组会话消息标识的标记事件给服务端，由服务端可以根据接收到的标记事件将对应的群组会话消息确定为必读消息。
当然，在实际的应用中，也可以采用其他的方式进行必读消息的标记，比如：在编辑好某条群组会话消息后，可以在消息编辑框中先将其标记为必读消息，然后再发送。采用这样的方式，客户端可以将必读消息的标记和该群组会话消息一同发送给服务端，无需在后续再次发送标记事件，本申请对此不作特殊限制。
步骤102，根据所述必读消息的阅读情况，确定是否满足群组解散条件。
在本实施例中，服务端可以统计所述必读消息的阅读情况，该阅读情况通常包括：已读或者未读。具体地，服务端可以检测每个群组成员对所述必读消息的阅读情况，然后根据所述必读消息在群组成员中的阅读情况群架是否满足群组解散条件。其中，所述阅读情况的检测可以采用相关技术中的实现方案来实现，本申请在此不再一一赘述。
在本实施例中，所述群组解散条件可以为默认的缺省条件，也可以由群主或者管理员根据需要进行个性化设置。
步骤103，若满足群组解散条件，则基于预设的策略解散该群组。
由以上描述可以看出，本申请可以根据群组中必读消息的阅读情况确定是否满足群组解散条件，并在满足该群组解散条件时，基于预设的策略解散该群组，从而解散大量的“僵尸群”，降低群组管理的复杂度，同时还可以释放服务端的存储、处理等各项资源。
下面以临时群组为例对本申请的实现过程进行详细描述。
在本实施例中，群主或管理员等有权限的群组成员可以根据需要设置必读消息的上限数量。举例来说，假设小白建立某临时群组的目的是向群组成员发布一条重要消息，那么小白可以将必读消息的上限数量设置为1，并在发送该条重要消息后，将这条重要消息标记为必读消息。值得注意的是，本申请中的必读消息上限数量不是固定不变的，在该临时群组解散之前，小白可以根据实际需要对该必读消息上限数量进行修改，本申请对此不作特殊限制。
在本实施例中，服务端基于小白的标记事件，可以检测各个群组成员对该必读消息的阅读情况。
在一个例子中，当服务端确定所述必读消息已经被所有群组成员阅读时，可以确定该临时群组满足群组解散条件，进而可以基于预设的策略解散该临时群组。
在另一个例子中，当服务端确定所述必读消息已被所有群组成员阅读，且所述必读消息的发布时长已到达第一时长时，可以确定该临时群组满足群组解 散条件，进而可以基于预设的策略解散该临时群组。其中，所述第一时长可以由小白预先进行定义，也可以是默认的缺省值，比如：1天、3天等。以1天为例，当服务端确定所述必读消息已被所有群组成员阅读，且该必读消息的发布时长已到达24小时，可以基于预设的策略解散该临时群组。在这样的实现方式中，在所述必读消息的发布时长到达第一时长之前，群组成员还可以在该临时群组中进行相关讨论，小白也可以根据需要重新设置必读消息上限数量，实现更为灵活，用户体验更好。
在另一个例子中，当服务端确定所述必读消息未被所有群组成员阅读，但所述必读消息的发布时长已到达第二时长时，可以确定该临时群组满足群组解散条件，进而可以基于预设的策略解散该临时群组。其中，所述第二时长可以由小白预先进行定义，也可以是默认的缺省值，比如：15天、30天等，该第二时长通常大于前述第一时长。以15天为例，当服务端确定所述必读消息一直未被所有群组成员阅读，且该必读消息的发布时长已到达15天，则可以基于预设的策略解散该临时群组。换言之，当该必读消息的发布时长已到达15天时，即便还有群组成员没有阅读该必读消息，那么也可以基于预设的策略解散该临时群组。采用这样的实现方式，可以有效避免个别群组成员未阅读该必读消息，导致该临时群组一直不能被解散的问题。
在另一个例子中，当服务端确定已阅读所述必读消息的群组成员数量到达预设的比例时，可以确定该临时群组满足群组解散条件，进而可以基于预设的策略解散该临时群组。其中，所述预设的比例也可以由小白进行设置，比如：80％、90％等。举例来说，假设该临时群组共有10个群组成员，当服务端确定8个成员已阅读所述必读消息后，就可以基于预设的策略解散该临时群组。在实际应用中，也可以将这样的实现方式与前述第一时长、第二时长相结合，以作为群组解散条件的判定基准。
在另一个例子中，若小白设置的必读消息上限数量是大于1的数值，那么服务端可以在确定该临时群组中必读消息的数量已到达所述必读消息上限数量时，再根据所有必读消息的阅读情况，确定是否满足群组解散条件。
举例来说，假设小白将该临时群组的必读消息上限数量设置为3，则服务端可以在确定该临时群组中必读消息的数量到达3条时，进行群组解散条件的判定，比如：若这3条必读消息均已被所有群组成员阅读，可以确定该临时群组满足群组解散条件；若这3条必读消息均已被所有群组成员阅读，且发布时间最晚的必读消息的发布时长已到达24小时，可以确定该临时群组满足群组解散条件；若这3条必读消息中至少有1条必读消息未被所有群组成员阅读，且发布时间最晚的必读消息的发布时长已到达15天，可以确定该临时群组满足群组解散条件等，本申请在此不再一一赘述。
在本实施例中，当确定上述临时群组满足群组解散条件时，可基于预设的策略解散该群组。其中，所述预设的策略可以由开发人员进行设置。
在一个例子中，服务端可以立刻解散该临时群组，具体地，可以删除已保存的和该临时群组相关的所有信息，比如：群组标识、群组成员信息、群组会话消息等。
在另一个例子中，在解散该临时群组之前，可以给用户留一段缓冲时间。请参考图3，基于预设的策略解散该群组可以包括以下步骤：
步骤301，发送隐藏通知给客户端，以使客户端在群组列表中隐藏该群组。
在本实施例中，服务端在确定上述临时群组满足群组解散条件时，可先发送隐藏通知给客户端，客户端在接收到该隐藏通知后，可以在群组列表中隐藏该临时群组。这样，对于该临时群组的群组成员而言，已无法在群组列表中看见该临时群组，避免了已不使用的临时群组对用户的干扰。
步骤302，当该群组的隐藏时长到达第三时长时，解散该群组。
在本实施例中，服务端可以在确定该临时群组的隐藏到达第三时长时，解散该临时群组。其中，所述第三时长可以由开发人员进行设置，比如：20天、30天等。
举例来说，假设服务端在2017年3月1日18时确定上述临时群组满足群组解散条件，则服务端可以先发送隐藏通知给该临时群组的各个群组成员的客户端，客户端进而可以在群组列表中隐藏该临时群组。以上述第三时长是20天 为例，服务端可以在2017年3月21日18时解散该临时群组。
进一步地，在该临时群组的隐藏时长到达第三时长之前，若接收到小白的查询指令，则可以通知小白的客户端显示该临时群组，若确定该临时群组出现新的必读消息，则取消对该临时群组的解散。
仍以上述举例为例，在2017年3月21日18时之前，若小白还想向该临时群组中的群组成员发布必读消息，则可以通过查询指令进行该临时群组的查询，比如：小白可以输入该临时群组的群组名称进行查询。服务端通知小白的客户端显示该临时群组。基于查找到的该临时群组，小白可以再次发送必读消息，还可以修改必读消息上限数量。在一个例子中，若服务端确定该临时群组出现新的必读消息，可以取消对该临时群组的解散，后续等该临时群组的必读消息数量再次到达必读消息上限数量时，根据所有必读消息的阅读情况，确定该临时群组是否满足群组解散条件，本申请在此不再一一赘述。
本申请在解散满足群组解散条件的群组之前，给用户一定的缓冲时间，灵活性更高。
与前述即时通信群组的管理方法的实施例相对应，本申请还提供了即时通信群组的管理装置的实施例。
本申请即时通信群组的管理装置的实施例可以应用在服务提供商部署的服务器或者服务器集群上。装置实施例可以通过软件实现，也可以通过硬件或者软硬件结合的方式实现。以软件实现为例，作为一个逻辑意义上的装置，是通过其所在服务器的处理器将非易失性存储器中对应的计算机程序指令读取到内存中运行形成的。从硬件层面而言，如图4所示，为本申请即时通信群组的管理装置所在服务器的一种硬件结构图，除了图4所示的处理器、内存、网络接口、以及非易失性存储器之外，实施例中装置所在的服务器为通常根据该服务器的实际功能，还可以包括其他硬件，对此不再赘述。
图5是本申请一示例性实施例示出的一种即时通信群组的管理装置的框图。
请参考图5，所述即时通信群组的管理装置400可以应用在前述图4所示的服务器中，包括有：必读确定单元401、条件判断单元402以及群组解散单元 403。
其中，必读确定单元401，确定群组会话消息中的必读消息；
条件判断单元402，根据所述必读消息的阅读情况，确定是否满足群组解散条件；
群组解散单元403，若满足群组解散条件，则基于预设的策略解散该群组。
可选的，所述条件判断单元402，当所述必读消息已被所有群组成员阅读时，确定满足所述群组解散条件。
可选的，所述条件判断单元402，当所述必读消息已被所有群组成员阅读，且所述必读消息的发布时长已到达第一时长时，确定满足所述群组解散条件。
可选的，所述条件判断单元402，当所述必读消息未被所有群组成员阅读，但所述必读消息的发布时长已到达第二时长时，确定满足所述群组解散条件。
可选的，所述条件判断单元402，当已阅读所述必读消息的群组成员数量到达预设的比例时，确定满足所述群组解散条件。
可选的，所述条件判断单元402，还获取预定义的必读消息上限数量，并在所述群组会话消息中的必读消息数量已到达所述必读消息上限数量时，根据所有必读消息的阅读情况，确定是否满足群组解散条件。
可选的，所述必读消息上限数量由群主或管理员设定。
可选的，所述群组解散单元403，发送隐藏通知给客户端，以使客户端在群组列表中隐藏该群组；当该群组的隐藏时长到达第三时长时，解散该群组。
可选的，所述群组解散单元403，还在该群组的隐藏时长到达第三时长之前，若接收到来自群主或管理员的查询指令，则通知客户端显示该群组；并在确定该群组出现新的必读消息时，取消对该群组的解散。
可选的，所述群组为临时群组。
可选的，所述必读消息由群主或管理员标记。
上述装置中各个单元的功能和作用的实现过程具体详见上述方法中对应步骤的实现过程，在此不再赘述。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见 方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本申请方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机，计算机的具体形式可以是个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件收发设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任意几种设备的组合。
以上所述仅为本申请的较佳实施例而已，并不用以限制本申请，凡在本申请的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本申请保护的范围之内。

Claims (22)

  1. 一种即时通信群组的管理方法，所述方法包括：
    确定群组会话消息中的必读消息；
    根据所述必读消息的阅读情况，确定是否满足群组解散条件；
    若满足群组解散条件，则基于预设的策略解散该群组。
  2. 根据权利要求1所述的方法，所述根据所述必读消息的阅读情况，确定是否满足群组解散条件，包括：
    当所述必读消息已被所有群组成员阅读时，确定满足所述群组解散条件。
  3. 根据权利要求1所述的方法，所述根据所述必读消息的阅读情况，确定是否满足群组解散条件，包括：
    当所述必读消息已被所有群组成员阅读，且所述必读消息的发布时长已到达第一时长时，确定满足所述群组解散条件。
  4. 根据权利要求1所述的方法，所述根据所述必读消息的阅读情况，确定是否满足群组解散条件，包括：
    当所述必读消息未被所有群组成员阅读，但所述必读消息的发布时长已到达第二时长时，确定满足所述群组解散条件。
  5. 根据权利要求1所述的方法，所述根据所述必读消息的阅读情况，确定是否满足群组解散条件，包括：
    当已阅读所述必读消息的群组成员数量到达预设的比例时，确定满足所述群组解散条件。
  6. 根据权利要求1所述的方法，所述方法还包括：
    获取预定义的必读消息上限数量；
    所述根据所述必读消息的阅读情况，确定是否满足群组解散条件，包括：
    当所述群组会话消息中的必读消息数量已到达所述必读消息上限数量时，根据所有必读消息的阅读情况，确定是否满足群组解散条件。
  7. 根据权利要求6所述的方法，
    所述必读消息上限数量由群主或管理员设定。
  8. 根据权利要求1所述的方法，所述基于预设的策略解散该群组，包括：
    发送隐藏通知给客户端，以使客户端在群组列表中隐藏该群组；
    当该群组的隐藏时长到达第三时长时，解散该群组。
  9. 根据权利要求8所述的方法，所述方法还包括：
    在该群组的隐藏时长到达第三时长之前，若接收到来自群主或管理员的查询指令，则通知客户端显示该群组；
    若确定该群组出现新的必读消息，则取消对该群组的解散。
  10. 根据权利要求1所述的方法，所述群组为临时群组。
  11. 根据权利要求1所述的方法，所述必读消息由群主或管理员标记。
  12. 一种即时通信群组的管理装置，所述装置包括：
    必读确定单元，确定群组会话消息中的必读消息；
    条件判断单元，根据所述必读消息的阅读情况，确定是否满足群组解散条件；
    群组解散单元，若满足群组解散条件，则基于预设的策略解散该群组。
  13. 根据权利要求12所述的装置，
    所述条件判断单元，当所述必读消息已被所有群组成员阅读时，确定满足所述群组解散条件。
  14. 根据权利要求12所述的装置，
    所述条件判断单元，当所述必读消息已被所有群组成员阅读，且所述必读消息的发布时长已到达第一时长时，确定满足所述群组解散条件。
  15. 根据权利要求12所述的装置，
    所述条件判断单元，当所述必读消息未被所有群组成员阅读，但所述必读消息的发布时长已到达第二时长时，确定满足所述群组解散条件。
  16. 根据权利要求12所述的装置，
    所述条件判断单元，当已阅读所述必读消息的群组成员数量到达预设的比例时，确定满足所述群组解散条件。
  17. 根据权利要求12所述的装置，
    所述条件判断单元，还获取预定义的必读消息上限数量，并在所述群组会话消息中的必读消息数量已到达所述必读消息上限数量时，根据所有必读消息的阅读情况，确定是否满足群组解散条件。
  18. 根据权利要求17所述的装置，
    所述必读消息上限数量由群主或管理员设定。
  19. 根据权利要求12所述的装置，
    所述群组解散单元，发送隐藏通知给客户端，以使客户端在群组列表中隐藏该群组；当该群组的隐藏时长到达第三时长时，解散该群组。
  20. 根据权利要求19所述的装置，
    所述群组解散单元，还在该群组的隐藏时长到达第三时长之前，若接收到来自群主或管理员的查询指令，则通知客户端显示该群组；并在确定该群组出现新的必读消息时，取消对该群组的解散。
  21. 根据权利要求12所述的装置，所述群组为临时群组。
  22. 根据权利要求12所述的装置，所述必读消息由群主或管理员标记。
PCT/CN2018/084229 2017-04-25 2018-04-24 即时通信群组的管理方法和装置 WO2018196739A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
KR1020197018217A KR102248393B1 (ko) 2017-04-25 2018-04-24 인스턴트 메시징 그룹 관리 방법 및 장치
JP2019534784A JP6918116B2 (ja) 2017-04-25 2018-04-24 インスタントメッセージンググループ管理方法および装置
EP18790640.9A EP3544229B1 (en) 2017-04-25 2018-04-24 Instant messaging group management method and apparatus
ES18790640T ES2875793T3 (es) 2017-04-25 2018-04-24 Método y aparato de gestión de grupos de mensajería
PL18790640T PL3544229T3 (pl) 2017-04-25 2018-04-24 Sposób i przyrząd do zarządzania grupą komunikacji
US16/440,834 US10686615B2 (en) 2017-04-25 2019-06-13 Instant messaging group management method and apparatus
PH12019501485A PH12019501485A1 (en) 2017-04-25 2019-06-25 Instant messaging group management method and apparatus
US16/901,959 US20200313917A1 (en) 2017-04-25 2020-06-15 Instant messaging group management method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710273959.6A CN107181602A (zh) 2017-04-25 2017-04-25 即时通信群组的管理方法和装置
CN201710273959.6 2017-04-25

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/440,834 Continuation US10686615B2 (en) 2017-04-25 2019-06-13 Instant messaging group management method and apparatus

Publications (1)

Publication Number Publication Date
WO2018196739A1 true WO2018196739A1 (zh) 2018-11-01

Family

ID=59831458

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/084229 WO2018196739A1 (zh) 2017-04-25 2018-04-24 即时通信群组的管理方法和装置

Country Status (10)

Country Link
US (2) US10686615B2 (zh)
EP (1) EP3544229B1 (zh)
JP (1) JP6918116B2 (zh)
KR (1) KR102248393B1 (zh)
CN (1) CN107181602A (zh)
ES (1) ES2875793T3 (zh)
PH (1) PH12019501485A1 (zh)
PL (1) PL3544229T3 (zh)
TW (1) TW201839681A (zh)
WO (1) WO2018196739A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107181602A (zh) * 2017-04-25 2017-09-19 阿里巴巴集团控股有限公司 即时通信群组的管理方法和装置
CN107580304A (zh) * 2017-07-27 2018-01-12 努比亚技术有限公司 一种基于应用程序的群组解散方法及设备
CN109245906A (zh) * 2018-10-24 2019-01-18 阿里巴巴集团控股有限公司 即时通信群组的管理方法及装置
CN110971425A (zh) * 2019-12-02 2020-04-07 深圳市云歌人工智能技术有限公司 重新开启群组和请求重新开启群组的方法、装置
CN114465969B (zh) * 2021-12-23 2023-07-04 珠海格力电器股份有限公司 通讯消息组的管理方法、装置、设备和存储介质
CN116418607A (zh) * 2022-01-05 2023-07-11 腾讯科技（深圳）有限公司 消息处理方法、装置、设备、存储介质和程序产品
CN114531411B (zh) * 2022-04-01 2025-01-14 亿咖通(湖北)技术有限公司 消息显示方法、装置、电子设备和存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1662900A (zh) * 2002-06-19 2005-08-31 摩托罗拉公司 信息共享群组,服务器和客户端群组应用程序及其方法
CN104301125A (zh) * 2014-09-24 2015-01-21 鸿富锦精密工业（深圳）有限公司 群组解散控制系统及方法
CN105337839A (zh) * 2014-08-07 2016-02-17 小米科技有限责任公司 交流群组控制方法及装置
CN106067861A (zh) * 2016-06-06 2016-11-02 天脉聚源(北京)传媒科技有限公司 一种加入讨论群的方法及装置
CN106557376A (zh) * 2016-11-30 2017-04-05 北京奇虎科技有限公司 终端设备及其群组建立、加入方法和装置以及服务器
CN107181602A (zh) * 2017-04-25 2017-09-19 阿里巴巴集团控股有限公司 即时通信群组的管理方法和装置

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7937364B1 (en) * 1999-03-09 2011-05-03 Oracle International Corporation Method and system for reliable access of messages by multiple consumers
JP4191318B2 (ja) * 1999-05-21 2008-12-03 富士通株式会社 メッセージ処理装置、メッセージ管理方法及びメッセージ管理プログラムを記録した記録媒体
US7047030B2 (en) 2001-05-02 2006-05-16 Symbian Limited Group communication method for a wireless communication device
US7969959B2 (en) * 2004-12-16 2011-06-28 Critical Response Systems, Inc. Method and apparatus for efficient and deterministic group alerting
US20080071862A1 (en) * 2006-09-15 2008-03-20 International Business Machines Corporation Dynamic directory group creation via electronic event scheduling
JP2008134707A (ja) * 2006-11-27 2008-06-12 Hitachi Ltd コミュニティ生成支援方法及び装置
CN101345718A (zh) 2007-07-13 2009-01-14 阿里巴巴集团控股有限公司 一种在群内支持话题分类的方法、系统和装置
EP2475138B1 (en) * 2011-01-06 2019-03-13 BlackBerry Limited Delivery and management of status notifications for group messaging
US8799385B2 (en) * 2011-03-31 2014-08-05 Loment, Inc. Delivery control for email communicated among multiple end user communication devices
TWI591992B (zh) * 2011-11-16 2017-07-11 Alibaba Group Holding Ltd 群組通信關係的建立、以及網頁展現方法和相關設備
US20130229722A1 (en) * 2012-03-02 2013-09-05 Steven Vogel High throughput reflecting microscope objective
US9219881B2 (en) * 2014-03-07 2015-12-22 Shenzhen Seefaa Scitech Co., Ltd. Device and method for live video chat
US10142275B2 (en) * 2014-09-09 2018-11-27 Dan Tolley System and method for managing messages based on user rank
KR101631287B1 (ko) * 2015-03-18 2016-06-16 주식회사 카카오 채팅방 관리 방법 및 단말

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1662900A (zh) * 2002-06-19 2005-08-31 摩托罗拉公司 信息共享群组,服务器和客户端群组应用程序及其方法
CN105337839A (zh) * 2014-08-07 2016-02-17 小米科技有限责任公司 交流群组控制方法及装置
CN104301125A (zh) * 2014-09-24 2015-01-21 鸿富锦精密工业（深圳）有限公司 群组解散控制系统及方法
CN106067861A (zh) * 2016-06-06 2016-11-02 天脉聚源(北京)传媒科技有限公司 一种加入讨论群的方法及装置
CN106557376A (zh) * 2016-11-30 2017-04-05 北京奇虎科技有限公司 终端设备及其群组建立、加入方法和装置以及服务器
CN107181602A (zh) * 2017-04-25 2017-09-19 阿里巴巴集团控股有限公司 即时通信群组的管理方法和装置

Also Published As

Publication number Publication date
PH12019501485A1 (en) 2020-06-01
EP3544229A4 (en) 2020-01-08
JP6918116B2 (ja) 2021-08-11
US20200313917A1 (en) 2020-10-01
ES2875793T3 (es) 2021-11-11
TW201839681A (zh) 2018-11-01
CN107181602A (zh) 2017-09-19
JP2020508502A (ja) 2020-03-19
KR20190093591A (ko) 2019-08-09
EP3544229B1 (en) 2021-03-31
US10686615B2 (en) 2020-06-16
PL3544229T3 (pl) 2021-08-23
US20190296928A1 (en) 2019-09-26
KR102248393B1 (ko) 2021-05-10
EP3544229A1 (en) 2019-09-25

Similar Documents

Publication Publication Date Title
WO2018196739A1 (zh) 即时通信群组的管理方法和装置
US12231387B2 (en) Reminder generation method and apparatus in group session, device and medium
US7499926B1 (en) Maintaining and replicating chat histories
JP6204928B2 (ja) 時間管理される電子メール・メッセージ
CN103997454B (zh) 一种日志信息的使用方法和设备
WO2020135142A1 (zh) 项目群组的创建方法、项目管理方法及装置
US8495660B1 (en) Methods and systems for handling instant messages and notifications based on the state of a computing device
US20200111060A1 (en) Task reminder method and apparatus, and method and apparatus for generating and presenting reminder message
CN106068521A (zh) 关于合规策略更新的应用的通信状态
WO2018111426A1 (en) Detecting extraneous social media messages
US20160285799A1 (en) Systems and methods for supplementing real-time exchanges of instant messages with automatically updateable content
US9882849B2 (en) Action assignment and tracking functionality for email
CN105681173A (zh) 即时通讯中会话的创建方法、装置及系统
US9270630B1 (en) Integrating communication modes in persistent conversations
US20130311762A1 (en) Providing user access to specific programs and documents before the booting process is completed
CN111917560A (zh) 通信方法、装置和设备
WO2019109880A1 (zh) 群组任务的信息获取方法及装置
US12095714B2 (en) Method and apparatus for messaging service
WO2019062587A1 (zh) 任务生成方法及装置
TW201911158A (zh) 考勤設置方法及裝置
CN116471249A (zh) 信息处理方法、装置、电子设备及存储介质
WO2019019929A1 (zh) 签名档的生成方法、签名档模板的分享方法及装置
WO2018223858A1 (zh) 团队配置方法、团队配置方案的分享方法及装置
HK1244365A1 (zh) 即时通信群组的管理方法和装置
CN118827699A (zh) 一种显示方法及设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18790640

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20197018217

Country of ref document: KR

Kind code of ref document: A

Ref document number: 2019534784

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018790640

Country of ref document: EP

Effective date: 20190621

NENP Non-entry into the national phase

Ref country code: DE